Internet Draft                                           RJ Atkinson
draft-irtf-rrg-ilnp-icmpv4-00.txt                         Consultant
Expires:  09 JUL 2012                                      SN Bhatti
Category: Experimental                                 U. St Andrews
                                                     January 9, 2012

                 ICMP Locator Update message for ILNPv4

Status of this Memo

   Distribution of this memo is unlimited.

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

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

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before
   November 10, 2008. The person(s) controlling the copyright in
   some of this material may not have granted the IETF Trust the
   right to allow modifications of such material outside the IETF
   Standards Process.  Without obtaining an adequate license from
   the person(s) controlling the copyright in such materials, this
   document may not be modified outside the IETF Standards Process,
   and derivative works of it may not be created outside the IETF
   Standards Process, except to format it for publication as an RFC
   or to translate it into languages other than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other

Atkinson & Bhatti  Expires in 6 months                          [Page 1]

Internet Draft     ILNPv4             09 JAN 2012

   documents at any time. It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in

   The list of current Internet-Drafts can be accessed at

   The list of Internet-Draft Shadow Directories can be accessed at

   This document is not on the IETF standards-track and does not
   specify any level of standard. This document merely provides
   information for the Internet community.

   This document is part of the ILNP document set, which has had
   extensive review within the IRTF Routing Research Group.  ILNP is
   one of the recommendations made by the RG Chairs. Separately,
   various refereed research papers on ILNP have also been published
   during this decade. So the ideas contained herein have had much
   broader review than the IRTF Routing RG. The views in this
   document were considered controversial by the Routing RG, but the
   RG reached a consensus that the document still should be
   published. The Routing RG has had remarkably little consensus on
   anything, so virtually all Routing RG outputs are considered


   This document defines a new ICMP message type for IPv4 that is
   used only with ILNP for IPv4 (ILNPv4).  The Identifier-Locator
   Network Protocol (ILNP) is an experimental, evolutionary
   enhancement to IP.  This document is a product of the IRTF
   Routing RG.

Table of Contents - ### to be updated

     1. Introduction.............................?
     2. ICMP Locator Update message for ILNPv4...?
     3. Security Considerations..................?
     4. IANA Considerations......................?
     5. References...............................?


   The Identifier Locator Network Protocol (ILNP) is an proposal for
   evolving the Internet Architecture.  It differs from the current
   Internet Architecture primarily by deprecating the concept of an

Atkinson & Bhatti  Expires in 6 months                          [Page 2]

Internet Draft     ILNPv4             09 JAN 2012

   IP Address, and instead defining two new objects, each having
   crisp syntax and semantics.  The first new object is the Locator,
   a topology-dependent name for a subnetwork.  The other new object
   is the Identifier, which provides a topology-independent name for
   a node.

1.1  ILNP Document Roadmap

   The ILNP Architecture document [ILNP-ARCH] is the best place to
   start reading about ILNP.  ILNP has multiple instantiations.
   [ILNP-ENG] discusses engineering and implementation aspects
   common to all instances of ILNP.  [ILNP-v4opts] defines two new
   IPv4 options used with ILNPv4.  This document discusses a new
   ICMP for IPv4 message.  [ILNP-DNS] describes new Domain Name
   System (DNS) resource records used with ILNP.  Other documents
   describe ILNP for IPv6 (ILNPv6).

1.2  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   "OPTIONAL" in this document are to be interpreted as described
   in RFC 2119. [RFC-2119]

2.  ICMP Locator Update message for ILNPv4

   As described in [ILNP-ARCH] and [ILNP-ENG], an ILNP for IPv4
   (ILNPv4) node might need to inform correspondent ILNPv4 nodes of
   changes to the set of valid Locator values.  This message
   provides a mechanism to do so.  While it would be architecturally
   identical to perform this function using a new UDP protocol, this
   specification defines a new ICMP message type for such updates.

   The ICMP for IPv4 message described in this section has ICMP Type
   XXX and is used ONLY with a current ILNPv4 session.  This message
   enables an ILNPv4 node to inform ILNPv4 correspondent nodes of
   changes to the active Locator set for the ILNPv4 node that
   originates this message.  This particular ICMP for IPv4 message
   MUST ONLY be used with ILNPv4 communications sessions.

    ICMP Locator Update message

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      |     Type      |     Code      |           Checksum            |

Atkinson & Bhatti  Expires in 6 months                          [Page 3]

Internet Draft     ILNPv4             09 JAN 2012

      |   # Locators  |Addr Entry Size|           Lifetime            |
      |                       Locator [1]                             |
      |        Preference [1]         |           RESERVED            |
      |                       Locator [2]                             |
      |        Preference [2]         |           RESERVED            |
      |                               .                               |
      |                               .                               |
      |                               .                               |

      IP Fields:

         Source Address        An IPv4 address belonging to the node
                               from which this message is sent.

         Destination Address   An IPv4 address belonging to the node
                               to which this message is being sent.

      ICMP Fields:

         Type                  XXX

         Code                  0

         Checksum              The  16-bit one's complement of the one's
                               complement sum of the ICMP message,
                               starting with the ICMP Type.  For
                               computing the checksum, the Checksum
                               field is set to 0.

         # Locators            The number of 32-bit Locator values
                               that are advertised in this message.

         Locator Entry Size    The number of 32-bit words of
                               information per each router address
                               (2, in the version of the protocol
                               described here).

         Lifetime              The maximum number of seconds that the
                               Locators may be considered valid.

Atkinson & Bhatti  Expires in 6 months                          [Page 4]

Internet Draft     ILNPv4             09 JAN 2012

         Locator[i],           The 32-bit Locator values used at present
          i = 1..Num Addrs     by the sending ILNPv4 node.

         Preference[i],        The preferability of each Locator[i],
          i = 1..Num Addrs     relative to other valid Locator[i]
                               values. The Preference numbers here are
                               identical, both in syntax and semantics,
                               to the Preference values for L32 records
                               as specified by [ILNP-DNS].

          RESERVED             A field reserved for possible future
                               use.  At present, the sender MUST
                               initialise this field to zero.
                               Receivers should ignore this field at
                               present.  The field might be used for
                               some protocol function in future.

   All ILNPv4 ICMP Locator Update messages MUST contain a valid
   ILNPv4 Identifier option and MUST contain an ILNPv4 Nonce Option.

   ILNPv4 ICMP Locator Update messages also MAY be protected using
   IP Security for ILNP [ILNP-ENG] [RFC-4301].  Deployments in
   high-threat environments SHOULD also protect ILNPv4 ICMP Locator
   Update messages using IP Security.  While IPsec ESP can protect a
   payload, no form of IPsec ESP is able to protect an IPv4 option
   that appears prior to the ESP header.  Note that even when IP
   Security for ILNP is in use, the ILNP Nonce Option still MUST be
   present.  This simplifies protocol processing, and it also
   means that a receiver can perform the inexpensive check of
   the Nonce value before performing any (potentially expensive)
   cryptographic calculation.


   Security considerations for the overall ILNP Architecture
   are described in [ILNP-ARCH].  Additional common security
   considerations are described in [ILNP-ENG].  This section
   describes security considerations specific to ILNPv4 topics
   discussed in this document.

   If the ILNP Nonce value is predictable, then an off-path attacker
   might be able to forge data or control packets.  This risk also
   is mitigated by the existing common practice of IP Source Address
   filtering [RFC-2827] [RFC-3704].

   IP Security for ILNP [ILNP-ENG] [RFC-4301] provides cryptographic
   protection for ILNP data and control packets. The ILNP Nonce

Atkinson & Bhatti  Expires in 6 months                          [Page 5]

Internet Draft     ILNPv4             09 JAN 2012

   option [ILNP-v4opts] is required as described in Section 3, even
   if IP Security is also in use.  Deployments of ILNPv4 in
   high-threat environments SHOULD use IP Security for additional
   risk reduction.


   IANA is requested to assign a new ICMP Type number for this ICMP
   Locator Update message, replacing XXX above, following the
   procedures in [RFC-2939].

   The ICMP Locator Update message does not use the ICMP Extension
   Structure defined in [RFC-4884].  At present, the only ICMP Code
   valid for this ICMP Type is zero (0), which means "No Code".


   This document has both Normative and Informational

5.1  Normative References

   [ILNP-ARCH]  R. Atkinson and S. Bhatti, "ILNP Architecture",
                draft-irtf-ilnp-arch, January 2012.

   [ILNP-DNS]   R. Atkinson and S. Bhatti, "DNS Resource Records
                for ILNP", draft-irtf-rrg-ilnp-dns, January 2012.

   [ILNP-ENG]   R. Atkinson and S. Bhatti, "ILNP Engineering
                Considerations", draft-irtf-rrg-ilnp-eng,
                January 2012.

   [ILNP-v4opts] R. Atkinson and S. Bhatti, "IPv4 Options for
                ILNPv4", draft-irtf-rrg-ilnp-v4opts,
                January 2012.

   [RFC-2119]  Bradner, S., "Key words for use in RFCs to
               Indicate Requirement Levels", BCP 14, RFC 2119,
               March 1997.

   [RFC-4301]  S. Kent and K. Seo, "Security Architecture for
               the Internet Protocol", RFC-4301, December 2005.

5.2  Informative References

Atkinson & Bhatti  Expires in 6 months                          [Page 6]

Internet Draft     ILNPv4             09 JAN 2012

   [ILNP-Nonce] R. Atkinson and S. Bhatti, "ILNPv6 Nonce
                Destination Option", draft-irtf-rrg-ilnp-noncev6,
                January 2012.

   [ILNP-ICMPv6]  R. Atkinson and S. Bhatti, "ICMP Locator
                Update Message for ILNPv6",
                draft-irtf-rrg-ilnp-icmpv6, January 2012.

   [RFC-2827]  P. Ferguson and D. Senie, "Network Ingress
               Filtering: Defeating Denial of Service Attacks
               which employ IP Source Address Spoofing",
               RFC-2827, May 2000.


   [RFC-3704]  F. Baker and P. Savola, "Ingress Filtering for
               Multihomed Networks", RFC-3704, March 2004.



   Steve Blake, Mohamed Boucadair, Noel Chiappa, Steve Hailes, Joel
   Halpern, Mark Handley, Volker Hilt, Paul Jakma, Dae-Young Kim,
   Tony Li, Yakov Rehkter and Robin Whittle (in alphabetical order)
   provided review and feedback on earlier versions of the ILNP
   documents.  Steve Blake provided an especially thorough review of
   an earlier version of the entire ILNP document set, which was
   extremely helpful.  We also wish to thank the anonymous reviewers
   for their feedback.


   RJ Atkinson
   San Jose, CA
   95125 USA


   SN Bhatti
   School of Computer Science
   University of St Andrews
   North Haugh, St Andrews
   Fife, Scotland
   KY16 9SX, UK


Atkinson & Bhatti  Expires in 6 months                          [Page 7]

Internet Draft     ILNPv4             09 JAN 2012

   Expires: 09 JUL 2012

Atkinson & Bhatti  Expires in 6 months                          [Page 8]