Subject: Consensus calls, Post-Singapore

From: Mark Nottingham <[email-masked]>
Date: Fri, 29 Nov 2019 12:40:38 +1100

The following issues have proposals for resolution, and discussion so far seems to support consensus to accept them. If you object, please do so on the issue or in response to this message (changing the Subject appropriately!). Absent any pushback, we'll direct the editors to incorporate them late next week.

Note that this group of issues includes some HTTP and recovery issues, as those documents are now under the Late Stage Process.

See <https://github.com/quicwg/base-drafts/projects/5> for the current state of issues in the Late Stage process, itself defined at <https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.

* #3258: Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 bytes
   The proposal is <https://github.com/quicwg/base-drafts/pull/3186>

* #3256: Packet reordering thresholds less than 3 are not sufficiently reordering tolerant
   The proposal is <https://github.com/quicwg/base-drafts/pull/3240>

* #3200: Definition of "active connection ID" is misleading (or the name is)
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3197: active_connection_id_limit defaults to 0
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3193: active_connection_id_limit interacts poorly with Retire Prior To
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3159: Server should not accept 1-RTT traffic before handshake completion
   The proposal is <https://github.com/quicwg/base-drafts/pull/3224>

* #3130: Does it matter if the the STOP_SENDING error code is something other than EARLY RESPONSE?
   The proposal is <https://github.com/quicwg/base-drafts/pull/3208>

* #3111: [Version Ossification] Alternative version and Initial Salt should be part of NEW_TOKEN
   The proposal is to close this with no action, but we may consider it for QUICv2 and/or an extension in the future.

* #3102: Add provisional registration for all registries
   The proposal is <https://github.com/quicwg/base-drafts/pull/3170>

* #3020: Transport parameter registry is too constraining for innovation
   The proposal is <https://github.com/quicwg/base-drafts/pull/3170>

* #2792: Timing side-channel on key updates
   The proposal is <https://github.com/quicwg/base-drafts/pull/3263>

* #2496: QUIC Version Ossification
   The proposal is to close this with no action, but we may consider it for QUICv2 and/or an extension in the future.

--
Mark Nottingham   https://www.mnot.net/