NAT Behavioral Requirements for TCP
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 31
- Abstract
- 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.
- Publication Date
- 2008-10-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC5382- Link
- https://doi.org/10.17487/RFC5382
- Author(s)
- Saikat GuhaKaushik BiswasBryan FordSenthil SivakumarPyda Srisuresh
- Keyword(s)
- NAT
Latest version of IETF RFC 5382
Document Versions — IETF RFC 5382
-
▶ IETF RFC 5382 (2008-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- Ford, B., Srisuresh, P., and D. Kegel, "Peer-to-peer communication across network address translators", Proceedings of the USENIX Annual Technical Conference (Anaheim, CA), April 2005. EXTERNAL
- Guha, S. and P. Francis, "NUTSS: A SIP based approach to UDP and TCP connectivity", Proceedings of the ACM SIGCOMM Workshop on Future Directions in Network Architecture (Portland, OR), August 2004. EXTERNAL
- Biggadike, A., Ferullo, D., Wilson, G., and A. Perrig, "NATBLASTER: Establishing TCP connections between hosts behind NATs", Proceedings of the ACM SIGCOMM Asia Workshop (Beijing, China), April 2005. EXTERNAL
- Guha, S. and P. Francis, "Characterization and Measurement of TCP Traversal through NATs and Firewalls", Proceedings of the Internet Measurement Conference (Berkeley, CA), October 2005. EXTERNAL
- Srisuresh, P., Ford, B., Sivakumar, S., and S. Guha, "NAT Behavioral Requirements for ICMP protocol", Work in Progress, June 2008. EXTERNAL
- IETF RFC 793 [Superseded*]
- IETF RFC 959 [Active*]
- IETF RFC 1122 [Active*]
- IETF RFC 1191 [Active*]
- IETF RFC 1337 [Active*]
- IETF RFC 1644 [Superseded*]
- IETF RFC 2018 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2663 [Active*]
- IETF RFC 2923 [Active*]
- IETF RFC 3022 [Active*]
- IETF RFC 4008 [Superseded*]
- IETF RFC 4614 [Superseded*]
- IETF RFC 4787 [Active*]
- IETF RFC 4953 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5382.json
Amended by:
RFC7857 — RFC7857 EXTERNAL
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5382, NAT Behavioral Requirements for TCP. Available at https://doi.org/10.17487/RFC5382
Snippet:
IETF RFC 5382, NAT Behavioral Requirements for TCP. Available at https://doi.org/10.17487/RFC5382
HTML (ISO 690 compliant)
Preview:
IETF RFC 5382, NAT Behavioral Requirements for TCP. Available at https://doi.org/10.17487/RFC5382
Snippet:
<span class="citation"><cite>IETF RFC 5382</cite>, NAT Behavioral Requirements for TCP. Available at <a href="https://doi.org/10.17487/RFC5382" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5382</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5382, NAT Behavioral Requirements for TCP
doi: 10.17487/RFC5382
url: https://doi.org/10.17487/RFC5382
doi: 10.17487/RFC5382
url: https://doi.org/10.17487/RFC5382
Snippet:
<li> <cite id="bib-rfc5382">IETF RFC 5382</cite>, NAT Behavioral Requirements for TCP <span class="doi">10.17487/RFC5382</span> </li>
Referenced By
- IETF RFC 5245 [Superseded*]
- IETF RFC 5383 [Active*]
- IETF RFC 5461 [Active*]
- IETF RFC 5508 [Active*]
- IETF RFC 5596 [Active*]
- IETF RFC 5597 [Active*]
- IETF RFC 5677 [Active*]
- IETF RFC 6056 [Active*]
- IETF RFC 6092 [Active*]
- IETF RFC 6135 [Active*]
- IETF RFC 6145 [Superseded*]
- IETF RFC 6146 [Active*]
- IETF RFC 6263 [Active*]
- IETF RFC 6333 [Active*]
- IETF RFC 6535 [Active*]
- IETF RFC 6544 [Active*]
- IETF RFC 6887 [Active*]
- IETF RFC 6888 [Active*]
- IETF RFC 7269 [Active*]
- IETF RFC 7413 [Active*]
- IETF RFC 7599 [Active*]
- IETF RFC 7915 [Active*]
- IETF RFC 8490 [Active*]