RFC 9301

Locator/ID Separation Protocol (LISP) Control Plane, October 2022

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
PROPOSED STANDARD
Obsoletes:
RFC 6830, RFC 6833
Authors:
D. Farinacci
F. Maino
V. Fuller
A. Cabellos, Ed.
Stream:
IETF
Source:
lisp (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC9301

Discuss this RFC: Send questions or comments to iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9301


Abstract

This document describes the control plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provide a simplified "front end" for one or more Endpoint IDs (EIDs) to Routing Locator mapping databases.

By using this control plane service interface and communicating with Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) are not dependent on the details of mapping database systems; this behavior facilitates modularity with different database designs. Since these devices implement the "edge" of the LISP control plane infrastructure, connecting EID addressable nodes of a LISP site, the implementation and operational complexity of the overall cost and effort of deploying LISP is reduced.

This document obsoletes RFCs 6830 and 6833.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search