Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
Time Warner Cable <Lee@asgard.org> Wed, 10 August 2016 15:35 UTC
Return-Path: <Lee@asgard.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 874CF12D7F1 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2016 08:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.127
X-Spam-Level:
X-Spam-Status: No, score=-1.127 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RDNS_NONE=0.793] 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 KQig6WBw3fGz for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2016 08:35:19 -0700 (PDT)
Received: from atl4mhob21.registeredsite.com (unknown [209.17.115.115]) by ietfa.amsl.com (Postfix) with ESMTP id B9A0E12D608 for <ietf@ietf.org>; Wed, 10 Aug 2016 08:35:19 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id u7AFZECa072716 for <ietf@ietf.org>; Wed, 10 Aug 2016 11:35:14 -0400
Received: (qmail 6267 invoked by uid 0); 10 Aug 2016 15:35:14 -0000
X-TCPREMOTEIP: 204.235.114.163
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?10.116.238.155?) (lee@asgard.org@204.235.114.163) by 0 with ESMTPA; 10 Aug 2016 15:35:14 -0000
User-Agent: Microsoft-MacOutlook/0.0.0.150911
Date: Wed, 10 Aug 2016 11:35:14 -0400
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
From: Time Warner Cable <Lee@asgard.org>
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Message-ID: <1701C0A2-CF98-43A9-A048-E72DA397412D@asgard.org>
Thread-Topic: New Version Notification for draft-leiba-rfc2119-update-00.txt
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
In-Reply-To: <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OjUWcKFY28NMcNyZ7v0NANHDZT0>
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: Wed, 10 Aug 2016 15:35:21 -0000
I don't like this update. Almost every sentences uses the passive voice. I think the use of "can," "are often," "do not have to be," and so on, is an awkward attempt to work around the use of the keywords as currently defined, or as redefined. These two usages do not help readability and clarity. How does this update affect interpretation of existing documents? It's ironic, I think, that the active voice clause, "Authors who follow these guidelines should incorporate this phrase" uses an uncapitalized "should," and I think it should be a "MUST." To Scott's semi-serious suggestion to deprecate "SHOULD," I'm hesitant. If there were another word for "do this unless you have a really good reason not to," I'd go for it. "Reasons not to" must be documented wherever possible, though sometimes not all reasons can be foreseen (see what I did there?). To another comment in the thread: I imagine that setting a reader to emphasize all caps would be annoying when reading specs with pronounceable acronyms. Lee On 8/9/16, 4:08 PM, "ietf on behalf of Barry Leiba" <ietf-bounces@ietf.org on behalf of 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. >> > >
- Re: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… John R Levine
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… John Levine
- Re: New Version Notification for draft-leiba-rfc2… Randall Gellens (IETF)
- Re: New Version Notification for draft-leiba-rfc2… Joe Touch
- Re: New Version Notification for draft-leiba-rfc2… Gmail
- Re: New Version Notification for draft-leiba-rfc2… Brian E Carpenter
- Re: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… Pete Resnick
- Re: New Version Notification for draft-leiba-rfc2… Joe Touch
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… Pete Resnick
- Re: New Version Notification for draft-leiba-rfc2… Julian Reschke
- Re: New Version Notification for draft-leiba-rfc2… Michael Richardson
- Re: New Version Notification for draft-leiba-rfc2… Julian Reschke
- Re: New Version Notification for draft-leiba-rfc2… Ted Lemon
- Re: New Version Notification for draft-leiba-rfc2… Ben Campbell
- Re: New Version Notification for draft-leiba-rfc2… HANSEN, TONY L
- RE: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- RE: New Version Notification for draft-leiba-rfc2… Dearlove, Christopher (UK)
- Re: New Version Notification for draft-leiba-rfc2… Ted Lemon
- Re: New Version Notification for draft-leiba-rfc2… Stewart Bryant
- RE: New Version Notification for draft-leiba-rfc2… Dearlove, Christopher (UK)
- Re: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… John C Klensin
- Re: New Version Notification for draft-leiba-rfc2… Michael Richardson
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- Re: New Version Notification for draft-leiba-rfc2… Doug Ewell
- Re: New Version Notification for draft-leiba-rfc2… Dave Cridland
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- Re: New Version Notification for draft-leiba-rfc2… Time Warner Cable
- Re: New Version Notification for draft-leiba-rfc2… Michael Richardson
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- Re: New Version Notification for draft-leiba-rfc2… Michael Richardson
- Re: New Version Notification for draft-leiba-rfc2… Ted Lemon
- Re: New Version Notification for draft-leiba-rfc2… Ted Lemon
- Re: New Version Notification for draft-leiba-rfc2… John Leslie
- Re: New Version Notification for draft-leiba-rfc2… Ted Lemon
- Re: New Version Notification for draft-leiba-rfc2… Stewart Bryant
- Re: New Version Notification for draft-leiba-rfc2… Stewart Bryant
- Re: New Version Notification for draft-leiba-rfc2… Stewart Bryant
- Re: New Version Notification for draft-leiba-rfc2… Stewart Bryant
- Re: New Version Notification for draft-leiba-rfc2… Randy Bush
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… Michael Richardson
- Re: New Version Notification for draft-leiba-rfc2… Mark Andrews
- Re: New Version Notification for draft-leiba-rfc2… John R Levine
- Re: New Version Notification for draft-leiba-rfc2… Mark Andrews
- Re: New Version Notification for draft-leiba-rfc2… John Levine
- Re: New Version Notification for draft-leiba-rfc2… Scott O. Bradner
- Re: New Version Notification for draft-leiba-rfc2… Joe Touch
- Re: New Version Notification for draft-leiba-rfc2… Sam Hartman
- Re: New Version Notification for draft-leiba-rfc2… Dave Crocker
- Re: New Version Notification for draft-leiba-rfc2… Sam Hartman
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- Re: New Version Notification for draft-leiba-rfc2… Stephan Wenger
- Re: New Version Notification for draft-leiba-rfc2… Barry Leiba
- Re: New Version Notification for draft-leiba-rfc2… Ted Hardie
- Re: New Version Notification for draft-leiba-rfc2… Paul Hoffman