[164218] 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 (Saku Ytti)
Sun Jun 30 04:32:20 2013

Date: Sun, 30 Jun 2013 11:15:14 +0300
From: Saku Ytti <saku@ytti.fi>
To: nanog@nanog.org
In-Reply-To: <870ED262-E77A-4FCF-9F31-B3716A416388@dotat.at>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On (2013-06-29 23:36 +0100), Tony Finch wrote:

> Reminds me of MinimaLT: http://cr.yp.to/tcpip/minimalt-20130522.pdf

ACK. Any cryptobased 0 RTT will necessarily have many things similar, and
indeed crypto is the key for low latency without major attack vectors.

But MinimaLT does not support multiplexing, which seems to be critical
design goal for QUIC.


I wonder how many years until this work materializes in practical NGL4, 10?
I'd really hate the final solution to be something riding on top of UDP,
because changing stuff is too hard.
Or should L4 be just 32b (16b SPORT, 16b DPORT) and L5 headers where magic
should live?

-- 
  ++ytti


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