[i2rs] YANG modules dependencies tool: result for the I2RS topology documents

Benoit Claise <bclaise@cisco.com> Mon, 14 November 2016 00:36 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C80A1295CA for <i2rs@ietfa.amsl.com>; Sun, 13 Nov 2016 16:36:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.594
X-Spam-Level:
X-Spam-Status: No, score=-14.594 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-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 UsiZRomfJq3o for <i2rs@ietfa.amsl.com>; Sun, 13 Nov 2016 16:35:59 -0800 (PST)
Received: from bgl-iport-3.cisco.com (bgl-iport-3.cisco.com [72.163.197.27]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D3E51295E4 for <i2rs@ietf.org>; Sun, 13 Nov 2016 16:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=393143; q=dns/txt; s=iport; t=1479083756; x=1480293356; h=to:from:subject:message-id:date:mime-version; bh=GWHtzb9IplxXxGtEGaNUm1Q7hj+M7oIGKj2vKiL+gW0=; b=Nvi+Rdl+KTCYaCeZQqYdc7/JujzBi1onFzkR9RpaJqwv4wOyRk7SzGI7 QwWiFX3IBv23Vd3q01J7LsmfNHvfELS5G1tsWGGKMuLDyaA4WRtCKIY6I Xfq3pfGijiFgvMHSWccrSSu9RRSb3fah7iGHVI6P3wgDsHtnsEDuQ8j4q E=;
X-Files: eaadhmmdikllhloo.png : 283037
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmBACzBSlY/xjFo0iEPQEBAQEBxigEAgECAYEK
X-IronPort-AV: E=Sophos;i="5.31,487,1473120000"; d="png'150?scan'150,208,217,150";a="30631677"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2016 00:35:52 +0000
Received: from [10.79.99.134] ([10.79.99.134]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id uAE0ZZ0a032634 for <i2rs@ietf.org>; Mon, 14 Nov 2016 00:35:37 GMT
To: "i2rs@ietf.org" <i2rs@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <9ea9df58-81a3-5398-c505-9b6703971a7c@cisco.com>
Date: Mon, 14 Nov 2016 09:33:05 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------7AEB3FD96C05F23FC6049F83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/LUoT5q8dP_0g-kgneHMzsdMjRWw>
Subject: [i2rs] YANG modules dependencies tool: result for the I2RS topology documents
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 00:36:01 -0000

Dear all,

Looking at the I2RS topology YANG models in:
draft-ietf-i2rs-yang-l3-topology-04.txt ( 
<http://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology>ietf-isis-topology@2016-09-19.yang, 
ietf-l3-unicast-topology@2016-09-19.yang, 
ietf-ospf-topology@2016-09-19.yang)
draft-ietf-i2rs-yang-network-topo-06.txt 
<http://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo> 
(ietf-network-topology@2016-09-19.yang, ietf-network@2016-09-19.yang)

During this week-end hackathon, Joe Clarke created a very useful visual 
tool.
http://yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-network-topology&modules[]=ietf-network&modules[]=ietf-l3-unicast-topology&modules[]=ietf-ospf-topology&modules[]=ietf-isis-topology&recurse=0&rfcs=0

Some info on the tool. You can add all the YANG modules you want, you 
can select the level of recursion, you can move the bubbles around, you 
can move the mouse over a YANG module to display the draft name, etc. 
 From there, you can see the bottleneck, i.e. the YANG module that 
should get our prioritized attention (the one with black circle). RFCs 
are in red (and there is a flag to remove them), and drafts are in 
green. See all options under the "graph options" pull down menu.

After selecting the right option, the conclusions are in the attached 
picture.
Un-selecting the "include RFCs" button provides even a clearer view, 
when looking for bottlenecks:


Probably obvious to the people knowledge with the those drafts, but 
there are not import YANG model dependencies.
The picture also displays which YANG models are depending on the 
publication of those two drafts.

Regards, Benoit