Re: Starlink --- "simpler than IPv6"

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
> --------------------------------------------------------------------
>
>