When enabling the Experimental Web Platform features toggle in Chrome 151, libdatachannel peers (when libdatachannel is the answerer) stop working.
This seems to be due to Chrome 151 experimentally enabling "SNAP" (SCTP Negotiation Acceleration Protocol) and libdatachannel echoing back the newly introduced a=sctp-init attribute, which incorrectly signals SNAP support to Chrome, which results in a broken datachannel.
See https://datatracker.ietf.org/doc/html/draft-hancke-tsvwg-snap-00#name-generating-the-sdp-answer
I attached a minimal reproduction.
When running the repro against a chrome 151 browser with the flag --enable-blink-features=WebRtcSctpSnap, you should see the datachannel fails.
repro.zip
Environment: libdatachannel v0.24.5, Chrome 151.0.7922.71, Linux x86_64
Refs: https://developer.chrome.com/release-notes/151#webrtc_data_channel_sctp_negotiation_acceleration_protocol
When enabling the
Experimental Web Platform featurestoggle in Chrome 151, libdatachannel peers (when libdatachannel is the answerer) stop working.This seems to be due to Chrome 151 experimentally enabling "SNAP" (SCTP Negotiation Acceleration Protocol) and libdatachannel echoing back the newly introduced
a=sctp-initattribute, which incorrectly signals SNAP support to Chrome, which results in a broken datachannel.See https://datatracker.ietf.org/doc/html/draft-hancke-tsvwg-snap-00#name-generating-the-sdp-answer
I attached a minimal reproduction.
When running the repro against a chrome 151 browser with the flag
--enable-blink-features=WebRtcSctpSnap, you should see the datachannel fails.repro.zip
Environment: libdatachannel v0.24.5, Chrome 151.0.7922.71, Linux x86_64
Refs: https://developer.chrome.com/release-notes/151#webrtc_data_channel_sctp_negotiation_acceleration_protocol