Re: SHOULD vs MUST case sensitivity

Dave Crocker <dhc2@dcrocker.net> Mon, 30 June 2008 14:27 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 7B1C63A6868; Mon, 30 Jun 2008 07:27:21 -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 E9BCE3A6868 for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 07:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=0.401, 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 UUhv40wXqSmZ for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 07:27:19 -0700 (PDT)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 9460D3A6816 for <ietf@ietf.org>; Mon, 30 Jun 2008 07:27:18 -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 m5UERMN8005679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 30 Jun 2008 07:27:27 -0700
Message-ID: <4868ED4A.6080506@dcrocker.net>
Date: Mon, 30 Jun 2008 07:27:22 -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: Re: SHOULD vs MUST case sensitivity
References: <20080525020040.4DE5A5081A@romeo.rtfm.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> <941D5DCD8C42014FAF70FB7424686DCF03527E8E@eusrcmw721.eamcs.ericsson.se> <025d01c8daba$e15b7a20$6501a8c0@china.huawei.com> <5CF12EE3-CA54-4493-B286-2FB3EC812337@cisco.com>
In-Reply-To: <5CF12EE3-CA54-4493-B286-2FB3EC812337@cisco.com>
X-Virus-Scanned: ClamAV 0.92/7586/Sun Jun 29 19:17:49 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]); Mon, 30 Jun 2008 07:27:27 -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


Ralph Droms wrote:
> Would a reasonable BCP for future docs looks something like:
> 
>   terms defined in RFC 2119 are to be capitalized for clarity; 
> alternatives for RFC 2119 terms, such as "ought" and "can" are to be 
> used in
>   non-normative text to avoid confusion

+1

Thanks.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

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