RFC 5135: IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT)
In plain English — editorial summary, not part of the RFC
This document specifies requirements for a for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT) that support Any Source IP Multicast or Source-Specific IP Multicast. An IP multicast-capable NAT device that adheres to the requirements of this document can optimize the operation of IP multicast applications that are generally unaware of IP multicast NAT devices. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5135
- Published
- February 2008
- Authors
- D. Wing; T. Eckert
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 16
- Also known as
- BCP135
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5128State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)Current
March 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?