Catalog and registry for YANG models
draft-openconfig-netmod-model-catalog-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

draft-openconfig-netmod-model-catalog-02.txt:
xym 0.4:
Extracting 'openconfig-catalog-types.yang'
Extracting 'openconfig-module-catalog.yang'
Extracting 'openconfig-extensions.yang'
Extracting 'openconfig-inet-types.yang'


openconfig-inet-types@2017-01-26.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.12.193: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model}:
No validation errors


openconfig-extensions@2017-01-29.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.12.193: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model}:
No validation errors


openconfig-catalog-types@2017-03-08.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.12.193: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model}:
No validation errors


openconfig-module-catalog@2017-03-08.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.12.193: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model}:
No validation errors

Network Working Group                                          A. Shaikh
Internet-Draft                                                 R. Shakir
Intended status: Informational                                    Google
Expires: September 13, 2017                                   K. D'Souza
                                                                    AT&T
                                                          March 12, 2017

                  Catalog and registry for YANG models
                draft-openconfig-netmod-model-catalog-02

Abstract

   This document presents an approach for a YANG model catalog and
   registry that allows users to find models relevant to their use cases
   from the large and growing number of YANG modules being published.
   The model catalog may also be used to define bundles of YANG modules
   required to realize a particular service or function.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 13, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Shaikh, et al.         Expires September 13, 2017               [Page 1]
Internet-Draft             YANG Model Catalog                 March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Model catalog and registry requirements . . . . . . . . . . .   3
   3.  Organizing YANG modules . . . . . . . . . . . . . . . . . . .   5
     3.1.  Module information  . . . . . . . . . . . . . . . . . . .   5
   4.  Identifying interoperable models  . . . . . . . . . . . . . .   7
     4.1.  Release bundle information  . . . . . . . . . . . . . . .   7
   5.  Specifying functionality with feature bundles . . . . . . . .   8
     5.1.  Feature bundle information  . . . . . . . . . . . . . . .   9
   6.  Module implementations  . . . . . . . . . . . . . . . . . . .  10
     6.1.  Implementation information  . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   9.  YANG modules  . . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  38
     10.1.  Normative references . . . . . . . . . . . . . . . . . .  38
     10.2.  Informative references . . . . . . . . . . . . . . . . .  38
   Appendix A.  Change summary . . . . . . . . . . . . . . . . . . .  39
     A.1.  Changes between revisions -01 and -02 . . . . . . . . . .  39
     A.2.  Changes between revisions -00 and -01 . . . . . . . . . .  39
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  39

1.  Introduction

   As YANG [RFC6020][RFC7950] adoption and usage grows, the number of
   YANG models (and corresponding module and submodule files) published
   is increasing rapidly.  This growing collection of modules
   potentially enables a large set of management use cases, but from a
   user perspective, it is a daunting task to navigate the largely ad-
   hoc landscape of models to determine their functionality,
   compatibility, and available implementations.  For example, the IETF
   Routing Area Coordination page [RTG-AD-YANG] currently tracks over
   150 YANG models related to layer 2 and layer 3 technologies.

   YANG models are also being developed and published beyond the IETF,
   for example by open source projects, other standards organizations,
   and industry forums.  These efforts are generally independent from
   each other and sometimes result in overlapping models.  While we