RFC 5382: NAT Behavioral Requirements for TCP
In plain English — editorial summary, not part of the RFC
This document defines a set of requirements for NATs that handle TCP that would allow many applications, such as peer-to-peer applications and online games 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
- RFC5382
- Published
- October 2008
- Authors
- S. Guha; K. Biswas; B. Ford; S. Sivakumar; P. Srisuresh
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 31
- Also known as
- BCP142
- Updated by:
- RFC 7857
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 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 5401Multicast Negative-Acknowledgment (NACK) Building BlocksCurrent
November 2008
- RFC 5356Reliable Server Pooling PoliciesCurrent
September 2008
- RFC 5355Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to ThreatsCurrent
September 2008
- RFC 5354Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) ParametersCurrent
September 2008
- RFC 5353Endpoint Handlespace Redundancy Protocol (ENRP)Current
September 2008
- RFC 5352Aggregate Server Access Protocol (ASAP)Current
September 2008
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?