Skip to content

alwaysNegotiateDataChannels: disallow setConfiguration #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guidou merged 1 commit into from
Aug 3, 2026
Merged

alwaysNegotiateDataChannels: disallow setConfiguration #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1625,10 +1625,20 @@ <h3>
"If channel is the first RTCDataChannel created on connection
update the negotiation-needed flag for connection"
with
"If channel is the first RTCDataChannel created on connection
"If channel is the first RTCDataChannel created on connection
and {{RTCPeerConnection/[[SctpTransport]]}} is null
update the negotiation-needed flag for connection".
</p>
<p>
{{RTCConfiguration/alwaysNegotiateDataChannels}} can only be set when constructing the
{{RTCPeerConnection}} and MUST NOT be changed afterwards.
In the <a data-cite="WEBRTC#set-the-configuration">set the configuration</a> algorithm,
add a step after the step saying
"If the value of configuration.rtcpMuxPolicy differs from oldConfig.rtcpMuxPolicy, then fail."
saying
"If the value of configuration.{{RTCConfiguration/alwaysNegotiateDataChannels}} differs from
oldConfig.{{RTCConfiguration/alwaysNegotiateDataChannels}}, then fail."
</p>
</section>
<section id="always-negotiating-datachannels-interface-extensions">
<h3>
Expand All @@ -1651,6 +1661,13 @@ <h3>
with
"Lastly, if a data channel has been created and no m=section has been generated for data, a m= section MUST be generated for data".
</p>
<p>
In setConfiguration in [[RTCWEB-JSEP]] section 4.1.18, replace
"The bundle and RTCP-multiplexing policies MUST NOT be changed after the construction of the PeerConnection."
with
"The bundle policy, the RTCP-multiplexing policy and the preference to always negotiate data channels
MUST NOT be changed after the construction of the PeerConnection."
</p>
</section>
</section>
<section class="informative">
Expand Down
Loading