Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT

Colin Perkins <csp@csperkins.org> Wed, 27 June 2007 10:00 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3UJy-0006Db-Pp; Wed, 27 Jun 2007 06:00:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3UJx-0006Ai-3M for avt@ietf.org; Wed, 27 Jun 2007 06:00:21 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3UJZ-0003Iu-6B for avt@ietf.org; Wed, 27 Jun 2007 06:00:21 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59643) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1I3UJW-0005HZ-1Y; Wed, 27 Jun 2007 10:59:54 +0100
In-Reply-To: <BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com> <18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org> <BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
Date: Wed, 27 Jun 2007 10:59:52 +0100
To: David McGrew <mcgrew@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>, tom.taylor@rogers.com, Dan Wing <dwing@cisco.com>, AVT <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

David, All,

That's fine. We therefore propose to accept this draft as an AVT work  
item, with the milestone listed. If there are any objections to this  
plan, please state them by 29th June 2007.

Colin





On 26 Jun 2007, at 22:05, David McGrew wrote:
> Hi Colin,
>
> how does this milestone sound?  "December 2007 Submit TLS-SRTP for  
> Proposed Standard"   Perhaps I'm aggressive in expecting us to have  
> the draft ready before the Vancouver meeting; we could push it back  
> to March 2008.
>
> David
>
> On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
>
>> Hi David,
>>
>> What milestone(s) do you see this work adding to the AVT charter,  
>> if accepted?
>>
>> Colin
>>
>>
>>
>>
>> On 20 Jun 2007, at 21:54, David McGrew wrote:
>>> Hi Colin, Roni, and Tom,
>>>
>>> I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
>>> working group action item in AVT, as part the plan for carrying  
>>> forward the RTPSEC work (as per Cullen's email of May 11 to the  
>>> rtpsec list).   I would like to continue on as an author of this  
>>> work, and Eric as agreed to do the same.  There are a small  
>>> number of minor open issues which I expect can be wrapped up  
>>> quickly:
>>>
>>> 1.  The draft needs to be clarified so that, in the Symmetric RTP  
>>> case, only one handshake is needed.
>>>
>>> 2.  Section 3.6.2.1 needs to be resolved to either decide on a  
>>> "symmetry breaking" rule or not.  It may be desirable to have  
>>> such a rule to handle cases in which the signaling system can't  
>>> tell a device which should act as client and which should act as  
>>> server.   This would allow opportunistic probing, i.e. a TLS-SRTP  
>>> implementation could attempt to find out whether another RTP  
>>> implementation supports TLS-SRTP, absent any help from signaling.
>>>
>>> 3.  The "single DTLS session per SRTP session" issue needs to be  
>>> decided, and Appendix A should then be removed from the draft.
>>>
>>> 4.  It should be decided to use, or not to use the "TLS  
>>> Extractor", and Section 3.3 should be rewritten accordingly.
>>>
>>> 5.  The duplicate list of srtp profiles needs to be eliminated.
>>>
>>> Best regards,
>>>
>>> David
>>>
>>> --
>>>
>>> p.s. - here's the AVT-specific part of Cullen note, so that you  
>>> don't need to dig it out of your mailbox: "AVT - Describe how  
>>> DTLS is used to key SRTP and how SRTP is used in combination with  
>>> DTLS. This includes the issues of multiplexing DTLS and SRTP on  
>>> one port. draft-mcgrew-tls-srtp will be the starting draft for  
>>> this."
>>
>>
>>
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
http://csperkins.org/



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt