Re: [quicwg/base-drafts] Fix some of the nits in #3214 (#4016)

[Martin Thomson <[e-mail]>]

@martinthomson approved this pull request.

Nits only.  Thanks for working through these.

> @@ -1076,8 +1076,9 @@ A zero-length connection ID can be used when a connection ID is not needed to
 route to the correct endpoint. However, multiplexing connections on the same
 local IP address and port while using zero-length connection IDs will cause
 failures in the presence of peer connection migration, NAT rebinding, and client
-port reuse; and therefore MUST NOT be done unless an endpoint is certain that
-those protocol features are not in use.
+port reuse. An endpoint MUST NOT use an IP address and port pair for multiple

```suggestion
port reuse. An endpoint MUST NOT use the same IP address and port for multiple
```

> +The definition of a new transport parameter ({{new-transport-parameters}}) is
+REQUIRED to specify whether it MUST, MAY, or MUST NOT be stored for 0-RTT. A

This is fine, but I tend to prefer:

```suggestion
The definition of a new transport parameter ({{new-transport-parameters}}) MUST
specify whether that storing the transport parameter for 0-RTT is mandatory, optional, or prohibited. A
```

(Whether an extension uses 2119 language or not is not relevant, the level of requirement is.  And as these keywords are not used in this context in the way described in RFC 2119, this is better.)

-- 
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/pull/4016#pullrequestreview-473080656