From: Benjamin Cronce <bcronce@gmail.com>
To: erik.taraldsen@telenor.com
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Fast snack, QUIC CAKE?
Date: Thu, 10 Aug 2017 19:16:40 -0500 [thread overview]
Message-ID: <CAJ_ENFHQodDtV9dUc6UC6aTnrpjRBGkrb8xVc=8G77CEYFWYEA@mail.gmail.com> (raw)
In-Reply-To: <1502267789764.33636@telenor.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
CAKE only works for endpoints you control. QUIC can benefit in situations
where you don't control the chokepoints. Not sure how QUIC interacts with
CAKE. I can't see it being more than a small percent better or worse.
On Wed, Aug 9, 2017 at 3:36 AM, <erik.taraldsen@telenor.com> wrote:
> Has anybody here done any experimentation on CAKE (and others) when using
> QUIC? Or other real world insights into other aspects of QUIC? For
> example proper CAKE and TCP version of youtube vs crappy quing/latency and
> QUIC.
>
>
> The overlapping design goals is making the user experience snappy, but
> QUICs approach is to control the end points with a new protocol to replace
> TCP. (Or improve TCP in the future).
>
>
> https://en.wikipedia.org/wiki/QUIC
>
>
>
> -Erik
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
[-- Attachment #2: Type: text/html, Size: 1507 bytes --]
next prev parent reply other threads:[~2017-08-11 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 8:36 erik.taraldsen
2017-08-11 0:16 ` Benjamin Cronce [this message]
2017-08-14 20:06 ` Dave Taht
2017-08-17 6:17 ` Jonathan Morton
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ_ENFHQodDtV9dUc6UC6aTnrpjRBGkrb8xVc=8G77CEYFWYEA@mail.gmail.com' \
--to=bcronce@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=erik.taraldsen@telenor.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