[quicwg/base-drafts] Single Packet Number Space (#1591)

[Nick Banks <[e-mail]>]

Fixes #1579 (see for more details on the problem).

- Moves back to a single packet number space across all encryption levels.
- Allows for a packet to be acknowledged in a greater than or equal encryption level.
- Initial packets cannot carry ACK frames, and therefore must be acknowledged in Handshake (or greater) encryption level.
- Handshake packets can acknowledge 0-RTT packets.

With these design changes, implementations do not have to track 3 separate packet number spaces (and all the overhead that goes with it). The number of QUIC packets (not UDP datagrams) required to be sent during the handshake is reduced (see Example Handshake Flows section). There is no Initial packet ACK spoofing since they must be acknowledged in a higher encryption level. 0-RTT packets can be acknowledged a bit quicker in the handshake process by using the Handshake encryption level; generally the first server ACK block will be able to ACK all Initial and 0-RTT packets it has received in one atomic operation.

Also makes sure #1018 and #1413 don't regress and are still solved.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/1591

-- Commit Summary --

  * Single Packet Number Space
  * Finish up changes

-- File Changes --

    M draft-ietf-quic-recovery.md (32)
    M draft-ietf-quic-tls.md (28)
    M draft-ietf-quic-transport.md (139)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/1591.patch
https://github.com/quicwg/base-drafts/pull/1591.diff

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