RE: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-00.txt
"Francois Audet" <audet@nortel.com> Tue, 04 December 2007 00:16 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzLSi-0006Nq-OX; Mon, 03 Dec 2007 19:16:32 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzLSh-0006Mi-Ia for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 19:16:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzLSh-0006Lc-8F for sip@ietf.org; Mon, 03 Dec 2007 19:16:31 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzLSg-0003CG-Ry for sip@ietf.org; Mon, 03 Dec 2007 19:16:31 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lB40GPC26436; Tue, 4 Dec 2007 00:16:25 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-00.txt
Date: Mon, 03 Dec 2007 18:16:24 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF1389A83F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <c164605b0712031606g61b15f6ai77bd869f582bd848@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-00.txt
Thread-Index: Acg2CZp505T/tMuMTHWnN+n48TlYbQAANMNA
References: <E1IrSL3-0006kt-LG@stiedprstage1.ietf.org> <1ECE0EB50388174790F9694F77522CCF13290B22@zrc2hxm0.corp.nortel.com> <c164605b0712031606g61b15f6ai77bd869f582bd848@mail.gmail.com>
From: Francois Audet <audet@nortel.com>
To: Jason Fischl <jason@counterpath.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: sip@ietf.org, Flemming Andreasen <fandreas@cisco.com>, Hannes.Tschofenig@nsn.com, Dan Wing <dwing@cisco.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
See below. > -----Original Message----- > From: jason.fischl@gmail.com [mailto:jason.fischl@gmail.com] > On Behalf Of Jason Fischl > Sent: Monday, December 03, 2007 16:07 > To: Audet, Francois (SC100:3055) > Cc: sip@ietf.org; Hannes.Tschofenig@nsn.com; > ekr@networkresonance.com; Flemming Andreasen > Subject: Re: [Sip] I-D > Action:draft-ietf-sip-dtls-srtp-framework-00.txt > > On Nov 13, 2007 11:50 AM, Francois Audet <audet@nortel.com> wrote: > > (copying Flemming) > > > > Good draft. Very helpful. > > > > On the SDP side of things. > > > > I didn't seen anything in the SDP format that specifically > indicated > > in the offer that you are trying to setup DTLS-SRTP. > > > This is signaled in the SDP with the token > "UDP/TLS/RTP/SAVP". See > http://www.ietf.org/internet-drafts/draft-fischl-mmusic-sdp-dt > ls-04.txt > for more details. Ah.... Can you explicitly say that in the document? I see there is a reference to this draft, but the document doesn't say that it is used for that purpose. > > > Is the assumption that if there is no indication besides > the RTP/SAVP > > in the tcap, that DTLS-SRTP may be negotiated, and that > therefore we > > do not need an explicit indication that DTLS-SRTP is supported? > > > More specifically, UDP/TLS/RTP/SAVP. to signal we're sending > SRTP over DTLS. > > > Do we think it's good enough? In other words, is RTP/SAVP without > > a=crypto or a=key-mgmt good enough to indicate DTLS-SRTP? > Or should we have another attribute? > > > I think this is good enough. Agreed. > > A side comment is that the example shows usage with > Best-Effort SRTP. > > My take is that it could also be used in "DTLS-SRTP-always" mode by > > having the m-line use UDP/TLS/RTP/AVP instead of RTP/AVP > and not using > > a a=tcap/a=pcfg line. It would probably be worthwile to > describe it in the draft. > > > I can add an example fragment to cover this case. That would be very useful. Thanks. _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framewo… Internet-Drafts
- RE: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-fra… Elwell, John
- RE: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-fra… Francois Audet
- Re: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-fra… Jason Fischl
- RE: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-fra… Francois Audet
- Re: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-fra… Flemming Andreasen