From: Bruce Atherton <bruce@callenish.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Google's QUIC has reached NANOG
Date: Fri, 28 Jun 2013 16:17:04 -0700 [thread overview]
Message-ID: <51CE1970.8010606@callenish.com> (raw)
In-Reply-To: <CAM6V40cBQMQVpEL7-iV9po3k1nKKCV2t_FjLJERKDunNNTVjng@mail.gmail.com>
On 28/06/2013 3:05 PM, Justin Andrusk wrote:
>
> So am I the only one concerned that they are looking to use udp
> instead of tcp?
>
>
It is an important part of the design. They want to multiplex streams
into a single connection, and ordered packets means one lost packet in
one stream holds up all the streams. Only way around that is with
something other than TCP right now. This is a major downside of
multiplexing SPDY over using multiple connections, which I believe was
one of the prime motivators to develop QUIC.
In the FAQ, they mention that they are hoping once they get a good
design in QUIC some of its ideas can be moved into TCP. Someday.
next prev parent reply other threads:[~2013-06-28 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 21:54 Hal Murray
2013-06-28 22:05 ` Justin Andrusk
2013-06-28 23:17 ` Bruce Atherton [this message]
2013-06-28 23:19 ` Dave Taht
2013-06-28 23:47 ` Jim Gettys
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=51CE1970.8010606@callenish.com \
--to=bruce@callenish.com \
--cc=bloat@lists.bufferbloat.net \
/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