[quicwg/base-drafts] Editorial Fixes for quick-http (#3960)

[Sho Miyamoto <[e-mail]>]

- Ambiguous description with `MAY` for user agents in [server-push](https://github.com/quicwg/base-drafts/blob/e0aa78966fc74475b6a5ef8d12d9472497cdfd2d/draft-ietf-quic-http.md#server-push):

It'd be better to remove or clarify rather than ambiguously allowing user agents with `MAY`.

> These associations do not affect the operation of the protocol, **but MAY be considered by user agents when deciding how to use pushed resources**

- Misleading expression with `MAY` in [connection-shutdown](https://github.com/quicwg/base-drafts/blob/e0aa78966fc74475b6a5ef8d12d9472497cdfd2d/draft-ietf-quic-http.md#connection-shutdown)

> Endpoints MUST NOT initiate new requests or promise new pushes on the connection after receipt of a GOAWAY frame from the peer. **Clients MAY establish a new connection to send additional requests**.

This sentence looks to readers as if clients MAY send same requests on a new connection even when the server keeps canceling or something regardless of clients' requests. There should be additional sentences if it's expected or not.

- Some phrases in [connection-shutdown](https://github.com/quicwg/base-drafts/blob/e0aa78966fc74475b6a5ef8d12d9472497cdfd2d/draft-ietf-quic-http.md#connection-shutdown) look verbose and confusing

> 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**

> If a server receives a GOAWAY frame after having promised pushes with a Push ID greater than or equal to the identifier **received in a GOAWAY frame**

- The link `section 4.1 of [QUIC-TRANSPORT]` in [quic-http-29#section-4.4](https://tools.ietf.org/html/draft-ietf-quic-http-29#section-4.4) is wrong:

[quic-http#section-4.1](https://tools.ietf.org/html/draft-ietf-quic-http#section-4.1) should be replaced with [quic-transport#section-4.1](https://tools.ietf.org/html/draft-ietf-quic-transport#section-4.1).

> The client can use stream flow control (see section 4.1 of {{QUIC-TRANSPORT}}) to limit the amount of data a server may commit to the pushed stream.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3960