SHOULD vs MUST case sensitivity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SHOULD vs MUST case sensitivity
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 notFrom ietf-bounces at ietf.org Fri Jun 27 10:33:39 2008
Return-Path: <ietf-bounces at ietf.org>
X-Original-To: ietf-web-archive at megatron.ietf.org
Delivered-To: ietfarch-ietf-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 0FD6D3A6AFB;
Fri, 27 Jun 2008 10:33:39 -0700 (PDT)
X-Original-To: ietf at core3.amsl.com
Delivered-To: ietf at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 86B8D3A6AD5
for <ietf at core3.amsl.com>; Fri, 27 Jun 2008 10:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.638
X-Spam-Level:
X-Spam-Status: No, score=-2.638 tagged_above=-999 required=5 tests=[AWL=1.962,
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 y4sSpYTteFlT for <ietf at core3.amsl.com>;
Fri, 27 Jun 2008 10:33:37 -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 567213A6AE9
for <ietf at ietf.org>; Fri, 27 Jun 2008 10:33:37 -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 m5RGRfM5012696
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <ietf at ietf.org>; Fri, 27 Jun 2008 09:27:54 -0700
Message-ID: <486514FD.1060304 at dcrocker.net>
Date: Fri, 27 Jun 2008 09:27:41 -0700
From: Dave Crocker <dhc2 at dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: IETF Discussion <ietf at ietf.org>
Subject: SHOULD vs MUST case sensitivity
References: <20080525020040.4DE5A5081A at romeo.rtfm.com> <F66D7286825402429571678A16C2F5EE03ADF950 at zrc2hxm1.corp.nortel.com> <20080620195947.29D0B5081A at romeo.rtfm.com> <9D9CF008-7350-4831-8F21-E08A0A7B255E at insensate.co.uk> <7706.1214216391.855029 at peirce.dave.cridland.net> <g3ror8$2b9$1 at ger.gmane.org> <900B2F8D-5960-4277-9DBC-E59A05F1CFBA at cisco.com> <48623304.1050008 at employees.org> <2D990430F5F5D3C7984BDFDF at p3.JCK.COM><48627A42.6030907 at employees.org>
<4862920D.4060003 at dcrocker.net>
<941D5DCD8C42014FAF70FB7424686DCF034FC969 at eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <941D5DCD8C42014FAF70FB7424686DCF034FC969 at eusrcmw721.eamcs.ericsson.se>
X-Virus-Scanned: ClamAV 0.92/7575/Thu Jun 26 16:08:06 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 09:27:54 -0700 (PDT)
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker at bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
<mailto:ietf-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces at ietf.org
Errors-To: ietf-bounces at 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 tha 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 at ietf.org
https://www.ietf.org/mailman/listinfo/ietf
t 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 at ietf.org
https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.
