Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

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  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9301

Discuss this RFC: Send questions or comments to the mailing listiesg@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 theLocator/ID Separation Protocol (LISP), implemented by two types ofLISP-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 withMap-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) andEgress Tunnel Routers (ETRs) are not dependent on the details ofmapping database systems; this behavior facilitates modularity withdifferent database designs. Since these devices implement the "edge"of the LISP control plane infrastructure, connecting EID addressablenodes of a LISP site, the implementation and operational complexityof the overall cost and effort of deploying LISP is reduced.

This document obsoletes RFCs 6830 and 6833.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.