An Acceptable Use Policy for New ICMP Types and Codes (RFC7279)
Original Publication Date: 2014-May-01
Included in the Prior Art Database: 2014-May-31
Internet Society Requests For Comment (RFCs)
M. Shore: AUTHOR [+1]
There has been some recent concern expressed about a lack of clarity around when new message types and codes should be added to ICMP (including ICMPv4 [RFC0792] and ICMPv6 [RFC4443]). We lay out a policy regarding when (and when not) to move functionality into ICMP.
Internet Engineering Task Force (IETF) M. Shore Request for Comments: 7279 No Mountain Software BCP: 189 C. Pignataro Category: Best Current Practice Cisco Systems, Inc. ISSN: 2070-1721 May 2014
An Acceptable Use Policy for New ICMP Types and Codes
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.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7279.
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Pignataro Best Current
Practice [Page 1]
RFC 7279 ICMP AUP May 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Acceptable Use Policy . . . . . . . . . . . . . . . . . . . . 2
2.1. Classification of Existing Message Types . . . . . . . . 3
2.1.1. ICMP Use as a Routing Protocol . . . . . . . . . . . 6
2.1.2. A Few Notes on RPL . . . . . . . ...