- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 06:26:05 +0000
- To: public-webrtc-logs@w3.org
JSEP talks about "For each supported RTP header extension", so one might argue that a JSEP-compatible version of this PR that doesn't turn the API into a NO-OP might be to replaces the JSEP modifications with one new step at the end of `setHeaderExtensionsToNegotiate`: "Modify the internal set of supported RTP header extensions to match [[HeaderExtensionsToNegotiate]]." You might want to lawyer whether that is or is not OK but it seems better than a NO-OP until we have something in JSEP to do what we want. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/164#issuecomment-1524835673 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 April 2023 06:26:12 UTC