[rtcweb] JSEP: Order of m- lines in multiple PeerConnections

[Christer Holmberg <[e-mail]>]

Hi,

JSEP talks about the usage of multiple PeerConnection to support forking, i.e. for each new forked leg (SIP: early dialog) a new PeerConnection is created.

As has been indicated, as each new PeerConnection will have its own set of address properties, ICE properties etc, so a new Offer will have to be created and sent to inform the remote about the new properties.

So far so I good.

I also assume that the same camera/mic/etc sources are connection to each PeerConnection, so the number of m- lines in the Offer of the new PeerConnection should be the same.

However, according the 3264, the ORDER of the m- lines also need to be kept the same.

So, my question is: how can I ensure that the order of the m- lines in an Offer for a new PeerConnection is the same as in an Offer for an old PeerConnection?

Regards,

Christer