Re: [Sip] DTLS-SRTP - more work for the SIP group
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Thu, 20 September 2007 18:42 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 1IYQzI-0002dn-JC; Thu, 20 Sep 2007 14:42:56 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IYQzG-0002Wx-VT for sip-confirm+ok@megatron.ietf.org; Thu, 20 Sep 2007 14:42:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYQzG-0002PM-39 for sip@ietf.org; Thu, 20 Sep 2007 14:42:54 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IYQz8-0006n0-Ov for sip@ietf.org; Thu, 20 Sep 2007 14:42:48 -0400
Received: (qmail invoked by alias); 20 Sep 2007 18:42:30 -0000
Received: from p54985A96.dip.t-dialin.net (EHLO [192.168.1.4]) [84.152.90.150] by mail.gmx.net (mp048) with SMTP; 20 Sep 2007 20:42:30 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+3LoFJbWq3YkMEzFkbS8rwrKinQsJ9VXTW57BGr3 TTR0qpt3DBt7gA
Message-ID: <46F2BF16.2070207@gmx.net>
Date: Thu, 20 Sep 2007 20:42:30 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] DTLS-SRTP - more work for the SIP group
References: <5D1A7985295922448D5550C94DE29180016B8DDA@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180016B8DDA@DEEXC1U01.de.lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: sip@ietf.org
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
Good plan. Great to see some progress. Thanks to you and Cullen. DRAGE, Keith (Keith) wrote: > (As WG co-chair) > > You may remember that some time ago some work was identified that > crossed multiple working groups in the RAI area on the above subject. > Cullen took this ball away and played with it in a RAI BOF and there > came to some consensus on the way forward and what documentation was > required. > > However we now need to put that work through real working groups to get > it to IESG so we are reallocating it to working groups. > > I have requested milestones as follows: > > Sep 2007 Requirements for media keying to WGLC (Informational) > Nov 2007 Requirements for media keying to IESG (Informational) > > This will be WG milestones in support of progressing > http://www.ietf.org/internet-drafts/draft-wing-media-security-requiremen > ts-04.txt > And incorporating > draft-wing-rtpsec-keying-eval > > This charter item will essentially be a discussion of how we got where > we are now. It is therefore not the most earthshattering document, but > it has been considered valuable to retain some permanent record and an > informational RFC is the way to do this. > > Dec 2007 Establishment of secure media sessions using DTLS-SRTP > to WGLC (PS) > Feb 2008 Establishment of secure media sessions using DTLS-SRTP > to IESG (PS) > > This will be WG milestones in support of progressing > http://www.ietf.org/internet-drafts/draft-fischl-sipping-media-dtls-03.t > xt > > This charter item goes to SIP because it is security related, rather > than to SIPPING. This is one deliverable out of a package of 3, the > other two being: > > http://www.ietf.org/internet-drafts/draft-ietf-avt-dtls-srtp-00.txt > http://www.ietf.org/internet-drafts/draft-fischl-mmusic-sdp-dtls-03.txt > > Which will be handled by AVT and MMUSIC respectively. > > What do you need to do as SIP WG members > ---------------------------------------- > > Provide consensus or not to move these drafts forward. > > Do you agree with the identified author drafts above forming the basis > of these charter items listed above? If not please express your > objections to the list, with appropriate technical considerations. > Indications of support are appropriate as well, particularly if you have > a technical point you wish to make (alternatively address the WG chairs > with just "Yes I support"). > > Responses please within a calendar week, i.e. by Tuesday 25th September > 2007, unless there is a feeling that more time and discussion are > needed. > > > Regards > > Keith > > > > _______________________________________________ > 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 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] DTLS-SRTP - more work for the SIP group DRAGE, Keith (Keith)
- RE: [Sip] DTLS-SRTP - more work for the SIP group Francois Audet
- RE: [Sip] DTLS-SRTP - more work for the SIP group Dan Wing
- Re: [Sip] DTLS-SRTP - more work for the SIP group Hannes Tschofenig
- RE: [Sip] DTLS-SRTP - more work for the SIP group Fries, Steffen
- Re: [Sip] DTLS-SRTP - more work for the SIP group Eric Rescorla