-
Presently, there is no normative language for Transport Parameter omit_connection_id.
I would like to propose replacing "can" with a normative "MAY". It is important that this MAY is specified, so…
-
I think that this is one or other peer walking away from a conversation without saying goodbye. If we're going to talk about silent closes, we need to explain what it is, why a peer might choose to d…
-
The current setup with the start and stop functions is race-prone and pollutes Go's race detection output. We should figure out a way to run the tests without races.
-
In an ACK frame largest acked is "A variable-sized unsigned value". The text doesn't give a lot of guidance on exactly how its determined (other than its size), but presumably it uses the algorithm fr…
-
ILubashev's suggestion on #171 alludes to this; separating it out as a new issue.
Connection-level flow control is currently defined as a cumulative sum of all bytes _received_ on all streams. How…
-
A lost handshake packet is retransmitted after 400ms (assuming that you don't have prior knowledge of the RTT, if you do then it is 2xRTT). I realize that this is probably shorter than in TCP, but it…
-
I have a quick question about the HTTP2 frames.
The frames defined in the [QUIC draft](https://quicwg.github.io/base-drafts/draft-ietf-quic-http.html#rfc.section.5) are different from the ones in the…
-
#395 mentions bytes_in_flight, but does specify what this means: IP, UDP and QUIC header? ACK's, or just the sum of retransmittable frames, or just stream payload?
-
HTTP/2 has a pretty strong recommendation to have PUSH_PROMISE precede any text that mentions it. Failing to do so could mean that a client requests a resource that was pushed, which is wasteful.
…
-
We now forbid the generation of an ACK in response to an ACK (lest the two endpoints talk each other to death over nothing), rather than recommend acknowledging only a fraction of ACKs. That's great,…