RFC 5780: NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
In plain English — editorial summary, not part of the RFC
This specification defines an experimental usage of the Session Traversal Utilities for NAT (STUN) Protocol that discovers the presence and current behavior of NATs and firewalls between the STUN client and the STUN server. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5780
- Published
- May 2010
- Authors
- D. MacDonald; B. Lowekamp
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 27
- Also known as
- —
- Updated by:
- RFC 8553
Topics
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 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5769Test Vectors for Session Traversal Utilities for NAT (STUN)Current
April 2010
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 5795The RObust Header Compression (ROHC) FrameworkCurrent
March 2010
- RFC 5762RTP and the Datagram Congestion Control Protocol (DCCP)Updated
April 2010
- RFC 5740NACK-Oriented Reliable Multicast (NORM) Transport ProtocolCurrent
November 2009
- RFC 5856Integration of Robust Header Compression over IPsec Security AssociationsCurrent
May 2010
- RFC 5857IKEv2 Extensions to Support Robust Header Compression over IPsecCurrent
May 2010
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?