Re: [quicwg/base-drafts] Clarify HTTP/2 setting parameter reservation (#3955)

[Jana Iyengar <[e-mail]>]

@janaiyengar commented on this pull request.



> @@ -1395,6 +1395,10 @@ settings to have any meaning upon receipt.
 Because the setting has no defined meaning, the value of the setting can be any
 value the implementation selects.
 
+Setting identifiers which were used in HTTP/2 where there is no corresponding
+HTTP/3 setting have also been reserved ({{iana-settings}}). These settings MUST
+NOT be sent, and receipt MAY be treated as an error of type H3_SETTINGS_ERROR.

```suggestion
NOT be sent, and their receipt MAY be treated as an error of type H3_SETTINGS_ERROR.
```

> @@ -1395,6 +1395,10 @@ settings to have any meaning upon receipt.
 Because the setting has no defined meaning, the value of the setting can be any
 value the implementation selects.
 
+Setting identifiers which were used in HTTP/2 where there is no corresponding
+HTTP/3 setting have also been reserved ({{iana-settings}}). These settings MUST
+NOT be sent, and receipt MAY be treated as an error of type H3_SETTINGS_ERROR.

I would be in favor of `MUST treat as error`. This isn't hard to detect, and it seems quite reasonable to close the connection on such errors.

-- 
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/3955#pullrequestreview-454585794