From: dan <dandenson@gmail.com>
To: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
Cc: Dave Taht <dave.taht@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Fwd: A quick report from the WISPA conference
Date: Sat, 12 Nov 2022 09:15:51 -0700 [thread overview]
Message-ID: <CAA_JP8U-KC663yH0KBVxiF5FoNpBB6gSKx=hN3rd0OCqgh8+pw@mail.gmail.com> (raw)
In-Reply-To: <CAOZyJot1oWWfcdfCJZ3V+tiXuk5KKJNfM=Q+2uJbSBr_jgUbEQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Sat, Nov 12, 2022 at 9:09 AM Robert Chacón <
robert.chacon@jackrabbitwireless.com> wrote:
>
>
> Regarding TCP acceleration, I'm leaning toward the argument made by Dan
> from Preseem <https://youtu.be/3r4FWGKho3c?t=1879> that QUIC adoption is
> growing pretty quickly and we may not want to mess with TCP at the expense
> of UDP given the rise of QUIC.
> Cloudlfare says HTTP/3 and QUIC are already at 28% and growing
> <https://radar.cloudflare.com/adoption-and-usage?range=28d>.
> One point he brought up is that if we use TCP acceleration, and a
> middlebox has to be rebooted or something - all client TCP sessions will
> break when OSPF switches paths around the box.
>
>
>
I'll buy that. TCP accelleration is a *TODAY* fix with a decreasing gain
as time goes on.
[-- Attachment #2: Type: text/html, Size: 1493 bytes --]
next prev parent reply other threads:[~2022-11-12 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw77h=ztEOzyADriH2PnswUDQiyNvBdsuFi+K5EexpoxUQ@mail.gmail.com>
[not found] ` <938D9D45-DADA-4291-BD8A-84E4257CEE49@apple.com>
[not found] ` <CAA93jw4KOkgdfT2LunCtPYPjXL+=OtTrouJgPjM7U1bHKtErnw@mail.gmail.com>
[not found] ` <CACTgmGpgDjWF4d_+Kga4CL4vxb-YQ91Lu1U6Zt5vca0EGSwQ2w@mail.gmail.com>
[not found] ` <CAA93jw4f701R+4B538jF1+qAW=cUgP35EmWy8VZG-1h=w8woOA@mail.gmail.com>
2022-11-12 15:11 ` Dave Taht
2022-11-12 15:36 ` dan
2022-11-12 16:09 ` Robert Chacón
2022-11-12 16:15 ` dan [this message]
2022-11-12 17:19 ` Herbert Wolverson
2022-11-12 17:39 ` dan
2022-11-12 19:30 ` [LibreQoS] Various aspects of net neutrality Dave Taht
2022-11-12 19:58 ` dan
2022-11-14 13:45 ` Sascha Meinrath
2022-11-13 6:13 ` [LibreQoS] Fwd: A quick report from the WISPA conference Hayden Simon
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA_JP8U-KC663yH0KBVxiF5FoNpBB6gSKx=hN3rd0OCqgh8+pw@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=robert.chacon@jackrabbitwireless.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