Compliance matrix

View Source

This is the index of normative requirements the stack tracks, by protocol. Each protocol page lists requirements with their specification section, implementing module, test and status. Use it to see what is supported and what is missing before relying on a feature.

Statuses:

StatusMeaning
Not implementedNo code yet
Implemented, untestedCode exists, no test covers it
Unit testedCovered by eunit or PropEr tests
E2E testedCovered by an Erlang to Erlang test over real sockets
Interoperability testedCovered by a test against an independent implementation
Non-compliant / known limitationDeviates from the specification, see notes

A protocol is complete only when its mandatory requirements reach E2E tested, and interoperability tested where an independent peer exists.

Summary

What works today, end to end and against independent implementations (see INTEROP.md):

  • Full ICE and ICE-Lite, trickle, consent freshness, ICE restart in both directions, the ice2 option with checks paced at Ta, ICE-TCP (passive and active), TURN relays reached over UDP, TCP or TLS.
  • Remote candidates with mDNS .local names (Chromium's default) or DNS names, resolved over IPv4 and IPv6 multicast without blocking the transport; optional mDNS names for our own host candidates, answered with NSEC for the family they lack; a host address a STUN server maps to itself is found public and signaled as it is afterwards.
  • DTLS 1.3 (RFC 9147) by default with fallback to DTLS 1.2 (use_srtp, extended master secret), connection IDs on request (1.2 and 1.3; 1.2 CIDs verified with mbedTLS and pion/dtls): 1.3 verified with OpenSSL 4.1 and Chromium in both roles, 1.2 with OTP ssl, OpenSSL, Pion and aiortc.
  • SRTP and SRTCP (AES-CM and AES-GCM profiles), with CSRCs and header extensions encrypted by cryptex (RFC 9335) when the peer accepts it, verified with Pion, and single elements such as the audio level encrypted with RFC 6904 when negotiated.
  • One transport for a BUNDLE group, or one per group or unbundled section, offered and answered, verified with Chromium and Firefox.
  • RTP/RTCP with BUNDLE demultiplexing, sender and receiver reports, NACK with RTX, PLI and FIR, audio RED (RFC 2198) checked against Chromium and GStreamer, video FEC with ULPFEC in RED (checked against GStreamer) and FlexFEC (RFC 8627), SLI and RPSI handed to the encoder and sent when the decoder asks, rapid synchronisation of new streams (RFC 6051, ntp-64 and ntp-56, SR requests), one-byte and two-byte header extensions mixed when extmap-allow-mixed is negotiated, forwarding without decoding.
  • Frame assembly and a jitter buffer for VP8, VP9, H.264, AV1 and audio, checked against GStreamer's payloaders and ffmpeg, Chromium and Firefox.
  • The W3C statistics, with the decoder and encoder members from a codec plugin or the application.
  • SCTP over DTLS with data channels: reliable, unordered, partially reliable, large messages, channel close by stream reset, priorities through a weighted fair queueing scheduler.
  • JSEP offer/answer with answers and re-offers checked against the offer, renegotiation, rollback from offers and provisional answers, pranswer; a new DTLS certificate is accepted only with an ICE restart and starts a new association (RFC 8842).
  • Simulcast with rid negotiation and the rid / repaired-rid header extensions: receiving layers from Chromium, sending layers to Pion, asking Firefox for layers it then sends, per-layer NACK, RTX, keyframe requests and RTP stream pause and resume (RFC 7728, between Erlang peers).
  • Congestion control: transport-wide CC feedback in both directions, RFC 8888 feedback with ECN when transport-cc is not negotiated, a GCC delay and loss based estimator, bandwidth probing at the start (in simulation a 2 Mbps link reaches 70% in 200 ms), while application limited, after a drop and on a raised maximum, a pacer with audio and retransmission priority, RFC 8083 circuit breakers that halt a stream (timeouts) or cut its rate by ten then halt it (congestion), and receiver report based control for peers without transport-cc. Chromium's estimate grows on our feedback and encodes its top simulcast layer. The RFC 8867 evaluation cases pass in simulation, fairness between flows with different RTTs included; the two left are coupled congestion control (RFC 8699, not implemented) and multiple bottlenecks (not tested). TMMBR and TMMBN (RFC 5104) limit a sender with a bounding set, in both directions.
  • DSCP marking by flow type and priority (RFC 8835, RFC 8837) on UDP and TCP, with a lower drop precedence for key frames.
  • Behavior under loss, bursts, reordering, duplication, jitter, a 1200 byte MTU, outages, spoofing, replay, floods and SSRC churn; per-connection state stays bounded (DTLS reassembly, receive streams, SRTP state, data channel message size, per-SSRC statistics, the 0-RTT replay table). Private keys, credentials and session keys stay out of logs and crash reports, every process of a peer connection ends with it, and 0-RTT tickets stop working when the application restarts.

The gaps that once mattered for a full WebRTC deployment are closed; what remains not implemented is listed per area, with the reason, in the pages below.

Codec encoding and decoding are not part of the library. Opus, G.711, VP8, VP9, H.264 and AV1 are negotiated, packetized, assembled into frames and forwarded; producing or consuming the media is the application's job, or a codec plugin's (webrtc_media_codec).

Specifications tracked

Superseded documents named in older WebRTC RFCs are tracked under their replacement.

AreaSpecificationReplaces / updatesPage
STUNRFC 8489obsoletes RFC 5389stun
STUN test vectorsRFC 5769stun
ICERFC 8445updated by RFC 8863ice
ICE SDPRFC 8839ice
Trickle ICERFC 8838ice
Consent freshnessRFC 7675ice
mDNS ICE candidatesdraft-ietf-mmusic-mdns-ice-candidates-03ice
Multicast DNSRFC 6762ice
TURNRFC 8656obsoletes RFC 5766turn
STUN URIRFC 7064turn
TURN URIRFC 7065turn
TURN server discoveryRFC 5928turn
MultiplexingRFC 7983updated by RFC 9443transport
DTLS 1.2RFC 6347dtls
DTLS 1.3RFC 9147dtls
Extended master secretRFC 7627dtls
DTLS-SRTPRFC 5764updated by RFC 7983dtls
ICE and DTLSRFC 8842dtls
FingerprintsRFC 8122updated by RFC 8842dtls
SRTPRFC 3711srtp
SRTP AES-GCMRFC 7714srtp
Encrypted header extensionsRFC 6904srtp
CryptexRFC 9335srtp
RTP/RTCPRFC 3550rtp
RTP usage in WebRTCRFC 8834rtp
AVPFRFC 4585rtp
CCMRFC 5104rtp
RTP stream pause and resumeRFC 7728rtp
Header extensionsRFC 8285rtp
RTXRFC 4588rtp
Redundant audioRFC 2198rtp
WebRTC FECRFC 8854rtp
rtcp-muxRFC 5761, RFC 8858rtp
Congestion controlRFC 8836, RFC 8888rtp
Congestion control test casesRFC 8867, RFC 8868rtp
SCTPRFC 9260obsoletes RFC 4960sctp
PR-SCTPRFC 3758sctp
Stream reconfigurationRFC 6525sctp
Message interleavingRFC 8260sctp
SCTP over DTLSRFC 8261sctp
Zero checksumRFC 9653sctp
Data channelsRFC 8831datachannel
DCEPRFC 8832datachannel
SDP for SCTPRFC 8841sdp
SDPRFC 8866obsoletes RFC 4566sdp
Offer/answerRFC 3264sdp
JSEPRFC 9429obsoletes RFC 8829sdp
BUNDLERFC 9143obsoletes RFC 8843sdp
Security architectureRFC 8826, RFC 8827security
TransportsRFC 8835transport
WebRTC statisticsW3C webrtc-statsCandidate Recommendationstats

Interoperability results are tracked separately in INTEROP.md.