From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] the future is in high speed symmetrical internet speeds!!!!
Date: Mon, 5 Jul 2021 23:21:21 +0200 [thread overview]
Message-ID: <D98ED57A-9ADB-452B-AE28-ED6F0C46AD82@gmx.de> (raw)
In-Reply-To: <CAA93jw7iyF1iy6k1sETaup41J80f2pGfJ54mNX5kURD5gN_pew@mail.gmail.com>
Hi Dave,
Well, less asymmetric down/up ratios are certainly worth fighting for (for one NTP should work better). And, as I might add, something that is orthogonal to better router software ;) a fast symmetric link with a craptastic router is still roughly as much fun as a dial-up connection with the best router software we can wish for... ;)
Regarding that EFF article, while I think that light over fiber is "the obvious way forward", I fear that the strategy of asking for 100/100 under the assumption, it can only be reliably achieved by fiber roll out, ignores the full duplex technologies that are either ready for deployment (full duplex g.fast) or a much cheaper plant upgrade away than rolling our new fiber (full duplex docsis comes to mind, which might require changes to the physical plant layout with nested/hierarchical amplifiers*). I note that local docsis ISPs in Germany are aiming for 100 Mbps upload in the next 12-24 months (simply by switching more upload spectrum to docsis 3.1 coding schemes). In short 100/100 might not be the "only with fiber" speed grade the authors seem to think, and if the goal is full fiber than it seems best to actually require full fiber.
Best Regards
Sebastian
*) Or not might be possible to run full duplex over some level of hierarchical amplifiers...
> On Jul 5, 2021, at 20:46, Dave Taht <dave.taht@gmail.com> wrote:
>
> or at least, in more politicking, for fiber.
>
> https://www.eff.org/deeplinks/2021/07/future-symmetrical-high-speed-internet-speeds
>
> I emailed the authors and mentioned that better routers might be a
> cheaper start...
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2021-07-05 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 18:46 Dave Taht
2021-07-05 21:21 ` Sebastian Moeller [this message]
2021-07-06 10:43 ` [Cerowrt-devel] [Bloat] " Wheelock, Ian
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=D98ED57A-9ADB-452B-AE28-ED6F0C46AD82@gmx.de \
--to=moeller0@gmx.de \
--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