[164180] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Google's QUIC

daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Jun 28 17:04:51 2013

In-Reply-To: <CAPhg-wTi7d7S1_ATj-iuR-g2FYAi8oqnBTaAS1UEsL3chAM+Yw@mail.gmail.com>
Date: Fri, 28 Jun 2013 17:00:08 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Phil Fagan <philfagan@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Fri, Jun 28, 2013 at 4:49 PM, Phil Fagan <philfagan@gmail.com> wrote:
> "In the presence of layer-3 load-balancers, a multiplexed transport has the
> potential to allow the different data flows, coming and going to a client,
> to be served on a single server." - Google
>
> I'll drink the juice

i don't think much juice is required... doesn't that just say that the
same 'flow' will follow the same path through the network? and that
most/all (save a10/yahoo!) loadbalancers just LB based on 5-tuple (at
best)? so keeping things in a single flow/stream/5-tuple will drop
packets from one host deterministicaly on a single other host at the
far side?


home help back first fref pref prev next nref lref last post