Internet Engineering Task Force (IETF) M. Boucadair Request for Comments: 8113 C. Jacquenet Updates: 6830 Orange Category: Experimental March 2017 ISSN: 2070-1721
Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
This document specifies a Locator/ID Separation Protocol (LISP) shared message type for defining future extensions and conducting experiments without consuming a LISP packet type codepoint for each extension. It also defines a registry for LISP Packet Type allocations, thus updating RFC 6830.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
This document defines an Experimental Protocol for the Internet community. 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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
Copyright (c) 2017 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.
The Locator/ID Separation Protocol (LISP) base specification, [RFC6830], defines a set of primitives that are identified with a packet type code. Several extensions have been proposed to add more LISP functionalities. For example, new message types are proposed in [LISP-DDT], [LISP-MN-EXT], [LISP-BULK], [NAT-LISP], or [LISP-SUBSCRIBE]. It is expected that additional LISP extensions will be proposed in the future.
In order to ease the tracking of LISP message types, this document proposes to create a "LISP Packet Types" IANA registry (see Section 5).
Because of the limited type space [RFC6830] and the need to conduct experiments to assess new LISP extensions, this document specifies a shared LISP extension message type and proposes a procedure for registering LISP shared extension sub-types (see Section 3).
Boucadair & Jacquenet Experimental [Page 2]
RFC 8113 LISP Packet Type Allocations March 2017
Concretely, one single LISP message type code is dedicated to future LISP extensions; sub-types are used to uniquely identify a given LISP extension making use of the shared LISP extension message type. These identifiers are selected by the author(s) of the corresponding LISP specification that introduces a new LISP extension message type.
The values in the ranges 5-7 and 9-14 can be assigned via Standards Action [RFC5226]. Documents that request for a new LISP packet type may indicate a preferred value in the corresponding IANA sections.
IANA has created the "LISP Shared Extension Message Type Sub-types" registry. No initial values are assigned at the creation of the registry; (0-4095) are available for future assignments.
The values in the range 0-1023 are assigned via Standards Action. This range is provisioned to anticipate, in particular, the exhaustion of the LISP Packet types.
The values in the range 1024-4095 are assigned on a First Come, First Served (FCFS) basis. The registration procedure should provide IANA with the desired codepoint and a point of contact; providing a short description (together with an acronym, if relevant) of the foreseen usage of the extension message is also encouraged.