WebRTC RTP header extension control

Extend the WebRTC RTCRTPTransceiver API to offer control over which RTP header extensions are negotiated. Extend the WebRTC RTCRTPSender API to offer control over which RTP header extensions are sent.

With the number of RTP header extensions being proposed, experimented with or included in implementations, sending them all all the time will incur considerable overhead, and trying to negotiate too many of them has led to interoperability issues. A mechanism for negotiating them is available in SDP, but a control mechanism for this negotiation has not been available.

Documentation

Specification

Public discussion

Status in Chromium

Blink>WebRTC>PeerConnection


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No public signals
  • No public signals
  • No public signals
  • No signals

Owners

Last updated on 2020-02-13