RFC 6836: Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)
In plain English — editorial summary, not part of the RFC
This document describes a simple distributed index system to be used by a Locator/ID Separation Protocol (LISP) Ingress Tunnel Router (ITR) or Map-Resolver (MR) to find the Egress Tunnel Router (ETR) that holds the mapping information for a particular Endpoint Identifier (EID). The MR can then query that ETR to obtain the actual mapping information, which consists of a list of Routing Locators (RLOCs) for the EID. Termed the Alternative Logical Topology (ALT), the index is built as an overlay network on the public Internet using the Border Gateway Protocol (BGP) and Generic Routing Encapsulation (GRE). This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6836
- Published
- January 2013
- Authors
- V. Fuller; D. Farinacci; D. Meyer; D. Lewis
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6835The Locator/ID Separation Protocol Internet Groper (LIG)Current
January 2013
- RFC 6834Locator/ID Separation Protocol (LISP) Map-VersioningObsoleted
January 2013
- RFC 6833Locator/ID Separation Protocol (LISP) Map-Server InterfaceObsoleted
January 2013
- RFC 6832Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP SitesCurrent
January 2013
- RFC 6831The Locator/ID Separation Protocol (LISP) for Multicast EnvironmentsCurrent
January 2013
- RFC 6830The Locator/ID Separation Protocol (LISP)Obsoleted
January 2013
- RFC 6829Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6Obsoleted
January 2013
- RFC 6827Automatically Switched Optical Network (ASON) Routing for OSPFv2 ProtocolsCurrent
January 2013
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?