[netmod] YANG modules publication: what to focus on next? March 14th

Benoit Claise <bclaise@cisco.com> Wed, 14 March 2018 14:56 UTC

Return-Path: <bclaise@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 7EF091270FC for <netmod@ietfa.amsl.com>; Wed, 14 Mar 2018 07:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.61
X-Spam-Level:
X-Spam-Status: No, score=-12.61 tagged_above=-999 required=5 tests=[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, T_RP_MATCHES_RCVD=-0.01, 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 0IG6SlBRt_KW for <netmod@ietfa.amsl.com>; Wed, 14 Mar 2018 07:56:11 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EE9B127337 for <netmod@ietf.org>; Wed, 14 Mar 2018 07:56:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27991; q=dns/txt; s=iport; t=1521039371; x=1522248971; h=subject:references:from:to:message-id:date:mime-version: in-reply-to; bh=flSyQPaiFT4IssCrrB58XbmGsVmHCYrX3tpcgSwEJgw=; b=VM2Sdy5GPo0B5BIkeGlyV7XygddjjGbnFomPn0ctEPwVPOmh90YPzSyE E6ekHHs0Yjq42u6qkJDewSRxIvYeIbc1oDCTKEJG7MECqfRMT4bR2kWAJ YDfYBiyRHssSbQ+2fkeNGevODgIhIZVrQHqve1Leo8g9wvlThDbE+y3IH k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B6AQBhM6la/xbLJq1DGhwBAQEEAQEKA?= =?us-ascii?q?QGENXAog1CKGnKPBIEWlDYUgX8KHAGEdAIagy00GAECAQEBAQEBAmsohSUBBiN?= =?us-ascii?q?mHAMBAisCAgJNCAYNBgIBAYUUDzKsEoImJoRJg3KCBwWFLoNpgVQohDmBXQIBA?= =?us-ascii?q?QEBgSoiLQmCaIJiBJM6hx4JhkaKFweBY4Q1gnOFVol8gU2GBIEsHjiBUjMaCBs?= =?us-ascii?q?Vgn2CP44xPzcBj0sBAQE?=
X-IronPort-AV: E=Sophos;i="5.47,470,1515456000"; d="scan'208,217";a="2606824"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Mar 2018 14:56:08 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w2EEu86X013924 for <netmod@ietf.org>; Wed, 14 Mar 2018 14:56:08 GMT
References: <42d768a1-2b28-3269-e450-d88bf8b3b441@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
To: NETMOD Working Group <netmod@ietf.org>
X-Forwarded-Message-Id: <42d768a1-2b28-3269-e450-d88bf8b3b441@cisco.com>
Message-ID: <b8ca956c-89aa-85da-5e7f-942fdf6c5a97@cisco.com>
Date: Wed, 14 Mar 2018 15:56:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <42d768a1-2b28-3269-e450-d88bf8b3b441@cisco.com>
Content-Type: multipart/alternative; boundary="------------47097A6644E502A1C9B67891"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/S9i3D6QXZiHzOaEJMuC5pAloLT4>
Subject: [netmod] YANG modules publication: what to focus on next? March 14th
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, 14 Mar 2018 14:56:14 -0000

Added: draft-ietf-lime-yang-connection-oriented-oam-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection-oriented-oam-model/> 



-------- Forwarded Message --------
Subject: 	[netmod] YANG modules publication: what to focus on next? Feb 
16th
Date: 	Fri, 16 Feb 2018 11:35:45 +0100
From: 	Benoit Claise <bclaise@cisco.com>;
To: 	NETMOD Working Group <netmod@ietf.org>;



Dear all,

At the last IETF meeting, Alia, Deborah and I looked at the publication 
status of most YANG modules.
Since that time, I've been keeping a summary of the situation. Let me 
share it with everybody.

Before publishing YANG modules, we have two series of bottlenecks:
- the YANG module import (shown by tooling below)
- the normative references (MISSREF in the RFC editor queue 
<https://www.rfc-editor.org/current_queue.php>)

Recently, we processed some more YANG modules:
     On the Feb 22nd telechat we added: 
draft-ietf-lime-yang-connection-oriented-oam-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection-oriented-oam-model/>
     On the March 8th telechat, we added: 
draft-ietf-netmod-syslog-model-24 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/>
     One last DISCUSS on draft-ietf-pim-yang-15 
<https://datatracker.ietf.org/doc/draft-ietf-pim-yang/>

We now have many YANG modules in RFC editor queue:**
**draft-ietf-netconf-rfc6536bis-09 (AUTH48) 
<https://datatracker.ietf.org/doc/draft-ietf-netconf-rfc6536bis>**
****draft-ietf-netmod-revised-datastores-10 (AUTH48) 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/>
*draft-ietf-netmod-yang-tree-diagrams-05 (expedited processing) 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-tree-diagrams/>
**draft-ietf-lime-yang-connectionless-oam-18 
<https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam>**
****draft-ietf-lime-yang-connectionless-oam-methods-13 
<https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam-methods>**
**draft-ietf-lime-yang-connection-oriented-oam-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection-oriented-oam-model/>
****draft-ietf-i2rs-yang-l3-topology-16 
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology>**
****draft-ietf-i2rs-yang-network-topo-20 
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo>**
****draft-wu-l3sm-rfc8049bis-11 
<https://datatracker.ietf.org/doc/draft-wu-l3sm-rfc8049bis>****
*draft-ietf-netmod-rfc7223bis-03 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7223bis/>
draft-ietf-netmod-rfc7277bis-03 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7277bis/>
draft-ietf-rtgwg-yang-vrrp-09 
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-vrrp/>
draft-ietf-rtgwg-yang-rip-08 
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rip/>
draft-ietf-netmod-rfc8022bis-10 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc8022bis/>
draft-ietf-netmod-entity-08 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/>
draft-ietf-rtgwg-ni-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/>
draft-ietf-rtgwg-lne-model-09 
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>
draft-ietf-pim-yang-15 (almost there: one last DISCUSS) 
<https://datatracker.ietf.org/doc/draft-ietf-pim-yang/>


Here are the YANG module dependencies 
<https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-ip&modules[]=ietf-connectionless-oam&modules[]=ietf-lime-time-types&modules[]=ietf-connectionless-oam-methods&modules[]=ietf-l3-unicast-topology&modules[]=ietf-l3-unicast-topology-state&modules[]=ietf-network-topology&modules[]=ietf-network-topology-state&modules[]=ietf-network&modules[]=ietf-network-state&modules[]=ietf-l3vpn-svc&modules[]=ietf-netconf-acm&modules[]=ietf-interfaces&modules[]=ietf-vrrp&modules[]=ietf-rip&modules[]=ietf-datastores&modules[]=ietf-origin&modules[]=ietf-ipv4-unicast-routing&modules[]=ietf-ipv6-unicast-routing&modules[]=ietf-ipv6-router-advertisements&modules[]=ietf-routing&modules[]=iana-hardware&modules[]=ietf-hardware&modules[]=ietf-hardware-state&modules[]=ietf-logical-network-element&modules[]=ietf-network-instance&modules[]=ietf-syslog&modules[]=ietf-connection-oriented-oam&modules[]=ietf-pim-base&modules[]=ietf-pim-dm&modules[]=ietf-pim-sm&modules[]=ietf-pim-bidir&modules[]=ietf-pim-rp&recurse=1&rfcs=1&show_subm=1&show_dir=dependencies> 
for these RFC editor modules, as requirement before publishing.

It takes a little bit of re-arrangering the elements, but all the 
information regarding YANG module dependency is there.

The next bottlenecks for publishing those YANG modules are:
     draft-ietf-netmod-schema-mount (kind of an impasse right now: to be 
discussed in NETMOD)
     ietf-bfd-yang (currently under review by the YANG doctors)
     draft-ietf-ospf-yang (currently under review by the YANG doctors)
     draft-ietf-isis-yang-isis-cfg (currently under review by the YANG 
doctors)
     draft-ietf-netconf-keystore (to be discussed in NETMOD)
     draft-ietf-netconf-tls-client-server
Please progress those documents asap

Some more updates below.

_L2SM:_
draft-ietf-l2sm-l2vpn-service-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/> 
(on the next IESG telechat)

_I2RS:_
draft-ietf-i2rs-rib-data-model-10 
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/> (on 
the next IESG telechat)
draft-ietf-i2rs-yang-dc-fabric-network-topology-06 
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-dc-fabric-network-topology/> 
(in IETF LC)

_NETMOD:_
draft-ietf-netmod-acl-model-15 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-model/>(WG LC 
closed, writeup time)
     draft-ietf-netmod-schema-mount: to be discussed at this meeting
     draft-ietf-netmod-acl-model, shepherd writeup needed

_NETCONF:_
     Time to progress this set of documents (TLS, SSH, client, server, 
keystore) 
<https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-tls-client&modules[]=ietf-tls-server&modules[]=ietf-ssh-client&modules[]=ietf-ssh-server&modules[]=ietf-restconf-client&modules[]=ietf-restconf-server&modules[]=ietf-keystore&modules[]=ietf-netconf-client&modules[]=ietf-netconf-server&orgs[]=ietf&recurse=&rfcs=1>
     draft-ietf-netconf-rfc7895bis, shepherd writeup needed
     draft-ietf-netconf-nmda-restconf, shepherd writeup needed
     draft-ietf-netconf-nmda-netconf, shepherd writeup needed
     draft-ietf-netconf-zerotouch, shepherd writeup needed
     draft-ietf-netconf-yang-push: WG LC
draft-ietf-netconf-subscribed-notifications-10: WG LC

_OPSAWG:
__draft-ietf-opsawg-mud-18 
<https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/>(on the April 
19th telechat)
_ draft-ietf-opsawg-nat-yang-12 
<https://datatracker.ietf.org/doc/draft-ietf-opsawg-nat-yang/> (in WG LC)

_IPPM:_
draft-ietf-ippm-twamp-yang/ 
<https://datatracker.ietf.org/doc/draft-ietf-ippm-twamp-yang/> (WG 
Consensus: Waiting for Write-Up)
draft-ietf-ippm-stamp-yang/ 
<https://datatracker.ietf.org/doc/draft-ietf-ippm-stamp-yang/>

Regards, Benoit