Re: [quicwg/base-drafts] HTTP/3 settings frames and prioritization (#2772)

["Tom D." <[e-mail]>]

In my opinion, adding something like you just said to the specifications would be perfect. Given that section 7.2.5.2 already mentions default settings values, it might not be bad to just expand it there. For example:

```
For clients using a 1-RTT QUIC connection, the initial value of each server setting is the default value. When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session. 
Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are received.
```

could be appended with something along the lines of:

```
These values can be used by a client in a situation where it wants to send requests before the server's settings frame has arrived. 
This removes the need for a client to block and wait before sending its first request.
```

I think the most important part here is being a little more verbose about the edge case instead of just implying its existence by mentioning the default values for settings. 
If anyone has any other thoughts about it I'd love to hear them.

-- 
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/2772#issuecomment-500006509