metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5389: Session Traversal Utilities for NAT (STUN)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8489.

Current document in this lineage: 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 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]

Document record

Document ID
RFC5389
Published
October 2008
Authors
J. Rosenberg; R. Mahy; P. Matthews; D. Wing
Status
PROPOSED STANDARD
Stream
IETF
Area
tsv
Pages
51
Also known as
—
Obsoletes:
RFC 3489
Obsoleted by:
RFC 8489
Updated by:
RFC 7350, RFC 8553

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 3489 (2003)
  2. RFC 5389 (2008)
  3. RFC 8489 (2020) ✓

Read the full history of Session Traversal Utilities for NAT (STUN) →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5389-session-traversal-utilities-for-nat-stun