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

Barry Leiba <barryleiba@computer.org> Sat, 06 September 2014 14:59 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D6D1A0417; Sat, 6 Sep 2014 07:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.38
X-Spam-Level: **
X-Spam-Status: No, score=2.38 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FR_3TAG_3TAG=1.758, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JjekQ-jh_ZE; Sat, 6 Sep 2014 07:59:11 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EC941A0416; Sat, 6 Sep 2014 07:59:10 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id gi9so4145738lab.2 for <multiple recipients>; Sat, 06 Sep 2014 07:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8KP6OyOOUmHNBFqyu5xcaEdA2sw+25XPxd8JKHPZ+W0=; b=RlXx3ac72bWy/mRVWmkpgXyM/cKlgulwFrPlYgCoxFmPXaAVG5dCzv7R2nb3T3pJfh n1jwDITksoLzOrWmbqLfHQcniRP6p0EVx0RqsslV26AOYttaTaiL+y/ENT0+m4QIfTT5 pw3w17PvOj76TwVqXi+u56NeS8ZNiHXDSutSxJxGJbl91/P6vqZbq0bdZWps2Wo4IdZu 5p9K+lVfmpTjAtIxvWKZ+hkK+iB9LQ6s6uM2K5eWUX8pkWmoRd6U6TwYvM5FnI4qf2UA UuSLBahoRxdgfqqyLqsU+D6cBADa/E5oJNJ8mJ/hkBue/aYcWosRYWPSVE5WdIvG0Ocs ecDA==
MIME-Version: 1.0
X-Received: by 10.152.8.165 with SMTP id s5mr18149064laa.3.1410015549340; Sat, 06 Sep 2014 07:59:09 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.152.8.45 with HTTP; Sat, 6 Sep 2014 07:59:09 -0700 (PDT)
In-Reply-To: <540A3309.90802@gmail.com>
References: <540A3309.90802@gmail.com>
Date: Sat, 6 Sep 2014 17:59:09 +0300
X-Google-Sender-Auth: Z8igvsKLvOm3415JMgASJekJ4y8
Message-ID: <CALaySJLfgZ6EfnUGSJGQjwgJ1W4YnnHq27-Nf+5D626LCQSfKQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Chris Lonvick <lonvick.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e0153807af242ad050266d350
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/pekiLUyTtPSmbS15brSJRQEh8AQ
Cc: "draft-kyzivat-case-sensitive-abnf.all@tools.ietf.org" <draft-kyzivat-case-sensitive-abnf.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: [secdir] SECDIR review of draft-kyzivat-case-sensitive-abnf
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Sep 2014 14:59:13 -0000

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.

Barry