From: Aaron Wood <woody77@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [Bloat] Really getting 1G out of ISP?
Date: Tue, 6 Jul 2021 15:13:59 -0700 [thread overview]
Message-ID: <CALQXh-PBYpRyre0iPe_d3jvZhD1yx77EbaL-GjqhMsV+ojVfjw@mail.gmail.com> (raw)
In-Reply-To: <383273DA-3700-469D-9FE2-524C9D21C4DA@cable.comcast.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Are these in-flux changes to where the upstream split is why some modems
report DOCSIS 3.1 downstream, but only 3.0 upstream? (and therefore aren't
enabling AQM on the upstream?)
-Aaron
On Tue, Jun 22, 2021 at 4:04 PM Livingood, Jason via Bloat <
bloat@lists.bufferbloat.net> wrote:
> > For DOCSIS the issue seems to be an unfortunate frequency split between
> up and downstream and use of lower efficiency coding schemes.
>
> Performance really takes a big step forward once a person has a D3.1 modem
> in their home, bringing OFDM and OFDMA as key advancements. Also in flux at
> the moment is where the upstream split is in cable networks, which are
> moving to mid-split or high-split designs that bring more upstream
> bandwidth. As well, over the past 18+ months, most cable networks have
> added substantially more upstream channels as well as performed quite a
> number of fiber node splits. And that is just below the physical layer
> stuff - there's also a lot of work at the software layer for modems and
> CMTSes that is quite interesting.
>
> JL
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1750 bytes --]
next prev parent reply other threads:[~2021-07-06 22:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:00 Stephen Hemminger
2021-06-22 6:12 ` Sebastian Moeller
2021-06-22 7:44 ` Giuseppe De Luca
2021-07-06 22:31 ` Aaron Wood
2021-07-07 2:26 ` Dave Taht
2021-07-07 2:53 ` Aaron Wood
2021-07-08 19:56 ` [Bloat] [Cake] " David P. Reed
2021-06-22 23:04 ` [Bloat] " Livingood, Jason
2021-06-23 15:56 ` Stephen Hemminger
2021-07-06 22:13 ` Aaron Wood [this message]
2021-07-06 22:28 ` Wheelock, Ian
2021-07-06 22:40 ` Aaron Wood
2021-07-07 2:10 ` Dave Taht
2021-07-07 9:27 ` Wheelock, Ian
2021-07-07 16:17 ` Jonathan Morton
2021-07-07 16:24 ` Wheelock, Ian
2021-06-22 22:51 ` Livingood, Jason
2021-06-29 19:48 ` Stephen Hemminger
2021-06-29 20:09 ` Sebastian Moeller
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=CALQXh-PBYpRyre0iPe_d3jvZhD1yx77EbaL-GjqhMsV+ojVfjw@mail.gmail.com \
--to=woody77@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=stephen@networkplumber.org \
/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