RFC 7279: An Acceptable Use Policy for New ICMP Types and Codes
In plain English — editorial summary, not part of the RFC
In this document we provide a basic description of ICMP's role in the IP stack and some guidelines for future use. This document is motivated by concerns about lack of clarity concerning when to add new Internet Control Message Protocol (ICMP) types and/or codes. These concerns have highlighted a need to describe policies for when adding new features to ICMP is desirable and when it is not.
Document record
- Document ID
- RFC7279
- Published
- May 2014
- Authors
- M. Shore; C. Pignataro
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- BCP189
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6791Stateless Source Address Mapping for ICMPv6 PacketsCurrent
November 2012
- RFC 8335PROBE: A Utility for Probing InterfacesCurrent
February 2018
- RFC 5461TCP's Reaction to Soft ErrorsCurrent
February 2009
- RFC 4890Recommendations for Filtering ICMPv6 Messages in FirewallsCurrent
May 2007
- RFC 4065Instructions for Seamoby and Experimental Mobility Protocol IANA AllocationsCurrent
July 2005
- RFC 2463Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 1256ICMP Router Discovery MessagesCurrent
September 1991
- RFC 1393Traceroute Using an IP OptionObsoleted
January 1993
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?