Re: [quicwg/base-drafts] Applications need to disable or selectively reject 0-RTT (#3138)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> @@ -1159,7 +1159,7 @@ the operations described in this section on a QUIC connection.
 When implementing the client role, applications need to be able to:
 
 - open a connection, which begins the exchange described in {{handshake}};
-- enable 0-RTT; and
+- disable or selectively reject 0-RTT; and

That was silly.  I think that "enable 0-RTT *when available*" suffices.  We don't need to go into detail about 0-RTT keys or any of that mess, that's an internal concern of the transport.

For our stack, we enable 0-RTT always (you can't turn it off), and rely on applications using the handshake state to determine whether what is being sent is 0-RTT (or 0.5-RTT) or not.  If there is no 0-RTT, then attempts to create streams will fail.

-- 
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/3138#discussion_r338347580