Re: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-00.txt
Flemming Andreasen <fandreas@cisco.com> Wed, 05 December 2007 19:11 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 1Izzf2-0005Ov-6s; Wed, 05 Dec 2007 14:11:56 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Izzf0-0005OX-3j for sip-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 14:11:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izzez-0005Nh-NH for sip@ietf.org; Wed, 05 Dec 2007 14:11:53 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Izzey-0004Ia-Pn for sip@ietf.org; Wed, 05 Dec 2007 14:11:53 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 05 Dec 2007 11:11:51 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lB5JBqst021005; Wed, 5 Dec 2007 11:11:52 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lB5JBb7Z029450; Wed, 5 Dec 2007 19:11:52 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 11:11:50 -0800
Received: from [10.21.125.119] ([10.21.125.119]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 11:11:50 -0800
Message-ID: <4756F7F5.9040609@cisco.com>
Date: Wed, 05 Dec 2007 14:11:49 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Thunderbird 1.5.0.13 (Windows/20070809)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-00.txt
References: <E1IrSL3-0006kt-LG@stiedprstage1.ietf.org> <1ECE0EB50388174790F9694F77522CCF13290B22@zrc2hxm0.corp.nortel.com> <c164605b0712031606g61b15f6ai77bd869f582bd848@mail.gmail.com> <1ECE0EB50388174790F9694F77522CCF1389A83F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1389A83F@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 05 Dec 2007 19:11:50.0586 (UTC) FILETIME=[B06E09A0:01C83772]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7228; t=1196881912; x=1197745912; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fandreas@cisco.com; z=From:=20Flemming=20Andreasen=20<fandreas@cisco.com> |Subject:=20Re=3A=20[Sip]=20I-D=20Action=3Adraft-ietf-sip-dtls-srtp-frame work-00.txt |Sender:=20; bh=u4Y7KI0SJnYdt0Jj5jJbAQLZ0lalq97Yk9XYMK4t+Ms=; b=qCRFYmnee1qd5fvpgouU3/i3oPXfRu7LhbiR015/beZjWRY9t6dJjO1VL6IvD2JHC/yOpxMx 19Nryj3+UzlD9yFiu24SK+hXLho3poxafUJnvkj/6YKapHsRNDyojoiY;
Authentication-Results: sj-dkim-4; header.From=fandreas@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Cc: sip@ietf.org, 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>
Content-Type: multipart/mixed; boundary="===============1616237653=="
Errors-To: sip-bounces@ietf.org
The SDP Capability Negotiation part is fine albeit you could argue it would be cleaner to have the DTLS-SRTP related attributes encoded as attribute capabilities rather than as first-level attributes. -- Flemming Francois Audet wrote: > 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