%% You should probably cite draft-ietf-lisp-rfc6830bis-27 instead of this revision. @techreport{ietf-lisp-rfc6830bis-21, number = {draft-ietf-lisp-rfc6830bis-21}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6830bis-21}, author = {Dino Farinacci and Vince Fuller and David Meyer and Darrel Lewis and Albert Cabellos-Aparicio}, title = {{The Locator/ID Separation Protocol (LISP)}}, pagetotal = 45, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {This document describes the Data-Plane protocol for the Locator/ID Separation Protocol (LISP). 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. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features. This document obsoletes RFC 6830.}, }