Re: SHOULD vs MUST case sensitivity

John Leslie <john@jlc.net> Tue, 01 July 2008 16:50 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 017BE3A6B96; Tue, 1 Jul 2008 09:50:41 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8EBB3A6B86 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 09:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaJ0JQ5dnil5 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 09:50:39 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id F1A4E3A6B96 for <ietf@ietf.org>; Tue, 1 Jul 2008 09:50:38 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 017AC33C21; Tue, 1 Jul 2008 12:50:48 -0400 (EDT)
Date: Tue, 1 Jul 2008 12:50:47 -0400
From: John Leslie <john@jlc.net>
To: John Levine <johnl@iecc.com>
Subject: Re: SHOULD vs MUST case sensitivity
Message-ID: <20080701165047.GB3847@verdi>
References: <2788466ED3E31C418E9ACC5C316615572FF95C@mou1wnexmb09.vcorp.ad.vrsn.com> <20080701154010.14410.qmail@simone.iecc.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20080701154010.14410.qmail@simone.iecc.com>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John Levine <johnl@iecc.com>; wrote:
> 
>>* Whenever the keywords are used they are to be considered normative
>>* Whenever the keywords are used they SHOULD be capitalized
> 
> Ahem:
> 
> * Whenever the keywords are used they MUST be capitalized

   I did an exercise today: I looked at the first item on Thursday's
IESG Agenda, and I counted "may".

   I found

-   6 occurances of upper-case "MAY",
-  40 occurances of mixed-case "May",
- 111 occurances of lower-case "may".

   I frankly can imagine no way to avoid occasional occurances of the
month "May" -- in this case the header of every page.

   At least four of the lower-case "may"s were in the boilerplate.

   I dread to think how many grammarians might expire during a primal
scream if we replaced over 100 "may"s with "can"s. ;^)

>>* Editors SHOULD avoid use of normative keywords for non-normative
>>language, even in drafts.

   Perhaps they should -- but what do folks actually want to do about
documents like this?

   Those "May" months were probably added by automated software --
I hope nobody expects editors to end-run that! Likewise the boilerplate
"may"s...

   We certainly shouldn't be asking the RFC Editor to "fix" over 100
lower-case "may"s.

   Should the Area Director send this back to the Working Group?
Speak now (well, before Thursday morning) if you think so -- otherwise
the IESG is likely to approve this document which so blatantly ignores
the expressed wishes of this mailing-list.

   ;^)

--
John Leslie <john@jlc.net>;
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf