- From: Harald Alvestrand via GitHub <noreply@w3.org>
- Date: Thu, 14 Aug 2025 10:11:47 +0000
- To: public-webrtc@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-extensions: == RTP header extension control: Incompatible extensions == In some cases, the set of extensions in an answer needs to be a subset of the offered extensions, and this needs to be reflected in [[NegotiatedExtensions]], even when the incoming answer is offering the extension. (The current case is that the transport-sequence-number extension needs to be turned off when CCFB is in use) To correct, add a step to section 5.2, when processing _negotiatedExtensions_, allow the UA to modify the set of accepted extensions to be consistent with the PeerConnection state. Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/239 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 August 2025 10:11:48 UTC