%% You should probably cite draft-ietf-lisp-nexagon-52 instead of this revision.
@techreport{ietf-lisp-nexagon-50,
    number =    {draft-ietf-lisp-nexagon-50},
    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-nexagon/50/},
    author =    {Sharon Barkai and Bruno Fernandez-Ruiz and Rotem Tamir and Alberto Rodriguez-Natal and Fabio Maino and Albert Cabellos-Aparicio and Jordi Paillisse and Dino Farinacci},
    title =     {{Network-Hexagons:Geolocation Mobility Network Based On H3 and LISP}},
    pagetotal = 32,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This specification describes the use of the Locator/ID Separation Protocol (LISP) for network virtualization overlays (NVO) that support mobility geolocation network functions. Distributed network functions are anchored by logically addressable geolocation agents, which are distributed between the automotive-edge and vehicular far-edge agents. Geolocation agents' endpoint identifiers (EID) are determined by the H3 hexagonal grid jurisdiction and the functions they anchor. Geolocation agents consolidate, delegate, federate, and propagate information and logic to and from in-vehicle agents. In-vehicle agents' EIDs are ephemeral to protect the vehicle owner's geo-privacy while interacting with geolocation agents. In-vehicle agents' EIDs are obtained and renewed through an authorization, authentication, and accounting procedure (AAA). Geolocation functions include mapping, training, and notification prompts using an H3-based key-value language and messages. Primary functions are invoked while vehicles are driving, and secondary distributed functions while vehicles are parked use the same LISP network overlay and EID addressing scheme.},
}