[rtcweb] m=section recycling and a=mid

[Suhas Nandakumar <[e-mail]>]

After thinking about it a bit, I think there are some side effects
associated with changing/not changing mid attribute of a re-cycled m=
section and it being part of a BUNDLE group or not..

example

say , we have these video m=section part of BUNDLE group as below
a=group:BUNDLE 1, 2

m=video .....
a=mid:1
a=inactive

m=video .....
a=mid:2
a=sendrecv

Now If JS user adds a new video track and he wants it to be out of BUNDLE.
If we recycle first video m=section and dont change mid attribute,  we end
up BUNDLing even if the user dint want to

On the other hand, if we allowed mid value to be changed, we might end up
UNBundling a video stream , when the user did want to BUNDLE them

So allowing a mid value to be changed or not should be tied to what the JS
API is asking on behalf of the user


Any thoughts ?

Cheers
Suhas