Re: [netmod] RFC 2119 language [was Re: WG Last Call: draft-ietf-netmod-revised-datastores-04 updates]

Lou Berger <lberger@labn.net> Wed, 27 September 2017 17:20 UTC

Return-Path: <lberger@labn.net>
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 B262F134E91 for <netmod@ietfa.amsl.com>; Wed, 27 Sep 2017 10:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 W1rexLGHC4Fr for <netmod@ietfa.amsl.com>; Wed, 27 Sep 2017 10:20:21 -0700 (PDT)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 154D6134E8E for <netmod@ietf.org>; Wed, 27 Sep 2017 10:20:21 -0700 (PDT)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id BEF3C1E0850 for <netmod@ietf.org>; Wed, 27 Sep 2017 11:20:20 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id EhLG1w00g2SSUrH01hLKlQ; Wed, 27 Sep 2017 11:20:20 -0600
X-Authority-Analysis: v=2.2 cv=K4VSJ2eI c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=2JCJgTwv5E4A:10 a=NEAV23lmAAAA:8 a=j3Z76cjpAAAA:8 a=48vgC7mUAAAA:8 a=ZdAbnrQtolJFRyD-KY0A:9 a=QEXdDO2ut3YA:10 a=FvgKqOQ44qUA:10 a=JrSEOxZJtCQA:10 a=9ZYBcOd_X9kS2t7VFny2:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=VRfuZNlqLhtq05ZA3xwmG8iRPNwg+laTW9H0BWghM/8=; b=RLe/ia3Tj1XtqF0ZHfwBDD8EY8 pDu7oIlIRHOPFuoNopVydmKl19j+xkj14rtjmMTpHwveLmYyctL3YYE5uzRAKvynbVkVhXSeJopSk UPY2nKEAjw+Ft8dYzskIu8jRF;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:35250 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1dxG0O-003txJ-Ac; Wed, 27 Sep 2017 11:20:16 -0600
To: Robert Wilton <rwilton@cisco.com>, netmod WG <netmod@ietf.org>, NetMod WG Chairs <netmod-chairs@ietf.org>, draft-ietf-netmod-revised-datastores@ietf.org
References: <511deba5-34ca-dde2-6637-ceaf4c4af125@labn.net> <022001d32e14$8d5d4540$4001a8c0@gateway.2wire.net> <20170915123443.kvagu7dut7oaqoo2@elstar.local> <CABCOCHQcSUSUZMvzVGyaXObHadZqksKge89_6YcH9PCbxMCG=g@mail.gmail.com> <20170916072403.xp37556z6g7b42gr@elstar.local> <CABCOCHT8CMCAnqf6Oe1bKMzQ-B_0GjrQiQ8YXgQJvCo-NBOBBA@mail.gmail.com> <07b5a5df-794e-2ba8-6cad-abfcfadfc4cc@cisco.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <4d345c3b-a28b-a0e0-27cb-306ff4618d0e@labn.net>
Date: Wed, 27 Sep 2017 13:20:13 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <07b5a5df-794e-2ba8-6cad-abfcfadfc4cc@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1dxG0O-003txJ-Ac
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:35250
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/MpiX38BbU6KAmMAnc0Sku48Mq_Q>
Subject: Re: [netmod] RFC 2119 language [was Re: WG Last Call: draft-ietf-netmod-revised-datastores-04 updates]
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: Wed, 27 Sep 2017 17:20:26 -0000

I think this goes to if this, or any, draft is a proposed standard or
not. In other words, if it specifies any behavior that for which
interoperability between independent implementations is the objective. 
My general view is that in a Proposed Standard RFC, if it impacts
interoperability, the text should be normative and an RFC should use
2119 language to identify such normative text.  I accept that this is
not strictly required by IETF process, but it has become the norm for PS
track RFCs produced today  -- and I see no reason to not follow IETF norm.

In the context of this draft , as I read it, at least section 5.1 and
some portions of 4.

Lou

On 9/27/2017 12:28 PM, Robert Wilton wrote:
>
> The authors discussed this, and we will close this issue
> (https://github.com/netmod-wg/datastore-dt/issues/14 - title: Does the
> NMDA architecture need to use RFC 2119 language?) by adding RFC 2119
> text to the document, which will probably be best illustrated with an
> updated draft revision.
>
> For the record, the majority of the authors had the view that RFC 2119
> language does not particularly aid readability in this architecture
> document.
>
> Thanks,
> Rob
>
>
> On 16/09/2017 10:56, Andy Bierman wrote:
>>
>>
>> On Sat, Sep 16, 2017 at 12:24 AM, Juergen Schoenwaelder
>> <j.schoenwaelder@jacobs-university.de
>> <mailto:j.schoenwaelder@jacobs-university.de>> wrote:
>>
>>     On Fri, Sep 15, 2017 at 02:07:58PM -0700, Andy Bierman wrote:
>>     > Hi,
>>     >
>>     > I strongly agree with Tom that the current draft is an update
>>     to RFC 7950.
>>     > I also strongly disagree with the decision to omit RFC 2119 in
>>     a standards
>>     > track document. IMO RFC 2119 terms need to be used in normative
>>     text,
>>     > especially when dealing with XPath and YANG compiler behavior.
>>     >
>>
>>     RFC 8174:
>>
>>        o  These words can be used as defined here, but using them is not
>>           required.  Specifically, normative text does not require
>>     the use
>>           of these key words.  They are used for clarity and consistency
>>           when that is what's wanted, but a lot of normative text
>>     does not
>>           use them and is still normative.
>>
>>
>> So what?
>> Existing YANG specifications use RFC 2119 terms.
>> This draft uses those terms, just with lower-case.
>> Either way, the new YANG rules seem half-baked and not ready
>> for standardization.
>>
>>  
>>
>>     /js
>>
>>
>> Andy
>>  
>>
>>     --
>>     Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>>     Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen |
>>     Germany
>>     Fax:   +49 421 200 3103         <http://www.jacobs-university.de/
>>     <http://www.jacobs-university.de/>>
>>
>>
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod