IETF Logo Mail Archive

SHOULD vs MUST case sensitivity

Dave Crocker <dhc2@dcrocker.net> Fri, 27 June 2008 23:23 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 2A8AC28C21D; Fri, 27 Jun 2008 16:23:52 -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 19CE828C21D for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 16:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.964
X-Spam-Level:
X-Spam-Status: No, score=-2.964 tagged_above=-999 required=5 tests=[AWL=1.635, BAYES_00=-2.599, GB_I_LETTER=-2]
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 rUVU1zHIe1Nj for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 16:23:50 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 836CE28C21C for <ietf@ietf.org>; Fri, 27 Jun 2008 16:23:49 -0700 (PDT)
Received: from [192.168.0.3] (adsl-67-127-53-97.dsl.pltn13.pacbell.net [67.127.53.97]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m5RNNlgJ005847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 27 Jun 2008 16:23:53 -0700
Message-ID: <48657683.2050608@dcrocker.net>
Date: Fri, 27 Jun 2008 16:23:47 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: SHOULD vs MUST case sensitivity
References: <20080525020040.4DE5A5081A@romeo.rtfm.com> <F66D7286825402429571678A16C2F5EE03ADF950@zrc2hxm1.corp.nortel.com> <20080620195947.29D0B5081A@romeo.rtfm.com> <9D9CF008-7350-4831-8F21-E08A0A7B255E@insensate.co.uk> <7706.1214216391.855029@peirce.dave.cridland.net> <g3ror8$2b9$1@ger.gmane.org> <900B2F8D-5960-4277-9DBC-E59A05F1CFBA@cisco.com> <48623304.1050008@employees.org> <2D990430F5F5D3C7984BDFDF@p3.JCK.COM><48627A42.6030907@employees.org> <4862920D.4060003@dcrocker.net> <941D5DCD8C42014FAF70FB7424686DCF034FC969@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <941D5DCD8C42014FAF70FB7424686DCF034FC969@eusrcmw721.eamcs.ericsson.se>
X-Virus-Scanned: ClamAV 0.92/7579/Fri Jun 27 12:52:12 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 27 Jun 2008 16:23:53 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


Eric Gray wrote:
>> (By the way, I hope folks are clear that IETF use of these words as
> normative
>> does not depend upon the case that is used?)
> 
> This is NOT true.  These terms are explicitly defined in all capital letters
> to make it possible to distinguish when they are being used as normative and
> when they are not.


Sorry, no.  Please re-read rfc 2219.  Specifically:

      "These words are often capitalized."

The key word is "often" which means not always which means not required.

Computer science long ago made the mistake of imposing semantic difference on
case differences, which is distinct from other uses of case.  Absent explicit
specification of case sensitivity for the keywords, the rules of English writing
apply, I would think.


> In text that is not meant to be normative, the special terms should be
> avoided - even in lower case - but this can lead to exceptionally stilted use
> of the English language.

Not really.  Words like "can" and "ought" do the job nicely.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email