IETF Logo Mail Archive

Re: RFC 2119 terms, ALL CAPS vs lower case

Ole Jacobsen <ole@cisco.com> Wed, 16 May 2012 18:46 UTC

Return-Path: <ole@cisco.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 4CFDF21F866C for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.682
X-Spam-Level:
X-Spam-Status: No, score=-110.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 yytLfFD3dkrn for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:46:28 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id BE32721F865A for <ietf@ietf.org>; Wed, 16 May 2012 11:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=926; q=dns/txt; s=iport; t=1337193988; x=1338403588; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=herdpmaQUqv+BiNCbvchNVoGnqQeo1wDDdZheV0Mdhk=; b=O65OAOnsuTOz6+wMEdHPI0AlG3YDK07CeP5rvygoli7R+yvYN3zG1scF FEq/rQyqaa08AHcNF1a9yAto7naiARaauhPV9ZCt9w5B4J52kklUbiY46 kEFhEDlW+Z1Afv9+eBu1l0cHUoJmeQ5GYhUUxyERLtv04juEIr0XB9dKZ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIvTs0+tJV2d/2dsb2JhbABBA7QLgQeCFQEBAQMBEgECJT8FCwsYLlcGEyKHZwWbI4NFEJwwixMZghSDKAOIY5hXgxeBAmeDCYE/
X-IronPort-AV: E=Sophos;i="4.75,604,1330905600"; d="scan'208";a="83653715"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 16 May 2012 18:46:28 +0000
Received: from bxb-vpn3-744.cisco.com (bxb-vpn3-744.cisco.com [10.86.250.232]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q4GIkPp6010058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 18:46:27 GMT
Date: Wed, 16 May 2012 11:46:24 -0700
From: Ole Jacobsen <ole@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <4FB3F54F.2030705@stpeter.im>
Message-ID: <alpine.OSX.2.01.1205161144580.47757@bxb-vpn3-744.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>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
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:46:29 -0000

Yeah, that's probably a safer approach. One could of course
imagine some kind of hybrid and parsing in the form of *very*
or /very/ explicit terms. Maybe this is orthogonal to the
other discussion we are having...

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 16 May 2012, Peter Saint-Andre wrote:

> 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
>

v2.23.0 | Report a Bug | By Email