RFC 5508: NAT Behavioral Requirements for ICMP
In plain English — editorial summary, not part of the RFC
This document specifies the behavioral properties required of the Network Address Translator (NAT) devices in conjunction with the Internet Control Message Protocol (ICMP). The objective of this memo is to make NAT devices more predictable and compatible with diverse application protocols that traverse the devices. Companion documents provide behavioral recommendations specific to TCP, UDP, and other protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5508
- Published
- April 2009
- Authors
- P. Srisuresh; B. Ford; S. Sivakumar; S. Guha
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 29
- Also known as
- BCP148
- 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 1739A Primer On Internet and TCP/IP ToolsObsoleted
December 1994
- RFC 6791Stateless Source Address Mapping for ICMPv6 PacketsCurrent
November 2012
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 8335PROBE: A Utility for Probing InterfacesCurrent
February 2018
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 1574Essential Tools for the OSI InternetCurrent
February 1994
- RFC 5510Reed-Solomon Forward Error Correction (FEC) SchemesCurrent
April 2009
- RFC 5525Reliable Server Pooling MIB Module DefinitionCurrent
April 2009
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?