Re: RFC 2119 terms, ALL CAPS vs lower case

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 19 May 2012 06:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 B8A3721F8661 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level:
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 n3SOPPe4ypxR for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:48:55 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 138FA21F8670 for <ietf@ietf.org>; Fri, 18 May 2012 23:48:54 -0700 (PDT)
Received: by werb13 with SMTP id b13so1090078wer.31 for <ietf@ietf.org>; Fri, 18 May 2012 23:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vQt3OCwEv2CC6fDj0iag2PwaMYG3TMRJ57iycCb2Cpo=; b=QJ/T8RvpWKjCIbGx2XeAzrb+EnOtMsDEwhBNYt6n2O4uip0txhVnQOy5GXScts/Tu6 L7rLiIQqa3xf/nYi6/F0QBBJTKop3Y6Z79T8XGvNuD05x9vgb1cmTufCoZomx6KdgdS/ j0BS6PAyKp7tKgNOKHR0+WfbGLShd0WFCFC+XNgTi5sGaGVYqnrvpDKe2rYs0Ugqm91c TeCOhaJnRdTiffjcIIXOzZh3i6fVLgMDlbRbdA3zAkHHmvxdGFQ/7+RVYVP1Px5TkCmM YVKpXKP35a8WU30TfMIobFK8vUQ1utnar/YGiMQ5JhcjZGhUyGnKf4i3CKrFo06vfnoj Fppw==
Received: by 10.180.100.2 with SMTP id eu2mr8112175wib.1.1337410134233; Fri, 18 May 2012 23:48:54 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-67.as13285.net. [2.102.216.67]) by mx.google.com with ESMTPS id fm1sm6749344wib.10.2012.05.18.23.48.52 (version=SSLv3 cipher=OTHER); Fri, 18 May 2012 23:48:53 -0700 (PDT)
Message-ID: <4FB7424C.8070508@gmail.com>
Date: Sat, 19 May 2012 07:48:44 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com>
In-Reply-To: <m2396x73az.wl%randy@psg.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: IETF list 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: Sat, 19 May 2012 06:48:55 -0000

On 2012-05-18 19:27, Randy Bush wrote:
>> I recommend an errata to RFC 2119: "These words MUST NOT appear in a
>> document in lower case."
> 
> first, that is not an erratum, it is a non-trivial semantic change.
> 
> second, do we not already have enough problems being clear and concise
> without removing common words from our language?

May I say "+1"?

Very seriously - after all that has been said on this thread, I see
no reason to change anything. Authors and the RFC Editor can create
unambiguous language with a bit of thought. There is an erratum
in 2119 ("NOT RECOMMENDED" is not mentioned in the recommended
boilerplate) but we know how to deal with that.

A strong argument against updating RFC 2119 is the fact that it's
one of the most cited RFCs *outside* the RFC series. Several other
SDOs commonly cite RFC 2119 and use its terminology. If it was
a protocol, we'd be proud of its success, but that makes changing
it a source of unintended consequences.

   Brian