RFC 8113: Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9304.
Current version: 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. It also defines a registry for LISP Packet Type allocations, thus updating RFC 6830.
Document record
- Document ID
- RFC8113
- Published
- March 2017
- Authors
- M. Boucadair; C. Jacquenet
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8111Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)Current
May 2017
- RFC 8116Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
May 2017
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 8102Remote-LFA Node Protection and ManageabilityCurrent
March 2017
- RFC 8099OSPF Topology-Transparent ZoneCurrent
February 2017
- RFC 8097BGP Prefix Origin Validation State Extended CommunityCurrent
March 2017
- RFC 8131RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource SharingCurrent
March 2017
- RFC 8093Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243Current
February 2017
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?