Re: SHOULD vs MUST case sensitivity

John Levine <johnl@iecc.com> Tue, 01 July 2008 15:40 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 262B23A686C; Tue, 1 Jul 2008 08:40:02 -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 9554F3A686C for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 08:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.288
X-Spam-Level:
X-Spam-Status: No, score=-10.288 tagged_above=-999 required=5 tests=[AWL=0.611, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, 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 UB5VMQErgVfa for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 08:40:00 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 837E93A6830 for <ietf@ietf.org>; Tue, 1 Jul 2008 08:40:00 -0700 (PDT)
Received: (qmail 91791 invoked from network); 1 Jul 2008 15:40:10 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 1 Jul 2008 15:40:10 -0000
Date: Tue, 01 Jul 2008 15:40:10 -0000
Message-ID: <20080701154010.14410.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: SHOULD vs MUST case sensitivity
In-Reply-To: <2788466ED3E31C418E9ACC5C316615572FF95C@mou1wnexmb09.vcorp.ad.vrsn.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
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

>* Whenever the keywords are used they are to be considered normative
>* Whenever the keywords are used they SHOULD be capitalized

Ahem:

* Whenever the keywords are used they MUST be capitalized

>* Editors SHOULD avoid use of normative keywords for non-normative
>language, even in drafts.

Yes, I agree.  I've done this in recent drafts that I've been working
on and found it to be quite effective.  Looking at each magic word and
thinking about whether it's telling the reader something important
about interoperating is good discipline, yet not terribly hard.

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf