RFC 3489: STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5389.
Current document in this lineage: RFC 8489 — Session Traversal Utilities for NAT (STUN)
In plain English — editorial summary, not part of the RFC
Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) (STUN) is a lightweight protocol that allows applications to discover the presence and types of NATs and firewalls between them and the public Internet. It also provides the ability for applications to determine the public Internet Protocol (IP) addresses allocated to them by the NAT. STUN works with many existing NATs, and does not require any special behavior from them. As a result, it allows a wide variety of applications to work through existing NAT infrastructure. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3489
- Published
- March 2003
- Authors
- J. Rosenberg; J. Weinberger; C. Huitema; R. Mahy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 47
- Also known as
- —
- Obsoleted by:
- 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) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2428FTP Extensions for IPv6 and NATsCurrent
September 1998
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3150End-to-end Performance Implications of Slow LinksCurrent
July 2001
- RFC 3095RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressedUpdated
July 2001
- RFC 2694DNS extensions to Network Address Translators (DNS_ALG)Current
September 1999
- RFC 4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPUpdated
January 2007
- RFC 4815RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095Current
February 2007
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?