Re: Starlink --- "simpler than IPv6"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 21 October 2020 16:07 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 180D93A12E1 for <ipv6@ietfa.amsl.com>; Wed, 21 Oct 2020 09:07:24 -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_H3=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 vI7XU81RO4OC for <ipv6@ietfa.amsl.com>; Wed, 21 Oct 2020 09:07:22 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 25D013A12E0 for <ipv6@ietf.org>; Wed, 21 Oct 2020 09:07:20 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09LG7Hg0025185 for <ipv6@ietf.org>; Wed, 21 Oct 2020 18:07:17 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 178252070E2 for <ipv6@ietf.org>; Wed, 21 Oct 2020 18:07:17 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0C0A0207066 for <ipv6@ietf.org>; Wed, 21 Oct 2020 18:07:17 +0200 (CEST)
Received: from [10.11.241.180] ([10.11.241.180]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09LG7GnL015159 for <ipv6@ietf.org>; Wed, 21 Oct 2020 18:07:16 +0200
Subject: Re: Starlink --- "simpler than IPv6"
To: ipv6@ietf.org
References: <f2c646b0a2434a1198dca54343db8f78@boeing.com> <CAC8QAcdXvusT30p3appTFFcvUJOdr1WVVN79MkYy9LKkmZ_Q0w@mail.gmail.com> <62D7C8B9-6E92-4EFD-8BC8-9328B00EF635@gmail.com> <CAC8QAcc2deQSBPUTmB89J8RQmoW4zOpggoTDJPJRSvGicBcEQw@mail.gmail.com> <E45A0AAB-8EB2-4FA8-8702-298D6350599A@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d476b1a0-c80c-9512-77ce-b8465343ef35@gmail.com>
Date: Wed, 21 Oct 2020 18:07:15 +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: <E45A0AAB-8EB2-4FA8-8702-298D6350599A@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/zyYQ3wd4gBbelaHPRC0iPLIpolE>
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: Wed, 21 Oct 2020 16:07:24 -0000

Le 21/10/2020 à 17:30, Bob Hinden a écrit :
> Behcet,
> 
>> On Oct 21, 2020, at 8:11 AM, Behcet Sarikaya
>> <sarikaya2012@gmail.com> wrote:
> 
>> On Tue, Oct 20, 2020 at 11:50 AM Bob Hinden <bob.hinden@gmail.com>
>> wrote: Can anyone point to a specification on Starlink?
>> 
>> Without that, this thread seems pretty content free.
>> 
>> I had started this thread with a mail to Fred thinking that as a
>> person from a major vendor in aviation industry, he Or someone in
>> this list may have something technical. That includes yourself as
>> the chair.
> 
> Thanks, actually I did some searches and couldn’t find anything.
> Also couldn’t find an email to try to contact someone at Starlink.
> If someone knows anyone there on the technical side, I would be happy
> to try to see what I could find out.

Thanks for the explanation.

I heard these discussions about Starlink Beta testing available to 
someone situated in USA.  It's said that it is probably sufficient to 
subscribe to a newsletter and then they might contact back.

Alex

>>> <sarikaya2012@gmail.com> wrote:
>>> 
>>> Hi Fred,
>>> 
>>> On Mon, Oct 19, 2020 at 2:24 PM Templin (US), Fred L
>>> <Fred.L.Templin@boeing.com> wrote: Behcet,
>>> 
>>> 
>>> 
>>> It is 12GHz
>>> 
>>> 
>>> 
>>> Would that frequency spectrum be compatible for use on mobile
>>> vehicular platforms
>>> 
>>> (e.g., cars, drones, helicopters, planes, etc.). Because it comes
>>> from Tesla, can we
>>> 
>>> expect at least cars?
>>> 
>>> 
>>> 
>>> 
>>> Yes, Starlink certainly aims at connecting Tesla cars to their
>>> network, they are currently connected with 4G links
>>> 
>>> Do you think that 12GHz causes issues on mobile vehicular
>>> platforms?
>>> 
>>> Behcet Thanks - Fred
>>> 
>>> 
>>> 
>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Behcet
>>> Sarikaya Sent: Monday, October 19, 2020 12:17 PM To: Alexandre
>>> Petrescu <alexandre.petrescu@gmail.com> Cc: 6man WG
>>> <ipv6@ietf.org> Subject: Re: Starlink --- "simpler than IPv6"
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, Oct 19, 2020 at 11:12 AM Alexandre Petrescu
>>> <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>> 
>>>> 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
>>> 
>>> 
>>> 
>>> 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>] *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 
>>>> --------------------------------------------------------------------
>>>>
>>>
>>>
>>>> 
--------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
>>> --------------------------------------------------------------------
>>>
>>>
>>> 
--------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
>>> --------------------------------------------------------------------
>>
>
>>> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>