Intent to Implement & Ship: RTCPeerConnection::onicecandidateerror

ma...@microsoft.com

unread,

Jun 14, 2019, 11:48:11 AM6/14/19

to blink-dev

Contact emails

elr...@microsoft.com, ma...@microsoft.com

Spec

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

Summary

ICE candidate error event provides detailed information about WebRTC ICE candidate gathering failures, including the ones defined by STUN (RFC5389) and TURN (RFC5766).

Motivation

Diagnosing ICE connectivity issues without having access to detailed gathering failures can be a challenge. Support for ICE candidate errors is targeted towards better connectivity troubleshooting and network diagnostics.

Risks

Interoperability and Compatibility

Low, this is not yet available on other browsers.

Ergonomics

N/A

Activation

N/A

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

Yes.

Link to entry on the feature dashboard

Need help creating a feature on https://www.chromestatus.com, as I don't have access.

Requesting approval to ship?

Yes.

Philip Jägenstedt

unread,

Jun 17, 2019, 9:07:47 AM6/17/19

to ma...@microsoft.com, blink-dev

LGTM1, this is very minor, just a new event and event interface.

Note that on interoperability, the risk when shipping new things which aren't yet in other browsers is that they never are. In other words, low interop risk would be when we have high confidence that all engines will ship this, and it's high if we think they won't. However, this is a larger concern with a big new feature, this is just a new event, and one that ended up in the WebRTC spec following a working group process with multi-vendor participation.

--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/23a37727-3df5-40bc-86cf-a053d3f6bf6a%40chromium.org.

Max Solodovnikov

unread,

Jun 17, 2019, 9:24:07 AM6/17/19

to blink-dev, ma...@microsoft.com

Thanks, Philip! Does it need an entry on chromestatus.com? If so, can you help with it (either grant write access or help creating an entry)?

Philip Jägenstedt

unread,

Jun 17, 2019, 11:16:08 AM6/17/19

to Max Solodovnikov, Johnny Stenback, blink-dev

It used to be possible to request an account at the bottom of chromestatus.com, I'm not sure what's happened there. +Johnny Stenback, can you help Max get set up with an account to create an entry? If it doesn't work I can create an entry.

On Mon, Jun 17, 2019 at 3:24 PM 'Max Solodovnikov' via blink-dev <blin...@chromium.org> wrote:

Thanks, Philip! Does it need an entry on chromestatus.com? If so, can you help with it (either grant write access or help creating an entry)?

--

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+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/66428f06-7fa7-4680-9cae-c6c6cd98e68c%40chromium.org.

sol...@gmail.com

unread,

Jun 19, 2019, 12:38:15 PM6/19/19

to blink-dev, ma...@microsoft.com, jste...@google.com

@jstenback, I wonder if you had a chance to look into permission issues that I am hitting? Is there a way to get write access to chromestatus.com?

Johnny Stenback

unread,

Jun 19, 2019, 8:38:30 PM6/19/19

to sol...@gmail.com, blink-dev, ma...@microsoft.com

Sorry for the delay in getting back on this. I've added sol...@gmail.com as a user in chromestatus.com. Enjoy!

Cheers,

Johnny

- jstenback (he/him)

Daniel Bratell

unread,

Jun 20, 2019, 9:54:07 AM6/20/19

to sol...@gmail.com, 'Johnny Stenback' via blink-dev, Johnny Stenback, ma...@microsoft.com

LGTM2

/Daniel

--
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+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz5477977jO72-uVvxQWzkAJ57XOF%3DPgEPi94A1U4iH5pw%40mail.gmail.com.

--

/* Opera Software, Linköping, Sweden: CEST (UTC+2) */

Yoav Weiss

unread,

Jun 20, 2019, 9:59:39 AM6/20/19

to Daniel Bratell, sol...@gmail.com, 'Johnny Stenback' via blink-dev, Johnny Stenback, ma...@microsoft.com

As Philip said, interop risk is about chances of adoption by other engines.

Have you reached out to other engines? Opened issues? Do you know if they intend to implement?

Any links to WG discussions on this that can show objections or lack-there-of?

I agree that's a minor change. That also means it would be easy for other engines to follow if they so desire. I just want to make sure there aren't any objections we're missing here.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.z3orj5tmrbppqq%40cicero2.linkoping.osa.

Henrik Boström

unread,

Jun 26, 2019, 10:35:40 AM6/26/19

to blink-dev, bra...@opera.com, sol...@gmail.com, jste...@google.com, ma...@microsoft.com

This will expose it to Chromium and Edge, and someone from Opera seem to have approved the intent in this thread.

I don't know if this exact feature has been discussed recently, but this is part of WebRTC 1.0 that all major browsers are working on implementing, and this has not been marked a feature at risk.

There's a chromestatus page now: https://www.chromestatus.com/feature/6602864602382336

Can we proceed with the shipping?

On Thursday, June 20, 2019 at 3:59:39 PM UTC+2, Yoav Weiss wrote:

As Philip said, interop risk is about chances of adoption by other engines.
Have you reached out to other engines? Opened issues? Do you know if they intend to implement?
Any links to WG discussions on this that can show objections or lack-there-of?

I agree that's a minor change. That also means it would be easy for other engines to follow if they so desire. I just want to make sure there aren't any objections we're missing here.

On Thu, Jun 20, 2019 at 3:54 PM Daniel Bratell <bra...@opera.com> wrote:

LGTM2

/Daniel

On Wed, 19 Jun 2019 21:35:27 +0200, 'Johnny Stenback' via blink-dev <blin...@chromium.org> wrote:

Sorry for the delay in getting back on this. I've added sol...@gmail.com as a user in chromestatus.com. Enjoy!

Cheers,
Johnny

- jstenback (he/him)

On Wed, Jun 19, 2019 at 2:03 AM <sol...@gmail.com> wrote:
@jstenback, I wonder if you had a chance to look into permission issues that I am hitting? Is there a way to get write access to chromestatus.com?

On Monday, June 17, 2019 at 5:16:08 PM UTC+2, Philip Jägenstedt wrote:
It used to be possible to request an account at the bottom of chromestatus.com, I'm not sure what's happened there. +Johnny Stenback, can you help Max get set up with an account to create an entry? If it doesn't work I can create an entry.

On Mon, Jun 17, 2019 at 3:24 PM 'Max Solodovnikov' via blink-dev <blin...@chromium.org> wrote:
Thanks, Philip! Does it need an entry on chromestatus.com? If so, can you help with it (either grant write access or help creating an entry)?

--
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.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz5477977jO72-uVvxQWzkAJ57XOF%3DPgEPi94A1U4iH5pw%40mail.gmail.com.

--
/* Opera Software, Linköping, Sweden: CEST (UTC+2) */

--
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.

Philipp Hancke

unread,

Jun 26, 2019, 11:24:55 AM6/26/19

to Henrik Boström, blink-dev, Daniel Bratell, sol...@gmail.com, jste...@google.com, ma...@microsoft.com

https://mozilla.logbot.info/media/20190614#c16397544

- I think that can be counted as "not opposed" from Firefox.

And this is much better than the heuristics currently used in https://github.com/webrtc/samples/blob/gh-pages/src/content/peerconnection/trickle-ice/js/main.js#L225-L245

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

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz5477977jO72-uVvxQWzkAJ57XOF%3DPgEPi94A1U4iH5pw%40mail.gmail.com.

--
/* Opera Software, Linköping, Sweden: CEST (UTC+2) */

--
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+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.z3orj5tmrbppqq%40cicero2.linkoping.osa.

--

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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e4294d32-88cd-49fd-a90b-cc82bf8b5c72%40chromium.org.