RFC 9305: Locator/ID Separation Protocol (LISP) Generic Protocol Extension
In plain English — editorial summary, not part of the RFC
This document describes extensions to the Locator/ID Separation Protocol (LISP) data plane, via changes to the LISP header, to support multiprotocol encapsulation and allow the introduction of new protocol capabilities.
Document record
- Document ID
- RFC9305
- Published
- October 2022
- Authors
- F. Maino; J. Lemon; P. Agarwal; D. Lewis; M. Smith
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6454The Web Origin ConceptCurrent
December 2011
- RFC 5698Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)Current
November 2009
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 9055Deterministic Networking (DetNet) Security ConsiderationsCurrent
June 2021
- RFC 9005Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)Current
March 2021
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
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?