Re: RFC 2119 terms, ALL CAPS vs lower case

Julian Reschke <julian.reschke@gmx.de> Thu, 17 May 2012 14:00 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD1221F86BB for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 07:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level:
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYOed6sB9txM for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 07:00:59 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7AF1D21F86B3 for <ietf@ietf.org>; Thu, 17 May 2012 07:00:58 -0700 (PDT)
Received: (qmail invoked by alias); 17 May 2012 14:00:57 -0000
Received: from p54BB26EE.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.38.238] by mail.gmx.net (mp040) with SMTP; 17 May 2012 16:00:57 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18VxPJsDMQVsDL/0cnHZqCXvwGyGvhRSq7Y0VLnVa RYKICJkK1Ap3dF
Message-ID: <4FB50486.2@gmx.de>
Date: Thu, 17 May 2012 16:00:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com> <m2mx57c2g5.wl%randy@psg.com> <22965.1337200180.525898@puncture>
In-Reply-To: <22965.1337200180.525898@puncture>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Thu, 17 May 2012 14:00:59 -0000

On 2012-05-16 22:29, Dave Cridland wrote:
> On Wed May 16 21:10:02 2012, Randy Bush wrote:
>> > Authors must be fastidious about this.
>>
>> s/this/documents/
>
> RFC 2119 §6 says:
>
> Imperatives of the type defined in this memo must be used with care
> and sparingly. In particular, they MUST only be used where it is
> actually required for interoperation or to limit behavior which has
> potential for causing harm (e.g., limiting retransmisssions). For
> example, they must not be used to try to impose a particular method
> on implementors where the method is not required for
> interoperability.
>
> I note two things:
>
> 1) RFC 2119 also uses lower-case "must" and "may" throughout.
>
> 2) RFC 2119 also clearly states that using the terms too much will harm
> interoperability.
>
> The second is the one I feel we have violated much more, and caused much
> more damage, than any possible problem with the first.
> ...

+100