Fwd: YANG modules publication: what to focus on next?

Benoit Claise <bclaise@cisco.com> Tue, 16 January 2018 11:33 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11FE1131454 for <rtg-bfd@ietfa.amsl.com>; Tue, 16 Jan 2018 03:33:38 -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 kxrwSnnjQKI6 for <rtg-bfd@ietfa.amsl.com>; Tue, 16 Jan 2018 03:33:36 -0800 (PST)
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 AB42012DA4F for <rtg-bfd@ietf.org>; Tue, 16 Jan 2018 03:33:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19300; q=dns/txt; s=iport; t=1516102402; x=1517312002; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=dYCE4PsuX+DWxG+5PRg6jluibWHiooTDLegFE/JrL1U=; b=fJf0mUnNALcn4o8hnyujfso+nXIv+VIH0TcZXkOgy8kxlRgazsoqQGVq eDZtcIrpC3MOub/Ntt7W3JlXALV06vfZGDs6rzNEjuBxFApcp3TTfqKBJ UmA00HbFtGOpO4SMCuC66n2vfU/abFk1j5OxhB37R9+nM3nRiUbdpw3rA s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsBAAB4l1a/xbLJq1DGhwBAQEEAQEKA?= =?us-ascii?q?QGEJ3QnhBOLGI9HJ5FbhWWCAgomhRUCGoUCFAEBAQEBAQEBAWsdC4UjAQMDI2Y?= =?us-ascii?q?JEwMBAisCAgJLAggGDQYCAQEWihkQNIdwnXCCJyaJIwEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEaBYgogWkpDIJ5gy8CAQEBAYE1TwmCd4JlBZlyiXKIDI0/ghmGHYNvh2u?= =?us-ascii?q?NPoFeiAmBPDYigVAyGggbFYJnhFhANwGNQwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,368,1511827200"; d="scan'208,217";a="1431724"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2018 11:33:20 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0GBXKgH032437 for <rtg-bfd@ietf.org>; Tue, 16 Jan 2018 11:33:20 GMT
Subject: Fwd: YANG modules publication: what to focus on next?
References: <62e07326-e682-70d6-f87e-60475008acb1@cisco.com>
To: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <62e07326-e682-70d6-f87e-60475008acb1@cisco.com>
Message-ID: <3bafb09c-0dc1-2023-2ba2-74b84777874c@cisco.com>
Date: Tue, 16 Jan 2018 12:33:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <62e07326-e682-70d6-f87e-60475008acb1@cisco.com>
Content-Type: multipart/alternative; boundary="------------E002C442E2019D823F825F93"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/nQT-9iTHhmgq2xbyY4cuXY2Zi18>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 11:33:38 -0000

Dear all,

So that you know that ietf-bfd-yang is a bottleneck to publish many YANG 
modules.
Please progress it asap.

Regards, Benoit


-------- Forwarded Message --------
Subject: 	YANG modules publication: what to focus on next?
Date: 	Tue, 16 Jan 2018 12:27:01 +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>)
   Note that draft-ietf-netmod-revised-datastores, a normative reference 
for many YANG modules,
   was just approved. Good news!

We now have many YANG modules in RFC editor queue:
***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-netconf-rfc6536bis-09 
<https://datatracker.ietf.org/doc/draft-ietf-netconf-rfc6536bis>
*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-revised-datastores-10 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/>

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&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)
     draft-ietf-netmod-rfc8022bis is on the Jan 25th IESG telechat
     draft-ietf-netmod-entity is on the Jan 25th IESG telechat

Assuming those are 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-pim-dm&modules[]=ietf-pim-base&modules[]=ietf-pim-sm&modules[]=ietf-pim-bidir&modules[]=ietf-pim-rp&modules[]=ietf-routing&modules[]=ietf-ipv6-router-advertisements&modules[]=ietf-ipv4-unicast-routing&modules[]=ietf-ipv6-unicast-routing&modules[]=ietf-entity&modules[]=ietf-datastores&modules[]=ietf-origin&recurse=1&rfcs=1&show_subm=1&show_dir=dependencies>;.
It takes a little bit of re-arrangering the elements, but all the 
information is there.

The next bottlenecks for publishing those YANG modules are:
     draft-ietf-netmod-schema-mount
     draft-ietf-rtgwg-ni-model
     ietf-bfd-yang
     draft-ietf-ospf-yang
     draft-ietf-isis-yang-isis-cfg
Please progress those documents asap

Some more updates below.

_NI, LNE, and schema mount, RFC7895bis, schema mount:_
     draft-ietf-rtgwg-lne-model
         Status: Publication requested, Alia's AD review
     draft-ietf-rtgwg-ni-model
         Status: Publication requested, Alia's AD review
     draft-ietf-netmod-schema-mount:
         Status:  WG LC closed, not sure on the next steps ...
     draft-ietf-netconf-rfc7895bis
         Status not clear...

_LIME:_
draft-ietf-lime-yang-connection-oriented-oam-model-00
         Status: Benoit to perform the AD review.

Regards, Benoit