RFC 8489: Session Traversal Utilities for NAT (STUN)
In plain English — editorial summary, not part of the RFC
Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with 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 document obsoletes RFC 5389.
Document record
- Document ID
- RFC8489
- Published
- February 2020
- Authors
- M. Petit-Huguenin; G. Salgueiro; J. Rosenberg; D. Wing; R. Mahy; P. Matthews
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 67
- Also known as
- —
- Obsoletes:
- RFC 5389
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3489 (2003)
- RFC 5389 (2008)
- RFC 8489 (2020)
Read the full history of Session Traversal Utilities for NAT (STUN) →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5630The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 8547TCP-ENO: Encryption Negotiation OptionCurrent
May 2019
- RFC 8548Cryptographic Protection of TCP Streams (tcpcrypt)Current
May 2019
- RFC 8593Video Traffic Models for RTP Congestion Control EvaluationsCurrent
May 2019
- RFC 8382Shared Bottleneck Detection for Coupled Congestion Control for RTP MediaCurrent
June 2018
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 8298Self-Clocked Rate Adaptation for MultimediaCurrent
December 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?