RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
In plain English — editorial summary, not part of the RFC
This memo documents the various methods known to be in use by applications to establish direct communication in the presence of Network Address Translators (NATs) at the current time. Although this memo is intended to be mainly descriptive, the Security Considerations section makes some purely advisory recommendations about how to deal with security vulnerabilities the applications could inadvertently create when using the methods described. This memo covers NAT traversal approaches used by both TCP- and UDP-based applications. This memo is not an endorsement of the methods described, but merely an attempt to capture them in a document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5128
- Published
- March 2008
- Authors
- P. Srisuresh; B. Ford; D. Kegel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 32
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5135IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT)Current
February 2008
- RFC 5170Low Density Parity Check (LDPC) Staircase and Triangle Forward Error Correction (FEC) SchemesCurrent
June 2008
- RFC 5189Middlebox Communication (MIDCOM) Protocol SemanticsCurrent
March 2008
- RFC 5190Definitions of Managed Objects for Middlebox CommunicationCurrent
March 2008
- RFC 5053Raptor Forward Error Correction Scheme for Object DeliveryCurrent
October 2007
- RFC 5052Forward Error Correction (FEC) Building BlockCurrent
August 2007
- RFC 5049Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)Updated
December 2007
- RFC 5048Internet Small Computer System Interface (iSCSI) Corrections and ClarificationsObsoleted
October 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?