From: Dave Taht <dave.taht@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Doug Sicker <dsicker@bitag.org>
Subject: Re: [Starlink] BITAG Paper - Seeking LEO Experts
Date: Thu, 11 May 2023 08:12:56 -0700 [thread overview]
Message-ID: <CAA93jw7wwPni+jXy+BtooygF4Z0jBsNMM4bPiVGDopt_sFO7CA@mail.gmail.com> (raw)
In-Reply-To: <2B2F585E-207B-4623-A9AE-A4ACC793C206@cable.comcast.com>
I would like to give a +1 to BITAG´s efforts. It is a chance to write
a technically accurate document that can be presented a higher policy
layer. I enjoyed my time on the "understanding latency" project
(although I think the single most effective thing I did was recruit
stuart cheshire to the team, whose wordsmithing and erudition dwarfs
mine!)
It is a pretty significant time sump however, and if I could somehow
sucker^H^H^H^Hencourage someone else with a background in these areas
into joining this latest effort, I won´t have to. I would really like
to see a sane systems approach to expanding the internet in all its
aspects.
PS Recently a truly remarkable blog citing BITAG´s recent work on
secure routing using "the prisoner" analogies appeared.
https://ntia.gov/blog/2023/secure-internet-routing
On Thu, May 11, 2023 at 6:56 AM Livingood, Jason via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> The BITAG (https://www.bitag.org/) is working on it’s next paper – this one an updated technical overview of various broadband access network types (LEO, DOCSIS, PON, etc.). It is hoped this can inform US states and other grant makers in the coming years as they seek to expand broadband service to unserved areas.
>
> To this end we are seeking LEO access network experts to help. If you think you are able to help – please contact the executive director - Doug Sicker dsicker@bitag.org.
>
>
>
> Thanks!
> Jason
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
prev parent reply other threads:[~2023-05-11 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 13:56 Livingood, Jason
2023-05-11 15:12 ` Dave Taht [this message]
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7wwPni+jXy+BtooygF4Z0jBsNMM4bPiVGDopt_sFO7CA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=dsicker@bitag.org \
--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