Skip to main content

The Locator/ID Separation Protocol (LISP)
RFC 6830

Revision differences

Document history

Date By Action
2021-09-10
Jenny Bui Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 6830 and RFC 6833
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document describes a network-layer-based protocol that enables separation of IP addresses into two new numbering …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from lisp-chairs@ietf.org, draft-ietf-lisp@ietf.org to (None)
2014-09-19
(System) Posted related IPR disclosure: Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 6830
2013-06-26
(System) IANA registries were updated to include RFC6830
2013-01-25
(System) RFC published