From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] ntia broadband RFC
Date: Thu, 20 Jan 2022 15:11:10 +0000 [thread overview]
Message-ID: <6EB1B7F0-A906-4254-8DD7-8EAE47DB7490@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw6NE+GJK2UDfCx_Qvb_knpVXhcmRWUV_8d+WVdPYSwRMw@mail.gmail.com>
In my personal opinion, these agencies are usually quite happy to have comments from technical experts. If any of you do make comments, making them concise and not too complex will tend to ensure they are widely read and internalized. ;-)
In the details, I could certainly see folks in this community being able to credibly comment on question 13 [1] given its mention of latency and quality.
Jason
[1] "What guidance or requirements, if any, should NTIA consider with respect to network
reliability and availability, cybersecurity, resiliency, latency, or other service quality features and
metrics? What criteria should NTIA establish to assess grant recipients’ plans to ensure that service providers maintain and/or exceed thresholds for reliability, quality of service, sustainability, upgradability and other required service characteristics?"
On 1/18/22, 16:19, "Bloat on behalf of Dave Taht" <bloat-bounces@lists.bufferbloat.net on behalf of dave.taht@gmail.com> wrote:
This is the first time in years that I felt that maybe something we
said could get through to an agency of the US government. The deadline
for filing is feb 4th,
and it would be nice if some of the billions on the table got spent on
better routers, software, and networks.
https://urldefense.com/v3/__https://ntia.gov/files/ntia/publications/fr-iija-broadband-rfc.pdf__;!!CQl3mcHX2A!TEn3rSNYwOHZ6E_RnvIDoIT2cXlisfhHkmtpnbIfCiAk63Rac2aqOnzG6nZnLUlLAE9NwQ$
In their RFC there are 36 questions, some of which are pretty good.
I've been participating a bit in this forum:
https://urldefense.com/v3/__https://discuss.broadband.money/c/broadband-grant-events/scott-woods-ama__;!!CQl3mcHX2A!TEn3rSNYwOHZ6E_RnvIDoIT2cXlisfhHkmtpnbIfCiAk63Rac2aqOnzG6nZnLUlnwITAjA$
among other things I dragged out last week was the "upgrade in place"
idea. There's 3 weeks or so to come up with
something worth filing, but as usual these days I'm always looking for
collaborators?
--
I tried to build a better future, a few times:
https://urldefense.com/v3/__https://wayforward.archive.org/?site=https*3A*2F*2Fwww.icei.org__;JSUl!!CQl3mcHX2A!TEn3rSNYwOHZ6E_RnvIDoIT2cXlisfhHkmtpnbIfCiAk63Rac2aqOnzG6nZnLUnbOe7hAA$
Dave Täht CEO, TekLibre, LLC
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!TEn3rSNYwOHZ6E_RnvIDoIT2cXlisfhHkmtpnbIfCiAk63Rac2aqOnzG6nZnLUnPllTvyw$
next prev parent reply other threads:[~2022-01-20 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 21:19 [Cerowrt-devel] " Dave Taht
2022-01-20 15:11 ` Livingood, Jason [this message]
2022-01-20 19:50 ` [Cerowrt-devel] [Bloat] " Dave Taht
2022-02-01 20:38 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6EB1B7F0-A906-4254-8DD7-8EAE47DB7490@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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