- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 07:58:11 +0000
- To: public-webrtc-logs@w3.org
@henbos RFC 8829bis assumes that "supported" RTP header extensions are always offered, and if offered, are answered. But with the RTP header extension API only the "mandatory to use" RTP header extensions are automatically offered/answered; a "supported" RTP header extension also needs to be in the [[HeaderExtensionsToNegotiate]]. So if we can still change RFC 8829bis, perhaps we can swap out the word "supported" for something better without having to refer to internal slots. IF we can't modify RFC 8829bis, your suggestion might work. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/164#issuecomment-1525037000 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 07:58:13 UTC