[quicwg/base-drafts] Single Stream of Bytes for CRYPTO Frames (#1592)

[Nick Banks <[e-mail]>]

Currently, the spec states:

> There is a separate flow of cryptographic handshake data in each encryption level, each of which starts at an offset of 0. This implies that each encryption level is treated as a separate CRYPTO stream of data.

This means you must track set of bytes in each encryption level (Initial, 0-RTT, Handshake and 1-RTT) as a separate stream and manage them accordingly; separate outstanding sent byte ranges, recovery ranges, acked ranges.

Additionally, it makes it a little unclear where one 'stream' stops and another 'starts'. For instance, in the 0-RTT case, the client (is supposed to) sends EOED with 0-RTT key, immediately followed by (ideally in the same UDP datagram, but not required) FIN with the Handshake key. If the 0-RTT EOED is lost, but the FIN isn't it could look like the client just skipped EOED. Instead, if they were all in the same stream, with FIN's offset starting where EOED left off, it would be easier to track this.

For these reasons, I propose each CRYPTO stream in each encryption level's offset starts where the previous level stopped.

-- 
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/1592