Contact emails [email protected], [email protected], [email protected], [email protected]
Explainer No information provided Specification https://datatracker.ietf.org/doc/draft-hancke-tsvwg-snap Summary WebRTC Data Channels use the Stream Control Transmission Protocol (SCTP) over a Datagram Transport Layer Security (DTLS) association. The standard SCTP connection establishment requires a handshake that introduces latency. A new Internet draft specifies a method to accelerate the datachannel establishment by embedding the SCTP initialization parameters within the Session Description Protocol (SDP) offer/answer exchange. This reduces the time required to open a data channel by up to two network round-trip times. Blink component Blink>WebRTC>DataChannel Web Feature ID webrtc TAG review n/a, part of WebRTC covered by IETF drafts TAG review status Not applicable Origin Trial Name WebRTC Data Channel: SCTP Negotiation Acceleration Protocol (SNAP) Goals for experimentation This feature should be gated until the IETF has had a chance to adopt the current draft into a WG and we know whether changes will be required. Chromium Trial Name WebRtcSctpSnap Origin Trial documentation link https://datatracker.ietf.org/doc/draft-hancke-tsvwg-snap WebFeature UseCounter name kRTCSctpSnapNegotiated Risks Interoperability and Compatibility No information provided Gecko: No signal WebKit: No signal Web developers: No signals Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? No information provided Reason this experiment is being extended Presented the IETF 126 TSVWG (and asked for agenda time at the upcoming one), list discussion is at https://mailarchive.ietf.org/arch/msg/tsvwg/Kuq5b8FrZe0kDDkFw6NY77QP6Ww/ The only remaining open issue is how this gets represented in the SDP, which is expected to be settled by the next IETF meeting. Positive deployment feedback from Microsoft (improvement of 23% in P50 and 22% on P90 Transport setup latency) https://github.com/fippo/warp-snap-sped/issues/21#issuecomment-6308379637 and mention in the OpenAI blog post: https://openai.com/index/continuous-voice-interaction-with-gpt-live/ Ongoing technical constraints No information provided Debuggability No information provided 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? No Flag name on about://flags No information provided Finch feature name WebRtcSctpSnap Requires code in //chrome? False Tracking bug https://issues.webrtc.org/issues/426480601 Measurement The UMA WebRTC.PeerConnection.NegotiatedSctpSnap is measured at connection setup, allowing measurement of the percentage of connections using the feature. Estimated milestones Origin trial desktop first 151 Origin trial desktop last 156 Origin trial extension 1 end milestone 162 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5137946677215232?gate=4906997945335808 Links to previous Intent discussions Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADxkKiJJzDXOUwYx%3DznrQz1hPkZCZnNWOAucF%2BK%3DoSymgGyDFA%40mail.gmail.com This intent message was generated by Chrome Platform Status. -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6aeb35dd.95dfa6d9.3d0ae5.0276.GAE%40google.com.
