From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Rpm] broadband cost analysis
Date: Fri, 15 Apr 2022 14:48:05 +0000 [thread overview]
Message-ID: <7192A1F0-8747-4921-90BD-1E7FD565D9E7@cable.comcast.com> (raw)
In-Reply-To: <9363DD4A-BADD-4AD3-9730-406F5B3F7F3B@gmail.com>
On 4/14/22, 11:40, "Bloat on behalf of Rich Brown" <bloat-bounces@lists.bufferbloat.net on behalf of richb.hanover@gmail.com> wrote:
> $2K-$4K per premise for the drop cable from the pole and the router in the premise
What is the CPE router? Does it have AQM or some other latency control mechanism?
Thx!
Jason
next prev parent reply other threads:[~2022-04-15 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 15:18 [Bloat] " Dave Taht
2022-04-14 15:24 ` Dave Taht
2022-04-14 15:40 ` [Bloat] [Rpm] " Rich Brown
2022-04-15 14:48 ` Livingood, Jason [this message]
2022-04-15 15:28 ` Dave Taht
2022-04-14 17:28 ` [Bloat] " Michael Richardson
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7192A1F0-8747-4921-90BD-1E7FD565D9E7@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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