- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 26 Jul 2018 09:19:57 -0700
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Cc: Vasiliy Faronov <vfaronov@gmail.com>
Any further thoughts on this? It looks like we agree that something needs to change; AFAICT we can either accept the proposed errata, or change the MUST on sending HTTP2-Settings. Cheers, > On 31 Jan 2018, at 5:43 pm, Martin Thomson <martin.thomson@gmail.com> wrote: > > The observation is correct. However, I'm not sure that this is the > solution I would choose. I'm not sure, but I think that an empty > header field would cause problems. Maybe the right conclusion to draw > here is that you have to include at least one setting if you use this > header field. > > On Thu, Feb 1, 2018 at 12:19 PM, RFC Errata System > <rfc-editor@rfc-editor.org> wrote: >> The following errata report has been submitted for RFC7540, >> "Hypertext Transfer Protocol Version 2 (HTTP/2)". >> >> -------------------------------------- >> You may review the report below and at: >> http://www.rfc-editor.org/errata/eid5249 >> >> -------------------------------------- >> Type: Technical >> Reported by: Vasiliy Faronov <vfaronov@gmail.com> >> >> Section: 3.2.1 >> >> Original Text >> ------------- >> HTTP2-Settings = token68 >> >> Corrected Text >> -------------- >> HTTP2-Settings = [ token68 ] >> >> Notes >> ----- >> An initial SETTINGS frame is explicitly allowed by Section 3.5 to be empty. The payload of an empty SETTINGS frame is an empty sequence of octets, whose base64url encoding is an empty string. Thus, the HTTP2-Settings header field ought to permit an empty string as value. But the ABNF for "token68" does not match an empty string. >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". If necessary, please >> use "Reply All" to discuss whether it should be verified or >> rejected. When a decision is reached, the verifying party >> can log in to change the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC7540 (draft-ietf-httpbis-http2-17) >> -------------------------------------- >> Title : Hypertext Transfer Protocol Version 2 (HTTP/2) >> Publication Date : May 2015 >> Author(s) : M. Belshe, R. Peon, M. Thomson, Ed. >> Category : PROPOSED STANDARD >> Source : Hypertext Transfer Protocol Bis APP >> Area : Applications >> Stream : IETF >> Verifying Party : IESG > -- Mark Nottingham https://www.mnot.net/
Received on Thursday, 26 July 2018 16:20:38 UTC