Skip to main content

The Locator/ID Separation Protocol (LISP)
draft-farinacci-lisp-rfc6830bis-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Dino Farinacci , Vince Fuller , David Meyer , Darrel Lewis , Albert Cabellos-Aparicio
Last updated 2016-11-13
Replaced by draft-ietf-lisp-rfc6830bis
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-lisp-rfc6830bis
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This document describes the Locator/ID Separation Protocol (LISP) data-plane encapsulation protocol. LISP defines two namespaces, End- point Identifiers (EIDs) that identify end-hosts and Routing Locators (RLOCs) that 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. The map-cache is populated by the LISP Control-Plane protocol [REF_TO_RFC6833bis]. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features.

Authors

Dino Farinacci
Vince Fuller
David Meyer
Darrel Lewis
Albert Cabellos-Aparicio

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