Re: [quicwg/base-drafts] Define terms for application actions (#2857)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



> +
+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
+- be informed when 0-RTT has been accepted or rejected by a server.
+
+When implementing the server role, applications need to be able to:
+
+- listen for incoming connections, which prepares for the exchange described in
+  {{handshake}};
+- if Early Data is supported, embed application-controlled data in the TLS
+  resumption ticket sent to the client; and
+- if Early Data is supported, retrieve application-controlled data from the
+  client's resumption ticket and enable rejecting Early Data based on that
+  information.

Added to stream requirements, but now I'm not so sure that's correct.  Early-Data has to be added when the server "forwards a request prior to the completion of the TLS handshake".  That would mean the server really only needs a yes/no about the current state of the connection when the request is being forwarded.  If the handshake has completed, it doesn't matter that the request was originally early -- it's now retroactively validated as a non-replay by the successful handshake.

-- 
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/2857#discussion_r310233324