webrtc - When is an endpoint bundle-aware and when not?

Question

From Link: www.w3.org/TR/webrtc/#dom-rtcbundlepolicy Content: 4.2.5 RTCBundlePolicy Enum

"If the remote endpoint is bundle-aware, all media tracks and data channels are bundled onto the same transport."

When is an endpoint bundle-aware and when not? And what does bundle-aware means?

question from:https://stackoverflow.com/questions/65926913/when-is-an-endpoint-bundle-aware-and-when-not

Answer 1

To establish a p2p connection, WebRTC will allocate and do STUN network checks on up to 3 ports (multiplied by ways they can be reached) on either end, and as they're discovered (which takes time), ask JS to trickle-exchange info on each of these "ICE candidates" across a signaling channel, once for video, once for audio, and once for data (if you have it).

WebRTC does this mostly to support connecting to non-browser legacy devices, because all modern browsers support BUNDLE, which is when all but one candidate end up being thrown away, and all media gets bundled over that single port.

WebRTC even has a "max-compat" mode that goes even further, allocating a port for each piece of media, just in case the other endpoint is really old.

WebRTC doesn't know the other endpoint is a browser until it receives an "answer" from it, but if you know, you can specify "max-bundle" and save a couple of milliseconds.