%% You should probably cite draft-ietf-lisp-nexagon-52 instead of this revision.
@techreport{ietf-lisp-nexagon-33,
    number =    {draft-ietf-lisp-nexagon-33},
    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/33/},
    author =    {Sharon Barkai and Bruno Fernandez-Ruiz and Rotem Tamir and Alberto Rodriguez-Natal and Fabio Maino and Albert Cabellos-Aparicio and Dino Farinacci},
    title =     {{Network-Hexagons: Geolocation Mobility Edge Network Based On LISP}},
    pagetotal = 32,
    year =      2022,
    month =     jun,
    day =       16,
    abstract =  {Geolocation-Services aggregate data uploaded from vehicles in edge compute locations and process it to verified, localized, geospatial detection-channels. Channels' updates are used by mobility clients for crowed-sourced dynamic mapping and driving applications. Geolocation Services are broken to shards (areas), each one delegated dynamically to compute locations per road activity. This dynamics combined with clients' IP Anchor dynamics causes coherency, context- switching, geo-privacy, and service continuity key issues. Key issues are resolved using dataflow virtualization, an inline indirection between mobility clients and Geolocation Services. LISP overlay network-virtualization offers a fully distributed dataflow virtualization at the edge networking level. Geolocation mobility-network based on LISP is described in this informational.},
}