Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.

[Suhas Nandakumar <[e-mail]>]

Hello Christer

  Comments Inline.

Cheers
Suhas


On Mon, Mar 3, 2014 at 2:27 PM, Christer Holmberg <
[e-mail]> wrote:

>  Hi,
>
>
>
> >  A small twist on your proposal
>
> >
>
> >  I think the recommendation in the BUNDLE document should say 2 points
>
> >
>
> >  1. Reuse of PT is allowed only in the cases where the end-point is
> able to uniquely map the >   incoming RTP Streams to its corresponding
> m=line. The specific mechanisms to do so are >   out of the scope of this
> document . Informally, SSRC, AppID or similar stream correlators >   can
> be used.
>
>
>
> But, again, when you send the offer, how do you know what "correlators"
> the answerer supports? Should we say that is out of the scope?
>
>
>

[Suhas] I am happy with some text similar to here:
https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-00#section-3.2.

If the Offer/Answer can't prove any mechanism possible, It would imply new
Offer/Answer with unique PTs. I don't see if one can escape the worst-case
scenario though.




>   > Also using the same PT across multiple m=lines implies the same
> underlying codec
>
> > configuration.
>
>
>
> So, what is YOUR definition of "codec configuration"? J
>
>
>
[Suhas] I shall stick with Colin's suggestion.


>  Regards,
>
>
>
> Christer
>