RFC 9300

The Locator/ID Separation Protocol (LISP), October 2022

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
PROPOSED STANDARD
Obsoletes:
RFC 6830
Authors:
D. Farinacci
V. Fuller
D. Meyer
D. Lewis
A. Cabellos, Ed.
Stream:
IETF
Source:
lisp (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC9300

Discuss this RFC: Send questions or comments to iesg@ietf.org

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


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search