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

[Christer Holmberg <[e-mail]>]

Hi,

The question is whether we shall specify exactly how entities associate RTP packets with the correct m= lines, or whether we shall simply give some guidelines and hints.

For example, a client can choose to use unique PT values per m- values, within a given BUNDLE group, and everything should work fine. And, if the endpoint runs out of PT values, the create a new BUNDLE group. Now, whether it's religiously correct, I don't know :)

OR, if the endpoints are able to signal which SSRCs they are going to use, they can use that.

OR, if the endpoints support some kind of RTP header extension for this purpose, they can use that.

Etc.

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Bernard Aboba [[e-mail]]
To: Christer Holmberg [[e-mail]]; Harald Alvestrand [[e-mail]]
CC: [e-mail] [[e-mail]]
Subject: RE: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)

Christer said:

"The suggested text currently says that, in case you have multiple "m=" lines associated with the same transport protocol (e.g. RTP/AVP), selecting which of those "m=" lines received media belongs (whether it's based on PT, SSRC or something else) to is outside the scope of the document.

But, IF we think that shall be described, then we need to add text."

[BA] Leaving this out could result in interoperability problems (unless it is specified elsewhere and this document references that).     So I do think that some text is needed, somewhere.