Visual RFC.
ALL RFCs / RFC 8489
Read the RFC ↗
RFC 8489 / PROTOCOL MECHANISMS

Learn the server-observed address

01

A Binding transaction can reveal the source address and port observed by the STUN server.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 2 ↗
RFC 8489 · § 2EXAMPLE
3 / 3
Learn the server-observed addressA Binding transaction can reveal the source address and port observed by the STUN server.clientNATSTUNBindingtranslated sourceserver observes public IP:portXOR-MAPPED-ADDRESSreflexive candidateObserved mapping is not universal reachability
03
The response reports that address to the client.

The response reports that address to the client.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

XOR-MAPPED-ADDRESS reports a reflexive transport address, not a guaranteed universally reachable endpoint.

  • XOR-MAPPED-ADDRESS reports a reflexive transport address, not a guaranteed universally reachable endpoint.
  • A different destination can encounter different NAT mapping or filtering behavior.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Learn the server-observed address
  2. Match a response to its transaction
  3. Parse the STUN header and attributes
  4. Use credentials for message integrity
  5. Separate discovery from connectivity and privacy
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗