IETF Logo Mail Archive

Re: [lisp] Rechartering Thread 2: From Experimental to ST: these are a bunch of RFC that may be considered

Sharon Barkai <sharon.barkai@getnexar.com> Wed, 15 March 2023 08:06 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 DB609C152574 for <lisp@ietfa.amsl.com>; Wed, 15 Mar 2023 01:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 waU9QGYq4Ehc for <lisp@ietfa.amsl.com>; Wed, 15 Mar 2023 01:06:05 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 ADE2DC1522DB for <lisp@ietf.org>; Wed, 15 Mar 2023 01:06:05 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id h12-20020a17090aea8c00b0023d1311fab3so1051104pjz.1 for <lisp@ietf.org>; Wed, 15 Mar 2023 01:06:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; t=1678867565; 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=E5LnEUSvOpldcGcM4QtPDqPHydoEEQP5mv/DZ00jf+o=; b=lLCfAXPsnh4Xg+ph0uGnUrd9pnWdzfYWvlGFI9UvvHFLTwGbB89DzHlpDCmbF0uuiB 7BDfATG4s1DxzIvIpnuNSzb9xZP7i+1HLgBI6oTiToIby3AvFMG9Bt2PV6BLrRApvI15 /eZFVmDbQzQ0E6Jc9H6JpNb2iWKGret6+8++o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678867565; 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=E5LnEUSvOpldcGcM4QtPDqPHydoEEQP5mv/DZ00jf+o=; b=oRAxpCrnDRtCRvvFruaJKFGUFFStGpGHg2gHBshr3xSG/lddho4POgXSNmvgmS0qYz JlQS6B9tae2bic/1FsO+fFu/P7NZTxSR2zco5DxnRI4TQ7xv20DeIC6ASGNk/HASW9HI vzyFBRLqzSagVpM4aZg6MjD7X1focPMde92lo6INPvGmL+JAwQKxmuAFTHYlnUvS/bXN eEPOCMNeeHvjSKIfa1aeUfsKEsU94kZlw5773oCXAZLQyKVQb0uUDi6wpXXnb+EsRtXd wIEx7xktBoGaq+cJhXdj2B0wgKSOsHQo1iRoyIbJmUuK8yj7tvKvcrikixE5TKqkMomS dXoA==
X-Gm-Message-State: AO0yUKWQC0m5Ld6zptQAIk6jbi2NuyYksyHNaDsz4LUv0Nz2485uTVVz e1/OIXUMxatYI27LsyOOpY/5sg==
X-Google-Smtp-Source: AK7set8t4/9SH2h4gLT/JveW+Y7oVQo3madq095XaZdq1P9VtqZZQlY4fThfgmCLbE4nBDGz4IfZNw==
X-Received: by 2002:a17:902:c40f:b0:19a:96ea:3850 with SMTP id k15-20020a170902c40f00b0019a96ea3850mr1527630plk.17.1678867564839; Wed, 15 Mar 2023 01:06:04 -0700 (PDT)
Received: from smtpclient.apple ([46.120.74.150]) by smtp.gmail.com with ESMTPSA id b14-20020a170903228e00b0019cbabf127dsm2968661plh.182.2023.03.15.01.06.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 01:06:04 -0700 (PDT)
Content-Type: multipart/mixed; boundary="Apple-Mail-17E4C6B4-9652-4FDC-99E8-830B8DCE5475"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Sharon Barkai <sharon.barkai@getnexar.com>
In-Reply-To: <5D6B421D-4847-45F2-97BD-3670EA1D5BF0@gmail.com>
Date: Wed, 15 Mar 2023 10:05:57 +0200
Cc: Luigi Iannone <ggx@gigix.net>, "lisp@ietf.org list" <lisp@ietf.org>, lisp-chairs@ietf.org
Message-Id: <7EB3218F-B5D5-4EE8-B115-0632F42C5E3C@getnexar.com>
References: <5D6B421D-4847-45F2-97BD-3670EA1D5BF0@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/YyIT_MV8zblAvIPERGyvXNRYgl4>
Subject: Re: [lisp] Rechartering Thread 2: From Experimental to ST: these are a bunch of RFC that may be considered
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, 15 Mar 2023 08:06:11 -0000

A full solution project example hopefully all addressing, encapsulation, mcast, and security items are in charter (adopted and wg last call)




Cost reduction of infotainment data:
- Infotainment connected to Internet
- Using public OEM IP address space
- Vehicles toggle wifi/cellular RLOC
- Seamless to the Internet sessions

Automotive Edge Compute Applications:
- Dynamic HdMapping while vehicles Driving
- Regional Ad-Hoc Datacenter while Parked 
- Edge Geo Agents’  EIDs are based on H3 
- Vehicle (far-edge) AI EIDs are ephemeral 

The value: 
- realtime automatic map generation, increase safety, reduced corner cases 
- mobile edge location capacity multiplied by engaging available far-edge-ai 



--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On Mar 14, 2023, at 21:38, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> 
>> 
>> Hi LISP WG,
>> 
>> As for the subject, this email starts the discussion about: From Experimental to ST: these are a bunch of RFC that may be considered to move ST
>> 
>> There are a few experimental RFCs which is worth to be considered to be moved to standard track (if we have documented deployment experience), namely:
>> 
>> RFC 6832: Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP Sites
>> RFC 8060: LISP Canonical Address Format (LCAF) [This is largely used and may be merged with 9306]
>> RFC 8111: Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT) [The only scalable Mapping System so far…..] 
> 
> Agree.
> 
>> Multicast can be another one work item. 
>> RFC 6831: The Locator/ID Separation Protocol (LISP) for Multicast Environments
>> RFC 8378: Signal-Free Locator/ID Separation Protocol (LISP) Multicast 
> 
> The new draft that Prasad submitted this week makes it a trio with the above to. It addresses how to mix the functionality of 6831 and 8378 when there is a mix of native multicast and non-native multicast in the underlay.
> 
> Dino
> 
>> 
>> Please send us back your thoughts.
>> 
>> 
>> Padma and Luigi
>> _______________________________________________
>> 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

v2.23.0 | Report a Bug | By Email