RFC 8111: Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)
In plain English — editorial summary, not part of the RFC
This document describes the Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT), a hierarchical distributed database that embodies the delegation of authority to provide mappings from LISP Endpoint Identifiers (EIDs) to Routing Locators (RLOCs). It is a statically defined distribution of the EID namespace among a set of LISP-speaking servers called "DDT nodes". Each DDT node is configured as "authoritative" for one or more EID-prefixes, along with the set of RLOCs for Map-Servers or "child" DDT nodes to which more-specific EID-prefixes are delegated.
Document record
- Document ID
- RFC8111
- Published
- May 2017
- Authors
- V. Fuller; D. Lewis; V. Ermagan; A. Jain; A. Smirnov
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8378Signal-Free Locator/ID Separation Protocol (LISP) MulticastCurrent
May 2018
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
- RFC 9299An Architectural Introduction to the Locator/ID Separation Protocol (LISP)Current
October 2022
- RFC 9303Locator/ID Separation Protocol Security (LISP-SEC)Current
October 2022
- RFC 9306Vendor-Specific LISP Canonical Address Format (LCAF)Current
October 2022
- RFC 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- RFC 8047Host Multihoming with the Host Identity ProtocolCurrent
February 2017
- RFC 8046Host Mobility with the Host Identity ProtocolCurrent
February 2017
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?