Orange

Rennes 35000 France mohamed.boucadair@orange.com

Orange

Rennes 35000 France christian.jacquenet@orange.com

RTG LISP Shared Experiment Code LISP codepoints Experiment Identifier Experiment ID LISP Experimental Registry LISP Extension Extending LISP Exhausted LISP types LISP IANA IANA 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. This document obsoletes RFC 8113.

Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2022 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
• .  Requirements Language
• .  LISP Shared Extension Message Type
• .  Security Considerations
• .  IANA Considerations
  • .  LISP Packet Types
  • .  Sub-Types
• .  Changes from RFC 8113
• .  Normative References
• Acknowledgments
• Authors' Addresses

Introduction 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. It is expected that additional LISP extensions will be proposed in the future. The "LISP Packet Types" IANA registry (see ) is used to ease the tracking of LISP message types. Because of the limited type space and the need to conduct experiments to assess new LISP extensions, this document specifies a shared LISP extension message type and describes a procedure for registering LISP shared extension sub-types (see ). 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.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

LISP Shared Extension Message Type depicts the common format of the LISP shared extension message. The type field MUST be set to 15 (see ).

LISP Shared Extension Message Type 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=15| Sub-type | extension-specific | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // extension-specific // // // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The 'Sub-type' field conveys a unique identifier that MUST be registered with IANA (see ). The exact structure of the 'extension-specific' portion of the message is specified in the corresponding specification document.

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

IANA Considerations

LISP Packet Types IANA has created a registry titled "LISP Packet Types", numbered 0-15. Values 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. IANA has replaced the reference to RFC 8113 with the RFC number of this document. Also, IANA has updated the table as follows: OLD:

Message	Code	Reference
LISP Shared Extension Message	15	[RFC8113]

NEW:

Message	Code	Reference
LISP Shared Extension Message	15	RFC 9304

Sub-Types IANA has created the "LISP Shared Extension Message Type Sub-types" registry. IANA has updated that registry by replacing the reference to RFC 8113 with the RFC number of this document. 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 is to 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.

Changes from RFC 8113 The following changes were made from RFC 8113:

• Changed the status from Experimental to Standards Track.
• Indicated explicitly that the shared extension is used for two purposes: extend the type space and conduct experiments to assess new LISP extensions.
• Deleted pointers to some examples illustrating how the shared extension message is used to extend the LISP protocol.
• IANA has updated the "IANA LISP Packet Types" and "LISP Shared Extension Message Type Sub-types" registries to point to this document instead of RFC 8113.

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Acknowledgments This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-009-X. Many thanks to , , and for the review. Thanks to , , , and for the review.

Authors' Addresses Orange

Rennes 35000 France mohamed.boucadair@orange.com

Orange

Rennes 35000 France christian.jacquenet@orange.com