RFC 9306: Vendor-Specific LISP Canonical Address Format (LCAF)
In plain English — editorial summary, not part of the RFC
This document describes a new Locator/ID Separation Protocol (LISP) Canonical Address Format (LCAF), the Vendor-Specific LCAF. This LCAF enables organizations to have implementation-specific encodings for LCAF addresses. This document updates RFC 8060.
Document record
- Document ID
- RFC9306
- Published
- October 2022
- Authors
- A. Rodriguez-Natal; V. Ermagan; A. Smirnov; V. Ashtaputre; D. Farinacci
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 8060
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2606Reserved Top Level DNS NamesUpdated
June 1999
- RFC 9303Locator/ID Separation Protocol Security (LISP-SEC)Current
October 2022
- RFC 9299An Architectural Introduction to the Locator/ID Separation Protocol (LISP)Current
October 2022
- RFC 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- 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 8061Locator/ID Separation Protocol (LISP) Data-Plane ConfidentialityCurrent
February 2017
- RFC 7898Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE)Current
June 2016
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?