Open aboba opened 11 months ago
This issue was mentioned in WEBRTCWG-2023-12-05 (Page 58)
For send side, there would be a need for a registration API that would modify the SDP and map the header extension URI to the extension ID.
For read side, this API would be nice but is not mandatory if the extension ID is exposed directly. Note also that reading header extension is easier since there is no issue related to bad data or conflicting IDs.
Does RtpTransport allow an application to send arbitrary octets in RTP header extensions?
What restrictions are placed on the IDs/content of RTP header extensions?