Re: Uppercase question for RFC2119 words
John C Klensin <john-ietf@jck.com> Mon, 28 March 2016 18:23 UTC
Return-Path: <john-ietf@jck.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 66EE812D1D3;
Mon, 28 Mar 2016 11:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01]
autolearn=ham autolearn_force=no
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 v_T_T6j5VVSt; Mon, 28 Mar 2016 11:23:50 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id A798012D4FE;
Mon, 28 Mar 2016 11:23:50 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com)
by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD))
(envelope-from <john-ietf@jck.com>)
id 1akbpH-000GH8-8o; Mon, 28 Mar 2016 14:23:43 -0400
Date: Mon, 28 Mar 2016 14:23:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, "Scott O. Bradner" <sob@sobco.com>
Subject: Re: Uppercase question for RFC2119 words
Message-ID: <4D8EE9FD4F1B5C0FC90322DE@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com>
<949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
<CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.c
om>
<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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eNU-whyV0z8PTAzf4cNA0Z5mjCc>
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.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 18:23:52 -0000
Yes. +1. About time and long overdue. john --On Monday, March 28, 2016 10:09 -0400 Barry Leiba <barryleiba@computer.org> wrote: > 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. - 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.
- Uppercase question for RFC2119 words John Leslie
- Re: Uppercase question for RFC2119 words Scott O. Bradner
- Re: Uppercase question for RFC2119 words Barry Leiba
- Re: Uppercase question for RFC2119 words Scott O. Bradner
- Re: Uppercase question for RFC2119 words John C Klensin
- Re: Uppercase question for RFC2119 words Barry Leiba
- Fuzzy words [was Uppercase question for RFC2119 w… Brian E Carpenter
- RE: Fuzzy words [was Uppercase question for RFC21… Eric Gray
- Re: Fuzzy words [was Uppercase question for RFC21… Barry Leiba
- Re: Uppercase question for RFC2119 words John Levine
- Re: Uppercase question for RFC2119 words David Farmer
- Re: Uppercase question for RFC2119 words Dick Franks
- Re: Uppercase question for RFC2119 words S Moonesamy
- Re: Fuzzy words [was Uppercase question for RFC21… Tony Finch
- Re: Fuzzy words [was Uppercase question for RFC21… Scott Bradner
- Re: Fuzzy words [was Uppercase question for RFC21… Loa Andersson
- Re: Fuzzy words [was Uppercase question for RFC21… Randy Bush
- Re: Fuzzy words [was Uppercase question for RFC21… John C Klensin
- Re: Fuzzy words [was Uppercase question for RFC21… Scott Bradner
- Re: Fuzzy words [was Uppercase question for RFC21… Ben Campbell
- Re: Fuzzy words [was Uppercase question for RFC21… Dave Cridland
- Re: Fuzzy words [was Uppercase question for RFC21… John C Klensin
- Re: Fuzzy words [was Uppercase question for RFC21… Heather Flanagan (RFC Series Editor)
- Re: Fuzzy words [was Uppercase question for RFC21… HANSEN, TONY L
- Re: Fuzzy words [was Uppercase question for RFC21… John C Klensin
- Re: Fuzzy words [was Uppercase question for RFC21… Dave Cridland
- Re: Fuzzy words [was Uppercase question for RFC21… HANSEN, TONY L
- Re: Fuzzy words [was Uppercase question for RFC21… John C Klensin
- Re: Fuzzy words [was Uppercase question for RFC21… Eliot Lear
- Re: Fuzzy words [was Uppercase question for RFC21… Brian E Carpenter
- Re: Fuzzy words [was Uppercase question for RFC21… Scott O. Bradner
- Re: Fuzzy words [was Uppercase question for RFC21… Brian E Carpenter
- Re: Fuzzy words [was Uppercase question for RFC21… Brian E Carpenter
- Re: Fuzzy words [was Uppercase question for RFC21… Dave Cridland
- Re: Uppercase question for RFC2119 words Adam Roach
- Re: [rtcweb] Uppercase question for RFC2119 words Dave Crocker
- Re: [rtcweb] Uppercase question for RFC2119 words Adam Roach
- Re: [rtcweb] Uppercase question for RFC2119 words Eliot Lear
- Re: Uppercase question for RFC2119 words Lee Howard
- Re: [rtcweb] Uppercase question for RFC2119 words Ben Campbell
- Re: Uppercase question for RFC2119 words Warren Kumari
- Re: [rtcweb] Uppercase question for RFC2119 words Dave Cridland
- Re: [rtcweb] Uppercase question for RFC2119 words Adam Roach
- Re: [rtcweb] Uppercase question for RFC2119 words Dave Crocker
- Re: [rtcweb] Uppercase question for RFC2119 words John C Klensin
- Re: [rtcweb] Uppercase question for RFC2119 words Pat Thaler
- Re: [rtcweb] Uppercase question for RFC2119 words Ole Jacobsen
- Re: [rtcweb] Uppercase question for RFC2119 words Barry Leiba
- Re: [rtcweb] Uppercase question for RFC2119 words Stephan Wenger
- Re: [rtcweb] Uppercase question for RFC2119 words Dave Cridland
- Re: [rtcweb] Uppercase question for RFC2119 words Mark Andrews
- RE: [rtcweb] Uppercase question for RFC2119 words Drage, Keith (Nokia - GB)
- RE: [rtcweb] Fuzzy words [was Uppercase question … Drage, Keith (Nokia - GB)
- Re: [rtcweb] Uppercase question for RFC2119 words tom p.
- Re: [rtcweb] Uppercase question for RFC2119 words Lee Howard
- Re: Fuzzy words [was Uppercase question for RFC21… Abdussalam Baryun
- Re: Uppercase question for RFC2119 words Francis Dupont