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

"Scott O. Bradner" <sob@sobco.com> Tue, 09 August 2016 22:52 UTC

Return-Path: <sob@sobco.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 72E5112D8CF for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 15:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level:
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 2IExvz8ermAA for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 15:52:11 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E3F412D8D4 for <ietf@ietf.org>; Tue, 9 Aug 2016 15:52:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id DCEA7287DB09; Tue, 9 Aug 2016 18:52:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jZsZbWgIubG; Tue, 9 Aug 2016 18:52:08 -0400 (EDT)
Received: from [10.0.1.16] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 6DD61287DAFB; Tue, 9 Aug 2016 18:52:08 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
Date: Tue, 09 Aug 2016 18:52:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <802DF288-DBC8-49C1-9E75-09DF28923E09@sobco.com>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X7icBbCC56SHjBwmxMrkU-0kJuw>
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 22:52:12 -0000

my only suggestion would be to consider removing SHOULD

(semi-serious) 

Scott

> On Aug 9, 2016, at 4: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.
>> 
>