- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 5 May 2016 06:08:07 -0700 (PDT)
- To: quae@daurnimator.com, fielding@gbiv.com, julian.reschke@greenbytes.de
- Cc: aamelnikov@fastmail.fm, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been held for document update for RFC7230, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7230&eid=4683 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Daurnimator <quae@daurnimator.com> Date Reported: 2016-05-04 Held by: Alexey Melnikov (IESG) Section: 4 Original Text ------------- Corrected Text -------------- The name part of a transfer-parameter is case insensitive and MUST not be "q" (as this would be ambiguous when used as part of the TE header). Notes ----- Nothing is said about how to handle transfer-parameters. Notably, nothing is said about the case sensitivity of the parameter key. This results in a conflict with the TE header: if you see a "q" token, you cannot know if it is a transfer-parameter vs a t-ranking. It *is* noted that the "q" token is case insensitive in section 4.3. > When multiple transfer codings are acceptable, the client MAY rank > the codings by preference using a case-insensitive "q" parameter Alexey: as per Mark, this should be discussed in the HTTPBis WG. -------------------------------------- RFC7230 (draft-ietf-httpbis-p1-messaging-26) -------------------------------------- Title : Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Publication Date : June 2014 Author(s) : R. Fielding, Ed., J. Reschke, Ed. Category : PROPOSED STANDARD Source : Hypertext Transfer Protocol Bis APP Area : Applications Stream : IETF Verifying Party : IESG
Received on Thursday, 5 May 2016 13:09:13 UTC