- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Mar 2023 10:39:23 +0000
- To: public-webrtc@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-extensions: == Header extension API lets the remote end control the remote preferences == https://w3c.github.io/webrtc-extensions/#rtp-header-extension-control-modifications > If description is of type "[offer](https://www.w3.org/TR/webrtc/#dom-rtcsdptype-offer)", then for each extension in transceiver.[[[HeaderExtensionsToNegotiate]]](https://w3c.github.io/webrtc-extensions/#dfn-headerextensionstonegotiate), run the following steps: > [...] >>Set extension.[direction](https://w3c.github.io/webrtc-extensions/#dom-rtcrtpheaderextensioncapability-direction) to offeredDirection. This lets the remote end control what the local end offers. This is not what the API intends to do (primarily enabling non-default header extensions) nor is it consistent with the SDP principles involved which (in some interpretations) enable sending an extension when the remote offers it already. Suggested fix: remove those steps. Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/153 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 March 2023 10:39:25 UTC