RE: Starlink --- "simpler than IPv6"

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 19 October 2020 17:03 UTC

Return-Path: <Fred.L.Templin@boeing.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 5DC923A0C8A for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 10:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 6gC91U-8CSWj for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 10:03:29 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 5B8993A0C7E for <ipv6@ietf.org>; Mon, 19 Oct 2020 10:03:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09JH3Rr1031623; Mon, 19 Oct 2020 13:03:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1603127007; bh=gcQCnmtvKMGUeMc6HdlIYXTttdwZaZ6LvsPxd5Eidj0=; h=From:To:Subject:Date:References:In-Reply-To:From; b=e44g1eYLw4zRo/Z/KJncrcEijKV643IT/XyBTiHNpdFhktkauDoXhMhqimoU4tLkm S836sVn5Q1exnQ/sGGKI2+mLAugg3XTmH+aj9x/qnkyG09FhdIjhlNLqgRVix+geaD ETkYwDuD8+SYnbOZ96cDUrcWnruajJue55fvz50cbiXnY9xOQcMe7Ks+B1nAR1oYrt mHtADOuEY3scS1vd2WkEIKcDjD9ZorOYC8F+ZYRZP2TMhbaJrw9WXtuLIWGLOaeg0b 1ki0v2MCSPMBv/G2b2KAwXDiJ1aX3kLjSp9F7JJrP61RmdyZOcPRL53PPlP7QSZmdx KTNELEuGeTtQw==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09JH3Lxg030711 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 19 Oct 2020 13:03:21 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 19 Oct 2020 10:03:19 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Mon, 19 Oct 2020 10:03:19 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Starlink --- "simpler than IPv6"
Thread-Topic: Starlink --- "simpler than IPv6"
Thread-Index: AdamM6ooCrvYXKKlS8eHo1KODLUqMQABeS5A
Date: Mon, 19 Oct 2020 17:03:19 +0000
Message-ID: <d5e27c812aac4c6a9c0809ac584d8938@boeing.com>
References: <becd5eca105d485882725453a61af3b1@boeing.com>
In-Reply-To: <becd5eca105d485882725453a61af3b1@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 0DD20C97949C99D9DCB6B68327177DC859F2E7EAD10719ACFC2E4B0A82A0FBBF2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WRByxemolmxsq6McpF0ySF_e3-M>
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 17:03:31 -0000

BTW, in addition to Iridium NEXT and Starlink there are other possible new
developments in LEO satellite constellations - OneWeb is another example,
and there may be others.

Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin (US), Fred L
> Sent: Monday, October 19, 2020 9:26 AM
> To: Alexandre Petrescu <alexandre.petrescu@gmail.com>om>; ipv6@ietf.org
> Subject: Re: Starlink --- "simpler than IPv6"
> 
> Alex, thanks for the good reminder about Iridium. Iridium did provide input to the
> ICAO discussions that "Iridium NEXT" will be an IPv4-only service. We determined
> that we could accommodate IPv6 end system communications over their service
> using IPv6-in-IPv4 encapsulation ala' RFC5214 or possibly even RFC2529. But, we
> would not use the RFC5214 LLA format - we would use OMNI LLA format instead.
> IPv6/IPv4 translation could also play a role in the data plane....
> 
> Thanks - Fred
> 
> > -----Original Message-----
> > From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> > Sent: Monday, October 19, 2020 9:09 AM
> > To: ipv6@ietf.org
> > Subject: [EXTERNAL] Re: Starlink --- "simpler than IPv6"
> >
> > This message was sent from outside of Boeing. Please do not click links or open attachments unless you recognize the sender and
> > know that the content is safe.
> >
> >
> > 'Simpler than IPv6' might mean a smaller and easier to use device than
> > the bigger core routers which currently are known to run IPv6 natively.
> >
> > I doubt though that the Starlink service will be on IPv6.  That service
> > might be NATted IPv4, or maybe no IP at all - a network layer-less
> > application-specific protocol, maybe http over satellite.
> >
> > When Starlink service comes up it wont be in a vacuum.  At least Iridium
> > upgraded their services continuously, up to a point that nowadays one
> > can buy easily a cheap device with subscription comparable to ADSL, that
> > offers DHCP on WiFi on one hand, and Iridium on another hand gatewayed
> > down to the Internet.  An Iridium consumer-oriented chip is not bigger
> > than a typical 4G chip for the same service.  It is 'simpler',
> > 'cheaper', 'smaller'.
> >
> > I remember also Toyota talked about a potential own satellite
> > constellation for their cars, and even went far with the novel Kismeta
> > antenna design for future cars.  I dont know where that constellation
> > plans are now.
> >
> > But I really dont know how the Starlink service is designed and whether
> > IPv6 has a place in it or no.  Let's see(?)
> >
> > Alex
> >
> >
> > Le 19/10/2020 à 17:13, Behcet Sarikaya a écrit :
> > > 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
> --------------------------------------------------------------------