Since the designers of SPDY also figured security is important, they made use of TLS' protocol negotiation feature: they actually announce themselves as a TLS protocol in these first milliseconds of a HTTPS connection. Brilliant.
For more information, see: http://www.chromium.org/spdy/spdy-protocol/spdy-protocol-dra...
The way you describe it comes of as more complicated?!
Of the things to note is that nothing of SPDY describes encryption, which is why a lot of people have thought about using it without TLS via some other negotiation strategy (but nobody have really implemented this, since the value is only minor/non-existent outside internal networks).
And now excuse me, i have to have a look at what happens when authenticating with my wlan router at the same level of depth :)
I figured that enough time had passed since the last time since it's such an excellent article. ;-)
What does my cellphone send to the nearest cell-phone tower?
What does the cell-phone tower send to the phone company servers? How do they tie back together packets coming back from https://news.ycombinator.com back to my phone?
To me, it seems better to use a possible-to-crack SSL with hidden hostname vs. hard/impossible to crack TLS where anyone can see I'm trying to go to https://anonymous-upload.wikileaks.org.
If it's a self-signed certificate scrubbed from anything identifiable then a server could still try to correlate what website you visited by the public key from the certificate.
FWIW, it was the first time I'd seen it. Very comprehensive.