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

[Mike Bishop <[e-mail]>]

@MikeBishop 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.

We've used MUST NOT send / MAY error elsewhere when we haven't wanted to mandate checking.  It's enough of a deterrent to the bad behavior, when the requirement to treat as an error isn't vital to interop.  That said, it also isn't difficult to do the check, so if there's consensus to require it, I'm not opposed to the suggestion.

-- 
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#discussion_r460224632