CurrentPROPOSED STANDARDIETF stream

RFC 9300: The Locator/ID Separation Protocol (LISP)

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

This document describes the data plane protocol for the Locator/ID Separation Protocol (LISP). LISP defines two namespaces: Endpoint Identifiers (EIDs), which identify end hosts; and Routing Locators (RLOCs), which identify network attachment points. With this, LISP effectively separates control from data and allows routers to create overlay networks. LISP-capable routers exchange encapsulated packets according to EID-to-RLOC mappings stored in a local Map-Cache. LISP requires no change to either host protocol stacks or underlay routers and offers Traffic Engineering (TE), multihoming, and mobility, among other features. This document obsoletes RFC 6830.

Document record

Document ID
RFC9300
Published
October 2022
Authors
D. Farinacci; V. Fuller; D. Meyer; D. Lewis; A. Cabellos
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
33
Also known as
Obsoletes:
RFC 6830

Topics

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/9300-the-locator-id-separation-protocol-lisp