Formally Deprecating Some ICMPv4 Message Types
draft-gp-obsolete-icmp-types-iana-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-01-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            F. Gont
Internet-Draft                                    UTN-FRH / SI6 Networks
Obsoletes: 1788, 2521                                       C. Pignataro
(if approved)                                              Cisco Systems
Updates: 792, 950 (if approved)                         January 11, 2013
Intended status: Standards Track
Expires: July 15, 2013

             Formally Deprecating Some ICMPv4 Message Types
                  draft-gp-obsolete-icmp-types-iana-00

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 RFC792 and RFC950, and obsoletes
   RFC1788 and RFC2521.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 15, 2013.

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

Gont & Pignataro          Expires July 15, 2013                 [Page 1]
Internet-Draft      Deprecating Some ICMPv4 Messages        January 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   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)  . . . . . . . . . . . . . . . . . . . 4
     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) . . . . . . . . . . . . . . . 5
     2.14. Domain Name Reply (Type 38) . . . . . . . . . . . . . . . . 5
     2.15. SKIP (Type 39)  . . . . . . . . . . . . . . . . . . . . . . 5
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   4.  Changing the status of the corresponding RFCs . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Gont & Pignataro          Expires July 15, 2013                 [Page 2]
Internet-Draft      Deprecating Some ICMPv4 Messages        January 2013

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.

   Section 4 obsoletes some of the corresponding RFCs and requests the
   RFC Editor to change their status to "Historic".

2.  Discussion of Deprecated ICMPv4 Message Types

   The following subsections discuss the details of those ICMPv4 message
Show full document text