Locator/ID Separation Protocol (LISP) Control-Plane
draft-farinacci-lisp-rfc6833bis-00

Document Type Replaced Internet-Draft (individual)
Last updated 2016-11-13
Replaced by draft-ietf-lisp-rfc6833bis
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-lisp-rfc6833bis
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
https://www.ietf.org/archive/id/draft-farinacci-lisp-rfc6833bis-00.txt

Abstract

This document describes the Control-Plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two new types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provides a simplified "front end" for one or more Endpoint ID to Routing Locator mapping databases. By using this control-plane service interface and communicating with Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) are not dependent on the details of mapping database systems, which facilitates experimentation with different database designs. Since these devices implement the "edge" of the LISP infrastructure, connect directly to LISP-capable Internet end sites, and comprise the bulk of LISP-speaking devices, reducing their implementation and operational complexity should also reduce the overall cost and effort of deploying LISP.

Authors

Vince Fuller (vaf@vaf.net)
Dino Farinacci (farinacci@gmail.com)
Albert Cabellos-Aparicio (acabello@ac.upc.edu)

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