Re: Starlink --- "simpler than IPv6"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 23 October 2020 06:57 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 8203F3A078F for <ipv6@ietfa.amsl.com>; Thu, 22 Oct 2020 23:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.424
X-Spam-Level:
X-Spam-Status: No, score=0.424 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.247, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 JiOCujorCo1v for <ipv6@ietfa.amsl.com>; Thu, 22 Oct 2020 23:57:07 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 638A33A05D0 for <ipv6@ietf.org>; Thu, 22 Oct 2020 23:57:07 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09N6v4X8033966; Fri, 23 Oct 2020 08:57:04 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CC97E200CB3; Fri, 23 Oct 2020 08:57:04 +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 BBE40201F00; Fri, 23 Oct 2020 08:57:04 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09N6v4S9027753; Fri, 23 Oct 2020 08:57:04 +0200
Subject: Re: Starlink --- "simpler than IPv6"
To: sarikaya@ieee.org
Cc: 6man WG <ipv6@ietf.org>
References: <a8dc258cca214efd902a717e08c5bda0@boeing.com> <CAC8QAcfWVN4om0GPC2JnqtBxW5CdOzARK_x25Mw5=Pgv38DTEw@mail.gmail.com> <9c940e46-d865-e7c6-3fa9-9b59a957a91b@gmail.com> <CAC8QAccob_d=NuSntb-E1-=gZ0WEJum4DGAjQMGZjq6Tx7NKBg@mail.gmail.com> <faec81d6-8d4f-04b4-aa22-0f0158a79556@gmail.com> <CAC8QAccQTG6GVi8GEwkXKzo+0K_UbAy3aF-zy+DqES1AfBJTMw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <42e7ec17-b5cc-0a73-22ea-7cde299e03b2@gmail.com>
Date: Fri, 23 Oct 2020 08:57:05 +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: <CAC8QAccQTG6GVi8GEwkXKzo+0K_UbAy3aF-zy+DqES1AfBJTMw@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/zdQITcvmN4BQ-Q7qObl61mx0xxc>
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: Fri, 23 Oct 2020 06:57:10 -0000

Thank you very much for the pointers.

Bob, please allow me this last post and then I pause.

The pdf contains an IP address on the lower left of page 6, titled
'SpaceX Starlink' which does reply to ping with an RTT of 145ms from
here.  Traceroute might hint at some things as well since that IP
resolves inversely.

Alex

Le 22/10/2020 à 17:45, Behcet Sarikaya a écrit :
> SpaceX IB Ex Parte (10-15-20).pdf 
> <https://ecfsapi.fcc.gov/file/101548191460/SpaceX%20IB%20Ex%20Parte%20(10-15-20).pdf>
>
>  
> https://ecfsapi.fcc.gov/file/101548191460/SpaceX%20IB%20Ex%20Parte%20(10-15-20).pdf
>  
> <https://ecfsapi.fcc.gov/file/101548191460/SpaceX%20IB%20Ex%20Parte%20(10-15-20).pdf>
>
>  This is their latest FCC application.
> 
> Behcet
> 
> On Wed, Oct 21, 2020 at 11:17 AM Alexandre Petrescu 
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
> wrote:
> 
> 
> 
> Le 19/10/2020 à 21:17, Behcet Sarikaya a écrit :
>> 
>> 
>> On Mon, Oct 19, 2020 at 11:12 AM Alexandre Petrescu 
>> <alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com> 
> <mailto:alexandre.petrescu@gmail.com 
> <mailto:alexandre.petrescu@gmail.com>>>
>> wrote:
>> 
>> 
>> 
>> 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>
> <mailto:Fred.L.Templin@boeing.com
> <mailto:Fred.L.Templin@boeing.com>>
>> <mailto:Fred.L.Templin@boeing.com
>> <mailto:Fred.L.Templin@boeing.com> 
>> <mailto: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.
>> 
>> 
>> 
>> It is 12GHz
> 
> It seems you know that for sure?  How?
> 
> I could find some approved applications at FCC and they say more 
> frequency bands (around 18GHz, 19GHz, 28GHz and 30GHz), but not
> 12GHz. https://fcc.report/IBFS/SES-LIC-INTR2020-03068 
> <https://fcc.report/IBFS/SES-LIC-INTR2020-03068>
> 
> There is a listof applications from this company to FCC, visible at 
> https://fcc.report/company/SpaceX-Services-Inc 
> <https://fcc.report/company/SpaceX-Services-Inc>
> 
> One would check themm all, to find out the frequencies and the names
> of the manufacturers of devices.  After that, one could see for the
> device specifications.
> 
> It might also be that the end user does not talk to satellite (like 
> Iridium users do) but to ground stations on WiFi, which them do talk
> to satellites.  At that point there would be no interest of 
> "IPv6-over-starlink" but a simpler "IPv6-over-WiFi-at-5GHz-in-USA".
> 
> Alex
> 
>> 
>> 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.
>> 
>> 
>> I don't know how to do these?
>> 
>> Behcet
>> 
>> Alex
>> 
>> 
>>> 
>>> Behcet
>>> 
>>> __
>>> 
>>> Fred____
>>> 
>>> __ __
>>> 
>>> *From:*Behcet Sarikaya [mailto:sarikaya2012@gmail.com
> <mailto:sarikaya2012@gmail.com>
>> <mailto:sarikaya2012@gmail.com <mailto:sarikaya2012@gmail.com>>
>>> <mailto:sarikaya2012@gmail.com <mailto:sarikaya2012@gmail.com>
> <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>
>> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>>
>>> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>
> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>>>>; 6man WG
>> <ipv6@ietf.org <mailto:ipv6@ietf.org> <mailto:ipv6@ietf.org
> <mailto:ipv6@ietf.org>>
>>> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>
> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>>>> *Cc:* Templin
>> (US), Fred L
>>> <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>
> <mailto:Fred.L.Templin@boeing.com
> <mailto:Fred.L.Templin@boeing.com>>
>> <mailto:Fred.L.Templin@boeing.com
>> <mailto:Fred.L.Templin@boeing.com> 
>> <mailto: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>
> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>>
>>> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>
> <mailto: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>
>> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>>
> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>
>> <mailto:mcr@sandelman.ca <mailto:mcr@sandelman.ca>>>
>>> http://www.sandelman.ca/ <http://www.sandelman.ca/>
> <http://www.sandelman.ca/ <http://www.sandelman.ca/>>
>> <http://www.sandelman.ca/ <http://www.sandelman.ca/>
> <http://www.sandelman.ca/ <http://www.sandelman.ca/>>>        | ruby
>> on
>>> rails    [
>>> 
>>> 
>>> ____
>>> 
>>> 
>>> --------------------------------------------------------------------
>
>>> 
> 
>>> 
>> IETF IPv6 working group mailing list ipv6@ietf.org
> <mailto:ipv6@ietf.org>
>> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>> Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> <https://www.ietf.org/mailman/listinfo/ipv6>
>> <https://www.ietf.org/mailman/listinfo/ipv6
> <https://www.ietf.org/mailman/listinfo/ipv6>>
>>> --------------------------------------------------------------------
>
>>> 
> 
>>> 
>> 
>> 
>> --------------------------------------------------------------------
>
>> 
> IETF IPv6 working group mailing list ipv6@ietf.org 
> <mailto:ipv6@ietf.org>
>> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>> Administrative
> Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
> <https://www.ietf.org/mailman/listinfo/ipv6>
>> <https://www.ietf.org/mailman/listinfo/ipv6
> <https://www.ietf.org/mailman/listinfo/ipv6>>
>> --------------------------------------------------------------------
>
>> 
> 
>