IETF Logo Mail Archive

[lisp] Quick Mobility Update

Sharon Barkai <sharon.barkai@getnexar.com> Sun, 23 May 2021 07:00 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 69CA53A30B9 for <lisp@ietfa.amsl.com>; Sun, 23 May 2021 00:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmZ3GRA53V_0 for <lisp@ietfa.amsl.com>; Sun, 23 May 2021 00:00:03 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926DD3A30B3 for <lisp@ietf.org>; Sun, 23 May 2021 00:00:02 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id f75-20020a1c1f4e0000b0290171001e7329so9304413wmf.1 for <lisp@ietf.org>; Sun, 23 May 2021 00:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; h=from:mime-version:date:subject:cc:to:message-id; bh=YJYZoF2Q1OkCo/MNQCNptRZsoiSrhZ1uuPcPp3+7+Y8=; b=QrqpIsNTuAs2h+Wg7UaXNLjDbu9ZiC1BU4ecQcXTHIb44uFF2XDHfuinAT4ScdvgR1 nlgt2LrH/FajHeYKo/kv9pTHsj8QY87jhNZAegYvbGNxS1TDamYCEMtHip3U9SjnulIW xraEoDynDWaWB/xN7vTpfyGARn+vgl1hRHqzY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:subject:cc:to:message-id; bh=YJYZoF2Q1OkCo/MNQCNptRZsoiSrhZ1uuPcPp3+7+Y8=; b=mCsq3g+O3WHdRtKOv/xNbvjInU8uiHCZUAtYbnwfAyIZ2pH08F/d6KLBm3qP84gevO au0CzmSIH2x6vIZeUN6TUdgt11Qzar71XcfnUti9sUBcta634n/l5uNry6xy80QPoe7k MzZZ+x/pnEEnZ9RL2SuozItuw9stNYUjhKP2ceVfU5KhMAu5T5nldI2mYNy7NVG0GmFq uwA2JnXWBu3AFNoWtRewsrPitEzuYOO3mCM0Jo+sX8m/5lAVxjWLhKXMGGUKs3HbS9SY +WKftgCBcMYXGpj/9sBv0Auel0kba1dflLz7Pd+cc3wjSj9rA/EQuj9Tlce22FNVmW5R YbtA==
X-Gm-Message-State: AOAM533rtoZsHbiFz2X/9keDneeiHd8tV90vt/eh8NHPEbE8j47Am+e6 cljViCQHE9o6z0oyIV6L3Tdxpw==
X-Google-Smtp-Source: ABdhPJyghoQwlmr2SdPWZ7q/mBd3GnduQMCArRFe4a/1bxXEcJ7Snp4vb795F/tnT9sf+SBXm6zmPg==
X-Received: by 2002:a7b:cc84:: with SMTP id p4mr14602517wma.171.1621753199663; Sat, 22 May 2021 23:59:59 -0700 (PDT)
Received: from smtpclient.apple ([2a02:14c:3bf:300:adeb:31bd:56c0:fb79]) by smtp.gmail.com with ESMTPSA id x206sm1115315wmx.47.2021.05.22.23.59.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 May 2021 23:59:58 -0700 (PDT)
From: Sharon Barkai <sharon.barkai@getnexar.com>
Content-Type: multipart/mixed; boundary="Apple-Mail=_DB55178E-F532-4CC7-919A-1D7F260EE977"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Sun, 23 May 2021 09:59:54 +0300
Cc: "lisp@ietf.org list" <lisp@ietf.org>
To: lisp-chairs@ietf.org
Message-Id: <91B48F0A-5188-4DE5-99CF-24D5C1B9AD0D@getnexar.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/aJUk-_uj_nEgnMzztRIsLqZt9_M>
Subject: [lisp] Quick Mobility Update
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 23 May 2021 07:00:11 -0000

The LISP-Nexagon interface is being used in this AECC TR (Toyota, Oracle) to express mobility transient data management requirements,  LISP itself is used as basis for requirements for P2P / P2MP mobility edge service continuity.

1. Mobility Transient Data Management
* these are deviation from the HDMaps, that will update the map (new signs) or remain transient (parking, blockages).

- the addressable (EID) interface allows for low-latency high-yield (resolution-less, connectionless) vehicle<> edge exchange.
- the geo-spatial indexing allows for representation of transient data as enumeration w/o frequent distributed creation/ deletion.  
- the object interface allow for stable interoperable construct while allowing flexible/differentiated: ingest, curation, propagation.


2. Mobility Edge Service Continuity 
* this is the distributed compute network between many vehicles and edge compute locations in a major metro area.

- allow for P2P P2MP sessions between EIDs to continue as IOT modems switch carriers due to reception change while driving.
- allow for P2P P2MP session between EIDs while addressable (low-latency) services migrate between edge servers/ locations.
- allow for lode-balanced highly available anchoring of roaming clients and services per each private enterprise mobility network.


When can we expect RFC numbers for bis and nexagons?
It can really help specifications and references.

v2.23.0 | Report a Bug | By Email