RE: RFC 2119 terms, ALL CAPS vs lower case
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 16 May 2012 18:45 UTC
Return-Path: <adrian@olddog.co.uk>
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 0EA5721F8655 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599]
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 84Afs+j4wf5H for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:45:36 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6021F861C for <ietf@ietf.org>; Wed, 16 May 2012 11:45:35 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4GIjV22018119; Wed, 16 May 2012 19:45:31 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4GIjUgR018108 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 May 2012 19:45:31 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Peter Saint-Andre' <stpeter@stpeter.im>, 'Ole Jacobsen' <ole@cisco.com>
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> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im>
In-Reply-To: <4FB3F54F.2030705@stpeter.im>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Date: Wed, 16 May 2012 19:45:28 +0100
Message-ID: <097701cd3394$113cb520$33b61f60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFpat9TDb/FjKlnnRfytPU9brudgAJtdb6SAUcBXMACpPelUwJZ29rfAeBZyNoBw7xEwgH5kHzhlyHKdWA=
Content-Language: en-gb
Cc: 'Sam Hartman' <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Wed, 16 May 2012 18:45:37 -0000
Remind me: Is bold must more or less compelling that underlined must. And where does uppercase MUST fit in? I fear the slightly richer publication format will give rise to a slightly more complex revision of RFC 2119. Adrian > -----Original Message----- > From: Peter Saint-Andre [mailto:stpeter@stpeter.im] > Sent: 16 May 2012 19:43 > To: Ole Jacobsen > Cc: Mary Barnes; adrian@olddog.co.uk; Sam Hartman; ietf@ietf.org > Subject: Re: RFC 2119 terms, ALL CAPS vs lower case > > On 5/16/12 12:26 PM, Ole Jacobsen wrote: > > > > And of course if we had a slightly richer publication format we could > > use, oh, say, underline, bold, italics and maybe even a special font > > for normative terms, but I guess I am dreaming decades ahead... > > Although I too dream the impossible dream, I would prefer not to trust > in formatting to enforce the semantic distinction in this instance. > > Peter
- RFC 2119 terms, ALL CAPS vs lower case Barry Leiba
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Scott Kitterman
- Re: RFC 2119 terms, ALL CAPS vs lower case Edward Lewis
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Adrian Farrel
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Andrew Sullivan
- Re: RFC 2119 terms, ALL CAPS vs lower case Simon Perreault
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Sam Hartman
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case Peter Saint-Andre
- Re: RFC 2119 terms, ALL CAPS vs lower case Mary Barnes
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Ole Jacobsen
- Re: RFC 2119 terms, ALL CAPS vs lower case Peter Saint-Andre
- RE: RFC 2119 terms, ALL CAPS vs lower case Adrian Farrel
- Re: RFC 2119 terms, ALL CAPS vs lower case Ole Jacobsen
- RE: RFC 2119 terms, ALL CAPS vs lower case John C Klensin
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Worley, Dale R (Dale)
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Cridland
- Re: [IETF] RE: RFC 2119 terms, ALL CAPS vs lower … Warren Kumari
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Jaap Akkerhuis
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Doug Barton
- Re: RFC 2119 terms, ALL CAPS vs lower case t.p.
- Re: RFC 2119 terms, ALL CAPS vs lower case Tony Finch
- Re: RFC 2119 terms, ALL CAPS vs lower case Tony Finch
- Re: RFC 2119 terms, ALL CAPS vs lower case Julian Reschke
- RE: RFC 2119 terms, ALL CAPS vs lower case Lee Howard
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case Marshall Eubanks
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Marshall Eubanks
- Re: RFC 2119 terms, ALL CAPS vs lower case Eric Rosen
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Carsten Bormann
- Re: RFC 2119 terms, ALL CAPS vs lower case Ofer Inbar
- Re: RFC 2119 terms, ALL CAPS vs lower case Eliot Lear
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Yaakov Stein
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Bill McQuillan
- Re: RFC 2119 terms, ALL CAPS vs lower case Stephen Farrell
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case John C Klensin
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Stephane Bortzmeyer
- Re: RFC 2119 terms, ALL CAPS vs lower case Marc Petit-Huguenin
- Re: RFC 2119 terms, ALL CAPS vs lower case Yoav Nir
- Re: RFC 2119 terms, ALL CAPS vs lower case Abdussalam Baryun