All specs
RFC 8489RFCShould KnowProduct2020

Session Traversal Utilities for NAT

WebRTC·RFC Editor
WHY YOU NEED THIS

STUN is how WebRTC discovers the public-facing address for peer-to-peer connections. Every WebRTC deployment needs a STUN server.

What It Defines

STUN lets a client behind NAT discover its public IP address and port. Used by ICE as the mechanism for srflx candidate gathering. Defines the STUN message format and binding request/response.

Canonical (Normative)

stunnatwebrtcconnectivity
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 8445RFCShould Know

ICE

NAT traversal is why WebRTC calls fail. ICE is how browsers find a working path between peers. Know it when debugging call connectivity failures.

ProductWebRTC
Details
RFC 8656RFCShould Know

TURN

~15-20% of WebRTC calls require TURN relay because both peers are behind symmetric NAT. Without TURN, those calls fail silently.

ProductWebRTC
Details
W3C WebRTCW3CShould Know

WebRTC

Video calls (Meet, Zoom web), voice calls, peer-to-peer file transfer, and collaborative tools. The browser API surface for real-time A/V communication.

ProductWebRTC
Details