Intended status: Standards Track
draft-eromenko-ipff-icmp-04

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
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)
INTERNET-DRAFT
"Internet Protocol Five Fields - Internet Control Message Protocol", 
Alexey Eromenko, 2016-09-29,
<draft-eromenko-ipff-icmp-04.txt>
expiration date: 2017-03-29

Intended status: Standards Track

                                                              A.Eromenko
                                                          September 2016

                   INTERNET CONTROL MESSAGE PROTOCOL v5
           (for Internet Protocol "Five Fields", aka IPFF-ICMPv5)

                         PROTOCOL SPECIFICATION draft

Abstract

   This document describes the format of a set of control messages used
   in ICMPv5 (Internet Control Message Protocol).  ICMPv5 is the
   Internet Control Message Protocol for Internet Protocol Five Fields
   (IPFF).

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."

Copyright Notice

   Copyright (c) 2015 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.

Summary of Message Types

Error messages:
    1  Destination Unreachable
    2  Packet Too Big
    3  Hops Exceeded
    4  Parameter Problem
    5  Redirect

Other messages:
  128  Echo Request
  129  Echo Reply

Introduction

   The Internet Protocol (IP) is used for host-to-host packet
   service in a system of interconnected networks called the
   Internet.  The network connecting devices are called Routers.
   These routers communicate between themselves for control purposes
   via various routing protocols.  Occasionally a
   router or destination host will communicate with a source host, for
   example, to report an error in packet processing.  For such
   purposes this protocol, the Internet Control Message Protocol (ICMP),
   is used.  ICMP, uses the basic support of IP as if it were a higher
   level protocol, however, ICMP is actually an integral part of IP, and
   must be implemented by every IP module.

   ICMP messages are sent in several situations:  for example, when a
   packet cannot reach its destination, and when the router
   can direct the host to send traffic on a shorter route.

   The Internet Protocol is not designed to be absolutely reliable.  The
   purpose of these control messages is to provide feedback about
   problems in the communication environment, not to make IP reliable.
   There are still no guarantees that a packet will be delivered or a
   control message will be returned.  Some packets may still be
   undelivered without any report of their loss.  The higher level
   protocols that use IP must implement their own reliability procedures
   if reliable communication is required.

   The ICMP messages typically report errors in the processing of
   packets.  To avoid the infinite regress of messages about messages
   etc., no ICMP error messages are sent about ICMP error messages.

Message Formats

   ICMP messages are sent using the basic IP header.  The first byte of
   the data portion of the packet is a ICMP type field; the value of
   this field determines the format of the remaining data.  Any field
   labeled "unused" is reserved for later extensions and must be zero
   when sent, but receivers should not use these fields (except to
   include them in the checksum).  Unless otherwise noted under the
   individual format descriptions, the values of the internet header
   fields are as follows:

   Version

      5

   Payload Length

      Length of this ICMP header.

   Hops to Live

      Hops to live; as this field is decremented at each
      machine in which the packet is processed, the value in this
      field should be at least as great as the number of routers which
      this packet will traverse.

   Protocol

      ICMP = 1

   Source Address

      The address of the router or host that composes the ICMP message.
Show full document text