[ieee-ietf-coord] IEEE - IESG call => Fwd: YANG Catalog Latest Developments - October 2017
Benoit Claise <bclaise@cisco.com> Mon, 16 October 2017 13:50 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F30132320 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 16 Oct 2017 06:50:11 -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 Fe2W4G6qXXNM for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 16 Oct 2017 06:50:08 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2649D124B17 for <ieee-ietf-coord@ietf.org>; Mon, 16 Oct 2017 06:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=856396; q=dns/txt; s=iport; t=1508161807; x=1509371407; h=subject:references:to:cc:from:message-id:date: mime-version:in-reply-to; bh=BZAi3XjmZutFABnzhANqZTUIJWHO11I3NRP8yKQp2qU=; b=f926+TyI48BPAzZfPIkgqVj1yeqLVy3QjlrM9e3oZq/F4SpOGWB4LfOC 2T74qWqvoRNYcOMcRKvuznqhTXc49OUqq7KJl3pQCzMLohCRrBhMIZTev w0aF6RtsRZRXPsFybg0UrOdB/7ysVWgHdRUZaGI0ri0lqA27PM6W/94uD Q=;
X-Files: bbogkgoccfdpebem.png : 540709
X-IronPort-AV: E=Sophos;i="5.43,387,1503360000"; d="png'150?scan'150,208,217,150";a="658110872"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Oct 2017 13:50:05 +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 v9GDo3Yu030520; Mon, 16 Oct 2017 13:50:03 GMT
References: <9689d6db-eca9-52f0-7134-c2b6ec6ccfcb@cisco.com>
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
Cc: "Robert Wilton -X (rwilton - Ensoft Ltd at Cisco)" <rwilton@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <9689d6db-eca9-52f0-7134-c2b6ec6ccfcb@cisco.com>
Message-ID: <69dfe210-618b-2b14-0187-37ef3c6dd1aa@cisco.com>
Date: Mon, 16 Oct 2017 15:50:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <9689d6db-eca9-52f0-7134-c2b6ec6ccfcb@cisco.com>
Content-Type: multipart/alternative; boundary="------------31A810962C236D59E8557DED"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/rDtmU6zHkV59YsaLrh-BQ2egK_k>
Subject: [ieee-ietf-coord] IEEE - IESG call => Fwd: YANG Catalog Latest Developments - October 2017
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Oct 2017 13:50:11 -0000
Dear all, From our previous meeting minutes in July 1. YANG Catalog Benoit Claise described the work on the YANG catalog <https:// yangcatalog.org/>. There are more than 2000 modules in the catalog, but they still need tooling for the operators, as well as the metadata. Joe Clarke added that the goal is to provide a tool chain. All of the code that has been contributed is open source. Improvements to the metadata are still in progress. Dorothy Stanley asked what the process is for tracking changes over time. Joe Clarke replied that vendors or standards developers can see the maturity level at any time, as well as when it was ratified. Rather than serving local copies of the modules, they will have pointers to the canonical places from where to download the modules. There is a draft in NETMOD that defines the catalog schema. Benoit Claise said that the next steps include working with the IEEE to add their YANG models to the catalog. Benoit and Glenn Parsons will coordinate offline about how to best handle this; IEEE 802 recently formed a YANG coordination group to coordinate internally on their YANG modules. We improved the YANG catalog quite a lot since our last meeting. Since I can't attend the call today, please ask your questions either via email or via the meeting minutes. Regards, Benoit. -------- Forwarded Message -------- Subject: YANG Catalog Latest Developments - October 2017 Date: Sun, 8 Oct 2017 23:00:56 +0200 From: Benoit Claise <bclaise@cisco.com> To: announce@yangcatalog.org CC: Joe Clarke (jclarke) <jclarke@cisco.com>, me <bclaise@cisco.com> Dear all, On behalf of the full team of dedicated people, we would like to share the latest developments on the yangcatalog.org project. - We added a belongs-to leaf to track parent modules. Use case: an easy lookup of the name of the module that includes this submodule - We added lists to track dependents and dependencies for a given module. Use case: an easy lookup of all dependents (those YANG modules that depend on the target module) and dependencies (those YANG modules are imported by the target module). This is a key feature for the impact analysis tool <https://www.yangcatalog.org/yang-search/impact_analysis.php>. - We simplified the generated-from enumerated values. Use case: knowing whether a YANG module is generated from a MIB per RFC6643, whether a YANG module is generated from platform internal, proprietary structure, or code, or whether a YANG module is authored manually. - We refined the type for compilation-result to be an inet:uri. Use case: we now store the compilation result (from pyang, confdc, yangdump-pro, and yanglint) as a separate file, in order to improve the performance and readability. - We added the concept of semantic versioning Two distinct leaves in the YANG module contains this semver semantic: the semantic-version leaf contains the value reported as metadata by a specific YANG module. the derived-semantic-version leaf is established by examining the the YANG module themselves.As such, only the YANG syntax, as opposed to the implementation changes that lead some some semantic changes. Use case: we want to understand if two YANG modules (with the same YANG module name) are backward compatible. This is especially important for generated models and openconfig models, but might be important for IETF YANG modules as well. See the discussion on the NETMOD mailing list <https://www.ietf.org/mail-archive/web/netmod/current/maillist.html>. - We reorderedthe « organization »leaf to be with other module keys. Use case: the YANG module details view <https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-interfaces>(which starts to be quite complete) combined the metedata in a more logical way. - All of the above points are documented in our new draft version (-02): YANG module for yangcatalog.org <https://datatracker.ietf.org/doc/draft-clacla-netmod-model-catalog/>. This YANG module is used as the foundation for the APIs for yangcatalog.org. - We improved the YANG impact analysis to quickly be able to determine the different impacted standard development organizations, consortia, and manufacturers. See an example here <https://www.yangcatalog.org/yang-search/impact_analysis.php?modules%5B%5D=ietf-interfaces&recurse=0&rfcs=1&show_subm=1&show_dir=both>. By clicking on an organization, the YANG modules from this organization are highlighted. Note that this function is also cumulative. Next to that, the rim colors expresses that maturity level (INITIAL, RATIFIED, ADOPTED), the compilation failure, or the bottleneck for ratification. - We developed a feature to determine the combined email addresses of all dependent YANG modules. Use case: when a YANG module is updated, we proactively want to warn all authors of impacted YANG modules (because they import the target module). As an example, for the ietf-routing YANG module, this produces the following list. { "output": { "author-email": [ "draft-ietf-mpls-static-yang@ietf.org" <mailto:draft-ietf-mpls-static-yang@ietf.org>, "draft-ietf-mpls-base-yang@ietf.org" <mailto:draft-ietf-mpls-base-yang@ietf.org>, "draft-ietf-ospf-sr-yang@ietf.org" <mailto:draft-ietf-ospf-sr-yang@ietf.org>, "draft-ietf-pim-yang@ietf.org" <mailto:draft-ietf-pim-yang@ietf.org>, "draft-ietf-bier-bier-yang@ietf.org" <mailto:draft-ietf-bier-bier-yang@ietf.org>, "draft-zhang-bier-te-yang@ietf.org" <mailto:draft-zhang-bier-te-yang@ietf.org>, "draft-ietf-isis-yang-isis-cfg@ietf.org" <mailto:draft-ietf-isis-yang-isis-cfg@ietf.org>, "draft-ietf-teas-yang-rsvp-te@ietf.org" <mailto:draft-ietf-teas-yang-rsvp-te@ietf.org>, "draft-ietf-mpls-mldp-yang@ietf.org" <mailto:draft-ietf-mpls-mldp-yang@ietf.org>, "draft-zhao-pim-igmp-mld-snooping-yang@ietf.org" <mailto:draft-zhao-pim-igmp-mld-snooping-yang@ietf.org>, "draft-ietf-isis-sr-yang@ietf.org" <mailto:draft-ietf-isis-sr-yang@ietf.org>, "draft-acee-rtgwg-yang-rib-extend@ietf.org" <mailto:draft-acee-rtgwg-yang-rib-extend@ietf.org>, "draft-ietf-pim-igmp-mld-yang@ietf.org" <mailto:draft-ietf-pim-igmp-mld-yang@ietf.org>, "draft-ietf-i2rs-fb-rib-data-model@ietf.org" <mailto:draft-ietf-i2rs-fb-rib-data-model@ietf.org>, "draft-ietf-ospf-yang@ietf.org" <mailto:draft-ietf-ospf-yang@ietf.org>, "draft-ietf-rtgwg-yang-rip@ietf.org" <mailto:draft-ietf-rtgwg-yang-rip@ietf.org>, "draft-ietf-spring-sr-yang@ietf.org" <mailto:draft-ietf-spring-sr-yang@ietf.org>, "draft-ietf-teas-yang-rsvp@ietf.org" <mailto:draft-ietf-teas-yang-rsvp@ietf.org>, "draft-ietf-i2rs-pkt-eca-data-model@ietf.org" <mailto:draft-ietf-i2rs-pkt-eca-data-model@ietf.org>, "draft-ietf-mpls-ldp-yang@ietf.org" <mailto:draft-ietf-mpls-ldp-yang@ietf.org>, "draft-ietf-bfd-yang@ietf.org" <mailto:draft-ietf-bfd-yang@ietf.org>, "draft-ietf-pim-msdp-yang@ietf.org" <mailto:draft-ietf-pim-msdp-yang@ietf.org> ] } } Don't hesitate to provide your feedback on the YANG catalag set of tools at info@yangcatalog.org <mailto:info@yangcatalog.org> Feel free to forward this email. Subscribe <https://www.marcuscom.com/mailman/listinfo/yangcatalog-announce>to announce@yangcatalog.org <mailto:announce@yangcatalog.org>to get updates about the YANG Catalog. Regards, Joe and Benoit, on behalf of the team.
- [ieee-ietf-coord] IEEE - IESG call => Fwd: YANG C… Benoit Claise