From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] anyone for quic?
Date: Sat, 3 Feb 2018 16:51:18 +0100 [thread overview]
Message-ID: <2DC702DF-D73D-4833-81C7-1AFFE4D75069@gmail.com> (raw)
In-Reply-To: <CAA93jw5n7D2POhVML0BAhMHAtiXs1n2NMUZHwD4WK8ab_z9rww@mail.gmail.com>
> On Jan 30, 2018, at 9:17 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> https://github.com/lucas-clemente/quic-go
Cool, in case it ends up in flent one day I’d like to add that to the “flenter” tests.
Two things I noticed:
- It’s possible to use BBR with QUIC (not implemented in quic-go yet, https://github.com/lucas-clemente/quic-go/issues/341).
- QUIC accounts for 5% of Internet traffic as of 2017. Wow.
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
prev parent reply other threads:[~2018-02-03 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 8:17 Dave Taht
2018-02-03 15:51 ` Pete Heist [this message]
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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2DC702DF-D73D-4833-81C7-1AFFE4D75069@gmail.com \
--to=peteheist@gmail.com \
--cc=dave.taht@gmail.com \
--cc=flent-users@flent.org \
--subject='Re: [Flent-users] anyone for quic?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox