Re: RFC2119 keywords in registration requirements
Ted Lemon <Ted.Lemon@nominum.com> Wed, 30 October 2013 03:10 UTC
Return-Path: <Ted.Lemon@nominum.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 B0DF521F9C99 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level:
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 XZ7+-hT0911J for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:10:06 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 53ED121E80FD for <ietf@ietf.org>; Tue, 29 Oct 2013 20:09:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUnB4ezKW4honXoWhozCVx0pqa2NgoVGM@postini.com; Tue, 29 Oct 2013 20:09:57 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6B5EE1B82D0 for <ietf@ietf.org>; Tue, 29 Oct 2013 20:09:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5C85A190043; Tue, 29 Oct 2013 20:09:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.03.0158.001; Tue, 29 Oct 2013 20:09:47 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OTt31k5HczOUEyidcQz8NpgJZoMlp0AgAAH1wCAAGgSgA==
Date: Wed, 30 Oct 2013 03:09:46 +0000
Message-ID: <29A5B270-AC17-49FB-B562-4CDEB227FEB5@nominum.com>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <7064681F-4BA2-470E-A302-8E393800CA69@vpnc.org>
In-Reply-To: <7064681F-4BA2-470E-A302-8E393800CA69@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A19E0D33BCCBAD458156C08FF7FC70D0@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Julian Reschke <julian.reschke@gmx.de>, "Bradner, Scott" <sob@harvard.edu>, IETF Discussion <ietf@ietf.org>
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, 30 Oct 2013 03:10:11 -0000
On Oct 29, 2013, at 4:57 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote: > It is also completely reasonable to say "needs to include" as well. Blargh. The word you want to use there is "must." You're saying "needs to" because you mean "must" but are trying to say it a different way. "Needs to" does not mean the same thing as "must." There has been some discussion of this topic recently in the IESG, which (AFAIK) has not reached consensus on the following: http://trac.tools.ietf.org/group/iesg/trac/wiki/Draft2119BoilerplateSuggestions I'd be curious to hear reactions, bearing in mind that this is _not_ an IESG statement, at least at the moment.
- RFC2119 keywords in registration requirements Julian Reschke
- Re: RFC2119 keywords in registration requirements Bradner, Scott
- Re: RFC2119 keywords in registration requirements Julian Reschke
- Re: RFC2119 keywords in registration requirements Bradner, Scott
- Re: RFC2119 keywords in registration requirements Julian Reschke
- Re: RFC2119 keywords in registration requirements Bradner, Scott
- Re: RFC2119 keywords in registration requirements Ted Lemon
- Re: RFC2119 keywords in registration requirements Barry Leiba
- Re: RFC2119 keywords in registration requirements ned+ietf
- Re: RFC2119 keywords in registration requirements Bjoern Hoehrmann
- Re: RFC2119 keywords in registration requirements Julian Reschke
- Re: RFC2119 keywords in registration requirements ned+ietf
- Re: RFC2119 keywords in registration requirements Paul Hoffman
- Re: RFC2119 keywords in registration requirements Ted Lemon
- Re: RFC2119 keywords in registration requirements John Levine