Re: [quicwg/base-drafts] Rejection of 0-RTT: start over? (#761)

[Martin Thomson <[e-mail]>]

@mikkelfj got it right.  This is what we do for TLS 1.3 now.  Simple example: we want to send "GET /favicon.ico", we have a 0-RTT capable ticket.  We start TLS 1.3 and h2 and send the request.  If we get a reject, we will mark the request as needing retry and try again.  We throw away all h2 state at that point.  The same connection can be used, but all the other intermediate stuff goes away.  The request is matched to the "new" connection and it starts over, even reassessing the protocol.  That is, if we get http/1.1 (which is possible), it works.

That's a bit of a pain to implement correctly, but not too bad if you get the abstractions right.  I think that the way we do it (@ddragana can confirm) is to add the connection back to the connection pool so that it gets picked up as though it were a new one.

-- 
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/issues/761#issuecomment-331779142