Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical a spects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	dickroy@alum.mit.edu,
	Frantisek Borsik <frantisek.borsik@gmail.com>
Subject: Re: [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF	Application
Date: Wed, 13 Dec 2023 18:46:47 -0800	[thread overview]
Message-ID: <55037f9a-bc2c-4bbb-a4bb-47ad30f16190@rjmcmahon.com> (raw)
In-Reply-To: <CAJUtOOi_-OsgRPSLvCV0UpDCQjv+R61uf02fxYW1PbkEQy4hqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3468 bytes --]

I think this common in that appointment of commissioners go through a political process. The FCC has a technology group, too. When I worked with them about 8 years ago, they had skilled researchers on staff and a highly skilled director. They asked good questions about engineering decisions, like what is limiting the number of mimo streams on devices.

Their physical facility is a bit dated, and they don't get stock grants. I respect the engineers I worked with for what they did.

⁣Bob

On Dec 13, 2023, 2:38 PM, at 2:38 PM, Frantisek Borsik via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>I would love for Nathan to be here with us, and comment on that :-) so
>I
>will add NN list as well.
>
>
>All the best,
>
>Frank
>Frantisek (Frank) Borsik
>
>https://www.linkedin.com/in/frantisekborsik
>Signal, Telegram, WhatsApp: +421919416714
>iMessage, mobile: +420775230885
>Skype: casioa5302ca
>frantisek.borsik@gmail.com
>
>
>On Wed, 13 Dec 2023 at 11:21 PM, Richard Roy <dickroy3777@comcast.net>
>wrote:
>
>>
>>
>>
>> ------------------------------
>>
>> *From:* Starlink [mailto:starlink-bounces@lists.bufferbloat.net] *On
>> Behalf Of *Frantisek Borsik via Starlink
>> *Sent:* Wednesday, December 13, 2023 1:26 PM
>> *To:* Dave Taht via Starlink
>> *Subject:* [Starlink] FCC Upholds Denial of Starlink’s RDOF
>Application
>>
>>
>>
>> “*Elon Musk*’s Starlink was not the only major company to inflate its
>> capabilities
>>
><https://broadbandbreakfast.com/2021/04/rdof-reverse-auction-criticized-google-makes-pandemic-gains-california-broadband-access-for-k-12/>
>in
>> RDOF bids. Nearly 100 bidders have defaulted since the auction,
>leaving in
>> limbo an estimated $2.8 billion
>>
><https://broadbandbreakfast.com/2023/06/what-happens-to-the-estimated-2-8-billion-in-rdof-defaults/>
>of
>> the $9.2 billion originally awarded.
>>
>>
>>
>> The FCC upheld another denial
>>
><https://broadbandbreakfast.com/2023/12/fcc-proposes-22-million-fine-against-ltd-over-rdof/>
>>  on Monday in the case of LTD Broadband, which appealed the
>commission’s
>> finding that it could not reasonably serve the more than 500,000
>locations
>> to which it had committed. The commission also hit LTD with a $21.7
>million
>> fine for its default.
>>
>> The commission’s two Republicans dissented to Starlink’s denial,
>claiming
>> they saw a path for the company to improve its speeds before the
>first
>> deployment deadline in 2025.”
>>
>> *[RR] The reason two lawyers “saw a path” is because they were
>> bribed/conned into to see it. In my nearly 50years of experience
>dealing
>> with the FCC, extremely rarely are the people at the top in the
>commission
>> tech savvy.  In general, they have NO CLUE when it comes to
>technology …
>> period! **JJ*
>>
>>
>>
>>
>>
>https://broadbandbreakfast.com/2023/12/fcc-upholds-denial-of-starlinks-rdof-application/
>>
>>
>>
>>
>> All the best,
>>
>> Frank
>> Frantisek (Frank) Borsik
>>
>> https://www.linkedin.com/in/frantisekborsik
>> Signal, Telegram, WhatsApp: +421919416714
>> iMessage, mobile: +420775230885
>> Skype: casioa5302ca
>> frantisek.borsik@gmail.com
>>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Nnagain mailing list
>Nnagain@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/nnagain

[-- Attachment #2: Type: text/html, Size: 12008 bytes --]

  reply	other threads:[~2023-12-14  2:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJUtOOi7rSiPTFGVkadh4XPvFOnmzLidX5=7-LTJnoiyPauNag@mail.gmail.com>
     [not found] ` <A8DC9114A92F47D5AAE1D332B5E5007D@SRA6>
2023-12-13 22:38   ` Frantisek Borsik
2023-12-14  2:46     ` Robert McMahon [this message]
2023-12-14  6:11       ` Frantisek Borsik
2023-12-14 17:48         ` David Bray, PhD
2023-12-14 18:47           ` Frantisek Borsik
2023-12-14 18:51           ` Nathan Simington
2023-12-14 19:44             ` Frantisek Borsik
     [not found]             ` <f7d6522d-db06-4ee6-a814-76810ad01e1f@gmail.com>
     [not found]               ` <ZXxIdbzif5ogB0IQ@Space.Net>
     [not found]                 ` <02cc2879-ef99-4388-bc1e-335a4aaff6aa@gmail.com>
     [not found]                   ` <ZXxKMZ-pEbS4QAzW@Space.Net>
2023-12-15 12:46                     ` Frantisek Borsik
2023-12-15 13:24                       ` Gert Doering
2023-12-15 13:40                       ` Sebastian Moeller
2023-12-15 18:06                         ` David Lang
2023-12-15 18:51                           ` rjmcmahon
2023-12-15 19:13                             ` David Lang
2023-12-15 21:29                               ` rjmcmahon
2023-12-15 21:42                                 ` David Lang
2023-12-15 22:04                                   ` David Bray, PhD
2023-12-15 22:10                                     ` David Lang
2023-12-15 22:13                                       ` David Bray, PhD
2023-12-15 22:33                                         ` Kenline, Doug
2023-12-15 22:36                                         ` Dave Taht
2023-12-17 21:22                                           ` Tanya Weiman
     [not found]                                         ` <de59330f-e05a-4c2e-9d64-e2821f113e76@gmail.com>
2023-12-19 20:49                                           ` [NNagain] detecting GPT-generated text Rich Brown
2023-12-22 12:23                                             ` le berger des photons
2023-12-22 13:06                                               ` Rich Brown
2023-12-15 22:05                                   ` [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF Application rjmcmahon
2023-12-15 22:13                                     ` David Lang
2023-12-15 22:26                                   ` Dave Taht
2023-12-16  4:16                                     ` David Lang
2023-12-16 17:30                                       ` rjmcmahon
2023-12-16 18:18                                         ` Dick Roy
2023-12-16 18:48                                         ` Robert McMahon
2023-12-16 21:44                                           ` Frantisek Borsik
2023-12-16 22:28                                             ` Robert McMahon
2023-12-17  0:25                                               ` Dave Taht
2023-12-23 21:17                                                 ` J Pan
2023-12-18  8:25                                               ` David Lang
2023-12-17  1:54             ` [NNagain] other fcc services at sea Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55037f9a-bc2c-4bbb-a4bb-47ad30f16190@rjmcmahon.com \
    --to=rjmcmahon@rjmcmahon.com \
    --cc=dickroy@alum.mit.edu \
    --cc=frantisek.borsik@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=starlink@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox