References

The specifications and documentation that define WebRTC. When behaviour is ambiguous, these are the authority.

Specifications

W3C, WebRTC: Real-Time Communication in Browsers

The browser API specification: RTCPeerConnection, RTCDataChannel, and the media model.

W3C: Media Capture and Streams

getUserMedia, MediaStream, MediaStreamTrack, and the constraints model. A separate specification, not part of WebRTC.

W3C: Screen Capture

getDisplayMedia and the display-surface model behind screen sharing.

W3C: Identifiers for WebRTC's Statistics API

Every dictionary and field getStats() can return.

MDN: WebRTC API

Practical, example-driven reference for every interface and event.

Core RFCs

RFC 8825: Overview of Browser-Based Real-Time Protocols

The map of the entire WebRTC protocol suite.

RFC 8829: JSEP

JavaScript Session Establishment Protocol: the offer/answer model behind signaling.

RFC 8835: Transports for WebRTC

How media and data ride over ICE, DTLS, SCTP, and SRTP.

RFC 8831: WebRTC Data Channels

The SCTP-over-DTLS data channel model.

RFC 8832: Data Channel Establishment Protocol

How peers open and label data channels (DCEP).

NAT Traversal

RFC 8445: ICE

Interactive Connectivity Establishment: gathering candidates, pairing them, and nominating a path.

RFC 8489: STUN

Session Traversal Utilities for NAT: discovering a public address.

RFC 8656: TURN

Relaying media when a direct peer-to-peer path is impossible.

Security

RFC 8826: Security Considerations

The threat model for browser-based real-time communication.

RFC 8827: Security Architecture

Why DTLS and SRTP are mandatory, not optional.