Re: [quicwg/base-drafts] TLS interface overview (#30)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



> +Additional functions might be needed to configure TLS.
+
+
+### Handshake Interface
+
+In order to drive the handshake, TLS depends on being able to send and receive
+handshake messages on stream 1.  There are two basic functions on this
+interface: one where QUIC requests handshake messages and one where QUIC
+provides handshake packets.
+
+A QUIC client starts TLS by requesting TLS handshake octets from
+TLS.  The client acquires handshake octets before sending its first packet.
+
+A QUIC server starts the process by providing TLS with any stream 1 octets that
+might have arrived.  Only in-sequence packets are delivered; packets that arrive
+out of order are buffered by QUIC until all preceding packets are available.

Should this be "frames"?  Packets might be lost and retransmitted, so you wouldn't necessarily have preceding packets becoming available.  (Not including in the purely-editorial commit I'm preparing, because I'm not certain if that's the correct wording.)

-- 
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/30#pullrequestreview-11928784