[164214] in North American Network Operators' Group
Re: Google's QUIC
daemon@ATHENA.MIT.EDU (Darius Jahandarie)
Sat Jun 29 10:27:59 2013
In-Reply-To: <51CECACD.3070206@Janoszka.pl>
Date: Sat, 29 Jun 2013 10:27:48 -0400
From: Darius Jahandarie <djahandarie@gmail.com>
To: Grzegorz Janoszka <Grzegorz@janoszka.pl>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sat, Jun 29, 2013 at 7:53 AM, Grzegorz Janoszka <Grzegorz@janoszka.pl> wrote:
> I am surprised nobody mentioned security issues. To minimize latency the
> following would be best: the client sends one UDP packet and receives
> stream of UDP packets with page code, styles, images and whatever else
> could be needed. The waiting time is just RTT plus browser processing.
>
> I am sure Google considered it, so I am really curious how they are
> going to solve it.
Of course they consider this. Read the "CONNECTION ESTABLISHMENT and
RESUMPTION" section of their design document [1]. If you're familiar
with TCP Fast Open, many of its techniques are reused.
[1] https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34/edit
--
Darius Jahandarie
