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

[Paul Kyzivat <[e-mail]>]

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