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 20:16 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 C6BE61A0AAC for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 12:16:49 -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 bPnhbMAA3-tq for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 12:16:48 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id C10C51A0A7E for <mmusic@ietf.org>; Sun, 2 Mar 2014 12:16:47 -0800 (PST)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA11.westchester.pa.mail.comcast.net with comcast id YiyM1n0050QuhwU5BkGliP; Sun, 02 Mar 2014 20:16:45 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta02.westchester.pa.mail.comcast.net with comcast id YkEc1n00f2LcPnE3NkEfZ3; Sun, 02 Mar 2014 20:14:43 +0000
Message-ID: <5313912D.9020202@alum.mit.edu>
Date: Sun, 02 Mar 2014 20:14:37 +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: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393791405; bh=CDlW81Tldtj/t8LRZAs6WZBaZtlxs+tV+j4Cj22gvk8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=hZCPE+/seXJogJwfIc9tJuLFzDgQ0wMqCcVPu++12hsgYxWxSuRc9XWcnlGsNGbto ujNyKrYt0/15CCNX3sF4iqDIkYQPUV5mvuvQtl8ZfqRiY3Bd1rdGw3/mgW6b88i6Xb Q7ak7dXx4sqkYTZQhmcNXznz5eVV4pTQULdjAQmThAYLrG6kMVOdNCFZhCA+h6mUpb sptzjRJq4eVTTTwiKXD0xi/kFPYrZtosTFublFIs4TyfZXEWhc8YCdUtzWwWCgByHX h8ol3+h2i3H0WpEeWRysAe/BJZ8/byjyy3ILI0pVVvK2e7ikwVhfchQJJVjFOX5DCp Ouhlo+klrjaSA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VluQNhwlILmS6WKKsWHiaUfkjUM
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 20:16:50 -0000

On 3/2/14 4:03 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.

	Thanks,
	Paul