--- 1/draft-ietf-netmod-yang-model-classification-05.txt 2017-04-27 03:13:11.087327213 -0700 +++ 2/draft-ietf-netmod-yang-model-classification-06.txt 2017-04-27 03:13:11.111327709 -0700 @@ -1,20 +1,20 @@ NETMOD D. Bogdanovic Internet-Draft Volta Networks, Inc. Intended status: Informational B. Claise -Expires: September 14, 2017 C. Moberg +Expires: October 29, 2017 C. Moberg Cisco Systems, Inc. - March 13, 2017 + April 27, 2017 YANG Module Classification - draft-ietf-netmod-yang-model-classification-05 + draft-ietf-netmod-yang-model-classification-06 Abstract The YANG data modeling language is currently being considered for a wide variety of applications throughout the networking industry at large. Many standards-defining 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. @@ -35,21 +35,21 @@ 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 14, 2017. + This Internet-Draft will expire on October 29, 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 @@ -65,21 +65,21 @@ 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2. First Dimension: YANG Module Abstraction Layers . . . . . . . 4 2.1. Network Service YANG Modules . . . . . . . . . . . . . . 6 2.2. Network Element YANG Modules . . . . . . . . . . . . . . 7 3. Second Dimension: Module Types . . . . . . . . . . . . . . . 7 3.1. Standard YANG Modules . . . . . . . . . . . . . . . . . . 8 3.2. Vendor-specific YANG Modules and Extensions . . . . . . . 8 3.3. User-specific YANG Modules and Extensions . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 7. Change log [RFC Editor: Please remove] . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction The Internet Engineering Steering Group (IESG) has been actively encouraging IETF working groups to use the YANG data modeling @@ -237,32 +237,20 @@ service module does not expose the detailed configuration parameters of all participating network elements and features, but describes an abstract model that allows instances of the service to be decomposed into instance data according to the Network Element YANG Modules of the participating network elements. The service-to-element decomposition is a separate process with details depending on how the network operator chooses to realize the service. For the purpose of this document we will use the term "orchestrator" to describe a system implementing such a process. - As an example, the Network Service YANG Module defined in - [draft-ietf-l3sm-l3vpn-service-model] provides an abstract model for - Layer 3 IP VPN service configuration. This module includes e.g. the - concept of a 'site-network-access' to represent bearer and connection - parameters. An orchestrator receives operations on service instances - according to the service module and decomposes the data into specific - Network Element YANG Modules to configure the participating network - elements to the service. In the case of the L3VPN module, this would - include translating the 'site-network-access' parameters to the - appropriate parameters in the Network Element YANG Module implemented - on the constituent elements. - Network Service YANG Modules define service models to be consumed by external systems. External systems can be provisioning systems, service orchestrators, Operations Support Systems, Business Support Systems and applications exposed to network service consumers, being either internal network operations peole or extarnal customers. These modules are commonly designed, developed and deployed by network infrastructure teams. YANG allows for different design patterns to describe network services, ranging from monolithic to component-based approaches. @@ -283,20 +271,35 @@ speed. As an example, an L2VPN service can be built on many different types of transport network technologies, including e.g. MPLS or carrier ethernet. A component-based approach would allow for reuse of e.g. UNI-interface definitions independent of the underlying transport network (e.g. MEF UNI interface or MPLS interface). The monolithic approach would assume a specific set of transport technologies and interface definitions. + Another example for a network service model is [RFC8049]. Although + it provides information that can be used to achieve customer service + service level agreement, which is more then network service module + classification describes in this document, it provides an abstract + model for Layer 3 IP VPN service configuration which is a good + network service model. This module includes e.g. the concept of a + 'site-network-access' to represent bearer and connection parameters. + An orchestrator receives operations on service instances according to + the service module and decomposes the data into specific Network + Element YANG Modules to configure the participating network elements + to the service. In the case of the L3VPN module, this would include + translating the 'site-network-access' parameters to the appropriate + parameters in the Network Element YANG Module implemented on the + constituent elements. + 2.2. Network Element YANG Modules Network Element YANG Modules describe the characteristics of a network device as defined by the vendor of that device. The modules are commonly structured around features of the device, e.g. interface configuration [RFC7223], OSPF configuration [I-D.ietf-ospf-yang], and firewall rules definitions [I-D.ietf-netmod-acl-model]. Although the [RFC7950], [RFC7950] doesn't explain the relationship of the terms '(YANG) data model' and '(YANG) module', the authors @@ -423,54 +426,57 @@ version 01: Language fixes, collapsing of vendor data models and extensions, and the introduction of user data models and extensions. version 02: Updated the YANG Module Catalog section, terminology alignment (YANG data model versus YANG module), explain better the distinction between the Network Element and Service YANG data models even if sometimes there are grey areas, editorial pass. Changed the use of the term 'model' to 'module' to be better aligned with RFC6020. + version 06: updates based on comments from Adrian Farrel about YANG + Data Model for L3VPN Service Delivery. + 8. References 8.1. Normative References [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC7223] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . -8.2. Informative References + [RFC8049] Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data + Model for L3VPN Service Delivery", RFC 8049, DOI 10.17487/ + RFC8049, February 2017, + . - [draft-ietf-l3sm-l3vpn-service-model] - "YANG Data Model for L3VPN service delivery", - . +8.2. Informative References [I-D.ietf-netmod-acl-model] Bogdanovic, D., Koushik, K., Huang, L., and D. Blair, "Network Access Control List (ACL) YANG Data Model", draft-ietf-netmod-acl-model-10 (work in progress), March 2017. [I-D.ietf-ospf-yang] Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, "Yang Data Model for OSPF Protocol", draft-ietf-ospf- - yang-06 (work in progress), October 2016. + yang-07 (work in progress), March 2017. [Writable-MIB-Module-IESG-Statement] "Writable MIB Module IESG Statement", . Authors' Addresses Dean Bogdanovic Volta Networks, Inc.