RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
In plain English — editorial summary, not part of the RFC
This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4787
- Published
- January 2007
- Authors
- F. Audet; C. Jennings
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 29
- Also known as
- BCP127
Topics
Referenced by
2 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.
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 4815RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095Current
February 2007
- RFC 4896Signaling Compression (SigComp) Corrections and ClarificationsCurrent
June 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?