Re: [secdir] SECDIR review of draft-kyzivat-case-sensitive-abnf

[Chris Lonvick <[e-mail]>]

Hi Barry,

On 9/6/14, 7:59 AM, Barry Leiba wrote:
> Hi, Chris, and thanks for the review.
>
>     2 - The last sentence of section 2.1 is:
>
>         This mechanism has a clear readability
>         disadvantage, with respect to using a literal text string with a
>         prefix, and new the prefix mechanism is preferred.
>
>
>     Perhaps you meant:
>        This mechanism of using a literal text string with a prefix has
>     a clear
>        readability disadvantage.  The prefix mechanism described in this
>        specification can be much more easily read.
>
>
> No.  Take the sentence in context.  The context is that it's 
> describing the was we used to do case-sensitive text, giving each 
> character's numeric value.  It's *that* mechanism that has the 
> readability disadvantage.
>
> Do you really think that text is unclear, in the context that it's 
> given?  I suppose we could say "The old mechanism has...", to make it 
> even clearer.

The sentence is consistent with the context of the section and I get 
that.  What I was raising a concern about was the nearly unparsable last 
clause: "and new the prefix mechanism is preferred."  :-) Obviously I 
muddied the waters with my suggestion and I don't see the point of 
belaboring this with explanations of %d or %h prefixes make literal 
strings unreadable, so just find some way to clean up that last clause.

Best regards,
Chris
>
> Barry
>