--- 1/draft-ietf-teas-actn-vn-yang-02.txt 2018-12-30 21:13:12.130531317 -0800 +++ 2/draft-ietf-teas-actn-vn-yang-03.txt 2018-12-30 21:13:12.242534007 -0800 @@ -1,29 +1,29 @@ TEAS Working Group Y. Lee (Editor) Internet Draft Dhruv Dhody (Editor) Intended Status: Standard Track Huawei -Expires: March 19, 2019 D. Ceccarelli +Expires: June 30, 2019 D. Ceccarelli Ericsson Igor Bryskin Huawei Bin Yeong Yoon ETRI Qin Wu Huawei Peter Park KT - September 19, 2018 + December 30, 2018 A Yang Data Model for ACTN VN Operation - draft-ietf-teas-actn-vn-yang-02 + draft-ietf-teas-actn-vn-yang-03 Abstract This document provides a YANG data model for the Abstraction and Control of Traffic Engineered (TE) networks (ACTN) Virtual Network Service (VNS) operation. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with @@ -37,21 +37,21 @@ 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on March 19, 2019. + This Internet-Draft will expire on June 30, 2019. Copyright Notice Copyright (c) 2018 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 @@ -66,27 +66,28 @@ 1. Introduction...................................................3 1.1. Terminology...............................................4 1.2. Tree diagram..............................................4 1.3. Prefixes in Data Node Names...............................4 2. ACTN CMI context...............................................5 2.1. Type 1 VN.................................................5 2.2. Type 2 VN.................................................6 3. High-Level Control Flows with Examples.........................7 3.1. Type 1 VN Illustration....................................7 3.2. Type 2 VN Illustration....................................8 - 4. Justification of the ACTN VN Model on the CMI.................11 + 4. ACTN VN Model Usage...........................................11 4.1. Customer view of VN......................................11 - 4.2. Innovative Services......................................11 - 4.2.1. VN Compute..........................................11 - 4.2.2. Multi-sources and Multi-destinations................12 - 4.2.3. Others..............................................13 - 4.3. Summary..................................................13 + 4.2. Auto-creation of VN by MDSC..............................11 + 4.3. Innovative Services......................................11 + 4.3.1. VN Compute..........................................11 + 4.3.2. Multi-sources and Multi-destinations................12 + 4.3.3. Others..............................................12 + 4.3.4. Summary.............................................13 5. ACTN VN YANG Model (Tree Structure)...........................13 6. ACTN-VN YANG Code.............................................15 7. JSON Example..................................................27 7.1. ACTN VN JSON.............................................28 7.2. TE-topology JSON.........................................33 8. Security Considerations.......................................49 9. IANA Considerations...........................................51 10. Acknowledgments..............................................51 11. References...................................................52 11.1. Normative References....................................52 @@ -106,23 +107,25 @@ Control of Traffic Engineered (TE) networks (ACTN) Virtual Network Service (VNS) operation that is going to be implemented for the Customer Network Controller (CNC)- Multi-Domain Service Coordinator (MSDC) interface (CMI). The YANG model on the CMI is also known as customer service model in [RFC8309]. The YANG model discussed in this document is used to operate customer-driven VNs during the VN instantiation, VN computation, and its life-cycle service management and operations. - The VN model defined in this document can also work together with - other customer service models such as L3SM [RFC8299], L2SM [L2SM] - and L1CSM [L1CSM] to provide a complete life-cycle service + The VN model defined in this document is applicable in generic sense + outside of the ACTN context as an independent model in and of + itself. The VN model defined in this document can also work together + with other customer service models such as L3SM [RFC8299], L2SM + [L2SM] and L1CSM [L1CSM] to provide a complete life-cycle service management and operations. The YANG model discussed in this document basically provides the following: o Characteristics of Access Points (APs) that describe customer's end point characteristics; o Characteristics of Virtual Network Access Points (VNAP) that describe How an AP is partitioned for multiple VNs sharing the AP @@ -160,21 +163,21 @@ 1.3. Prefixes in Data Node Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in Table 1. +---------+------------------------------+-----------------+ | Prefix | YANG module | Reference | +---------+------------------------------+-----------------+ - | vn | ietf-actn-vn | [RFCXXXX] | + | vn | ietf-vn | [RFCXXXX] | | nw | ietf-network | [RFC8345] | | te-types| ietf-te-types | [TE-Tunnel] | | te-topo | ietf-te-topology | [TE-TOPO] | +---------+------------------------------+-----------------+ Table 1: Prefixes and corresponding YANG modules Note: The RFC Editor will replace XXXX with the number assigned to the RFC once this draft becomes an RFC. @@ -537,21 +540,21 @@ Members. No other details need to be set by customer, making for a simplified operations for the customer. * VN Type 2: Along with VN Members, the customer could also provide an abstract topology, this topology is provided by the Abstract TE Topology Yang Model. 5. ACTN VN YANG Model (Tree Structure) - module: ietf-actn-vn + module: ietf-vn +--rw actn +--rw ap | +--rw access-point-list* [access-point-id] | +--rw access-point-id uint32 | +--rw access-point-name? string | +--rw max-bandwidth? te-types:te-bandwidth | +--rw avl-bandwidth? te-types:te-bandwidth | +--rw vn-ap* [vn-ap-id] | +--rw vn-ap-id uint32 | +--rw vn? -> /actn/vn/vn-list/vn-id @@ -611,24 +614,24 @@ | +--ro multi-dest? boolean {multi-src-dest}? +--ro connetivity-matrix-id? -> /nw:networks/network/node/tet:te/te-node- attributes/connectivity-matrices/connectivity-matrix/id +--ro if-selected? boolean {multi-src-dest}? +--ro compute-status? identityref 6. ACTN-VN YANG Code The YANG code is as follows: - file "ietf-actn-vn@2018-02-27.yang" + file "ietf-vn@2018-12-30.yang" -module ietf-actn-vn { - namespace "urn:ietf:params:xml:ns:yang:ietf-actn-vn"; +module ietf-vn { + namespace "urn:ietf:params:xml:ns:yang:ietf-vn"; prefix "vn"; /* Import network */ import ietf-network { prefix "nw"; } /* Import TE generic types */ import ietf-te-types { prefix "te-types"; @@ -644,22 +647,21 @@ Working Group"; contact "Editor: Young Lee : Dhruv Dhody "; description "This module contains a YANG module for the ACTN VN. It describes a VN operation module that takes place in the context of the CNC-MDSC Interface (CMI) of the ACTN architecture where the CNC is the actor of a VN Instantiation/modification /deletion."; - - revision 2018-02-27 { + revision 2018-12-30 { description "initial version."; reference "TBD"; } /* * Features */ feature multi-src-dest { description @@ -1191,23 +1194,23 @@ figure in section 3.2). This VN has a single VN member 105 (L1 to L5) and an underlay path (S4 and S7) has been set in the connectivity matrix of abstract2 topology; o VN3 (Type 1): This VN has a multi-source, multi-destination feature enable for VN Member 104 (L1 to L4)/107 (L1 to L7) [multi-src] and VN Member 204 (L2 to L4)/304 (L3 to L4) [multi- dest] usecase. The selected VN-member is known via the field "if- selected" and the corresponding connectivity-matrix-id. - Note that the ACTN VN YANG model also include the AP and VNAP which - shows various VN using the same AP. -7.1. ACTN VN JSON + Note that the VN YANG model also include the AP and VNAP which shows + various VN using the same AP. +7.1. VN JSON { "actn":{ "ap":{ "access-point-list": [ { "access-point-id": 101, "access-point-name": "101", "vn-ap": [ { @@ -2309,40 +2315,40 @@ o dest o dest-vn-ap-id o connectivity-matrix-id 9. IANA Considerations This document registers the following namespace URIs in the IETF XML registry [RFC3688]: -------------------------------------------------------------------- - URI: urn:ietf:params:xml:ns:yang:ietf-actn-vn + URI: urn:ietf:params:xml:ns:yang:ietf-vn Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. -------------------------------------------------------------------- This document registers the following YANG modules in the YANG Module Names registry [RFC6020]: -------------------------------------------------------------------- - name: ietf-actn-vn - namespace: urn:ietf:params:xml:ns:yang:ietf-actn-vn + name: ietf-vn + namespace: urn:ietf:params:xml:ns:yang:ietf-vn reference: RFC XXXX (TDB) -------------------------------------------------------------------- 10. Acknowledgments - The authors would like to thank Xufeng Liu for his helpful comments - and valuable suggestions. + The authors would like to thank Xufeng Liu and Adrian Farrel for + their helpful comments and valuable suggestions. 11. References 11.1. Normative References [TE-TOPO] X. Liu, et al., "YANG Data Model for TE Topologies", work in progress: draft-ietf-teas-yang-te-topo. [TE-tunnel] T. Saad, et al., "A YANG Data Model for Traffic Engineering Tunnels and Interfaces", work in progress: