<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.farinacci-lisp-rfc6830bis" target="https://datatracker.ietf.org/doc/html/draft-farinacci-lisp-rfc6830bis-00">
   <front>
      <title>The Locator/ID Separation Protocol (LISP)</title>
      <author initials="D." surname="Farinacci" fullname="Dino Farinacci">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="V." surname="Fuller" fullname="Vince Fuller">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Meyer" fullname="David Meyer">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Lewis" fullname="Darrel Lewis">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Cabellos-Aparicio" fullname="Albert Cabellos-Aparicio">
         <organization>UPC/BarcelonaTech</organization>
      </author>
      <date month="November" day="13" year="2016" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-farinacci-lisp-rfc6830bis-00" />
   
</reference>
