Re: [MMUSIC] Bundling data channel and RTP?
Christian Groves <Christian.Groves@nteczone.com> Fri, 22 May 2015 07:20 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 7901C1ACE07
for <mmusic@ietfa.amsl.com>; Fri, 22 May 2015 00:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9] 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 GDM54pamClJu for <mmusic@ietfa.amsl.com>;
Fri, 22 May 2015 00:20:12 -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 D6C691ACDF6
for <mmusic@ietf.org>; Fri, 22 May 2015 00:20:11 -0700 (PDT)
Received: from ppp118-209-46-66.lns20.mel4.internode.on.net
([118.209.46.66]:52468 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 1YvhFZ-0008VW-Kl
for mmusic@ietf.org; Fri, 22 May 2015 17:20:09 +1000
Message-ID: <555ED8A4.9080601@nteczone.com>
Date: Fri, 22 May 2015 17:20:04 +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> <555D251A.4020004@nteczone.com>
<555DA696.4040109@ericsson.com>
In-Reply-To: <555DA696.4040109@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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/-n5KVrtwhpVnFaL-22uFnUQga7M>
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: Fri, 22 May 2015 07:20:13 -0000
Hello Magnus and Martin, Thanks for confirming that. It would be good to cover bundling the SRTP and DTLS/SCTP m-lines the BUNDLE and JSEP drafts. Regards, Christian On 20 May 2015 at 17:21, Christian Groves<Christian.Groves@nteczone.com> wrote: > Can anyone confirm the intention that a single DTLS connection is used for > SRTP key exchange and also SCTP packets? Yes, the record layer carries SCTP and exporters from the same session are used to key SRTP. On 21/05/2015 7:34 PM, Magnus Westerlund wrote: > Christian Groves skrev den 2015-05-21 02:21: >> 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? >> > > Yes, that is clearly the intention as I understand it in WebRTC. > > Cheers > > Magnus Westerlund > > ---------------------------------------------------------------------- > Services, Media and Network features, Ericsson Research EAB/TXM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > >
- [MMUSIC] Bundling data channel and RTP? Christian Groves
- Re: [MMUSIC] Bundling data channel and RTP? Christian Groves
- Re: [MMUSIC] Bundling data channel and RTP? Magnus Westerlund
- Re: [MMUSIC] Bundling data channel and RTP? Martin Thomson
- Re: [MMUSIC] Bundling data channel and RTP? Christian Groves
- Re: [MMUSIC] Bundling data channel and RTP? Christer Holmberg
- Re: [MMUSIC] Bundling data channel and RTP? Paul Kyzivat
- Re: [MMUSIC] Bundling data channel and RTP? Christer Holmberg
- Re: [MMUSIC] Bundling data channel and RTP? Paul Kyzivat