Re: RFC 2119 terms, ALL CAPS vs lower case
Hector Santos <hsantos@isdg.net> Wed, 16 May 2012 23:00 UTC
Return-Path: <hsantos@isdg.net>
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 E9F2011E8086 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 16:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level:
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[AWL=0.649, 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 Q1SS1HvLfVQ5 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 16:00:03 -0700 (PDT)
Received: from mail.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB8111E8085 for <ietf@ietf.org>; Wed, 16 May 2012 16:00:02 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2052; t=1337209201; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=/V1HM82Q20EGGwb+gZRPJzPqOtI=; b=WNeLjtYda+eYnD3U5a1y ujvBV+iLRzukS3AEMiq9AR+nZXs4xCAI0ZgW3cvU0w5ja51l9h0dZkXty8SyQX9F YmXLDss3jx7GJEEj/FXycIZXRSzsAqIss0PNuWbuymzBxbQt8r8kmi2w1MQY6c15 jxmbZQ/ro0YXe7ZtGbYbXxI=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 19:00:01 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1821028677.90.5388; Wed, 16 May 2012 19:00:00 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2052; t=1337209179; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Qdfnu0w GuwZg7FuojuCXh1D7e63od7Pv2ouHwIcMQkc=; b=iik4qeygPR5RL9TfdTxgs8w rDv0hESj7Rsd1XaVuQQjh7hA5TLaSC3TVmgV7+YoZaEzeSxDiqkoGFGTb3jiypw3 453qAiR91Bl8iRV4sV19j8DmCTm6GjIbcwMTvcBhzRNkEy2QQIWkItVJMw4E3Klf HbAxeA+RAjB9aTJ628g0=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 18:59:39 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2419911847.7642.2832; Wed, 16 May 2012 18:59:38 -0400
Message-ID: <4FB4317C.3000900@isdg.net>
Date: Wed, 16 May 2012 19:00:12 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
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> <4FB3EDB8.60809@gmail.com>
In-Reply-To: <4FB3EDB8.60809@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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 23:00:04 -0000
+1 My view that this is more about the specific issues of documents and not just RFC2119 itself. Sometimes it falls through the cracks. Sometimes a justification or argument is found to show the contrary of what is stated, especially when its uses lower cases or even terms like "choose." Sometimes its just new conflicts of integrated documents where perhaps an augmented RFC attempts to reinforce what the base RFC may have lacked. In my view, it will help if future I-D and RFC authors begin to have one new section called in chapter 1.0 1.x - Minimum Compliancy Requirement Summary Far too often documents have mixed functional and technical specifications, mixed normative and non-normative compliance semantics too spread out and peppered throughout the document making it harder to catch compliance level issues. -- HLS Brian E Carpenter wrote: > On 2012-05-16 18:53, Peter Saint-Andre wrote: >> On 5/16/12 9:58 AM, Sam Hartman wrote: > > ... >>> I'll note that in my normal reading mode I do not distinguish case, >>> but even so I find the ability to use may and should in RFC text without >>> the 2119 implications valuable. > > Agreed. But as a gen-art reviewer, I have several times had to ask > authors whether a particular lower case "may" was intended to be normative > or normal English. Authors must be fastidious about this. > >> Your mileage may (or is that MAY?) vary, but to forestall confusion I've >> settled on the practice of using "can" and "might" instead of lowercase >> "may", "ought to" and "is suggested to" instead of lowercase "should", >> and "needs to" or "has to" instead of lowercase "must" (etc.). I'm not >> saying that anyone else SHOULD or MUST use that convention, but you >> might consider it in your own spec-writing. > > It is indeed very important not to use "may" when it's ambiguous. > "It may rain today" is fine; "you may leave now" is not (I can think > of three different meanings). In RFC2119-talk, "you MAY leave now" > only has one meaning.
- 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