The following errata report has been verified for RFC9000, "QUIC: A UDP-Based Multiplexed and Secure Transport".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7365 -------------------------------------- Status: Verified Type: Editorial Reported by: yongboy <yong...@gmail.com> Date Reported: 2023-02-23 Verified by: Francesca Palombini (IESG) Section: 12.4. Original Text ------------- | 0x19 | RETIRE_CONNECTION_ID | Section 19.16 | __01 | | Corrected Text -------------- | 0x19 | RETIRE_CONNECTION_ID | Section 19.16 | ___1 | | Notes ----- Based on the context and section 12.5 ending says: Note that it is not possible to send the following frames in 0-RTT packets for various reasons: ACK, CRYPTO, HANDSHAKE_DONE, NEW_TOKEN, PATH_RESPONSE, and RETIRE_CONNECTION_ID. A server MAY treat receipt of these frames in 0-RTT packets as a connection error of type PROTOCOL_VIOLATION. So, I think the RETIRE_CONNECTION_ID frame should not appear in the 0-RTT packet, only contained in the 1-RTT package. -------------------------------------- RFC9000 (draft-ietf-quic-transport-34) -------------------------------------- Title : QUIC: A UDP-Based Multiplexed and Secure Transport Publication Date : May 2021 Author(s) : J. Iyengar, Ed., M. Thomson, Ed. Category : PROPOSED STANDARD Source : QUIC Stream : IETF Verifying Party : IESG
