From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Google's QUIC has reached NANOG
Date: Fri, 28 Jun 2013 19:47:30 -0400 [thread overview]
Message-ID: <CAGhGL2CJtOGDuN2SiP4ssjTwAf+DKNsb4enu3NNWcv=gWHejNQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6bi8JEoy+i8jzVRqc3kJisT-SvoGWzr+PQjpcCiCu7UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
I'm a fan of minion, myself. (along with ccn, in the revolutionary
category).
http://csweb1.fandm.edu/jiyengar/papers/minion-pfldnet2010.pdf
Jim
On Fri, Jun 28, 2013 at 7:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
> The design document is a very valuable read. Tons of good ideas in there...
>
>
> https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34/preview?sle=true
>
> On Fri, Jun 28, 2013 at 4:17 PM, Bruce Atherton <bruce@callenish.com>
> wrote:
> > 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.
> >
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 3221 bytes --]
prev parent reply other threads:[~2013-06-28 23:47 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
2013-06-28 23:19 ` Dave Taht
2013-06-28 23:47 ` Jim Gettys [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.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='CAGhGL2CJtOGDuN2SiP4ssjTwAf+DKNsb4enu3NNWcv=gWHejNQ@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=bloat@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