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

David McGrew <mcgrew@cisco.com> Wed, 20 June 2007 20:54 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 1I17CT-0005jx-B5; Wed, 20 Jun 2007 16:54:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I17CR-0005jq-HZ for avt@ietf.org; Wed, 20 Jun 2007 16:54:47 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I17CR-000672-6z for avt@ietf.org; Wed, 20 Jun 2007 16:54:47 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 20 Jun 2007 13:54:46 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAAoxeUarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,444,1175497200"; d="scan'208"; a="496221836:sNHT651327248"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5KKskfn008208; Wed, 20 Jun 2007 13:54:46 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l5KKsj06021249; Wed, 20 Jun 2007 20:54:45 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 13:54:44 -0700
Received: from [10.32.254.210] ([10.32.254.210]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 13:54:44 -0700
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
Content-Transfer-Encoding: 7bit
From: David McGrew <mcgrew@cisco.com>
Date: Wed, 20 Jun 2007 13:54:49 -0700
To: Colin Perkins <csp@csperkins.org>, Roni Even <roni.even@polycom.co.il>, tom.taylor@rogers.com, AVT <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 20 Jun 2007 20:54:44.0553 (UTC) FILETIME=[3B00A390:01C7B37D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1704; t=1182372886; x=1183236886; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mcgrew@cisco.com; z=From:=20David=20McGrew=20<mcgrew@cisco.com> |Subject:=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in=20AVT |Sender:=20; bh=G1Xtzl0X2S/CQfKu/+MqzZJv+o6DZxK6Jm1ratJireU=; b=ZYYW1p0ZfPTOQ5m5epXaAwSEZ6r9j94Aj8oqWIIrzbho87lU+zTdZBHgjyGdEzwS4/k2ONrw MDmg5aAcmsVjCK20hJkpEFQ1ur/KHheXt+HSfgIVzNCbCjZTIe4h8Yaj;
Authentication-Results: sj-dkim-3; header.From=mcgrew@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Cullen Jennings <fluffy@cisco.com>, Dan Wing <dwing@cisco.com>
Subject: [AVT] TLS-SRTP internet draft as a WG item in AVT
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

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."

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