Re: [netmod] upcoming adoptions - this appendix is normative

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Mon, 02 October 2017 16:37 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B86D71344D3 for <netmod@ietfa.amsl.com>; Mon, 2 Oct 2017 09:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level:
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4SL-n4s7Pun for <netmod@ietfa.amsl.com>; Mon, 2 Oct 2017 09:37:42 -0700 (PDT)
Received: from mail-pg0-f44.google.com (mail-pg0-f44.google.com [74.125.83.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B8D9132F65 for <netmod@ietf.org>; Mon, 2 Oct 2017 09:37:42 -0700 (PDT)
Received: by mail-pg0-f44.google.com with SMTP id u144so551191pgb.8 for <netmod@ietf.org>; Mon, 02 Oct 2017 09:37:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JKolFI7NH46aBUOp4sZjRRvUHwPdCrYMycMr2Xf2n3U=; b=ohofHLwnPYzkr3qn1LTbm/BWLmFYuLCI+paYR0Dk9Yj16WvMDcmY4QCUcDDrupEOZQ Vokd0kGuumW9OEpLxhMRRHTAAqgRl2rQh+gTTAsMEHczZ6EoeqB4Yc/NZaBXrgW/+Hon m/p7dsaupJcv0GHcFJreVU4bNvpiCJsTCopVDtoCYoIZwzSv1bZDvx+7qlkmWCcsMjbb LXbJuEXTpnl5OCJ/6fqmx5hvQhxGT30ZDtoW083XQREyC0Pp0k5MBk/sBxBd4+ytqrmc ngT1po9b+NxHcNl8HnQk5BRoscgbtj9ewBAaMGkKdesF52dNIGIZpH4EY0lpp9S9NEBn z41g==
X-Gm-Message-State: AHPjjUiTRw7nYEonkLLAnxyRF+fasmsQnucDRQsmV+AyubinsFHxcdb5 2EwJVRUfaQ503GZy67e0z2oaa6o2ARU=
X-Google-Smtp-Source: AOwi7QDuXrybhjXxjJ/lT0w95vbEdlZTcHkCx+IfMTF2cSPhj1CsWcEfslkpnIkXjLG86DKCZcvfyg==
X-Received: by 10.99.117.13 with SMTP id q13mr12861630pgc.366.1506962261390; Mon, 02 Oct 2017 09:37:41 -0700 (PDT)
Received: from [192.168.1.100] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id s62sm20572921pfe.91.2017.10.02.09.37.40 for <netmod@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Oct 2017 09:37:40 -0700 (PDT)
To: netmod@ietf.org
References: <36ba3d4b-1ae1-0666-12cf-db41e172924b@cisco.com> <75739d75-da96-b340-2403-d0949ac54ed7@labn.net> <19134054-D52E-4A6D-992A-A47F365557AD@juniper.net> <2891bd09-0e0d-415c-2714-15141a293e42@cisco.com> <D14158EF-77F4-4E0A-9A06-213F5CF04647@juniper.net> <011d01d32d77$c8e0a500$4001a8c0@gateway.2wire.net> <9c0d8394-b2a4-180a-2454-8955c1721423@labn.net> <003801d32e3f$ba625460$4001a8c0@gateway.2wire.net> <920d0500-e7ea-66ff-5124-a025a438dbac@cisco.com> <15edcab6a58.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <20171002110504.d6kscxoot3nb3c3a@elstar.local> <4f2f072c-ff80-30a9-5bc8-08a9d527f52b@labn.net> <4aac1910-dee9-9a8f-0b4a-1adf3103c9d4@cisco.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <c94273ff-9b71-e002-8a3c-695291e38fcd@alumni.stanford.edu>
Date: Mon, 02 Oct 2017 09:37:39 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <4aac1910-dee9-9a8f-0b4a-1adf3103c9d4@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/7U1UwhvIsDXrivir8_izZ7djdyM>
Subject: Re: [netmod] upcoming adoptions - this appendix is normative
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2017 16:37:49 -0000

Hi -

On 10/2/2017 7:18 AM, Robert Wilton wrote:
> This discussion may be conflating two issues:
> 
> (i) Does RFC text have to use RFC2119 terms to be normative?
> RFC 8174 categorically states that text can still be normative without 
> using RFC 2119 terms.

Thus it's clear that their usage is not necessarily necessary.

> (ii) Should standards track documents use RFC 2119 terms?
> If 93% of recently published standards track RFCs make use of RFC 2119 
> terms then that seems like a strong consistency argument to use them 
> unless there is a good reason not to.

I think RFC 2119 itself provides a fair counter-argument to the
imposition of such a requirement.  RFC 2119 states that "[i]mperatives
of the type defined in this memo must be used with care and sparingly."
To use "with care" and "sparingly" seems contrary to the notion of
employing them merely for "consistency."

Randy