[netmod] YANG modules publication: what to focus on next? Feb 16th

Benoit Claise <bclaise@cisco.com> Fri, 16 February 2018 10:35 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 CD2DD126C23 for <netmod@ietfa.amsl.com>; Fri, 16 Feb 2018 02:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, 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 3Z6x8x342P-3 for <netmod@ietfa.amsl.com>; Fri, 16 Feb 2018 02:35:49 -0800 (PST)
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 7CC0712D87E for <netmod@ietf.org>; Fri, 16 Feb 2018 02:35:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22976; q=dns/txt; s=iport; t=1518777348; x=1519986948; h=subject:references:from:to:message-id:date:mime-version: in-reply-to; bh=idf7e0p9l6jN0Ed40XWNavfSgXHXxJwRP3H3uPw2j1A=; b=Khj/RBPtKxElAPmv3JTzeSjUY1BT2XhQi8hA3iEfM1tQB6Qza+OAQlLn qTykOMh8i2NPz9KyybPvfYbh12v3odg08DIO1UtGQZ7CKq+F/MXXJJm9N A9ZpX9Y+NaRObQlcQ0BG5ihT8CxD2v2Lm7DspumcZlPpEFeWfexVfe/MO Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAQD0soZa/xbLJq1CGhoBAQEBAQIBA?= =?us-ascii?q?QEBCAEBAQGENXAog1SKJXSOaoE+kG2FXBSCAgomhRUCGoJ+GAECAQEBAQEBAms?= =?us-ascii?q?oQhABhFEGI2YJRAICAlUGDQgBAYodEDSPYZ10gicmhFuDe4ITAQEBAQEBBAEBA?= =?us-ascii?q?QEBAQEcBYUEg3+BaCkMhEKBZwIBAQEBgTUigy2CZQWKdo82igkJiCSNZoIghiq?= =?us-ascii?q?Dc4gLjgaBf4gagTwfOYFRMxoIGxWCfYJgghdANwGFD4hvAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,519,1511827200"; d="scan'208,217";a="2106063"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Feb 2018 10:35:46 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w1GAZjhs015806 for <netmod@ietf.org>; Fri, 16 Feb 2018 10:35:45 GMT
References: <7cd9c63c-8bbe-e7c3-3cb0-dc5c1ebc7304@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
To: NETMOD Working Group <netmod@ietf.org>
X-Forwarded-Message-Id: <7cd9c63c-8bbe-e7c3-3cb0-dc5c1ebc7304@cisco.com>
Message-ID: <42d768a1-2b28-3269-e450-d88bf8b3b441@cisco.com>
Date: Fri, 16 Feb 2018 11:35:45 +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: <7cd9c63c-8bbe-e7c3-3cb0-dc5c1ebc7304@cisco.com>
Content-Type: multipart/alternative; boundary="------------D7A329188AF94DB6EA62CBAF"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/erWFpddQBTOMOT3sNwo2WxUrpb4>
Subject: [netmod] YANG modules publication: what to focus on next? Feb 16th
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: Fri, 16 Feb 2018 10:36:00 -0000

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>)

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-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-05 
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/> 
(actually, almost in the RFC editor queue)


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&recurse=1&rfcs=1&show_subm=1&show_dir=dependencies> 
for these RFC editor modules, as requirement before publishing.

Some more YANG modules are on the IESG table:
     draft-ietf-pim-yang has a DISCUSS (Jan 11th IESG telechat)

Assuming this one is in the RFC editor queue, this is the new set of 
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-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>;.
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
     ietf-bfd-yang (currently in WG LC)
     draft-ietf-ospf-yang
     draft-ietf-isis-yang-isis-cfg
Please progress those documents asap

Some more updates below.

_NETMOD:_
draft-ietf-netmod-syslog-model-17 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/> (in 
IETF LC)
draft-ietf-netmod-acl-model-15 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-model/>(WG LC 
closed, writeup time)
draft-ietf-netmod-rfc6087bis-17 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc6087bis/> (AD 
review done)
     draft-ietf-netmod-schema-mount:

_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 (in WG LC)
         Status: Under discussion in NETCONF

_LIME:_
draft-ietf-lime-yang-connection-oriented-oam-model-05 (next IESG telechat)

_OPSAWG:_
draft-ietf-opsawg-nat-yang-12 
<https://datatracker.ietf.org/doc/draft-ietf-opsawg-nat-yang/> (in WG LC)

_L2SM:_
draft-ietf-l2sm-l2vpn-service-model-06 
<https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/> 
(in WG LC)

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

Regards, Benoit