Re: Uppercase question for RFC2119 words

Barry Leiba <barryleiba@computer.org> Mon, 28 March 2016 19:09 UTC

Return-Path: <barryleiba@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 C465412DBBC; Mon, 28 Mar 2016 12:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwwdd6PBDIQY; Mon, 28 Mar 2016 12:09:55 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A557D12D8E8; Mon, 28 Mar 2016 12:09:54 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id i4so86294142qkc.3; Mon, 28 Mar 2016 12:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=l5SgB7bTV5Z6FGV2ZPU+jB5kA6xWZMS7eRJVTJnMD9M=; b=xkuYyeC9qLMRst0JMaEesChXEg+T9GNzbcL0+/X8+JTaxLoaUlKN+/lTkE9/EnraNI /Sxrow0tfkyCPoKIY9ZVrjhZ5p3zj7xjwR5Zr3q3n2rsTBUO3bf32Pcray+g7feiJvo4 4QJ45kQnret82UZrl+aaY0BGkdcyaK9FdXj3B2CFDQPdKq87pZrpUmU4OJU0Ku/9w6V3 +/mZrdnOUrzVyNERv4kIh8D0r1/jSDJ3m9epZlV3s19swAItESUmnTTFYaEbJ3ZVwid4 I0jH0ESgu/Zh8CWNL/TXIq9Pk7Q0x99dQBqxLJMsyJYq96+Mc6EOwh+URyzJtfKrx8wM 9W1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=l5SgB7bTV5Z6FGV2ZPU+jB5kA6xWZMS7eRJVTJnMD9M=; b=chMX4qihH2JdKtd3tjXWOwjLpYSbFNQILcnMVEr7nzh81FHuMuvuOkoIkmeiKKFpPh Fq/CH2GPkI2uR8AcYWjg3MIaRpR+qPJt23o4QOpLt13dfLDVPYfUSKlQQTbzlB+NoCCi /Yb1VJdJa+MQQX+CY4n63o/tr69fW9ZhWIYMLQEl5G90DMfb+gbESAVgDeXbXuK8SLWA qJcaOZiRDx1cdIJq1kGe6rNeKWRQW/yeceGBn1hqQF2/Yjq+QXdWQZwcIC3spj18jZ1k gH2mDh5otm/d3mJGbq797NXbj/jkmR/tthDvpha5kLwwe/+lyOebwPlfRg5uMUyB2jYW SMYQ==
X-Gm-Message-State: AD7BkJIyMlvMiP3s3xMNDPQdbKWvrWTRyqAlNiheemGlwnNd/71LRd2hw9gP7BIdEWRkV4nh/XqBRGeAWY9OpA==
MIME-Version: 1.0
X-Received: by 10.37.18.198 with SMTP id 189mr11630305ybs.102.1459192193728; Mon, 28 Mar 2016 12:09:53 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Mon, 28 Mar 2016 12:09:53 -0700 (PDT)
In-Reply-To: <8975F15F-5C4C-4D02-98CD-BF4FDF104D35@sobco.com>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADEB0D16@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56F79D05.8070004@alvestrand.no> <326E6502-28E5-4D09-BB99-4A5D80625EB0@stewe.org> <56F88E18.2060506@it.aoyama.ac.jp> <20160328104731.GO88304@verdi> <CALaySJ+hYMMsKE7Ws-NJbyqH55E-mQM-duTEcJGc0TWvTP88Ew@mail.gmail.com> <20160328132859.GP88304@verdi> <28975138-9EA1-4A9F-A6C0-BC1416B8EA44@sobco.com> <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com> <8975F15F-5C4C-4D02-98CD-BF4FDF104D35@sobco.com>
Date: Mon, 28 Mar 2016 15:09:53 -0400
X-Google-Sender-Auth: OeHWXHxYoU3SmMqXZHVYM71ZJJQ
Message-ID: <CALaySJ+deDfJoMozK6qhYx6no2i+h9+=XidGkYe=Y3eW+AV5rQ@mail.gmail.com>
Subject: Re: Uppercase question for RFC2119 words
From: Barry Leiba <barryleiba@computer.org>
To: "Scott O. Bradner" <sob@sobco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-cx7oDmNsqYXnm_nJiM5BuRC9kQ>
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF discussion list <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 28 Mar 2016 19:09:57 -0000

> one minor tweak

A fine tweak.  I'll write it up and pass it to a few people before I
post the I-D.

I'd rather do it as an update to 2119, rather than a complete
revision, even though 2119 is so short, for two reasons:

1. I don't want to get into arguments about other changes.

2. I don't want to make 2119 obsolete: there's value in continuing to
refer to it with that RFC number.

Barry


>> On Mar 28, 2016, at 10:09 AM, Barry Leiba <barryleiba@computer.org> wrote:
>>
>>> The wishy washy descriptive rather than proscriptive language in the abstract was because I,
>>> the IESG and the community were not of one mind to say that the use of such capitalized
>>> terms should be mandatory - quite a few people felt that the english language was at
>>> least good enough to convey  the writer’s intent without having to aggrandize specific words.
>>> Thus the abstract basically was saying: if you want to use capitalized words here is a standard
>>> way to say what they mean
>>
>> Ah.  Then perhaps the clarification needs to go a little further and
>> make this clear:
>> - We're defining specific terms that specifications can use.
>> - These terms are always capitalized when these definitions are used.
>
> these definitions are only meaningful if the words are capitalized
>
>> - You don't have to use them.  If you do, they're capitalized and
>> their meanings are as specified here.
>> - There are similar-looking English words that are not capitalized,
>> and they have their normal English meanings; this document has nothing
>> to do with them.
>>
>> ...and I'd like to add one more, because so many people think that
>> text isn't normative unless it has 2119 key words in all caps in it:
>>
>> - Normative text doesn't require the use of these key words.  They're
>> used for clarity and consistency when you want that, but lots of
>> normative text doesn't need to use them, and doesn't use them.
>>
>> Barry
>