Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type Allocations
obsoletes
- rfc-8113 — Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
Extracted elements (9)
A single shared LISP extension message type (code 15) with sub-types was introduced because the LISP packet type space is limited and experiments for new extensions should not consume a dedicated codepoint for each extension. Sub-types uniquely identify each extension making use of the shared message type.
The sub-type range 0-1023 is provisioned via Standards Action specifically to anticipate exhaustion of the LISP Packet Types codepoint space, while 1024-4095 is available on a lighter-weight FCFS basis for experimentation.
This document obsoletes RFC 8113, changing the status of the shared extension mechanism from Experimental to Standards Track. IANA registries previously referencing RFC 8113 have been updated to reference RFC 9304.
The Sub-type field conveys a unique identifier that MUST be registered with IANA.
The Type field in the LISP Shared Extension Message MUST be set to 15.
The 'LISP Packet Types' registry covers codes 0-15, assigned via Standards Action. Code 15 is reserved for the LISP Shared Extension Message as defined in this document (obsoleting RFC 8113).
The 'LISP Shared Extension Message Type Sub-types' registry is created with values 0-1023 assigned via Standards Action and values 1024-4095 assigned on a First Come, First Served basis. Registrants must provide a desired codepoint and a point of contact.
This document does not introduce any additional security issues beyond those discussed in the LISP Control Plane specification (RFC 9301).
The LISP Shared Extension Message has a 4-bit Type field set to 15, followed by a 12-bit Sub-type field, and a variable-length extension-specific portion. The exact structure of the extension-specific portion is defined in the corresponding extension specification.