%% You should probably cite draft-ietf-lisp-rfc6830bis instead of this I-D.
@techreport{farinacci-lisp-rfc6830bis-00,
    number =    {draft-farinacci-lisp-rfc6830bis-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6830bis/00/},
    author =    {Dino Farinacci and Vince Fuller and David Meyer and Darrel Lewis and Albert Cabellos-Aparicio},
    title =     {{The Locator/ID Separation Protocol (LISP)}},
    pagetotal = 52,
    year =      2016,
    month =     nov,
    day =       13,
    abstract =  {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.},
}