Session Traversal Utilities for NAT (STUN)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 51
- Abstract
- Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with Network Address Translator (NAT) traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints, and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs, and does not require any special behavior from them. STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution. This is an important change from the previous version of this specification (RFC 3489), which presented STUN as a complete solution. This document obsoletes RFC 3489. [STANDARDS-TRACK]
- Publication Date
- 2008-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5389- Link
- https://doi.org/10.17487/RFC5389
- Author(s)
- Jonathan RosenbergRohan MahyPhilip MatthewsDan Wing
- Keyword(s)
- SIPs, NAT, STUN, NAT Traversal, ICE, Firewalls, TURN, VoIP
Latest version of IETF RFC 5389
Document Versions — IETF RFC 5389
-
▶ IETF RFC 5389 (2008-10-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Amended by:
- RFC7350 NOT IN REGISTRY
- RFC8553 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 791 [Active*]
- IETF RFC 1122 [Active*]
- IETF RFC 1321 [Active*]
- IETF RFC 2104 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 2617 [Superseded*]
- IETF RFC 2782 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 2988 [Superseded*]
- IETF RFC 3629 [Active*]
- IETF RFC 4013 [Superseded*]
- T-REC-V.42.2002 — ITU.V42.2002 EXTERNAL
Bibliographic Reference(s)
- Rosenberg, J., Mahy, R., and P. Matthews, "Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)", Work in Progress, July 2008. EXTERNAL
- Karn, P. and C. Partridge, "Improving Round-Trip Time Estimates in Reliable Transport Protocols", SIGCOMM 1987, August 1987. EXTERNAL
- Rosenberg, J., "TCP Candidates with Interactive Connectivity Establishment (ICE)", Work in Progress, July 2008. EXTERNAL
- Rosenberg, J., "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols", Work in Progress, October 2007. EXTERNAL
- MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery Using STUN", Work in Progress, July 2008. EXTERNAL
- Jennings, C. and R. Mahy, "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)", Work in Progress, June 2008. EXTERNAL
- IETF RFC 2616 [Superseded*]
- IETF RFC 3261 [Active*]
- IETF RFC 3264 [Active*]
- IETF RFC 3424 [Active*]
- IETF RFC 3489 [Superseded*]
- IETF RFC 4107 [Active*]
- IETF RFC 5226 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5389.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5389, Session Traversal Utilities for NAT (STUN). Available at https://doi.org/10.17487/RFC5389
Snippet:
IETF RFC 5389, Session Traversal Utilities for NAT (STUN). Available at https://doi.org/10.17487/RFC5389
HTML (ISO 690 compliant)
Preview:
IETF RFC 5389, Session Traversal Utilities for NAT (STUN). Available at https://doi.org/10.17487/RFC5389
Snippet:
<span class="citation"><cite>IETF RFC 5389</cite>, Session Traversal Utilities for NAT (STUN). Available at <a href="https://doi.org/10.17487/RFC5389" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5389</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5389, Session Traversal Utilities for NAT (STUN)
doi: 10.17487/RFC5389
url: https://doi.org/10.17487/RFC5389
doi: 10.17487/RFC5389
url: https://doi.org/10.17487/RFC5389
Snippet:
<li> <cite id="bib-rfc5389">IETF RFC 5389</cite>, Session Traversal Utilities for NAT (STUN) <span class="doi">10.17487/RFC5389</span> </li>
Referenced By
- IETF RFC 5687 [Active*]
- IETF RFC 5764 [Active*]
- IETF RFC 5766 [Superseded*]
- IETF RFC 5971 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6881 [Active*]