Re: [TLS] Request for review: Next Protocol Negotiation Extension

[Michael D'Errico <[e-mail]>]

Adam Langley wrote:
> 
> The computational overhead of TLS is unimportant for many applications
> and is only becoming less important over time.

Glad you agree.

> However, the number of round trips is critical. However fast the hosts
> might be, the speed of light always stays the same.

So then NPN is all about reducing a round trip?  You say you already
achieve that with false start.  Or do you need something in addition
that can only be achieved by sticking it in a TLS extension?

Sorry if this was answered before, but it is really hard to follow a
single message that is a line-by-line reply to 4 other messages.

<Somewhat off topic>

Every morning when I first get to my computer, I have to log in.  That
takes a few seconds.  My browser is already running because I hardly
ever shut it down.  I proceed to click the EXACT SAME 4 LINKS that I
click every morning.  I then wait several seconds for these pages to
load.

Do you see the problem here?  Everything waits for me to initiate an
action that is predictable.  The moment I touch the mouse, it is 100%
predictable which 4 links I'm going to click on within the next 15
seconds.  Yet nothing happens until after I type my password, after I
unhide the browser window, after I create 4 tabs, and then click on
the links.

This should all happen automatically so that I don't have to wait at
all for any of these four pages to load.  They will likely be fully
loaded and presentable before I even finish typing my password.

THAT is what you should be working on.  Prediction.  If I've clicked
the same link every morning for the past 18 months, what are the odds
that I'm going to click it today?  100%.  And even if for some reason
I don't, I'm not going to be at all upset that my browser fetched the
page for me.

</Somewhat off topic>

Mike