Re: [MMUSIC] Bundling data channel and RTP?

Christian Groves <Christian.Groves@nteczone.com> Thu, 21 May 2015 00:21 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E25F11ACD39 for <mmusic@ietfa.amsl.com>; Wed, 20 May 2015 17:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNNW9aqnq9cl for <mmusic@ietfa.amsl.com>; Wed, 20 May 2015 17:21:54 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39A5C1ACD48 for <mmusic@ietf.org>; Wed, 20 May 2015 17:21:54 -0700 (PDT)
Received: from ppp118-209-247-8.lns20.mel8.internode.on.net ([118.209.247.8]:50385 helo=[192.168.1.22]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <Christian.Groves@nteczone.com>) id 1YvEFD-000307-MB for mmusic@ietf.org; Thu, 21 May 2015 10:21:51 +1000
Message-ID: <555D251A.4020004@nteczone.com>
Date: Thu, 21 May 2015 10:21:46 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <5540C9BA.4090803@nteczone.com>
In-Reply-To: <5540C9BA.4090803@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/j9CHGMpiWPS4A67ME-TOOLw08M8>
Subject: Re: [MMUSIC] Bundling data channel and RTP?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2015 00:21:56 -0000

Can anyone confirm the intention that a single DTLS connection is used 
for SRTP key exchange and also SCTP packets?

draft-ietf-rtcweb-transports-08 indicates:

/WebRTC implementations MUST support multiplexing of DTLS and RTP over//
//   the same port pair, as described in the DTLS_SRTP specification//
//   [RFC5764], section 5.1.2.  All application layer protocol payloads//
//   over this DTLS connection are SCTP packets./

To me this implies a single DTLS connection. However in RFC5764 clause 
4.1 it says:
/Once the "use_srtp" extension is negotiated, the RTP or RTCP//
//   application data is protected solely using SRTP. Application data is//
//   never sent in DTLS record-layer "application_data" packets.  Rather,//
//   complete RTP or RTCP packets are passed to the DTLS stack, which//
//   passes them to the SRTP stack, which protects them appropriately.//
/
In the second sentence "application data" is not qualified with "RTP or 
RTCP" so it could be taken that its not possible to use the DTLS 
connection for anything else. However I take it that as the rest of the 
paragraph talks about RTP or RTCP that these were meant when application 
data is mentioned?

Can only one add some clarity?

Regards, Christian

On 29/04/2015 10:08 PM, Christian Groves wrote:
> Hello
>
> According to draft-ietf-rtcweb-data-channel-13 and 
> draft-ietf-rtcweb-transports-08, multiplexing of DTLS and RTP over the 
> same port pair must be supported and application layer protocol 
> payloads over this DTLS connection are SCTP packets, i.e. RTP and 
> datachannel share the same address:port.
>
> I assume this needs to be specified in SDP by two m-lines bundled 
> together. E.g. one with "UDP/TLS/RTP/SAVPF" & one with "UDP/DTLS/SCTP" 
> . However I can't find in any of the related drafts where this is 
> stated. I would think the BUNDLE and JSEP drafts should mention 
> something about this. Is there a draft that I've missed where this is 
> stated?
>
> Regards, Christian
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>