Intent to Ship: WebRTC Datachannel: Always negotiate data channels

[Philipp Hancke]

tContact emails

h...@chromium.org, philipp...@googlemail.com

Specification

https://w3c.github.io/webrtc-extensions/#always-negotiating-datachannels

Summary

Implement https://w3c.github.io/webrtc-extensions/#always-negotiating-datachannels

Blink component

Blink>WebRTC

Web Feature ID

Missing feature

TAG review status

Not applicable (incremental addition to WebRTC)

Risks

Interoperability and Compatibility

No information provided

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1335)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/599)

Web developers: No signals

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

Yes

Is this feature fully tested by web-platform-tests?

Yes, a WPT is part of https://chromium-review.googlesource.com/c/chromium/src/+/7080041

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/433898678

Estimated milestones

Shipping on desktop

146

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5113419982307328?gate=6516338099093504

This intent message was generated by Chrome Platform Status.

[Robert Flack]

The specification just says "alwaysNegotiateDataChannels defines a way for the application to negotiate data channels in the SDP offer before creating a datachannel". I'm finding it a bit hard to reason about what this means for me as a developer. I.e. when should I set it and how does this change the connection? Does this mean that a data channel will be negotiated without calling createDataChannel? Will that requested datachannel result in a datachannel event or does my code still need to call createDataChannel? If the latter, is this a performance optimization? Would I choose this when data is more important to connect first rather than e.g. voice / video?

The linked tracking bug appears to be a chrome-only bug report with a particular demo that doesn't use the alwaysNegotiateDataChannels attribute and works on Firefox. I don't quite understand what the new configuration extension has to do with the original bug report.

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADxkKiKuE79-xWUFiO9NCy%2Big9Pvn1oi6fVbkdomFLo4--bJQw%40mail.gmail.com.

[Rick Byers]

This is generally why we require explainers. Part of the point of this launch process is ensuring we've got the public material for web developers to understand the feature. Harald can you post an explainer somewhere which includes answers to Rob's questions?

Thanks,

   Rick

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJh39TPTxV5evdFUMnmfQE3aP2siNXNSZVpBr8wBitT56-nFCQ%40mail.gmail.com.