Re: [lisp] New Version Notification for draft-farinacci-lisp-satellite-network-00.txt

Sharon Barkai <sharon.barkai@getnexar.com> Mon, 04 April 2022 10:28 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 DAA913A2011 for <lisp@ietfa.amsl.com>; Mon, 4 Apr 2022 03:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 XPB2M_0k2JJ0 for <lisp@ietfa.amsl.com>; Mon, 4 Apr 2022 03:27:59 -0700 (PDT)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (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 37E4A3A2016 for <lisp@ietf.org>; Mon, 4 Apr 2022 03:27:32 -0700 (PDT)
Received: by mail-ej1-x630.google.com with SMTP id dr20so18847733ejc.6 for <lisp@ietf.org>; Mon, 04 Apr 2022 03:27:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=XsuHioEFoVh71+QUyEmYwkq9w6NBLr9759Ljy2xb3N8=; b=AcHNZ+kdl+CMGnEcmIMb5ZGJiAIUMNsCWGDjATUH3IP0YtVBHfGNOaKizTsXbtlwpd +9OieUrfGk3aS0x3wywjPpq/8O+D8dEzAPpvIdeZj5e0lMow0aSBBNOZChNWbRnKjqgN LmxrGnSnkoQ+hVoyAQU7XiciYAfSd3GV+d4G8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=XsuHioEFoVh71+QUyEmYwkq9w6NBLr9759Ljy2xb3N8=; b=mt5AZDgE99p8uCIt2l72fs+DD13hsaiNKaKGhQfs3B7ZiCodseQPMjFzxaySrK9Oy8 hWIXpCnHS8Pu5mQEaLSrg5m51grA14j2hMDHWef/FBzjWX3XaDND6RVnriI492he4Lc8 K1cLlA41Yr/9KqWGQiofbdG7+UaW3WaWlH2p9lLFy3ay3DwMZPGZ6AXqPLJiGwG3H1WD peST2elCitnfq77fzM2i1fuqZhgtnwmv/IPQP3fzzL+i7ZoZWqiYkweIWLVpmH/Q1JxE V1bM6nINADSm7aLJrysvNPnqGBCrUDteS3WHsQGwlnUJoLHIsII/7sJ5JJd9s4nNq+YK l4AQ==
X-Gm-Message-State: AOAM532zn82l/ylf0kTfnV8lDPZihp1EEKRLqzGd/5P7mm5tldDsVMNm 8ys1VMRP6CFHoTi3Y3kJqX/iNgZe0Qy9irkirbA2co9OhjSVOJbyk9Vi/3gZK/VOsSzhrj5DU8D SL2uTDdPCOH82F9DL5zaY6u5Bpn/l+wvmbko9ELg3gqrhRJAMAEz831TeIPc/Xyoykm4=
X-Google-Smtp-Source: ABdhPJyYnXLz9qbtK9bxkC2AaRP9XRhFmW0R2N8Kd5Royh5fAg5v9SxEAfwqqKptHqKcRQs2gqKTxg==
X-Received: by 2002:a17:907:7ba6:b0:6df:ee7d:10f2 with SMTP id ne38-20020a1709077ba600b006dfee7d10f2mr10336948ejc.98.1649068049694; Mon, 04 Apr 2022 03:27:29 -0700 (PDT)
Received: from smtpclient.apple ([2001:4df4:31c:e800:5cc2:1a4b:aba5:cd6a]) by smtp.gmail.com with ESMTPSA id js24-20020a170906ca9800b006c8aeca8fe8sm4174727ejb.58.2022.04.04.03.27.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Apr 2022 03:27:28 -0700 (PDT)
Content-Type: multipart/mixed; boundary="Apple-Mail-B35A0F13-B7A8-477F-925C-C57087E96948"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Sharon Barkai <sharon.barkai@getnexar.com>
In-Reply-To: <9CCCD9B0-F6D0-4164-83C0-62A493944839@gmail.com>
Date: Mon, 04 Apr 2022 13:27:26 +0300
Cc: "lisp@ietf.org list" <lisp@ietf.org>
Message-Id: <EBAEB0F2-D411-4C59-AA1A-593DE88B6854@getnexar.com>
References: <9CCCD9B0-F6D0-4164-83C0-62A493944839@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (19D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/WV9o4m13TVIpGyU8zY02d1k8a8A>
Subject: Re: [lisp] New Version Notification for draft-farinacci-lisp-satellite-network-00.txt
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: Mon, 04 Apr 2022 10:28:05 -0000

I thought the tiles have RLOCs and theres a live applet that can tell you at any given sec which tile is occupied by a sat and becomes its RLOC.
But maybe i misunderstood the preso. 

 


--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On Apr 3, 2022, at 22:37, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> 
>> 
>> Just curious what you think, if XTR could know at any given moment which IP addressable (sky) grid cell has a satellite, could the overlay source such underlay segment routing path, or it will be just way to many headers? 
> 
> Well if it knew that and the satellite's RLOC, then it could just LISP encapsulate to it. But the GS-xTR may not have connectivity to it. 
> 
> The GS-xTR could spray packets to say a few number of satellite RLOCs like we do for draft-ietf-lisp-predictive-rlocs. But in the predictive-RLOCs case we prune the spray-list when packets come back from RLOCs. This is likely not to be the case since there could be thousands of satellite nodes.
> 
> Dino
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp