Formally Deprecating Some ICMPv4 Message Types
RFC 6918
Document | Type |
RFC - Proposed Standard
(April 2013; No errata)
Obsoletes RFC 1788
Was draft-gp-obsolete-icmp-types-iana (individual in ops area)
|
|
---|---|---|---|
Authors | Fernando Gont , Carlos Pignataro | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6918 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ron Bonica | ||
IESG note | Joel Halpern (jmh@joelhalpern.com) is the Docment Shepherd | ||
Send notices to | jmh@joelhalpern.com |
Internet Engineering Task Force (IETF) F. Gont Request for Comments: 6918 UTN-FRH / SI6 Networks Obsoletes: 1788 C. Pignataro Updates: 792, 950 Cisco Systems Category: Standards Track April 2013 ISSN: 2070-1721 Formally Deprecating Some ICMPv4 Message Types Abstract A number of ICMPv4 message types have become obsolete in practice, but have never been formally deprecated. This document deprecates such ICMPv4 message types, thus cleaning up the corresponding IANA registry. Additionally, it updates RFC 792 and RFC 950, obsoletes RFC 1788, and requests the RFC Editor to change the status of RFC 1788 to Historic. Status of This Memo This is an Internet Standards Track document. 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 Internet Standards 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/rfc6918. Copyright Notice Copyright (c) 2013 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. Gont & Pignataro Standards Track [Page 1] RFC 6918 Deprecating Some ICMPv4 Messages April 2013 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Discussion of Deprecated ICMPv4 Message Types . . . . . . . . . 3 2.1. Alternate Host Address (Type 6) . . . . . . . . . . . . . . 3 2.2. Information Request (Type 15) . . . . . . . . . . . . . . . 3 2.3. Information Reply (Type 16) . . . . . . . . . . . . . . . . 3 2.4. Address Mask Request (Type 17) . . . . . . . . . . . . . . 3 2.5. Address Mask Reply (Type 18) . . . . . . . . . . . . . . . 3 2.6. Traceroute (Type 30) . . . . . . . . . . . . . . . . . . . 3 2.7. Datagram Conversion Error (Type 31) . . . . . . . . . . . . 4 2.8. Mobile Host Redirect (Type 32) . . . . . . . . . . . . . . 4 2.9. IPv6 Where-Are-You (Type 33) . . . . . . . . . . . . . . . 4 2.10. IPv6 I-Am-Here (Type 34) . . . . . . . . . . . . . . . . . 4 2.11. Mobile Registration Request (Type 35) . . . . . . . . . . . 4 2.12. Mobile Registration Reply (Type 36) . . . . . . . . . . . . 4 2.13. Domain Name Request (Type 37) . . . . . . . . . . . . . . . 4 2.14. Domain Name Reply (Type 38) . . . . . . . . . . . . . . . . 5 2.15. SKIP (Type 39) . . . . . . . . . . . . . . . . . . . . . . 5 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. Changing the Status of RFC 1788 to Historic . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 1. Introduction A number of ICMPv4 [RFC0792] message types have been specified over the years. A number of these message types have become obsolete in practice, but have never been formally deprecated. This document deprecates such ICMPv4 message types, "cleaning up" the corresponding IANA registry. Additionally, it updates RFC 792 and RFC 950, obsoletes RFC 1788, and requests the RFC Editor to change the status of RFC 1788 to Historic. Section 2 discusses each of the obsoleted ICMPv4 messages. Section 4 requests the RFC Editor to change the status of RFC 1788 to Historic. Gont & Pignataro Standards Track [Page 2] RFC 6918 Deprecating Some ICMPv4 Messages April 2013 2. Discussion of Deprecated ICMPv4 Message Types The following subsections discuss the details of those ICMPv4 message types being deprecated, based on publicly available informationShow full document text