Re: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?

Paul Kyzivat <pkyzivat@alum.mit.edu> Sun, 02 March 2014 21:32 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 6C65F1A0B1A for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 13:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 w_ECwG1n75jb for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 13:32:47 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 187981A0B18 for <mmusic@ietf.org>; Sun, 2 Mar 2014 13:32:46 -0800 (PST)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta12.westchester.pa.mail.comcast.net with comcast id Ykgy1n0070mv7h05ClYkeW; Sun, 02 Mar 2014 21:32:44 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta11.westchester.pa.mail.comcast.net with comcast id YlWY1n00T2LcPnE3XlWbRY; Sun, 02 Mar 2014 21:30:42 +0000
Message-ID: <5313A2F9.6000507@alum.mit.edu>
Date: Sun, 02 Mar 2014 21:30:33 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <5313912D.9020202@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393795964; bh=HtSwPDDgv99COjJY5M3Z00DsyjLKdKUmNto24CBuj9g=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=rnBRmM2VUh9KAGIoYIzbVQtc+19VPKCm+Y8W3Y5L00B7hHI0BhQVJ2hb/Nykeh91z 6QhKegpO8TndsxaGHyX8eH9QAT9CW40ODikjzIQWvt2Z/XZJl5Vsxh4Fjafvx4Gfh7 pt2TpGy1H1gCEGn9doH3JUCCUqQjGfKp+DMbsZMkTo8O71i4gXiOaWq8lvSVuqp71D IUI/qXci6K80JIaz32T30Oq5P0+Z/5kcVozRyIoB8gAoMcVdVSj1LoQfj9XhJos7+f oiv4x8Wk68HMSKUitIJ/Zj5d8x1lNxd0LaFxdQYKRf7RrVbJYvbp2i8S3/BmkqjYEg FoWOqZdtJW9Ow==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5hFAQWjf8GQ9T_NVlIhN1wA8CDA
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
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: Sun, 02 Mar 2014 21:32:48 -0000

Christer,

I'm not necessarily opposed to going in the direction you suggest.
(I'm still listening to what others have to say before deciding.)

But if we go that way then I think the bundle draft needs a big warning 
or implementers note explaining the issues involved in this.

And then I expect that there ought to be an rtcweb document that 
specifies how to do this for the common rtcweb cases.

	Thanks,
	Paul

On 3/2/14 8:21 PM, Christer Holmberg wrote:
> Hi,
>
>>> One of the open issues is what we, in the BUNDLE spec, are going to
>>> say about de-multiplexing about different media types, and for which
>>> (if any) media types we are going to specify how the de-multiplexing is done.
>>>
>>> We have previously agreed that we are NOT going to describe all
>>> different possibilities in BUNDLE, and that separate specifications
>>> how to perform (and, indicate support of) de-multiplexing will have to
>>> be written. However, we haven't really agreed on the details.
>>>
>>> I intend to suggest the following in London.
>>>
>>> In the BUNDLE spec we:
>>>
>>> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
>>>
>>> 2)Separate specifications are required to describe how to de-mulitplex
>>> other media types, and any type of information that needs to be
>>> exchanged between peers in order to perform the de-multiplexing.
>>>
>>> I think that DTLS/SRTP/STUN is going to be the main use-case (not only
>>> for WebRTC) in the near future, so I think it's a good approach.
>>
>> Note that 5764 is sufficient to demux SRTP traffic from DTLS payload messages. It doesn't say
>> anything about what those payload messages are used for.
>>
>> It will take another reference to specify that when using proto DTLS/SCTP those payload messages > are used exclusively for SCTP.
>
> I am fully aware of that. But, my proposal remains :)
>
> If you want to transport different things (e.g. data channel and something else) over DTLS, you need a specification that describes how the separation is done.
>
> Regards,
>
> Christer
>
>