Re: New Version Notification for draft-leiba-rfc2119-update-00.txt

Ted Hardie <ted.ietf@gmail.com> Tue, 09 August 2016 20:35 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76ADE12D67C for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 13:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4oFVUFof1kR5 for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 13:35:30 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D34C312D090 for <ietf@ietf.org>; Tue, 9 Aug 2016 13:35:29 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id c15so33604150oig.0 for <ietf@ietf.org>; Tue, 09 Aug 2016 13:35:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KjaMobMoncZ1z/cvGiDaOMKmCa5kZl3vj+EEJ+fxD9Q=; b=f7ioh3Oa7VNOAlsyuvTwpZb54DpXCCJ7y2mjAH1eCO/dn/dg1qPJtSLUb6DrlnuuzQ ZYx4kckCJpOMrIx5sMULdFWEq0QOccdTX8hiO5Nh3TgyVuNl3H2Q7LzXkKjTeOR4zb4/ tPIQmqJ7RO2JzdFsJpfoAS7zul315Q33NPSfpUmtAoFhSW5vegR1CY8HiHvct0jf8O4K uneoyKQoMIF+ffo2LGSgKO5A2I6T78jfdzAKFYmVdY2qO/MYfjhRL9vTlDU/5lN7x0hC qHk4xCJ7aJsOajFwvRTbzUvJlmMdnuFsawWYwamlrTdicX215dpybsaJzNVIMGuWlnFe VM0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KjaMobMoncZ1z/cvGiDaOMKmCa5kZl3vj+EEJ+fxD9Q=; b=TVYbDx6fnVSDaLntYnTdgcYr7V754y0Sm2T6GnXUqtsZq7MP4FtbhGdNrBxN/weUGb M8yWyeymRBpJfA2bO0CcSsY1djU9MvLeVa9Gv0YbXSUqnnZBxula1NXUVJ5OCHcohoKY K9Rs1BNCuUOI9JORvXjCbJNZO54FFzOaJMl84kCVX94KjLEEYElT4Xy16GSnw8t+TOxO nXU0iZF3JzjDcj0In7OZNA9bQVccMLZTP+2Q6WrqzP6CrGDoHMiHnHzU9LVORC9Vx2xI UPF6TVe8RQI+hRFD8C43kja7SXplIeNMlaCiEA8hqdlwL8gHfg7X8qYafi5U7PLIxqFt CddA==
X-Gm-Message-State: AEkoouum0P3yPkIqOaKkHavYiXbdHS5NCohaVqnjs2SzKbUYAB3UWzWNBp3n7ojk9LJPNfqufHjOcB+sfXTYpA==
X-Received: by 10.157.14.77 with SMTP id n13mr177257otd.118.1470774929212; Tue, 09 Aug 2016 13:35:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.222.213 with HTTP; Tue, 9 Aug 2016 13:34:58 -0700 (PDT)
In-Reply-To: <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 9 Aug 2016 13:34:58 -0700
Message-ID: <CA+9kkMC_hb_BWM5iEpvaWBQY_QsDBZcJDGC9WdcD_O+KHX=64g@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a113de2b6334beb0539a9790c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4eJj-ZLL-r5Ldwc5HRYau4K64_g>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 20:35:32 -0000

Hi Barry,

Do screen readers and other assistive technologies differentiate between
lower case and upper case appropriately and consistently?  When I try a
basic screen reader (the one that came with my Ubuntu distro), it doesn't
seem to make a distinction, but this may be misconfiguration on my part (I
don't use it in general).

regards,

Ted



On Tue, Aug 9, 2016 at 1:08 PM, Barry Leiba <barryleiba@computer.org> wrote:

> This draft should be self-explanatory -- and please be sure to look at
> Section 1.1 for some explanations that may short-cut some of the
> discussion.
>
> The bottom line is to update BCP 14 (RFC 2119) to
> (1) make it clear that the key words MUST(/NOT), SHOULD(/NOT), and MAY
> are only key words when they're in ALL CAPS, and
> (2) deprecate the use of the variants (SHALL, RECOMMENDED, OPTIONAL)
> so as to avoid reserving an unnecessarily number of key words.
>
> Discussion here, please, before Ben, who has kindly agreed to
> AD-sponsor this, sends it out for last call.  And we do expect there
> to be some significant discussion on this one.
>
> Barry
>
> On Tue, Aug 9, 2016 at 2:55 PM,  <internet-drafts@ietf.org> wrote:
> >
> > A new version of I-D, draft-leiba-rfc2119-update-00.txt
> > has been successfully submitted by Barry Leiba and posted to the
> > IETF repository.
> >
> > Name:           draft-leiba-rfc2119-update
> > Revision:       00
> > Title:          Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
> > Document date:  2016-08-09
> > Group:          Individual Submission
> > Pages:          4
> > URL:            https://www.ietf.org/internet-
> drafts/draft-leiba-rfc2119-update-00.txt
> > Status:         https://datatracker.ietf.org/doc/draft-leiba-rfc2119-
> update/
> > Htmlized:       https://tools.ietf.org/html/
> draft-leiba-rfc2119-update-00
> >
> >
> > Abstract:
> >    RFC 2119 specifies common key words that may be used in protocol
> >    specifications.  This document aims to reduce the ambiguity by
> >    clarifying that only UPPERCASE usage of the key words have the
> >    defined special meanings, and by deprecating some versions of the key
> >    words.
> >
>
>