Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

The Locator/ID Separation Protocol (LISP)
RFC 9300

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2022-10-20	(System)	Received changes through RFC Editor sync (created alias RFC 9300, changed abstract to 'This document describes the data plane protocol for the Locator/ID Separation … Received changes through RFC Editor sync (created alias RFC 9300, changed abstract to '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.', changed pages to 33, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2022-10-20, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-lisp-rfc6830bis and RFC 6830)
2022-10-20	(System)	RFC published