implementing bundle with ORTC

[fippo]

I am reviewing my bundle implementation in the wicked shim after running into some bundle-related issues during renegotation.

One thing I noticed in particular is that unless the bundlePolicy is set to max-bundle I create different ice gatherers when creating an offer in balanced mode. I do this to gather "ICE candidates for each media type in use (audio, video, and data)".

Unfortunately this means that the local parameters (ufrag/pwd) for each transport will be different which is differing from the behaviour of chrome and firefox (that behaviour probably comes from https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-39#section-11.1)

I think this an instance of the good old "I would like to be able to create a gatherer with ufrag/pwd" problem

[aboba]

@fippo When bundlePolicy is not “max-bundle” does the difference in ufrag/passwd cause interop problems with Chrome/FF/Safari? With legacy implementations?

@robin-raymond Several ideas come to mind... such as enabling creation of a new IceGatherer with the same ufrag/passwd as an existing one (e.g. cloneGatherer()).