RFC 9299: An Architectural Introduction to the Locator/ID Separation Protocol (LISP)
In plain English — editorial summary, not part of the RFC
This document describes the architecture of the Locator/ID Separation Protocol (LISP), making it easier to read the rest of the LISP specifications and providing a basis for discussion about the details of the LISP protocols. This document is used for introductory purposes; more details can be found in the protocol specifications, RFCs 9300 and 9301.
Document record
- Document ID
- RFC9299
- Published
- October 2022
- Authors
- A. Cabellos; D. Saucez
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9303Locator/ID Separation Protocol Security (LISP-SEC)Current
October 2022
- RFC 9306Vendor-Specific LISP Canonical Address Format (LCAF)Current
October 2022
- RFC 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- RFC 9730Interworking of GMPLS Control and Centralized Controller SystemsCurrent
March 2025
- RFC 10028Updates to Dynamic IPv6 Multicast Address Group IDsCurrent
August 2026
- RFC 8378Signal-Free Locator/ID Separation Protocol (LISP) MulticastCurrent
May 2018
- RFC 8111Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)Current
May 2017
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
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?