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

[Christer Holmberg <[e-mail]>]

Hi Thomas,
 
> although BUNDLE can be used independent of ICE, the de-mux should consider STUN messages which will also arrive at the BUNDLE address.
> If this is then in scope or out of the scope of the BUNDLE spec can be discussed.
> However, I would regard it being in scope.

Good point. I personally strongly think STUN shall be in the scope.

Regards,

Christer

 

________________________________________
Von: [e-mail] [mailto:[e-mail]] Im Auftrag von Christer Holmberg
Gesendet: Mittwoch, 19. Juni 2013 13:53
An: [e-mail]
Betreff: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)
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.

   In addition, if an endpoint assigns multiple "m=" lines representing
   the same transport protocol to a BUNDLE group, the endpoint MUST be
   able to, in addition to associating received data to its transport
   protocol, also associate the received data with a specific "m=" line
   representing that transport protocol.

   This specification defines how to de-multiplex received media
   associated with the following transport protocols:

   o  "RTP/AVP" [RFC4566];

   o  "RTP/AVPF" [RFC4585];

   o  "RTP/SAVP" [RFC3711];

   o  "RTP/SAVPF" [RFC5124];and

   o  "SCTP/DTLS" [ref-to-be added].

   This specification also specifies how RTP packats are separated from
   RTCP packets.

   If an endpoint assigns multiple "m=" lines representing RTP/RTCP
   media to a BUNDLE group, it is outside the scope of this
   specification how the endpoint associates received RTP/RTCP packets
   with a specific RTP/RTCP "m=" line (endpoints might use payload type
   values, or SSRC values, for the association).

   If endpoints want to assign "m=" lines representing other transport
   protocols to a BUNDLE group, it MUST be documented how the de-
   multiplexing is performed.  There might also be a need for signalling
   extensions in order for endpoints to exchange data needed for the de-
   multiplexing.