Intent to Implement and Ship: ICE candidate pooling for RTCPeerConnection

[Taylor Brandstetter]

Contact emails

dead...@chromium.org

Spec

https://www.w3.org/TR/webrtc/#dom-rtcconfiguration-icecandidatepoolsize

Tag review: https://github.com/w3ctag/spec-reviews/issues/14

Summary

Normally, ICE candidates are only gathered after RTCPeerConnection.setLocalDescription is called, because this is the point at which the PeerConnection knows how many ports it needs. The iceCandidatePoolSize member of RTCConfiguration instructs the PeerConnection to gather ICE candidates before this occurs, as a performance optimization. Thus, if setting the local description is delayed (by signaling, for example), interactions with STUN/TURN servers can occur in parallel.

Motivation

This is performance optimization that may result in quicker call setup.

Interoperability and Compatibility Risk

There are no existing implementations. However, this feature exists as a performance optimization only, which lowers the compatibility risk: the only observable effect of this API is that candidate gathering may appear to occur quicker.

Firefox bug entry: https://bugzilla.mozilla.org/show_bug.cgi?id=1291894

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

OWP launch tracking bug

crbug.com/673395

Link to entry on the feature dashboard

https://www.chromestatus.com/feature/4973817285836800

Requesting approval to ship?

Yes.

[Chris Harrelson]

LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Jochen Eisinger]

The referenced TAG review talks about IP address gather and its implications, however, I don't see how that would relate to the feature you're trying to ship here.

Could you please clarify whether there are privacy implications by gathering the ICE candidates earlier?

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Taylor Brandstetter]

That's the TAG review for WebRTC as a whole (maybe I shouldn't have linked it).

And no, there are no privacy implications. An application can already perform the same candidate gathering by creating an RTCPeerConnection and calling setLocalDescription. In fact, even when candidate pooling is used, the candidates aren't surfaced to the application until setLocalDescription is called; the interactions with the STUN/TURN servers simply happen in advance.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Rick Byers]

LGTM2

[TAMURA, Kent]

LGTM3

--

TAMURA Kent
Software Engineer, Google