ObsoletedEXPERIMENTALIETF stream

RFC 6833: Locator/ID Separation Protocol (LISP) Map-Server Interface

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9301.

Current document in this lineage: RFC 9300The Locator/ID Separation Protocol (LISP); RFC 9301Locator/ID Separation Protocol (LISP) Control Plane

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

This document describes the Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two new types of LISP- speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provides a simplified "front end" for one or more Endpoint ID to Routing Locator mapping databases. By using this service interface and communicating with Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers and Egress Tunnel Routers are not dependent on the details of mapping database systems, which facilitates experimentation with different database designs. Since these devices implement the "edge" of the LISP infrastructure, connect directly to LISP-capable Internet end sites, and comprise the bulk of LISP-speaking devices, reducing their implementation and operational complexity should also reduce the overall cost and effort of deploying LISP. This document defines an Experimental Protocol for the Internet community.

Document record

Document ID
RFC6833
Published
January 2013
Authors
V. Fuller; D. Farinacci
Status
EXPERIMENTAL
Stream
IETF
Area
rtg
Pages
13
Also known as
Obsoleted by:
RFC 9301

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

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/6833-locator-id-separation-protocol-lisp-map-server-interface