Re: [netmod] upcoming adoptions

Robert Wilton <rwilton@cisco.com> Thu, 07 September 2017 09:35 UTC

Return-Path: <rwilton@cisco.com>
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 434571326ED; Thu, 7 Sep 2017 02:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 WgmCeObn5-Rp; Thu, 7 Sep 2017 02:35:28 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5E82132EDE; Thu, 7 Sep 2017 02:35:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8984; q=dns/txt; s=iport; t=1504776928; x=1505986528; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=NoT6SXitmtAEl3aa4KIz8F1PBgowz3aQyHOu7v/BgkQ=; b=fVIPx0rIbIeuAr/76qo+rneG9ofhq6A2btyRScPIAC0WTwQgslxZ5ue7 ex2GIAmMxLdv8h/ywmWrYtbiqFIJk1ZKB2AY+a+sWXGGFmartKbINj4+7 c0CYCeRaZvrOETAIhMCaj+kjMA3aXFrG3GwquzkNNDtdm2hQvoGbtLC3N I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DhAwD3EbFZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhD5uJ4N3ixWQcyuQaYdRChgBCoRMTwKEQhUBAgEBAQEBAQFrKIU?= =?us-ascii?q?YAQEBAQIBAQEhSwsFCwsYJwMCAicfEQYBDAYCAQGKJQgQrUaCJyeLIgEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBARgFgyqDUIFjKwuCcogIgmEFkSiHDIhAlFGLVIcdjVe?= =?us-ascii?q?HVIE5NSKBDTIhCBwVSYccPzaLCgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.42,357,1500940800"; d="scan'208,217";a="655474278"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Sep 2017 09:35:25 +0000
Received: from [10.63.23.66] (dhcp-ensft1-uk-vla370-10-63-23-66.cisco.com [10.63.23.66]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v879ZPhN016457; Thu, 7 Sep 2017 09:35:25 GMT
To: Andy Bierman <andy@yumaworks.com>, Kent Watsen <kwatsen@juniper.net>
Cc: "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
References: <3620aafe-bc72-cc54-9dbd-b687a0178df2@cisco.com> <20170905.095949.1829098658779783521.mbj@tail-f.com> <CABCOCHRmNT=v9ivztzPh3OGmo-AeheHDct2XY9zbk_-FjEytmg@mail.gmail.com> <20170906.084124.2282926097915349446.mbj@tail-f.com> <38E666E2-EECE-4554-9A55-B98D829EB4CA@juniper.net> <CABCOCHQ-bBe307BgXJtxKOW3avmdkck4qrmj-oHTdmaRD5pU_w@mail.gmail.com> <A57EC752-3E23-4E8E-A802-C7CDD37A3DD1@juniper.net> <CABCOCHRcXUkzQb1g3rJzu3byxsASsCMD1ewtOwAbdfoYrZEMhg@mail.gmail.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <9cd0c109-6430-a649-66b1-8228c721538d@cisco.com>
Date: Thu, 7 Sep 2017 10:35:25 +0100
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: <CABCOCHRcXUkzQb1g3rJzu3byxsASsCMD1ewtOwAbdfoYrZEMhg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------001FF6F31DB488A4DD06A186"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hbtBoGupLgwgEKOQN-GtjIcmqAU>
Subject: Re: [netmod] upcoming adoptions
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: Thu, 07 Sep 2017 09:35:30 -0000


On 07/09/2017 03:36, Andy Bierman wrote:
>
>
> On Wed, Sep 6, 2017 at 10:57 AM, Kent Watsen <kwatsen@juniper.net 
> <mailto:kwatsen@juniper.net>> wrote:
>
>
>
>     >> /netconf-state and /restconf-state don't seem to follow the general
>     >> pattern we're correcting with the various NMDA updates. 
>     Particularly,
>     >> these -state trees are NOT for the purpose to providing the opstate
>     >> value for configured nodes.  These modules have the misfortune of
>     >> having "-state" in their name, but they're otherwise fine.
>     >
>     >
>     > This contradicts some details we have been told about NMDA
>     >
>     > 1) the transition guidelines say otherwise
>     >
>     > New modules and modules that are not concerned with the
>     > operational state of configuration information SHOULD
>     > immediately be structured to be NMDA-compatible
>
>     Yes, I'm suggesting we give ourselves some leeway, by taking
>     advantage of the SHOULD keyword above and defer updating these
>     two modules to when it makes more sense to do so.
>
>
>
> OK -- good.
> I think another sentence needs to be added.
>
>
> NMDA compatibility conversion MAY be deferred if the module
> does not contain any configuration datastore objects.
I agree.

>
>
>
>     > 2) RD defines operational state to include config=false nodes
>     > such as counters, so these modules are properly named.
>
>     module-name == top-level node name.  Either way, my point is that
>     the -state tree in these modules is not trying to provide the
>     opstate value for configured nodes (i.e. applied configuration).
>
>
> So a data node naming convention is needed?
> And a module naming convention?
>
> We need a rule that says the suffix "-state" is reserved for NMDA 
> compatibility
> so module names and data nodes SHOULD NOT be named with an identifier that
> ends in this suffix.
Also agree.

Thanks,
Rob


>
> (Automation tools like deterministic rules, not naming conventions.
> Here is an example why... there are always exceptions that do not follow
> the conventions. Always people who are unaware of the conventions.)
>
>
>
>     K.
>
>
>
>
> Andy
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod