Re: Starlink --- "simpler than IPv6"

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 19 October 2020 19:24 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 86C013A0039 for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 12:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level:
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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 5RLiGqWayd8P for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2020 12:24:48 -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 843EB3A003F for <ipv6@ietf.org>; Mon, 19 Oct 2020 12:24:48 -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 09JJOhOv018972; Mon, 19 Oct 2020 15:24:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1603135485; bh=L3pPIDkW2K06hqIm7po/SXIOoCYlbGnHzUUUhD0Ucys=; h=From:To:CC:Subject:Date:From; b=g7QZtwHQ+d8OMd4duX2X3GBnhcwTde9DVOszaH/gQfYsR9cS8tWPKyKUTJ/zcqam2 4zhtGtkd2COZPh8CoXhOB6VqrpK7KGNAfo6b1WUr2mEPLx12aGlQTs4QXQtBevM5yt BlfDhbL5ycvx5fgko1Jk8f6qcUCnl6i0OHjiH4gcW8TxnaIw/V9jxxZepUUW4SE402 /J+D5fOQrIcNxaTO3brYx2ZWhP5ewpedP38Qdy+E49r50HfMXl7YWOcpJ5dW8UHQC2 kdspLNnvlUnKCi5+GhQHsmc0RkDae+8AuXgrK9XvgSi3jqQJG0TuWgbNysjQ9mgk61 GishgjPW0IQcw==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09JJOZEn017674 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 19 Oct 2020 15:24:35 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) 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 12:24:33 -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 12:24:33 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: 6man WG <ipv6@ietf.org>
Subject: Re: Starlink --- "simpler than IPv6"
Thread-Topic: Starlink --- "simpler than IPv6"
Thread-Index: AdamTSYZCrvYXKKlS8eHo1KODLUqMQ==
Date: Mon, 19 Oct 2020 19:24:33 +0000
Message-ID: <f2c646b0a2434a1198dca54343db8f78@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: 4AC6BE2971877D69EB721BBF4E37DB6429CC17E0EA95F058CB1CBD6D19CE74BA2000:8
Content-Type: multipart/alternative; boundary="_000_f2c646b0a2434a1198dca54343db8f78boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SDdByExt88nNpUp_o1pl1VqKd7o>
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 19:24:51 -0000

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?

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<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>>>
> 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>
> <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>>>; 6man WG <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>>>
> *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>>> 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>>
> http://www.sandelman.ca/ <http://www.sandelman.ca/>        | ruby on
> rails    [
>
>
> ____
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.org> Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------