Re: [quicwg/base-drafts] Define transport parameters (#122)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



>  
 ## Crypto and Transport Handshake {#handshake}
 
 QUIC relies on a combined crypto and transport handshake to minimize connection
-establishment latency.  QUIC provides a dedicated stream (Stream ID 1) to be
-used for performing a combined connection and security handshake (streams are
-described in detail in {{streams}}).  The crypto handshake protocol encapsulates
-and delivers QUIC's transport handshake to the peer on the crypto stream.  The
-first QUIC packet from the client to the server MUST carry handshake information
-as data on Stream ID 1.
+establishment latency.  QUIC allocates stream 1 for the cryptographic handshake,
+which uses TLS.

I'm following the principles that I thought we had agreed: this version uses TLS (and only TLS) and a new version would be needed to change that.  We have a clear description of the interface between the two protocols that makes it a relatively easy process to forklift TLS.  What we don't need is some abstract definition of a "crypto handshake protocol" and then a specific embodiment of that.  That makes the protocol much harder to read and reason about.

My plan is to remove the entire "requirements on a crypto handshake protocol" section.  It's redundant with other more concrete text.  Any replacement crypto can then just provide the same services that TLS does (or not, because those services are not relevant in that context).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/122