Re: [netmod] RFC 8199 on YANG Module Classification
Benoit Claise <bclaise@cisco.com> Wed, 09 August 2017 12:32 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 9680B13219C for <netmod@ietfa.amsl.com>; Wed, 9 Aug 2017 05:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.478
X-Spam-Level:
X-Spam-Status: No, score=-13.478 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, WEIRD_PORT=0.001] 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 QE_MFm4-vpUt for <netmod@ietfa.amsl.com>; Wed, 9 Aug 2017 05:32:17 -0700 (PDT)
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 BB87B129B14 for <netmod@ietf.org>; Wed, 9 Aug 2017 05:32:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11599; q=dns/txt; s=iport; t=1502281936; x=1503491536; h=subject:cc:references:from:message-id:date:mime-version: in-reply-to; bh=+jRAc3Gkfe08iFzommb+I+bpBDTdFr1GUvn22sfNMfo=; b=WMda0pzIJ2XJlMcCPya4KnwJb9ZFAuOPQkYCIzA//OIc9u6I2f25LfkJ LsB5nHW8uMVcdt2oG6uaD8BI9A49fL4G4R05hpAi55pSAsqwEbODbusIf JYqhL11JfydokCsMKrJ2FcmELph1LEzK/EcNphSVNyjubnrY4eIuYbfka 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D7AQDW/4pZ/xbLJq1cGgEBAQECAQEBAQgBAQEBhD6BBQ+PApBPMZBihTMOggQhAQyBXoJXFU8CJoUXFgECAQEBAQEBAWsohRAJAgEDAQEhKyALEAkCFBAeAgInCiYTBgIBARAGAQIEhVGEPRCQIJ1kgiYniy0BAQEBAQEEAQEBAQEBAQEggyiDToIOgnyBPIMBFEKCcxOCTgEEiXmCEJQOh1OMY4JoiFqHD40iiGkmATCBCjIhCBwVHyp2D4QegXk+NodVgjIBAQU
X-IronPort-AV: E=Sophos;i="5.41,347,1498521600"; d="scan'208,217";a="654843028"
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; 09 Aug 2017 12:32:12 +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 v79CWBc9019277 for <netmod@ietf.org>; Wed, 9 Aug 2017 12:32:11 GMT
Cc: netmod@ietf.org
References: <20170731183346.AFB3CB8107F@rfc-editor.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <9ec8b82c-f746-20c9-95ac-b9a84bd1217a@cisco.com>
Date: Wed, 09 Aug 2017 14:32:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170731183346.AFB3CB8107F@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------234E2B9A64A314DD19684963"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/O4ngGj1UMpfjkQjdggLOxEzVLOQ>
Subject: Re: [netmod] RFC 8199 on YANG Module Classification
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, 09 Aug 2017 12:32:22 -0000
Dear all, The good news is that the module-classification is already added as a metadata in the yangcatalog.org. leaf module-classification { type enumeration { enum network-service { description "Network Service YANG Module that describes the configuration, state data, operations, and notifications of abstract representations of services implemented on one or multiple network elements."; } enum network-element { description "Network Element YANG Module that describes the configuration, state data, operations, and notifications of specific device-centric technologies or features."; } enum unknown { description "In case that there is not sufficient information about how to classify the module."; } enum not-applicable { description "The YANG module abstraction type is neither a Network Service YANG Module nor a Network Element YANG Module."; } } mandatory true; description "The high-level classification of the given YANG module."; reference "RFC8199 YANG Module Classification"; } description "These leafs are shared among the yang-catalog and its API."; } This metadata can't be extracted from the module, but must be populated. That's the reason why you would see "unknown" for most modules right now. Ex: https://yangcatalog.org:8443/search/modules/ietf-l3vpn-svc,2017-01-27,ietf When populated, this will provide the ability to search for service versus network elements YANG modules. Regards, Benoit > A new Request for Comments is now available in online RFC libraries. > > > RFC 8199 > > Title: YANG Module Classification > Author: D. Bogdanovic, > B. Claise, > C. Moberg > Status: Informational > Stream: IETF > Date: July 2017 > Mailbox: dean@voltanet.io, > bclaise@cisco.com, > camoberg@cisco.com > Pages: 11 > Characters: 23080 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-netmod-yang-model-classification-08.txt > > URL: https://www.rfc-editor.org/info/rfc8199 > > DOI: 10.17487/RFC8199 > > The YANG data modeling language is currently being considered for a > wide variety of applications throughout the networking industry at > large. Many standards development organizations (SDOs), open-source > software projects, vendors, and users are using YANG to develop and > publish YANG modules for a wide variety of applications. At the same > time, there is currently no well-known terminology to categorize > various types of YANG modules. > > A consistent terminology would help with the categorization of YANG > modules, assist in the analysis of the YANG data modeling efforts in > the IETF and other organizations, and bring clarity to the YANG- > related discussions between the different groups. > > This document describes a set of concepts and associated terms to > support consistent classification of YANG modules. > > This document is a product of the NETCONF Data Modeling Language Working Group of the IETF. > > > INFORMATIONAL: This memo provides information for the Internet community. > It does not specify an Internet standard of any kind. Distribution of > this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://www.ietf.org/mailman/listinfo/ietf-announce > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see https://www.rfc-editor.org/search > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > . >
- [netmod] RFC 8199 on YANG Module Classification rfc-editor
- Re: [netmod] RFC 8199 on YANG Module Classificati… Benoit Claise