Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 19 June 2013 19:11 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC46021F9ECB for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 12:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level:
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CivCktUbRWr for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 12:11:36 -0700 (PDT)
Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:96]) by ietfa.amsl.com (Postfix) with ESMTP id 0D22F21F995F for <mmusic@ietf.org>; Wed, 19 Jun 2013 12:11:35 -0700 (PDT)
Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta09.emeryville.ca.mail.comcast.net with comcast id qGgJ1l0041smiN4A9KBWSf; Wed, 19 Jun 2013 19:11:30 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([63.226.120.12]) by omta20.emeryville.ca.mail.comcast.net with comcast id qK9M1l00p0G8kgX8gK9PUu; Wed, 19 Jun 2013 19:09:27 +0000
Message-ID: <51C201E1.2000309@alum.mit.edu>
Date: Wed, 19 Jun 2013 15:09:21 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C3AFDB7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3AFDB7@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=1371669090; bh=uSfTGflNpg9p1Kn9JeUCYq55L7DsoW7wu9tq9Z8zoaM=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=eu0jpFp9s+5dC3LcQx40qSC2A6CZrVTGjQBUdfexAr+HJJoOcxEtAJj+BLQwZwh+C kiF1B/4qjuH4UbMlmuaxeqIouuwWaXc3jOVB9A32SpJrDBXnOjo9CnqedLux4JDHoi sf4tT3tEOJ+P3XUtxqql6Wky1VZ1O7G/AgKuWR05Kh6KuAfPQoCCuuUTr40hvRM8xO TD+cteyFjjgkQcVERyv4RpNApSJCqIQyZVzKEkQYgn0rmY6WGeFsU4vSG7t41rr7pq hEUCmZ+/rWVuigieFhqoPkx2Hd5iNiEpCz6C1BaX2gddh+3NdcN5AS1SInGO+MGQC/ jiP8KJ9ChyUHg==
Subject: Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 19 Jun 2013 19:11:41 -0000

On 6/19/13 7:53 AM, Christer Holmberg wrote:
> Hi,
>
> I put together some text regarding the de-muxing for BUNDLE.
>
> Note that there is yet no text on HOW the de-muxing is performed. The
> text only cover the SCOPE of what will be specified in the BUNDLE spec.
> I want us to agree on that first :)
>
> Regards,
>
> Christer
>
> ---------------------------------------------------
>
> 9.  Transport Protocol De-Multiplexing
>
> 9.1.  General
>
>     Endpoints can assign "m=" lines representing different transport
>
>     protocols [RFC4566], identified using the "m=" line proto value
>
>     [RFC4566].
>
>     As each "m=" line in a BUNDLE group share the BUNDLE address, an
>
>     endpoint MUST be able to de-multiplex data received on the BUNDLE
>
>     address, meaning it MUST be able to associate the received with one
>
>     of the transport protocols assigned to the BUNDLE group.  Endpoints
>
>     MUST NOT assign a transport protocols to a BUNDLE group, unless it is
>
>     able to separate received data from data associated with other
>
>     transport protocols assigned to the BUNDLE group.

There is something this doesn't address. Suppose I tried to bundle an 
RTP/AVP with a TCP/RTP/AVP. I could indeed demux them, because they 
actually travel over different 5-tuples. But I don't think we should 
consider this bundling.

So, to be bundled, I think at the lowest level they must all share the 
same transport protocol. But I don't know exactly what terminology to 
use to say that.

	Thanks,
	Paul