Re: Starlink --- "simpler than IPv6"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 19 October 2020 16:11 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB943A0BB6 for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 09:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.931
X-Spam-Level: ***
X-Spam-Status: No, score=3.931 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.247, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 apscHl2JHnMe for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 09:11:52 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5617F3A0BB3 for <ipv6@ietf.org>; Mon, 19 Oct 2020 09:11:52 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09JGBo0R017871 for <ipv6@ietf.org>; Mon, 19 Oct 2020 18:11:50 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 13A75206ADF for <ipv6@ietf.org>; Mon, 19 Oct 2020 18:11:50 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 09E0E2039A6 for <ipv6@ietf.org>; Mon, 19 Oct 2020 18:11:50 +0200 (CEST)
Received: from [10.11.240.110] ([10.11.240.110]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09JGBn8N013253 for <ipv6@ietf.org>; Mon, 19 Oct 2020 18:11:49 +0200
Subject: Re: Starlink --- "simpler than IPv6"
To: ipv6@ietf.org
References: <a8dc258cca214efd902a717e08c5bda0@boeing.com> <CAC8QAcfWVN4om0GPC2JnqtBxW5CdOzARK_x25Mw5=Pgv38DTEw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <9c940e46-d865-e7c6-3fa9-9b59a957a91b@gmail.com>
Date: Mon, 19 Oct 2020 18:11:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <CAC8QAcfWVN4om0GPC2JnqtBxW5CdOzARK_x25Mw5=Pgv38DTEw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/b-WxmW56SrBpk_HD4ruBItlgAfY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 16:11:54 -0000


Le 19/10/2020 à 17:58, Behcet Sarikaya a écrit :
> 
> 
> On Mon, Oct 19, 2020 at 10:20 AM Templin (US), Fred L 
> <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>>
> wrote:
> 
> Seems like an “IPv6-over-foo” document might be in order; anyone care
> to____
> 
> join me on that?____
> 
> __
> 
> 
> IPv6-over-foo on Starlink section would look like
> 
> TBD until more is revealed

One in USA could look at the regulator's public database and find which
frequency channel is allocated for Tesla for Starlink.  From that, one
could find which encoders are available on that frequency.  From that
one could find which protocols are on it.  It makes for a 'foo' in 'IPv6
over foo'.  The link layer.

Alex


> 
> Behcet
> 
> __
> 
> Fred____
> 
> __ __
> 
> *From:*Behcet Sarikaya [mailto:sarikaya2012@gmail.com 
> <mailto:sarikaya2012@gmail.com>] *Sent:* Monday, October 19, 2020
> 8:14 AM *To:* Michael Richardson <mcr@sandelman.ca 
> <mailto:mcr@sandelman.ca>>; 6man WG <ipv6@ietf.org 
> <mailto:ipv6@ietf.org>> *Cc:* Templin (US), Fred L
> <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>> 
> *Subject:* Re: Starlink --- "simpler than IPv6"____
> 
> __ __
> 
> ____
> 
> Thanks Michael, I'd like to know as much as possible how IPv6 works 
> in Starlink.____
> 
> __ __
> 
> Behcet____
> 
> __ __
> 
> On Fri, Oct 16, 2020 at 3:47 PM Michael Richardson <mcr@sandelman.ca 
> <mailto:mcr@sandelman.ca>> wrote:____
> 
> Anyone read anything more specific about what Starlink is doing that
> is "simpler than IPv6"?
> 
> I'd sure like to know that it permits end-terminal to end-terminal 
> communicatons without a trip through a data center.
> 
> -- ]               Never tell me the odds!                 | ipv6 
> mesh networks [ ]   Michael Richardson, Sandelman Software Works
> |    IoT architect   [ ] mcr@sandelman.ca <mailto:mcr@sandelman.ca> 
> http://www.sandelman.ca/ <http://www.sandelman.ca/>        | ruby on
> rails    [
> 
> 
> ____
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>