RFC 9304: Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type Allocations
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9304
- Published
- October 2022
- Authors
- M. Boucadair; C. Jacquenet
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Obsoletes:
- RFC 8113
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9184BGP Extended Community Registries UpdateCurrent
January 2022
- RFC 9029Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters RegistriesObsoleted
June 2021
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 6491Resource Public Key Infrastructure (RPKI) Objects Issued by IANACurrent
February 2012
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 6166A Registry for PIM Message TypesObsoleted
April 2011
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
- RFC 9371Registration Procedures for Private Enterprise Numbers (PENs)Current
March 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?