Re: [lisp] LISP minutes - IETF 117 San Francisco

[Alvaro Retana <[e-mail]>]

Sharon:

Hi!

My comment was in the context of the proposed update to rfc7215, and not
specific to nexagon (or any other draft).

Sorry if that wasn’t clear in the minutes.

Alvaro.

On August 9, 2023 at 1:15:22 AM, Sharon Barkai (
sharon.barkai=[e-mail]) wrote:



“Alvaro: It would be nice to have a document that gives ideas and talk
about deployment model or scenarios. Versus having documents from the WG on
how to use LISP on datacenters, satellites, cars, airplanes, etc. Those
documents don't change LISP, they tell you how to use it. If that is what
the WG is going to work on, make sure you say that.”


I would like to comment on lisp-nexagon in this context of the lisp
applicability discussion as it did come up according to the minutes,
unfortunately i could not travel or attend remotely.


1. The draft is not about LISP-based connectivity for boats, cars, or
airplanes, and this framing flattens the discussion.

2. Rather, it is about distributed computation, placing the LISP network at
its core due to interoperable AI federation by EIDs.

3. The geo-language model used assigns trafficability/mobility attributes
to EID addressable geo-tile objects. EID objects consolidate raw data to
generate contextual EID prompt feeds.

4. Unlike traditional mapping, which assigns geo-coordinates to
human-comprehensible objects, this mapping network is geared for real-time
machine (AI segmentation) -to-machine (AI navigation) network.

5. Such use case examples are prominent in newly formed routing area work
groups due to an emerging need for compute (AI)-aware networking, but
clearly, not enough is understood about the existing LISP qualities in this
context.

6. As a workgroup, we can add value not just by adding new headers to the
base protocol but also by including select examples of its usefulness in
decentralized reuse of resources, as per the IETF mission statement. Which
is why the draft was adopted to moved to publication.

7. lisp-nexagon, specifically, serves as a basis for automotive geolocation
specifications and drive planning. It has now also being adopted to enhance
Wildland Urban Interface (WUI)* disaster recovery.

* When trafficability/mobility attributes per tile change abruptly (due to
fires, blizzards, floods, earthquakes, or war zones), the LISP M2M mapping
network provides value by consolidating SAT, SAR, Drone, and Responders'
footage in near real time.

Im hopeful the WG will continue to add constructive networking value in the
IETF as it has, more so now that the base protocol is standard track.
Tremendous progress.

--szb
Cell: +972.53.2470068
WhatsApp: [phone]

On Aug 7, 2023, at 13:58, Alberto Rodriguez-Natal (natal) <natal=
[e-mail]> wrote:



Hi all,



The minutes from the LISP meeting in San Francisco are now available.



https://datatracker.ietf.org/doc/minutes-117-lisp/



Let us know if there is anything that should be fixed.



Thanks!

Alberto


_______________________________________________
lisp mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
lisp mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/lisp