Re: [quicwg/base-drafts] Mention every Transport Parameter in section on values for 0-RTT (#3756)

[Martin Thomson <[e-mail]>]

@martinthomson commented on this pull request.

The reason that this is left unstated is the problem I've identified below.  I would prefer not to do this.

> @@ -1749,6 +1749,16 @@ values for 0-RTT.  This includes initial_max_data and either
 initial_max_streams_bidi and initial_max_stream_data_bidi_remote, or
 initial_max_streams_uni and initial_max_stream_data_uni.
 
+When accepting 0-RTT data, a server may set values for the following parameters

```suggestion
When accepting 0-RTT data, a server MAY set values for the following parameters
```
?

> @@ -1749,6 +1749,16 @@ values for 0-RTT.  This includes initial_max_data and either
 initial_max_streams_bidi and initial_max_stream_data_bidi_remote, or
 initial_max_streams_uni and initial_max_stream_data_uni.
 
+When accepting 0-RTT data, a server may set values for the following parameters
+that are smaller than the values remembered by the client. Because the previous
+values set for these parameters do not affect what values can be set when
+accepting 0-RTT data, it is not necessary that the server be able to recover the
+values it previously sent.
+
+* max_idle_timeout
+* max_udp_payload_size

But this does affect 0-RTT.  Though we accepted @kazuho's argument that this manifests in a fashion indistinguishable from a change in Path MTU, that doesn't mean that changing it has no consequence, as this text implies.

-- 
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/3756#pullrequestreview-428504751