RFC 6830

The Locator/ID Separation Protocol (LISP), January 2013

File formats:
icon for text file icon for PDF icon for HTML
Status:
EXPERIMENTAL
Obsoleted by:
RFC 9300, RFC 9301
Updated by:
RFC 8113
Authors:
D. Farinacci
V. Fuller
D. Meyer
D. Lewis
Stream:
IETF
Source:
lisp (int)

Cite this RFC: TXT  |  XML  |   BibTeX

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

Discuss this RFC: Send questions or comments to the mailing list lisp@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 6830


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search