Sharon, just an FYI, get ready to change occurences of RFC6830 to RFC9300.

Dino

> On Sep 29, 2022, at 4:20 AM, Sharon Barkai 
> <sharon.barkai=40getnexar....@dmarc.ietf.org> wrote:
> 
>  HID LCAF spec corrected per comments ..
> 
> In a picture: The economical benefits of LISP application routing,
> managing own client/service compute location elasticity/mobility/continuity,
> makes new applications economically viable.
> 
> <PastedGraphic-5.png>
> 
> 
> 
>> On Sep 29, 2022, at 13:48, internet-dra...@ietf.org wrote:
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the Locator/ID Separation Protocol WG of the 
>> IETF.
>> 
>>        Title           : Network-Hexagons:Geolocation Mobility Edge Network 
>> Based On H3 and LISP
>>        Authors         : Sharon Barkai
>>                          Bruno Fernandez-Ruiz
>>                          Rotem Tamir
>>                          Alberto Rodriguez-Natal
>>                          Fabio Maino
>>                          Albert Cabellos-Aparicio
>>                          Dino Farinacci
>>  Filename        : draft-ietf-lisp-nexagon-41.txt
>>  Pages           : 31
>>  Date            : 2022-09-29
>> 
>> Abstract:
>>  This document uses virtual layer3 routing and geospatial addressing
>>  based on a hierarchical grid forming a Geolocation mobility-edge
>>  network. When vehicles with AI cameras detect objects of interest
>>  on the road, they use their GPS to calculate their high-resolution
>>  grid-tile position. Then they use this tile to calculate the
>>  high-resolution tile of the detection. A low-resolution tile which
>>  contains the detection-tile identifies a network-addressable object.
>>  The object tile-ID is used as basis for IPv6 endpoint identifier(EID).
>>  Geospatial EIDs are queue-destination and channel-source of objects.
>>  Geolocation objects consolidate detections form all vehicles in a
>>  given area. Geolocation objects based on EID queues and channels are
>>  network portable via the Locator/ID Separation Protocol (LISP).
>> 
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-lisp-nexagon/
>> 
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-lisp-nexagon-41
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-nexagon-41
>> 
>> 
>> Internet-Drafts are also available by rsync at 
>> rsync.ietf.org::internet-drafts
>> 
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to