IETF Logo Mail Archive

RE: RFC 2119 terms, ALL CAPS vs lower case

"Worley, Dale R (Dale)" <dworley@avaya.com> Wed, 16 May 2012 20:12 UTC

Return-Path: <dworley@avaya.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 205CB21F8655 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.81
X-Spam-Level:
X-Spam-Status: No, score=-102.81 tagged_above=-999 required=5 tests=[AWL=-0.211, 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 sm5W6rWwiZgd for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:12:04 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 37D4421F8616 for <ietf@ietf.org>; Wed, 16 May 2012 13:12:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADQJtE/GmAcF/2dsb2JhbABEtA6BB4IVAQEBAQIBEihECwIBCA0IIRAyJQEBBBMIGodnBZ5KnQ+QBmIDnBGKKYMF
X-IronPort-AV: E=Sophos;i="4.75,605,1330923600"; d="scan'208";a="9639095"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 16 May 2012 16:12:01 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 May 2012 16:10:23 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 16 May 2012 16:12:02 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 16 May 2012 16:10:24 -0400
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Thread-Topic: RFC 2119 terms, ALL CAPS vs lower case
Thread-Index: Ac0znvmgtEX0EYejSIWrtRJ02RoOnAAAPOzA
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.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> <097701cd3394$113cb520$33b61f60$@olddog.co.uk>, <867B9B680EBE3644D4CCD518@PST.JCK.COM>
In-Reply-To: <867B9B680EBE3644D4CCD518@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 16 May 2012 20:12:05 -0000

> From: John C Klensin [john-ietf@jck.com]
> 
> > 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.
> 
> Let's try to remember that many of the comments/ requests for
> alternate publication formats have been to make "display" more a
> function of the devices being used.  Depending on type style
> variations (style, size, font variations, underlining, etc.)
> would pretty much defeat that particular claimed requirement.
> As I take Sam's note to sort of point out, even the use of
> uppercase to imply specific semantics can be problematic; we
> should at least strive to not make things worse, IMO.

I'm looking forward to the normative use of <BLINK>...</BLINK>.

Dale

v2.23.0 | Report a Bug | By Email