Subject: Consensus Call on issues closed by the -02 drafts

From: Mark Nottingham <[email-masked]>
Date: Fri, 17 Mar 2017 20:22:29 +1100

Everyone,

The -02 drafts incorporate the proposed resolutions to a number of issues that have been discussed. 

Those issues are listed below. Please have a look through them, and if there are any resolutions that you feel need more discussion, please bring it up, either here on the mailing list or in the issue itself.

Issues that we need to discuss more will be reopened. The remaining ones will be flagged as `has-consensus`.

There are a lot of them, so we're not going to do this until after the Chicago meeting (at the earliest) to give people a chance to discuss on the list as well as in the meeting.

See <https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#resolving-issues> for a reminder about the process we're using here. Even when we have consensus, we can reopen an issue if new information emerges (and that can take a variety of forms).

This list is also available at <https://github.com/quicwg/base-drafts/issues?utf8=✓&q=is%3Aissue%20is%3Aclosed%20label%3Adesign%20-label%3Ahas-consensus>.

Cheers,

## Transport

#35  - Starting packet number
#40  - Variable-length fields
#49  - Transport parameter advertisements
#50  - Updating Transport parameters
#51  - QUIC version number scheme
#52  - Source address validation
#55  - What can change in a different version
#56  - Extending flags
#57  - Advice on STOP_WAITING
#59  - Define ICSL parameter
#62  - Finding frame lengths
#63  - ACK retransmission
#64  - Path MTU Discovery
#66  - Remove STOP_WAITING
#67  - Picking packet number length
#69  - Minimum packet size
#70  - Move ACK/STOP_WAITING into the packet header
#74  - Application-defined error codes
#104 - Priority in QUIC Transport
#108 - Maximum stream number
#112 - Greasing version negotiation
#114 - STREAM retransmission priority
#116 - COPTs as empty transport parameters
#117 - SCUP
#118 - Source Address Token encoding
#119 - Server-proposed connection ID
#124 - Alt-Svc quic version hint
#126 - Separate transport parameters for 0-RTT
#133 - Connection ID in version negotiation
#135 - DoS using Version Negotiation Packets
#136 - First client packet size
#139 - Minimum MTU
#147 - Reflection Attack Resistance
#148 - QUIC packet header complexity
#157 - Updated information in retransmitted frames
#158 - Padding between frames
#159 - Time format
#162 - RST_STREAM and flow control
#163 - RST_STREAM and connection-level flow control
#164 - Padding handshake packets
#168 - Ordering of ACK Frame fields
#174 - Stream Reservation
#181 - Remove SETTINGS[_ACK]
#185 - Reliable identification of the initial packet for a connection
#201 - Do streams 0 and 1 count towards MSPC?
#204 - Streams not contributing to connection-level flow control
#243 - AEAD Associated Data
#244 - Need a NONCE in version negotiation packets
#262 - Don't encrypt client handshake with 1-RTT keys
#285 - Policing packet number size
#286 - Outstanding packets and packet number size
#289 - Avoid using Public Reset where possible
#291 - ACKing ACK
#292 - Does any portion of the QUIC framing require 4 byte alignment?
#293 - Does the connection id need to be in a consistent location?
#295 - Connection ID on a version negotiation packet
#308 - "retransmitting" old timestamps in ACK frames
#323 - Smaller packet number representations
#340 - Scale flow control offsets
#341 - What does it mean to acknowledge something?
#347 - Clarify meaning/definition of GOAWAY
#349 - When should server-chosen connection IDs be sent and how are they indicated?
#352 - Does GOAWAY need an error code

## Recovery

#63  - ACK retransmission
#169 - Response to lost handshake packets

## TLS

#12  - Decouple QUIC version and ALPN 
#25  - Key update forward secrecy
#26  - Which bit can KEY_PHASE use?
#27  - Fix KEY_PHASE for early data
#34  - ACK rules and packet protection
#87  - QUIC advertisement description
#97  - Version Negotiation + TLS
#226 - Authenticating public parts of the packet header
#243 - AEAD Associated Data
#262 - Don't encrypt client handshake with 1-RTT keys
#272 - Signaling TLS handshake failure

## HTTP

75  - SETTING syncronization
87  - QUIC advertisement description
95  - CONNECT
104 - Priority in QUIC Transport
124 - Alt-Svc quic version hint
127 - Frame header reserved bits
154 - HTTP Stream ID Size
173 - Size of HTTP Header Sequence Numbers
176 - RST_STREAM breaks HPACK
181 - Remove SETTINGS[_ACK]
202 - HTTP: Why are we defining CONNECT?
204 - Streams not contributing to connection-level flow control
229 - Use a quic= parameter for Alt-Svc rather than collide with existing use of v=
242 - HTTP extension mechanisms
297 - Remove the quic parameter from Alt-Svc
364 - Mid-frame close

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