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

Joe Touch <touch@isi.edu> Tue, 09 August 2016 22:08 UTC

Return-Path: <touch@isi.edu>
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 246F412D098 for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 15:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.147
X-Spam-Level:
X-Spam-Status: No, score=-8.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=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 CAsHQfmg0QOl for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 15:08:29 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 34ECF12D8A0 for <ietf@ietf.org>; Tue, 9 Aug 2016 15:08:02 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u79M7eY2015123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 9 Aug 2016 15:07:41 -0700 (PDT)
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <e0e3e6e2-cdc0-dc23-c8aa-8a284fdd9c1c@isi.edu>
Date: Tue, 9 Aug 2016 15:07:39 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RNLO5kxG-O5F4gmpUiAM3Td7AYI>
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 22:08:31 -0000

Although I agree with dropping SHALL/SHALL NOT and requiring uppercase,
I'm not sure it's useful to drop REQUIRED, RECOMMENDED, and OPTIONAL.

I.e., MUST/MAY/SHOULD are directives to a person. The others are
adjectives describing the resulting features.

I appreciate that we say things like "X is a MUST", but it hurts
readability vs. "X is REQUIRED".

I'm in favor of retaining those three adjectives.


Joe


On 8/9/2016 1:08 PM, Barry Leiba 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.
>>