Re: RFC2119 keywords in registration requirements

Barry Leiba <barryleiba@computer.org> Tue, 29 October 2013 21:07 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 5000911E81C9 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.952
X-Spam-Level:
X-Spam-Status: No, score=-101.952 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 I75OgEkc9zyO for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:05 -0700 (PDT)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 1682D11E81DF for <ietf@ietf.org>; Tue, 29 Oct 2013 14:06:53 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id q12so310203vbe.27 for <ietf@ietf.org>; Tue, 29 Oct 2013 14:06:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=sMCfe7OArdgL+PXBeiazC8O//uIfZN7F7/SZl4oO03Q=; b=wUMTerilUwe11e6oEOOANFEb9U/+Lw0/AwuHQr06+ajf4XxdjSaL1FafazNwCinU0U UwUUUWzYWqF+57fp1/IwleYApQiwFJy/GCa4URdE4xhxWX9/1CPJCJO4Ibw2mjpF4bXJ GUPcMZQn8rMdQ1r7Bg6NVSSfwBAsLO1+aTMZZPSp/4Z92re2vxoHuSqtcbquYVTxdWkg eD1oFj1uauiikr+8QYb+gUK3RUVp8hLrQqgef9IqG3eDNlEwdQze47tMuD+DAZLKMqp2 xvnfOEboPW+8E7QJOaJrebKQs2LJB5MZTWLf84Z7cxWQGBv4JHykZjcAs+idyWv8c18E 5Y8Q==
MIME-Version: 1.0
X-Received: by 10.220.76.201 with SMTP id d9mr314099vck.49.1383080806919; Tue, 29 Oct 2013 14:06:46 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Tue, 29 Oct 2013 14:06:46 -0700 (PDT)
In-Reply-To: <52701D1D.3030004@gmx.de>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de>
Date: Tue, 29 Oct 2013 17:06:46 -0400
X-Google-Sender-Auth: giw2tbkMuxMRiZTD9GITUTtn8qk
Message-ID: <CAC4RtVAhNcXrOPhms=6+LNdiJZF5cj6gJUH2Kg=Pkru=g4A8bw@mail.gmail.com>
Subject: Re: RFC2119 keywords in registration requirements
From: Barry Leiba <barryleiba@computer.org>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary="001a11c2cfb03135ed04e9e7985b"
Cc: 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: Tue, 29 Oct 2013 21:07:08 -0000

First, I think we have to take the question of whether and when to use 2119
key words into the context of the document we're writing.  BCPs and
Informational documents can and do use them, but they use them in somewhat
different ways than Standards Track documents do, while still maintaining
the spirit of that text you quote from RFC 2119.

Second, I bristle when I see instructions to IANA in the form of "IANA MUST
[do this]."  We should not use 2119 key words in registration information
in that way.

Third, as instructions to registrants, I think it's absolutely fine to say
"you MUST [include this information," and "you SHOULD [include that
information]," and so on.  I think that respects the spirit of 2119, in
that things are more likely to interoperate if the documentation of
registered values is up to snuff.

Barry

On Tuesday, October 29, 2013, Julian Reschke wrote:

> On 2013-10-29 21:29, Bradner, Scott wrote:
>
>> seems to me to be completely reasonable to say MUST include the number of
>> the RFC that describes
>> the protocol being registered (for example)
>>
>> Scott
>>
>
> But then:
>
>  6. Guidance in the use of these Imperatives
>>
>>    Imperatives of the type defined in this memo must be used with care
>>    and sparingly.  In particular, they MUST only be used where it is
>>    actually required for interoperation or to limit behavior which has
>>    potential for causing harm (e.g., limiting retransmisssions)  For
>>    example, they must not be used to try to impose a particular method
>>    on implementors where the method is not required for
>>    interoperability.
>>
>
> To me this indicates that we should keep them out of registrations
> procedures.
>
> (I also note that the "MUST" in the text I quoted shouldn't been used if
> the text followed its own advice :-).
>
> Best regards, Julian
>