%% You should probably cite rfc9301 instead of this I-D.
@techreport{ietf-lisp-rfc6833bis-31,
    number =    {draft-ietf-lisp-rfc6833bis-31},
    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/31/},
    author =    {Dino Farinacci and Fabio Maino and Vince Fuller and Albert Cabellos-Aparicio},
    title =     {{Locator/ID Separation Protocol (LISP) Control Plane}},
    pagetotal = 42,
    year =      2022,
    month =     may,
    day =       2,
    abstract =  {This document describes the control plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provide a simplified "front end" for one or more Endpoint IDs (EIDs) 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; this behavior 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, the implementation and operational complexity of the overall cost and effort of deploying LISP is reduced. This document obsoletes RFCs 6830 and 6833.},
}