- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 May 2024 13:10:16 +0000
- To: public-webrtc-logs@w3.org
I think a plain `extensionId` is probably the better option. > 1. Add extensionId, keep uri as a convenience. This way `extensionId` and `uri` could be set in a conflicting way. > 2. Add API to register a given URI as a RTP header extension, like we might be doing for custom codecs. In that case, UA has the info and can translate the extensionId in a uri. > > The latter is somehow more appealing to me. What are the benefits of this? My spontaneous reaction is that this just makes it slightly more convoluted. -- GitHub Notification of comment by Philipel-WebRTC Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/29#issuecomment-2115208611 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 May 2024 13:10:16 UTC