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

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 09 August 2016 20:31 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 ACDD312D67C for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 13:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 3dTLvrufF-u5 for <ietf@ietfa.amsl.com>; Tue, 9 Aug 2016 13:31:33 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 94BF412D54C for <ietf@ietf.org>; Tue, 9 Aug 2016 13:31:33 -0700 (PDT)
Received: from [10.32.60.61] (50-1-98-193.dsl.dynamic.fusionbroadband.com [50.1.98.193]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u79KVUM6020996 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2016 13:31:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-193.dsl.dynamic.fusionbroadband.com [50.1.98.193] claimed to be [10.32.60.61]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
Date: Tue, 09 Aug 2016 13:31:30 -0700
Message-ID: <FD617F86-0F0D-4C11-99F0-A6CA2B89C4E3@vpnc.org>
In-Reply-To: <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZnJ2K65i-ACC1-uToaBw4xj3pkk>
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:31:35 -0000

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

+1. It is short, focused, and makes RFCs easier to understand.

--Paul Hoffman