RE: SHOULD vs MUST case sensitivity

"Eric Gray" <eric.gray@ericsson.com> Mon, 30 June 2008 13:51 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 94E263A68F3; Mon, 30 Jun 2008 06:51:32 -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 EC7F73A68F3 for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 06:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.01
X-Spam-Level:
X-Spam-Status: No, score=-6.01 tagged_above=-999 required=5 tests=[AWL=0.589, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0h3DTDLByefE for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 06:51:31 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id E0E843A6874 for <ietf@ietf.org>; Mon, 30 Jun 2008 06:51:30 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m5UDpZ83017042; Mon, 30 Jun 2008 08:51:35 -0500
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Jun 2008 08:52:11 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: SHOULD vs MUST case sensitivity
Date: Mon, 30 Jun 2008 08:52:09 -0500
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF03527E8E@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <486845B1.4050502@bbiw.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: SHOULD vs MUST case sensitivity
Thread-Index: AcjaWbN0dz7rCXvzTM2u56+x59gUQAAWKPnw
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><48657683.2050608@dcrocker.net><Pine.LNX.4.64.0806271844290.22369@shell4.bayarea.net> <DBE1F9D4-FA3E-4A8F-A90C-8095AEA809DA@muada.com><00cd01c8da42$592bd280$6801a8c0@oemcomputer> <48682966.9080007@dcrocker.net><000801c8da4a$d747c860$6801a8c0@oemcomputer> <486845B1.4050502@bbiw.net>
From: "Eric Gray" <eric.gray@ericsson.com>
To: "Dave Crocker" <dcrocker@bbiw.net>, "Randy Presuhn" <randy_presuhn@mindspring.com>
X-OriginalArrivalTime: 30 Jun 2008 13:52:11.0407 (UTC) FILETIME=[7EAB91F0:01C8DAB8]
Cc: IETF Discussion <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

Dave,

	Let's try to close this argument in a constructive way.

	We could argue the extent to which "Best Current Practice"
RFCs actually specify anything - rather than simply encouraging
a commonly accepted practice.  Based on that argument - and lots
of usage evidence (represented - among other things - by text 
you've quoted) - RFC 2119 appear to state that the terms in 
question are often capitalized.  And that supports a further
argument that RFC 2119 is suggesting this should be the case -
given that it is a common practice.

	We could also make the semantic argument that you've made
- i.e. - that capitalization is not essential to the semantics
that RFC 2119 encourages RFC authors to use.  It is certainly 
going to be the case that some RFCs will be published with the
intent for these terms to be normative, and where not every 
instance is in ALL-CAPS - and this should not mean necessarily
that these words are not meant to be taken as normative.

	However, there is abundant evidence to support argument
that prospective RFC authors should use the ALL-CAPS version of
these words - if for no other reason than because it removes any
possibility of doubt.  The evidence to support this is based at
least partly on current usage - such as a BCP like RFC 2119 is
meant to reflect.  It is also based at least in part on the the
arguments put forward in this thread.  And finally, it is based
at least in part on the common-sense proposition that anything
that adds clarity to a specification is generally a good thing.

	Hence I believe the one thing we should take away from
this discussion is that - while use of the ALL-CAPS version of
the requriements level terminology in RFC 2119 is probably not 
technically required to indicate the intended usage - it is a 
very good idea to do this.  Further, if we assume that is the
case (and I think reasonable people will agree that it is),
then continuing the argument about the semantics in this case
is merely a distraction from useful discussion and clarity in
the work we all want to be doing.

--
Eric Gray
Principal Engineer
Ericsson  

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of Dave Crocker
> Sent: Sunday, June 29, 2008 10:32 PM
> To: Randy Presuhn
> Cc: IETF Discussion
> Subject: Re: SHOULD vs MUST case sensitivity
> 
> 
> 
> Randy Presuhn wrote:
> >> English is not case sensitive.
> > 
> > Not so.  Case has long been used for emphasis in environments
> > lacking other typographical means, such as bolding, underlining,
> > or italicization.
> 
> 
> Emphasis is not semantics.
> 
> Normative intent is semantic.
> 
> d/
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf