W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: #409: is parsing OBS-FOLD mandatory?

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Wed, 12 Dec 2012 19:51:18 +1300
Message-ID: <50C82966.5060404@treenet.co.nz>
To: ietf-http-wg@w3.org
On 12/12/2012 4:48 p.m., Mark Nottingham wrote:
> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/409>
>
> """
> p1 2.5 Conformance and Error Handling says "...recipient MUST be able to parse any value that would match the ABNF rules..." yet 3.2.2 only make parsing obs-fold a SHOULD. Which is it?
> """
>
> Roy made a proposed edit to remove the MUST NOT generate and change the SHOULD parse to a MUST parse.
>    <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/2039>
>
> However, this has the effect of un-deprecating line folding; IIRC we added those requirements because folding is not interoperable.
>
> My suggestion would be to change:
>
> """
> If a received protocol element is processed, the recipient must be able to parse any value that would match the ABNF rules for that protocol element, excluding only those rules not applicable to the recipient's role.
> """
>
> to:
>
> """
> If a received protocol element is processed, the recipient MUST be able to parse any value that would match the ABNF rules for that protocol element, excluding only those rules not applicable to the recipient's role, and those rules whose names begin with "obs-" (e.g., obs-fold).
> """
>
> Note that we already say, in 1.2 Syntax Notation:
>
> """
> As a convention, ABNF rule names prefixed with "obs-" denote "obsolete" grammar rules that appear for historical reasons.
> """
>
> Comments?

+1. Sounds good.

Amos
Received on Wednesday, 12 December 2012 06:51:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 December 2012 06:51:58 GMT