Uberlay Interconnection of Multiple LISP overlays

Document Type Expired Internet-Draft (individual)
Authors Victor Moreno  , Dino Farinacci  , Alberto Rodriguez-Natal  , Marc Portoles-Comeras  , Fabio Maino  , Sanjay Hooda 
Last updated 2021-02-04 (latest revision 2020-08-03)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes the use of the Locator/ID Separation Protocol (LISP) to interconnect multiple disparate and independent network overlays by using a transit overlay. The transit overlay is referred to as the "uberlay" and provides connectivity and control plane abstraction between different overlays. Each network overlay may use different control and data plane approaches and may be managed by a different organization. Structuring the network into multiple network overlays enables the interworking of different overlay approaches to data and control plane methods. The different network overlays are autonomous from a control and data plane perspective, this in turn enables failure survivability across overlay domains. This document specifies the mechanisms and procedures for the distribution of control plane information across overlay sites and in the uberlay as well as the lookup and forwarding procedures for unicast and multicast traffic within and across overlays. The specification also defines the procedures to support inter-overlay mobility of EIDs and their integration with the intra-overlay EID mobility procedures defined in draft-ietf-lisp-eid-mobility.


Victor Moreno (vimoreno@cisco.com)
Dino Farinacci (farinacci@gmail.com)
Alberto Rodriguez-Natal (natal@cisco.com)
Marc Portoles-Comeras (mportole@cisco.com)
Fabio Maino (fmaino@cisco.com)
Sanjay Hooda (shooda@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)