Re: [lisp] I-D Action: draft-ietf-lisp-nexagon-52.txt

Sharon <sbarkai@gmail.com> Mon, 25 December 2023 06:17 UTC

Return-Path: <sbarkai@gmail.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 08D0FC14F5EC; Sun, 24 Dec 2023 22:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 (2048-bit key) header.d=gmail.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 1KJuuThkO8cG; Sun, 24 Dec 2023 22:17:48 -0800 (PST)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 2CAFAC14F5E0; Sun, 24 Dec 2023 22:17:48 -0800 (PST)
Received: by mail-wr1-x429.google.com with SMTP id ffacd0b85a97d-336c9acec03so117011f8f.2; Sun, 24 Dec 2023 22:17:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703485066; x=1704089866; darn=ietf.org; 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=TnZYV3Dd/9UO0ASwW8Rpwm64+jDK0SZ3RQ67X9l/fFM=; b=MlVa3j1cob8ZXFJRzHTV5RYA4dmRpKPuynzN90Ro5mWK1s8f7H7RWwRTsZC+ismFDb 4Yosy+T4kqmBvFZZRLCMDpuBYqt2jJJkHVB1Oxw6BJ+M9nA+xGwQkUR/qbbSDVgdjM0R rdtpoGPdaZwc9nxeAuoOuSIhTSpk0VoyZM9Kqx2comUSAPGadvfmw2xEtbXE9B0ZpZ/m 2aMKPCpTW5yVoOjA2u6BJTf8lhVYQLX774+UuKLyVhZXziY1x88Y7jtEVlwgcUVZtwiB am7JSnmv7td+qEZ2X9aXUT5SFceeGhoq4zCxt3qjVfoK2XdVEA9J0VDi0wb6mbQUgXaq o+Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703485066; x=1704089866; 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=TnZYV3Dd/9UO0ASwW8Rpwm64+jDK0SZ3RQ67X9l/fFM=; b=dhnBn37oGZialNfiC7raD+57/RGZf5rS5nNWnlWAVfl66ZH9KtEpB2OjKPGRXbKH5L FyXc/U/NRDZGs53OY58ZSIoUbiVRCTK8D5+y+2FmEFBQDSoXS1gPrgIAubw4g9G/gLRZ hzCXPnRTUYZD2SRL3WFSILy9Rsfq8AHzctoSEO/O8FTyHOU3j8V0ZcoXlUPVt+wMl2y3 SQnAdUIKzGe5mLKry7FOJf2Dt3fbwQv831X0JUF+7zEhciyig3BodLAUPhmuX0xecU0u 6pP405YILd4vOhZ5x/WDLFtbkFYLwdHZ/gHKMl+NIisSSI/V0FxggtMllm0+XL7saHay HTkA==
X-Gm-Message-State: AOJu0YySGZdSpKJL5F9d5TeaT8t2pHBB7YcmNrPOzN/NX66IT/ayoeRU yu3QlmbOxCrR1IsmYCS2dw==
X-Google-Smtp-Source: AGHT+IHp1srJF/0mLvgucbnLgH0hRK/7/xKDXlWEGnroqzGg7ONKREYxz3kVccJJhkay10JJOJDwMw==
X-Received: by 2002:a05:600c:520c:b0:40c:3891:b0a3 with SMTP id fb12-20020a05600c520c00b0040c3891b0a3mr2702315wmb.160.1703485065651; Sun, 24 Dec 2023 22:17:45 -0800 (PST)
Received: from smtpclient.apple ([2a0d:6fc2:4a90:4800:950:cfc:c757:3c7c]) by smtp.gmail.com with ESMTPSA id t17-20020a5d49d1000000b00336614e25d0sm9649898wrs.56.2023.12.24.22.17.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Dec 2023 22:17:45 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-A8C28930-7904-437E-A488-1B746B848C21"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
In-Reply-To: <170348362055.54725.1848658874340746427@ietfa.amsl.com>
Date: Mon, 25 Dec 2023 08:17:43 +0200
Cc: lisp-chairs@ietf.org
Message-Id: <F5D58913-DC7A-4E6B-B482-0BA387878413@gmail.com>
References: <170348362055.54725.1848658874340746427@ietfa.amsl.com>
To: lisp@ietf.org
X-Mailer: iPhone Mail (21B101)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/aPdatmFwP650cVAhqoqoh24A-2k>
Subject: Re: [lisp] I-D Action: draft-ietf-lisp-nexagon-52.txt
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: Mon, 25 Dec 2023 06:17:52 -0000

LISP NEXAGON Update

The version updates some of the wording used to describe the functionality of a LISP Nexagon network, which is to share the joint vision and sensory of any number of producing sources, fleets, drones, and satellite, to any number of consuming clients, maps, GIS, and path planning copilots. 

Specifically it outlines: 

	⁃	‘joint-vision’ enum tiles language
	⁃	changes, overlaps, points of view
	⁃	freshness, privacy, and localization
	⁃	stateful driving of stateless models 

(eg NexgonGPT)

Deployed applications of this LISP network are for safety (DoDs, DoTs, OEMs):

	1.	Safety on-road: blockages & hazards
	2.	Safety off-road: traffic-ability degrees
	3.	Safety during disasters: fires, floods.. 

(when on-road abruptly becomes offroad)

The use of LISP enables the network to function securely and uninterrupted while vision producers and consumers are constantly moving. This is due to the connectivity-anchoring properties of LISP EIDs.

However since EID logical addressing is based on mapping, LISP also provides semantic-anchoring: (HID EIDs)

	•	As EIDs are purely logical due to map-assisted routing aspect
	•	If semantic anchoring can be expressed in terms of EID unicast and multicast
	•	Then LISP, unlike other virtual networks, can be used for semantic anchoring while preserving privacy.

Semantic anchoring is typically provided at the application layer, but if it can be provided at the virtual routing layer the advantages are high as far as capacity, scale, interoperability, geo-distribution, latency & jitter, queuing & loss. This was shown in 5g performance tests (Foundry) and interoperability tests (AECC). 

Consequently it took joint effort of LISP expertise by the co-authors (Cisco, UPC, Lispers, Nexar) Joel and Luigi who served as wg chairs/ shepherds, and the active participants of the wg, to evolve this specification. Hopefully in addition to safety it will help promote more such interoperable decentralized applications.


--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On Dec 25, 2023, at 07:54, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-lisp-nexagon-52.txt is now available. It is a work
> item of the Locator/ID Separation Protocol (LISP) WG of the IETF.
> 
>   Title:   Network-Hexagons:Geolocation Mapping Network Based On H3 and LISP
>   Authors: Sharon Barkai
>            Bruno Fernandez-Ruiz
>            Rotem Tamir
>            Alberto Rodriguez-Natal
>            Fabio Maino
>            Albert Cabellos-Aparicio
>            Jordi Paillisse-Vilanova
>            Dino Farinacci
>   Name:    draft-ietf-lisp-nexagon-52.txt
>   Pages:   32
>   Dates:   2023-12-24
> 
> Abstract:
> 
> This specification describes functionality of LISP Nexagon networks.
> The network shares a joint vision of any number of producing sources,
> fleets, drones, and satellite, with any number of consuming clients,
> maps, GIS, and path planning copilots.
> 
> Specifically it outlines:
> - joint-vision tiled enumeration geolocation language channels
> - addressing change notifications, overlaps, points of view,
> - freshness, privacy, localization, seamless context-switching,
> - via stateful driving of stateless models by EID location agents
> 
> Safety applications of this network are:
> 1. Safety on-road: blockages & hazards beyond line of sight
> 2. Safety off-road: traffic-ability and varying risk degrees
> 3. Safety during disasters: fires, floods, snow, abrupt change
> 
> The use of LISP enables the network to function securely uninterrupted
> while vision producers and consumers are constantly moving due to the
> connectivity-anchoring properties of LISP EIDs. Since EIDs are logical
> being based on mapping-system, it provides semantic-anchoring as well.
> Semantic joint vision consolidation uses H3 EID unicast and multicast.
> 
> The IETF datatracker status page for this Internet-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-52
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-nexagon-52
> 
> 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