Re: [MMUSIC] Associating packets with m-lines in a bundle

[Bernard Aboba <[e-mail]>]

On May 23, 2013, at 11:50, "Paul Kyzivat" <[e-mail]> wrote:

> After all the discussion in the meeting today, I thought it would be good to unwind all the indenting and start a new thread on one issue that is part of the "demux" problem:
> 
> IMO the following should obviously be a truism. I want to know if all agree.
> 
> If an O/A exchange negotiates a bundle with multiple m-lines,
> then attributes in those m-lines and the associated media sections must provide sufficient information to associate each incoming packet on the 5-tuple to exactly *one* of those m-lines.

[BA] I would argue that this statement needs to be true for *both* RTP and RTCP packets.

> (If it doesn't, then there was no point in including those m-lines in the bundle.)
> 
> For instance a=ssrc, if unique to one m-line, can bind packets with that SSRC to the m-line.

[BA] That is only necessary for RTP (and RTCP) if the PT is not unique to an m line; otherwise PT demux is sufficient for RTP.  For RTCP the situation is more complicated. If we only need to bind RTCP packets from RTP senders, we can build an SSRC to PT to m line table dynamically, based on SSRCs and PTs seen in RTP packets.  However if we get a RR from a source that has not yet sent, we can't map it to an m line without a=ssrc if BUNDLE is in use.  

> If a property such as SSRC is used this way, then there is the possibility of receiving packets that don't match any of the m-lines. I think we ought to address that, by defining some syntax to specify what to do with packets that don't match any m-line. This might be to specify one m-line as the default, or that packets that don't match be discarded.

[BA] I do not believe that a default m line makes sense for RTCP packets that can't be bound to an m line.  Discard, while undesirable, seems like the only option. However this could create problems in diagnostics in some cases.