Re: [lisp] New Version Notification for draft-barkai-lisp-nexagon-03.txt

Sharon <sbarkai@gmail.com> Tue, 07 May 2019 10:28 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
In-Reply-To: <155721347060.29379.12962871324532678805.idtracker@ietfa.amsl.com>
Date: Tue, 07 May 2019 13:28:14 +0300
Cc: Alberto Rodriguez-Natal <natal@cisco.com>, Ohad Serfaty <sharon@fermicloud.io>, Dino Farinacci <farinacci@gmail.com>, Albert Cabellos-Aparicio <acabello@ac.upc.edu>, Bruno Fernandez-Ruiz <b@getnexar.com>, Fabio Maino <fmaino@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <91EB242D-FCA9-4246-9858-F779DF50B34A@gmail.com>
References: <155721347060.29379.12962871324532678805.idtracker@ietfa.amsl.com>
To: lisp@ietf.org, lisp-chairs@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/hTJpZI8IFy7gOA0kwirUzwBK1Ow>
Subject: Re: [lisp] New Version Notification for draft-barkai-lisp-nexagon-03.txt
Precedence: list

Dear lispers, chairs,

As outlined in 104 with draft-lisp-nexagon-00,
There is clear need in the industry for a mobility networks standard. Between the layer2 squabbles of who will operate the RF towers, LTE/5G carriers  or municipal Wifi, and the rigid layer1-7 DSRC specs taken from a playbook from the 50s, there is no clear way to share even the simplest annotation between cars, one that saw the problem but drove away, and one driving straight into it blind.

We put forth an H3-LISP based connectionless pure layer4 proposal, based on shared states of road-tiles, indexed-addressed using H3 HIDs, routed by LISP as EIDs. We leverage LISP connectionless indirection, and, the natural LISP map-assisted duality of indexing-addressing fully. 

The goal is to out  forth a proposal which - app vendors, vision-sensor-liadr vendors, car oem, cloud and network providers, gov and muni .. can finally refer to when targeting the value of having a mobility network layered on whatever access.

We've been working hard iterating the network hexagons H3-LISP draft since 104, and, Dino and the team feel we are far enough along (draft-03) to turn to a work group draft status. 

Hopefully we can hear what the workgroup thinks about it, so we can anticipate the timeline by which we can address the market need for a layered open standard. 
Thank you in advance for your consideration,
meanwhile we will continue working it.

All the best,
Sharon 

--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On May 7, 2019, at 10:17 AM, internet-drafts@ietf.org wrote:
> 
> 
> A new version of I-D, draft-barkai-lisp-nexagon-03.txt
> has been successfully submitted by Sharon Barkai and posted to the
> IETF repository.
> 
> Name:        draft-barkai-lisp-nexagon
> Revision:    03
> Title:        Network-Hexagons, an H3-LISP Based Mobility Network
> Document date:    2019-05-04
> Group:        Individual Submission
> Pages:        12
> URL:            https://www.ietf.org/internet-drafts/draft-barkai-lisp-nexagon-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-barkai-lisp-nexagon/
> Htmlized:       https://tools.ietf.org/html/draft-barkai-lisp-nexagon-03
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-barkai-lisp-nexagon
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-barkai-lisp-nexagon-03
> 
> Abstract:
>   This document specifies combined use of H3 and LISP for mobility-networks:
>   - Enabling real-time tile-by-tile localized-annotation of road-conditions
>   - Sharing of road annotations: hazards, blockages, maintenance, furniture
>   - Between MobilityClients producing and consuming road-state information
>   - Using in-network tile-state addressable-indexed-maintained in H3Servers.
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>

Re: [lisp] New Version Notification for draft-bar… Sharon