Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00
Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 25 October 2011 17:32 UTC
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A663621F8BAE for <rtcweb@ietfa.amsl.com>; Tue, 25 Oct 2011 10:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.293
X-Spam-Level:
X-Spam-Status: No, score=-2.293 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 139-6gcuME6X for <rtcweb@ietfa.amsl.com>; Tue, 25 Oct 2011 10:32:47 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1125321F8BA7 for <rtcweb@ietf.org>; Tue, 25 Oct 2011 10:32:46 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 25 Oct 2011 13:32:41 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Tue, 25 Oct 2011 13:32:41 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Thread-Topic: [rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00
Thread-Index: AQHMkzwYC3D0vszPzU6fGvL68kihrg==
Date: Tue, 25 Oct 2011 17:32:40 +0000
Message-ID: <0E8ADE67-75ED-4117-B27D-19FB714DD2D3@acmepacket.com>
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com> <6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com> <CALiegfmvBCCd3kG_3b2ojXhYryS3nry-5qZ1Z+ra03Wb9FU+ug@mail.gmail.com>
In-Reply-To: <CALiegfmvBCCd3kG_3b2ojXhYryS3nry-5qZ1Z+ra03Wb9FU+ug@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D85058B13A82C54CA16ED79FB6F92C2D@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2011 17:32:47 -0000
On Oct 25, 2011, at 5:50 AM, Iñaki Baz Castillo wrote: > Let me a question about section 4.2.2: > > ---------------------------- > 4.2.2 SRTP Termination [...] It should be noted that if SRTP > is required to be used for every call by RTCWeb but the [SDES] key > exchange model cannot be used on the RTCWeb side, then the > Interworking Function likely has to terminate SRTP from RTCWeb even > if the SIP-domain supports SRTP, because [SDES] is the most > commonly used form of key exchange in SIP > today.------------------------------ > > I was not aware of such limitation. Could you please point me to some > draft or mail thread in which that limitation (SDES key exchange model > cannot be used on the RTCWeb side) is explained? There were discussions at a previous meeting and an email thread a while back on whether (1) SRTP should be mandatory to use, and (2) on whether it must be dtls-srtp key exchange. I believe one thread on this was started here: http://www.ietf.org/mail-archive/web/rtcweb/current/msg00460.html I don't know if a conclusion/consensus was reached. Thus I wrote that section of the draft assuming it could go either way. -hadriel
- [rtcweb] draft-kaplan-rtcweb-sip-interworking-req… Hadriel Kaplan
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Ravindran Parthasarathi
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Ravindran Parthasarathi
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Hadriel Kaplan
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Hadriel Kaplan
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Iñaki Baz Castillo
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Iñaki Baz Castillo
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Iñaki Baz Castillo
- Re: [rtcweb] draft-kaplan-rtcweb-sip-interworking… Hadriel Kaplan
- [rtcweb] RTCWeb Forking usecase [was RE: draft-ka… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Harald Alvestrand
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Roman Shpount
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Christer Holmberg
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] RTCWeb Forking usecase [was RE:draft… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Hadriel Kaplan
- Re: [rtcweb] RTCWeb Forking usecase [was RE:draft… Christer Holmberg
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Randell Jesup
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Hadriel Kaplan
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Roman Shpount
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Roman Shpount
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Harald Alvestrand
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Harald Alvestrand
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Hadriel Kaplan
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Harald Alvestrand
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Christer Holmberg
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Christer Holmberg
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Timothy B. Terriberry
- [rtcweb] New usecase & requirement for media fork… Ravindran Parthasarathi
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Stefan Håkansson
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Roman Shpount
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Iñaki Baz Castillo
- Re: [rtcweb] New usecase & requirement for media … Harald Alvestrand
- Re: [rtcweb] RTCWeb Forking usecase [was RE: draf… Randell Jesup
- [rtcweb] SDES and forking [was RE: RTCWeb Forking… Christer Holmberg
- [rtcweb] SDES and forking [was RE: RTCWeb Forking… Christer Holmberg
- Re: [rtcweb] New usecase & requirement for media … Ravindran Parthasarathi
- Re: [rtcweb] New usecase & requirement for media … Harald Alvestrand
- Re: [rtcweb] New usecase & requirement for media … Ravindran Parthasarathi
- Re: [rtcweb] New usecase & requirement for media … Harald Alvestrand