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

Sharon Barkai <sharon.barkai@getnexar.com> Wed, 09 August 2023 05:15 UTC

Return-Path: <sharon.barkai@getnexar.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1854C15108D for <lisp@ietfa.amsl.com>; Tue, 8 Aug 2023 22:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=getnexar.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpplyGqZTEaY for <lisp@ietfa.amsl.com>; Tue, 8 Aug 2023 22:15:12 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98559C14CE51 for <lisp@ietf.org>; Tue, 8 Aug 2023 22:15:12 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-99c10ba30afso108182566b.1 for <lisp@ietf.org>; Tue, 08 Aug 2023 22:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; t=1691558111; x=1692162911; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=MnLWUpepJaZF1MG//zcsoj527R4jGV/hr6t9WeUjhXE=; b=WGt5FxLYTYmxxwbOu1ysKe3hffHgwueNX59kDLFQsTpePXV3J9mQiJq30uJyp7oPAY en2NTCxbkOtn0EyYEhEqTrATot1OTBvos7RwiFlynOZsUfdjf7v0GmgxUb/F168M3wV+ vBHGodVsXiO3zLMAf/WaAH/Kq0AZHy4XqBc1U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691558111; x=1692162911; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=MnLWUpepJaZF1MG//zcsoj527R4jGV/hr6t9WeUjhXE=; b=ilYUhFO7mIZWy/2C7eeOwLgtbQpQwq4tmWOHnLKap3Rbp994FnC5/p+DeKoCKAW1wn SJNWqGtoNE3JhlGcJ3/THADlnIoCtfHYWUburYo6Uj4K3WNMkTHL6NgTa5LjdYihckz0 pW6PU2WEiru86/AlaCOuWlzDFZV8tlZEjpkGQsoZTststHl00gB5YahXukhBhw+rOAub ccfd3NQpHg+pknmS22LC+Fs9v0RNXX7nhmWLCvU2RkvWii9Ld1jrm8OP4L+wVRUkn0E+ 76HewNGcA3JciSswK0qFn1AR2o+p9fbbmLdz72q6fvymloCXiebBTWIc9xpWc/9y3kpY JUVw==
X-Gm-Message-State: AOJu0Yy0skdvTrnfhWQ6Kct1PfcX6LFZmebx3fA7LjoVk1NLKTKbjqpK EkcJOJXvGWrFHY0ZCgqkTl53bTqVBkqZ0jkDXqw=
X-Google-Smtp-Source: AGHT+IG+0C+ZKb1L+GM4bFvXMWXD2BMXmMmzIHYNCLRdJA+cgDYtS6ck2VIk/3UaBGMjxHK3hKpxvQ==
X-Received: by 2002:a17:907:168a:b0:99b:f42d:b3f6 with SMTP id hc10-20020a170907168a00b0099bf42db3f6mr14503399ejc.32.1691558110528; Tue, 08 Aug 2023 22:15:10 -0700 (PDT)
Received: from smtpclient.apple ([46.120.75.84]) by smtp.gmail.com with ESMTPSA id m5-20020a1709061ec500b0098dfec235ccsm7442525ejj.47.2023.08.08.22.15.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Aug 2023 22:15:10 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-358123BE-017C-468F-88A8-59E21AF1FD5C"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Sharon Barkai <sharon.barkai@getnexar.com>
In-Reply-To: <BYAPR11MB3591993A2C2F32EF73C277DCB60CA@BYAPR11MB3591.namprd11.prod.outlook.com>
Date: Wed, 09 Aug 2023 08:15:06 +0300
Cc: lisp@ietf.org, lisp-chairs@ietf.org
Message-Id: <2F5022FB-C8F9-4BBB-9291-7C6DE78E5321@getnexar.com>
References: <BYAPR11MB3591993A2C2F32EF73C277DCB60CA@BYAPR11MB3591.namprd11.prod.outlook.com>
To: "Alberto Rodriguez-Natal (natal)" <natal=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (20G75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/6242Co8PaZTTAIy6I6lZFHOGfOg>
Subject: Re: [lisp] LISP minutes - IETF 117 San Francisco
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Aug 2023 05:15:16 -0000


“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: +1.650.492.0794

> On Aug 7, 2023, at 13:58, Alberto Rodriguez-Natal (natal) <natal=40cisco.com@dmarc.ietf.org> 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
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp