metasystema.org
ObsoletedEXPERIMENTALIETF stream

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

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

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

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

This document describes a network-layer-based protocol that enables separation of IP addresses into two new numbering spaces: Endpoint Identifiers (EIDs) and Routing Locators (RLOCs). No changes are required to either host protocol stacks or to the "core" of the Internet infrastructure. The Locator/ID Separation Protocol (LISP) can be incrementally deployed, without a "flag day", and offers Traffic Engineering, multihoming, and mobility benefits to early adopters, even when there are relatively few LISP-capable sites. Design and development of LISP was largely motivated by the problem statement produced by the October 2006 IAB Routing and Addressing Workshop. This document defines an Experimental Protocol for the Internet community.

Document record

Document ID
RFC6830
Published
January 2013
Authors
D. Farinacci; V. Fuller; D. Meyer; D. Lewis
Status
EXPERIMENTAL
Stream
IETF
Area
rtg
Pages
75
Also known as
—
Obsoleted by:
RFC 9300, RFC 9301
Updated by:
RFC 8113

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

3 later RFCs formally update or obsolete 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/6830-the-locator-id-separation-protocol-lisp