%% You should probably cite rfc9301 instead of this I-D. @techreport{ietf-lisp-rfc6833bis-18, number = {draft-ietf-lisp-rfc6833bis-18}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/18/}, author = {Vince Fuller and Dino Farinacci and Albert Cabellos-Aparicio}, title = {{Locator/ID Separation Protocol (LISP) Control-Plane}}, pagetotal = 58, year = , month = , day = , 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 modularity with different database designs. Since these devices implement the "edge" of the LISP Control-Plane infrastructure, connecting EID addressable nodes of a LISP site, their implementation and operational complexity reduces the overall cost and effort of deploying LISP. This document obsoletes RFC 6830 and 6833.}, }