2.3 Length Requirements

[mnot]

When a received protocol element is parsed, the recipient MUST be able to parse any value of reasonable length that is applicable to the recipient's role and that matches the grammar defined by the corresponding ABNF rules.

This MUST is very fuzzy, and obviously isn't testable. Should it just be prose?

[reschke]

Not convinced, but wouldn't object. Maybe "needs to"?

[royfielding]

That's what makes the ABNF normative. I don't see a need to change it now.

[mnot]

Sorry, what does the ABNF have to do with this? The issue is the phrase "MUST be able to parse any value of reasonable length", where "reasonable length" is not defined.

[royfielding]

It is defined as being reasonable. I have no problem testing that (subjectively). ;-)

[royfielding]

Sorry, what does the ABNF have to do with this? The issue is the phrase "MUST be able to parse any value of reasonable length", where "reasonable length" is not defined.

I meant the second half.

[royfielding]

How about

A recipient SHOULD parse a received protocol element defensively, with only marginal expectation that the element conforms to the ABNF and can be parsed within the scope of a reasonable buffer.

[mnot]

I like it