Re: [lisp] New Version Notification for draft-farinacci-lisp-satellite-network-00.txt
Dino Farinacci <farinacci@gmail.com> Mon, 04 April 2022 17:37 UTC
Return-Path: <farinacci@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 1B2673A0E42 for <lisp@ietfa.amsl.com>; Mon, 4 Apr 2022 10:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_IMAGE_ONLY_32=0.001, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eruy2oODQSUW for <lisp@ietfa.amsl.com>; Mon, 4 Apr 2022 10:37:42 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 A77683A0E16 for <lisp@ietf.org>; Mon, 4 Apr 2022 10:37:41 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id n6-20020a17090a670600b001caa71a9c4aso2622333pjj.1 for <lisp@ietf.org>; Mon, 04 Apr 2022 10:37:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NNON/ocPR/nczKCU8r2yLEL4b1H/5JnynXaUbTCETSI=; b=GbGsjrELiW1l8PMAEocryUZ2NcQfFmNJnU15fiIW1/U8oVbshKknuCbwq3V9vsvHEl AsTMZN4QC/2ZRt+OjjU5+b2t4HEDdhOO2ZhMabH92knsx2gIHyhzMX8e7z4r5k9WLJUC NqfCtVaaEViU5mWj/cGLTtlHcAyOF7G5gd7dX4QJc73IdScMUreHd9baVSj2tkc1VH0S rFuvuEfqb6+/HBj32Rn16w3GqVYmCwwQhgkGbgMDtZFh9ozVgTM9H6CwSuKxak+VeasV 4yJzGunYU1wIiR3adQYuHg2q0zdkWZPUtZNEP2XUrx8f9Fq9PYyqzlrz3rEx+UsU3D/7 XiXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NNON/ocPR/nczKCU8r2yLEL4b1H/5JnynXaUbTCETSI=; b=nHtutGHv1yGKFPJ4H2HWLbYahtVetg+W6W6JyTFc6rEoLAaRSbNR+PTwdHQBYxQOy5 yLxuh82jNpss/Mg8/WRrW5aHjTRkLNct4wOL/cNBUM3OptQA6J1374cKpuLwwIwBxz8k +/Kz0T+z10DDGA7C1HAqAm7KCqCBiezT4eeecS24UZ6Pga9fNBMShQNPoM1T7MwuHSCX dBMDXf9zysfgIJcy9akN/E7w//TCgma7ps2Y0m8oEmOrfbP0DzA1H8p8RHnrmKJbDp7G 3dMNZ6wCBibR8E2lRYLkQjL71NJnGedLVH0VUEqpEsIGYu/9+lyX3dI499UrZAakCQF8 gh6g==
X-Gm-Message-State: AOAM5320B/xnNc56HnSQqemU2YX9tErkDdHESLUo5wa7i/dY360uHkWc oLlghMBuDE+ujkj9huT6BowNJBSNV0E=
X-Google-Smtp-Source: ABdhPJz5f4A9OoJQ/zoGwunNkLsLEwYieWdD1RftX9gy1sgVX5lNm9r7age+nXzEP4j7aJy/Uw30qw==
X-Received: by 2002:a17:902:ecca:b0:154:5393:aa81 with SMTP id a10-20020a170902ecca00b001545393aa81mr972587plh.148.1649093859800; Mon, 04 Apr 2022 10:37:39 -0700 (PDT)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id p9-20020a17090adf8900b001ca69a4980asm101057pjv.5.2022.04.04.10.37.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Apr 2022 10:37:38 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <1DFC4834-CB4E-4D83-9928-9A856E84C8E3@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FE2189E2-34C7-4A76-AB5E-D1D83F45EEC7"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Mon, 04 Apr 2022 10:37:35 -0700
In-Reply-To: <EBAEB0F2-D411-4C59-AA1A-593DE88B6854@getnexar.com>
Cc: "lisp@ietf.org list" <lisp@ietf.org>
To: Sharon Barkai <sharon.barkai@getnexar.com>
References: <9CCCD9B0-F6D0-4164-83C0-62A493944839@gmail.com> <EBAEB0F2-D411-4C59-AA1A-593DE88B6854@getnexar.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/BrltLbaGSrwuPOawC9CYH2dyipk>
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 17:37:46 -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. Copying the really nicely drawn diagram below for reference. So if you wanted to do geographical addressing and map it to RLOCs that you could have connectivity to, that could work. This is a new idea (your idea) and we should think about it. This is how I envision it could be implemented by the LISP protocol: (1) The H3 index-id is stored in mapping system as a distinguished-name EID. (2) The EID maps to a RLOC-set which is a list of routable IP addresses inside a particular tile (at any resolution). The assumption is, if you are in a larger resolution tile, you may have reachability to the RLOCs for the tiles within your resolution. The path a packet may take could (obviously) leave the tile resoltuion area so you are not guaranteed a shortest topological path. RLOC-probing could test one-way latency and RTT to determine if the packet is leaving the area. With more distributed and decentrailzied wireless networks out there, there is a possibility packets can stay "within tile resolution". One comment on the diagram below. Its just a presentation commemnt. If you draw the word "RLOC" next to a satellite, it implies it could be registered in the mapping system and therefore runs as a LISP xTR. Theoretctically this can be the case but, again, we are not proposing this for the early work on draft-farinacci-lisp-satellite-network. Also, if you change "GS RTR" below to "GS xTR" then you have drawn the same diagram as the draft has. Making the label "xTR" means it can be any of ITR, ETR, pITR, pETR, and RTR. So more general. So another question, if the GS-xTR and a satellite are in the same H3 resolution does it mean the satellite have the field of view of the GS-xTR. If that is the case, we may be able to explore this idea. One more comment, maybe using GPS is better because you have 3-dimensionality where H3 is 2D. Comments? With 3D you can imply that one sat is in a closer orbit to earth than another sat. Thanks for the comments, Dino
- [lisp] Fwd: New Version Notification for draft-fa… Dino Farinacci
- Re: [lisp] Fwd: New Version Notification for draf… Sharon Barkai
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci
- Re: [lisp] New Version Notification for draft-far… Sharon Barkai
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci
- Re: [lisp] New Version Notification for draft-far… Sharon Barkai
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci
- Re: [lisp] New Version Notification for draft-far… Sharon Barkai
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci
- Re: [lisp] New Version Notification for draft-far… Sharon Barkai
- Re: [lisp] New Version Notification for draft-far… Dino Farinacci