LISP Experimental Message & IANA Registry for LISP Packet Type Allocations

The Locator/ID Separation Protocol (LISP, ) base specification 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 , , , , or . 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 ). Because of the limited type space , this document specifies a shared LISP message type for experimentation purposes and proposes a procedure for registering LISP experiment sub-types (see ) that make use of additional LISP capabilities associated with this message type. Concretely, one single LISP message type code is dedicated to experiments; sub-types are used to uniquely identify a given LISP experimental message. These identifiers are selected by the author(s) of the corresponding LISP specification that introduces a new experimental message type.

depicts a common LISP experimental message type. The type field MUST be set to 15 (see ).

The "Sub-type" field conveys a unique identifier that is assigned on a First Come, First Served (FCFS) basis . These identifiers are registered with IANA (see ). The exact structure of the 'experiment-specific' portion of the message is specified in the corresponding specification document.

This document does not introduce any additional security issues other than those discussed in .

IANA is requested to create a new protocol registry for LISP Packet Types, numbered 0-15. The registry must be initially populated with the following values:

The values in the ranges 5-7 and 9-14 can be assigned via Standards Action . Documents that request for a new LISP packet type may indicate a preferred value in the corresponding IANA sections. The value 15 is reserved for Experimental Use .

IANA is requested to create a "LISP Experimental Message Sub-types" registry. Entries are assigned on a 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 experimental message is also encouraged.

This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-009-X. Many thanks to Luigi Iannone and Dino Farinacci for the review.