Draft: draft-ietf-quic-http

Commentary: " A client that is unable to retry requests [ ... ] " sentence from the beginning of an entirely unrelated paragraph to somewhere more appropriate .  ID requirement on subsequent GOAWAY frames . This was presumably an oversight , because " An endpoint MAY send multiple GOAWAY frames indicating different identifiers [ ... ] " paragraph above is pretty clear and covers both directions already .
Paragraph (version A):
Upon receipt of a GOAWAY frame, if the client has already sent
requests with a Stream ID greater than or equal to the identifier
received in a GOAWAY frame, those requests will not be processed.
Clients can safely retry unprocessed requests on a different
connection.
Paragraph (version B):
Upon receipt of a GOAWAY frame, if the client has already sent
requests with a Stream ID greater than or equal to the identifier
received in a GOAWAY frame, those requests will not be processed.
Clients can safely retry unprocessed requests on a different
connection.  A client that is unable to retry requests loses all
requests that are in flight when the server closes the connection.
Paragraph (version A):
A client that is unable to retry requests loses all requests that are
in flight when the server closes the connection.  An endpoint MAY
send multiple GOAWAY frames indicating different identifiers, but the
identifier in each frame MUST NOT be greater than the identifier in
any previous frame, since clients might already have retried
unprocessed requests on another connection.  Receiving a GOAWAY
containing a larger identifier than previously received MUST be
treated as a connection error of type H3_ID_ERROR.
Paragraph (version B):
An endpoint MAY send multiple GOAWAY frames indicating different
identifiers, but the identifier in each frame MUST NOT be greater
than the identifier in any previous frame, since clients might
already have retried unprocessed requests on another connection.
Receiving a GOAWAY containing a larger identifier than previously
received MUST be treated as a connection error of type H3_ID_ERROR.
Paragraph (version A):
A client has more flexibility in the value it chooses for the Push ID
in a GOAWAY that it sends.  A value of 2^62 - 1 indicates that the
server can continue fulfilling pushes which have already been
promised, and the client can continue granting push credit as needed;
see frame-max-push-id.  A smaller value indicates the client will
reject pushes with Push IDs greater than or equal to this value.
Like the server, the client MAY send subsequent GOAWAY frames so long
as the specified Push ID is strictly smaller than all previously sent
values.
Paragraph (version B):
A client has more flexibility in the value it chooses for the Push ID
in a GOAWAY that it sends.  A value of 2^62 - 1 indicates that the
server can continue fulfilling pushes which have already been
promised, and the client can continue granting push credit as needed;
see frame-max-push-id.  A smaller value indicates the client will
reject pushes with Push IDs greater than or equal to this value.
Like the server, the client MAY send subsequent GOAWAY frames so long
as the specified Push ID is no greater than any previously sent
value.