Re: [MMUSIC] [rtcweb] Updating JSEP and BUNDLE: unfied plan

[Justin Uberti <[e-mail]>]

On Mon, Feb 1, 2021 at 1:59 AM Christer Holmberg <
[e-mail]> wrote:

> Hi,
>
> ...
>
> >>>>> If I remember correctly, there was a suggestion to keep the existing
> port zero + bundle-only procedure in JSEP, but define a NEW policy for it.
> Then, once the new policy gets implemented, it can be used.
> >>>>
> >>>> Yes. I had suggested that, and still think that could be a path
> forward. But we should first see what the aforementioned data says to
> understand the extent of the need for such a policy.
> >>>
> >>> We have been talking mostly about 'max-bundle'. But as far as I
> understand (and you also mentioned it earlier in the thread) we have the
> same issue with 'balanced', if the offer contains more than one m- line for
> the same media type. Or?
> >>
> >> You are correct, but the scope of this issue is believed to be far
> smaller, given the slow adoption of unified plan (which is required for
> multiple m= lines of the same type). IOW, we may choose a different
> solution here than in the max-bundle case.
> >
> > Are you saying that browsers currently don't support multiple m= lines
> of the same type?
>
> And, just to clarify the above: browsers are currently using "Plan B",
> where all tracks of a given media type is placed inside one m= line, and
> the tracks are then separated using SSRC?
>
>
See response in other thread.