Re: SHOULD vs MUST case sensitivity

Julian Reschke <julian.reschke@gmx.de> Fri, 27 June 2008 18:17 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 E1A933A6824; Fri, 27 Jun 2008 11:17:19 -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 3A4F73A67E2 for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level:
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=-1.000, 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 ZMMYeWHhwejC for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:17:18 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id DBB983A679C for <ietf@ietf.org>; Fri, 27 Jun 2008 11:17:17 -0700 (PDT)
Received: (qmail invoked by alias); 27 Jun 2008 18:17:20 -0000
Received: from p508FE879.dip.t-dialin.net (EHLO [192.168.178.22]) [80.143.232.121] by mail.gmx.net (mp007) with SMTP; 27 Jun 2008 20:17:20 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/HSOs2T2rH8HoffF9fT303IqTdiQ9DkRMLyX5rIA PPEs8mcF3Lw8tT
Message-ID: <48652EAE.2050902@gmx.de>
Date: Fri, 27 Jun 2008 20:17:18 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: 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> <486514FD.1060304@dcrocker.net>
In-Reply-To: <486514FD.1060304@dcrocker.net>
X-Y-GMX-Trusted: 0
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Dave Crocker wrote:
> 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.
> ...

Of course.

My understanding that everything in an RFC is normative, unless stated 
otherwise.

If this wouldn't be the case, how could something as important as STD66 
be written without a single RFC2119 keyword?

BR, Julian
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf