metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9301: Locator/ID Separation Protocol (LISP) Control Plane

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9301
Published
October 2022
Authors
D. Farinacci; F. Maino; V. Fuller; A. Cabellos
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
42
Also known as
—
Obsoletes:
RFC 6830, RFC 6833

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 6830 (2013)
  2. RFC 6833 (2013)
  3. RFC 9300 (2022)
  4. RFC 9301 (2022)

Read the full history of Locator/ID Separation Protocol (LISP) Control Plane →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9301-locator-id-separation-protocol-lisp-control-plane