Re: [Technical Errata Reported] RFC7230 (4169)

This seems to be a correct report: the grammar supports OWS before or
after a comma, but not before the first element or after the last.

Julian?

Barry

On Sun, Nov 9, 2014 at 7:20 PM, RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
> The following errata report has been submitted 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=4169
>
> --------------------------------------
> Type: Technical
> Reported by: Simon Schueppel <simon.schueppel@googlemail.com>
>
> Section: 7
>
> Original Text
> -------------
>      #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
>
>      1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )
>
>    Empty elements do not contribute to the count of elements present.
>    For example, given these ABNF productions:
>
>      example-list      = 1#example-list-elmt
>      example-list-elmt = token ; see Section 3.2.6
>
>    Then the following are valid values for example-list (not including
>    the double quotes, which are present for delimitation only):
>
>      "foo,bar"
>      "foo ,bar,"
>      "foo , ,bar,charlie   "
>
> Corrected Text
> --------------
>      #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
>
>      1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )
>
>    Empty elements do not contribute to the count of elements present.
>    For example, given these ABNF productions:
>
>      example-list      = 1#example-list-elmt
>      example-list-elmt = token ; see Section 3.2.6
>
>    Then the following are valid values for example-list (not including
>    the double quotes, which are present for delimitation only):
>
>      "foo,bar"
>      "foo ,bar,"
>      "foo , ,bar,charlie"
>
> Notes
> -----
> "foo , ,bar,charlie   " cannot be derived from 1#token (legacy list rule)
> "foo , ,bar,charlie" can be derived from 1#token (legacy list rule)
>
> 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 (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> 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
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
>
>

Received on Monday, 10 November 2014 06:00:11 UTC