TEAS Working Group Y. Lee (Editor) Internet Draft Dhruv Dhody Intended Status: Standard Track Huawei Expires: December 19, 2018 D. Ceccarelli Ericsson Igor Bryskin Huawei Bin Yeong Yoon ETRI Qin Wu Huawei Peter Park KT June 19, 2018 A Yang Data Model for ACTN VN Operation draft-ietf-teas-actn-vn-yang-01 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 the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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 Lee, et al. Expires December 2018 [Page 1] Internet-Draft ACTN VN YANG Model June 2018 This Internet-Draft will expire on December 19, 2018. 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 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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction...................................................3 1.1. Terminology...............................................4 2. ACTN CMI context...............................................4 2.1. Type 1 VN.................................................4 2.2. Type 2 VN.................................................5 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.................10 4.1. Customer view of VN......................................10 4.2. Innovative Services......................................11 4.2.1. VN Compute..........................................11 4.2.2. Multi-sources and Multi-destinations................11 4.2.3. Others..............................................12 4.3. Summary..................................................12 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.........................................34 8. Security Considerations.......................................50 9. IANA Considerations...........................................50 10. Acknowledgments..............................................50 Lee, et al. Expires December 2018 [Page 2] Internet-Draft ACTN VN YANG Model June 2018 11. References...................................................51 11.1. Normative References....................................51 11.2. Informative References..................................51 12. Contributors.................................................52 Authors' Addresses...............................................52 1. Introduction This document provides a YANG data model for the Abstraction and 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 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 and its reference to a Link Termination Point (LTP) of the Provider Edge (PE) Node; o Characteristics of Virtual Networks (VNs) that describe the customer's VNs in terms of VN Members comprising a VN, multi- source and/or multi-destination characteristics of VN Member, the VN's reference to TE-topology's Abstract Node; The actual VN instantiation and computation is performed with Connectivity Matrices sub-module of TE-Topology Model [TE-Topo] which provides TE network topology abstraction and management operation. Once TE-topology Model is used in triggering VN instantiation over the networks, TE-tunnel [TE-tunnel] Model will inevitably interact with TE-Topology model for setting up actual tunnels and LSPs under the tunnels. Lee, et al. Expires December 2018 [Page 3] Internet-Draft ACTN VN YANG Model June 2018 The ACTN VN operational state is included in the same tree as the configuration consistent with Network Management Datastore Architecture (NMDA) [NMDA]. The origin of the data is indicated as per the origin metadata annotation. 1.1. Terminology Refer to [ACTN-Frame], [RFC7926], and [RFC8309] for the key terms used in this document. 2. ACTN CMI context The model presented in this document has the following ACTN context. +-------+ | CNC | +-------+ | | VN YANG + TE-topology YANG | +-----------------------+ | MDSC | +-----------------------+ Figure 1. ACTN CMI Both ACTN VN YANG and TE-topology models are used over the CMI to establish a VN over TE networks. 2.1. Type 1 VN As defined in [ACTN-FW], a Virtual Network is a customer view of the TE network. To recapitulate VN types from [ACTN-FW], Type 1 VN is defined as follows: The VN can be seen as a set of edge-to-edge abstract links (a Type 1 VN). Each abstract link is referred to as a VN member and is formed as an end-to-end tunnel across the underlying networks. Such tunnels may be constructed by recursive slicing or abstraction of paths in the underlying networks and can encompass edge points of the Lee, et al. Expires December 2018 [Page 4] Internet-Draft ACTN VN YANG Model June 2018 customer's network, access links, intra-domain paths, and inter- domain links. If we were to create a VN where we have four VN-members as follows: VN-Member 1 L1-L4 VN-Member 2 L1-L7 VN-Member 3 L2-L4 VN-Member 4 L3-L8 Where L1, L2, L3, L4, L7 and L8 correspond to a Customer End-Point, respectively. This VN can be modeled as one abstract node representation as follows in Figure 2: +---------------+ L1 ------| |------ L4 L2 ------| AN 1 |------ L7 L3 ------| |------ L8 +---------------+ Figure 2. Abstract Node (One node topology) Modeling a VN as one abstract node is the easiest way for customers to express their end-to-end connectivity; however, customers are not limited to express their VN only with one abstract node. In some cases, more than one abstract nodes can be employed to express their VN. 2.2. Type 2 VN For some VN members of a VN, the customers are allowed to configure the actual path (i.e., detailed virtual nodes and virtual links) over the VN/abstract topology agreed mutually between CNC and MDSC prior to or a topology created by the MDSC as part of VN instantiation. Type 2 VN is always built on top of a Type 1 VN. If a Type 2 VN is desired for some or all of VN members of a type 1 VN (see the example in Section 2.1), the TE-topology model can Lee, et al. Expires December 2018 [Page 5] Internet-Draft ACTN VN YANG Model June 2018 provide the following abstract topology (that consists of virtual nodes and virtual links) which is built on top of the Type 1 VN. +----------------------------------------------+ | S1 S2 | | O---------------O | | ________/ \______ \ | | / \ \ | |S3 / \ S4 \ S5 | L1----|-O----------------------O---------O-----------|------L4 | \ \ \ | | \ \ \ | | \ S6 \ S7 \ S8 | | O ----------------O---------O-------|------L7 | / \ / \ ____/ | |S9 / \ /S10 \ / | L2-----|---O-----O---------------------O--------------|------L8 | / S11 | L3-----|-- | | | +----------------------------------------------+ Figure 3. Type 2 topology As you see from Figure 3, the Type 1 abstract node is depicted as a Type 1 abstract topology comprising of detailed virtual nodes and virtual links. As an example, if VN-member 1 (L1-L4) is chosen to configure its own path over Type 2 topology, it can select, say, a path that consists of the ERO {S3,S4,S5} based on the topology and its service requirement. This capability is enacted via TE-topology configuration by the customer. Lee, et al. Expires December 2018 [Page 6] Internet-Draft ACTN VN YANG Model June 2018 3. High-Level Control Flows with Examples 3.1. Type 1 VN Illustration If we were to create a VN where we have four VN-members as follows: VN-Member 1 L1-L4 VN-Member 2 L1-L7 VN-Member 3 L2-L4 VN-Member 4 L3-L8 Where L1, L2, L3, L4, L7 and L8 correspond to Customer End-Point, respectively. This VN can be modeled as one abstract node representation as follows: +---------------+ L1 ------| |------ L4 L2 ------| AN 1 |------ L7 L3 ------| |------ L8 +---------------+ If this VN is Type 1, the following diagram shows the message flow between CNC and MDSC to instantiate this VN using ACTN VN and TE- Topology Model. +--------+ +--------+ | CNC | | MDSC | +--------+ +--------+ | | | | CNC POST TE-topo | POST /nw:networks/nw:network/ | model(with Conn. | nw:node/te-node-id/tet:connectivity- | Matrix on one | matrices/tet:connectivity-matrix | Abstract node |---------------------------------------->| | HTTP 200 | |<----------------------------------------| | | CNC POST the ACTN| POST /ACTN VN | VN identifying |---------------------------------------->| If there is AP, VNAP and VN- | | multi-dest'n Members and maps | | module, then Lee, et al. Expires December 2018 [Page 7] Internet-Draft ACTN VN YANG Model June 2018 to the TE-topo | HTTP 200 | MDSC selects a |<----------------------------------------| src or dest'n | | and update | | ACTN VN YANG CNC GET the ACTN | GET /ACTN VN | VN YANG status |---------------------------------------->| | | | HTTP 200 (ACTN VN with status: selected| | VN-members in case of multi s-d | |<----------------------------------------| | | 3.2. Type 2 VN Illustration For some VN members, the customer may want to "configure" explicit routes over the path that connects its two end-points. Let us consider the following example. VN-Member 1 L1-L4 VN-Member 2 L1-L7 (via S4 and S7) VN-Member 3 L2-L4 VN-Member 4 L3-L8 (via S10) Where the following topology is the underlay for Abstraction Node 1 (AN1). S1 S2 O---------------O ________/ \______ \ / \ \ S3 / \ S4 \ S5 L1------O----------------------O---------O------------------L4 \ \ \ \ \ \ \ S6 \ S7 \ S8 O ----------------O---------O--------------L5 / \ / \ ____/ \_____________L6 Lee, et al. Expires December 2018 [Page 8] Internet-Draft ACTN VN YANG Model June 2018 S9 / \ /S10 \ / L2---------O-----O---------------------O---------------------L7 / S11\____________________L8 L3-------- If CNC creates the single abstract topology, the following diagram shows the message flow between CNC and MDSC to instantiate this VN using ACTN VN and TE-Topology Model. +--------+ +--------+ | CNC | | MDSC | +--------+ +--------+ | | | | CNC POST TE-topo | POST /nw:networks/nw:network/ | model(with Conn. | nw:node/te-node-id/tet:connectivity- | Matrix on one | matrices/tet:connectivity-matrix | Abstract node and|---------------------------------------->| Explicit paths in| | The conn. Matrix | HTTP 200 | |<----------------------------------------| | | CNC POST the ACTN| POST /ACTN VN | VN identifying |---------------------------------------->| AP, VNAP and VN- | | Members and maps | | to the TE-topo | HTTP 200 | |<----------------------------------------| | | | | CNC GET the ACTN | GET /ACTN VN | VN YANG status |---------------------------------------->| | | | HTTP 200 (ACTN VN with status) | |<----------------------------------------| | | On the other hand, if MDSC create single node topology based ACTN VN YANG posted by the CNC, the following diagram shows the message flow between CNC and MDSC to instantiate this VN using ACTN VN and TE- Topology Model. Lee, et al. Expires December 2018 [Page 9] Internet-Draft ACTN VN YANG Model June 2018 +--------+ +--------+ | CNC | | MDSC | +--------+ +--------+ | | | | CNC POST ACTN VN | | Identifying AP, | | VNAP and VN- | POST /ACTN VN | MDSC populates Members |---------------------------------------->| a single Abst. | HTTP 200 | node topology |<----------------------------------------| by itself | | CNC POST the ACTN| POST /ACTN VN | VN identifying |---------------------------------------->| AP, VNAP and VN- | | Members and maps | | to the TE-topo | HTTP 200 | |<----------------------------------------| | | | | CNC GET the ACTN | GET /ACTN VN | VN YANG status |---------------------------------------->| | | | HTTP 200 (ACTN VN with status) | |<----------------------------------------| | | 4. Justification of the ACTN VN Model on the CMI. 4.1. Customer view of VN The VN-Yang model allows to define a customer view, and allows the customer to communicate using the VN constructs as described in the [ACTN-INFO]. It also allows to group the set of edge-to-edge links (i.e., VN members) under a common umbrella of VN. This allows the customer to instantiate and view the VN as one entity, making it easier for some customers to work on VN without worrying about the details of the provider based YANG models. This is similar to the benefits of having a separate YANG model for the customer services as described in [SERVICE-YANG], which states that service models do not make any assumption of how a service is actually engineered and delivered for a customer. Lee, et al. Expires December 2018 [Page 10] Internet-Draft ACTN VN YANG Model June 2018 4.2. Innovative Services 4.2.1. VN Compute ACTN VN supports VN compute (pre-instantiation mode) to view the full VN as a single entity before instantiation. Achieving this via path computation or "compute only" tunnel setup does not provide the same functionality. 4.2.2. Multi-sources and Multi-destinations In creating a virtual network, the list of sources or destinations or both may not be pre-determined by the customer. For instance, for a given source, there may be a list of multiple-destinations to which the optimal destination may be chosen depending on the network resource situations. Likewise, for a given destination, there may also be multiple-sources from which the optimal source may be chosen. In some cases, there may be a pool of multiple sources and destinations from which the optimal source-destination may be chosen. The following YANG module is shown for describing source container and destination container. The following YANG tree shows how to model multi-sources and multi-destinations. +--rw actn . . . +--rw vn +--rw vn-list* [vn-id] +--rw vn-id uint32 +--rw vn-name? string +--rw vn-topology-id? te-types:te-topology-id +--rw abstract-node? -> /nw:networks/network/node/tet:te-node-id +--rw vn-member-list* [vn-member-id] | +--rw vn-member-id uint32 | +--rw src | | +--rw src? -> /actn/ap/access-point-list/access-point-id | | +--rw src-vn-ap-id? -> /actn/ap/access-point-list/vn-ap/vn-ap-id | | +--rw multi-src? boolean {multi-src-dest}? | +--rw dest | | +--rw dest? -> /actn/ap/access-point-list/access-point- id | | +--rw dest-vn-ap-id? -> /actn/ap/access-point-list/vn-ap/vn-ap-id | | +--rw multi-dest? boolean {multi-src-dest}? Lee, et al. Expires December 2018 [Page 11] Internet-Draft ACTN VN YANG Model June 2018 | +--rw connetivity-matrix-id? -> /nw:networks/network/node/tet:te/te- node-attributes/connectivity-matrices/connectivity-matrix/id | +--ro oper-status? identityref +--ro if-selected? boolean {multi-src-dest}? +--rw admin-status? identityref +--ro oper-status? identityref 4.2.3. Others The VN Yang model can be easily augmented to support the mapping of VN to the Services such as L3SM and L2SM as described in [TE-MAP]. The VN Yang model can be extended to support telemetry, performance monitoring and network autonomics as described in [ACTN-PM]. 4.3. Summary This section summarizes the innovative service features of the ACTN VN Yang. o Maintenance of AP and VNAP along with VN. o VN construct to group of edge-to-edge links o VN Compute (pre-instantiate) o Multi-Source / Multi-Destination o Ability to support various VN and VNS Types * VN Type 1: Customer configures the VN as a set of VN 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. Lee, et al. Expires December 2018 [Page 12] Internet-Draft ACTN VN YANG Model June 2018 5. ACTN VN YANG Model (Tree Structure) module: ietf-actn-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 | +--rw abstract-node? -> /nw:networks/network/node/tet:te-node-id | +--rw ltp? te-types:te-tp-id +--rw vn +--rw vn-list* [vn-id] +--rw vn-id uint32 +--rw vn-name? string +--rw vn-topology-id? te-types:te-topology-id +--rw abstract-node? -> /nw:networks/network/node/tet:te-node-id +--rw vn-member-list* [vn-member-id] | +--rw vn-member-id uint32 | +--rw src | | +--rw src? -> /actn/ap/access-point- list/access-point-id | | +--rw src-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | | +--rw multi-src? boolean {multi-src-dest}? | +--rw dest | | +--rw dest? -> /actn/ap/access-point- list/access-point-id Lee, et al. Expires December 2018 [Page 13] Internet-Draft ACTN VN YANG Model June 2018 | | +--rw dest-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | | +--rw multi-dest? boolean {multi-src-dest}? | +--rw connetivity-matrix-id? -> /nw:networks/network/node/tet:te/te-node-attributes/connectivity- matrices/connectivity-matrix/id | +--ro oper-status? identityref +--ro if-selected? boolean {multi-src-dest}? +--rw admin-status? identityref +--ro oper-status? identityref +--rw vn-level-diversity? vn-disjointness rpcs: +---x vn-compute +---w input | +---w abstract-node? -> /nw:networks/network/node/tet:te-node-id | +---w vn-member-list* [vn-member-id] | | +---w vn-member-id uint32 | | +---w src | | | +---w src? -> /actn/ap/access-point- list/access-point-id | | | +---w src-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | | | +---w multi-src? boolean {multi-src-dest}? | | +---w dest | | | +---w dest? -> /actn/ap/access-point- list/access-point-id | | | +---w dest-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | | | +---w multi-dest? boolean {multi-src-dest}? | | +---w connetivity-matrix-id? -> /nw:networks/network/node/tet:te/te-node-attributes/connectivity- matrices/connectivity-matrix/id | +---w vn-level-diversity? vn-disjointness +--ro output +--ro vn-member-list* [vn-member-id] +--ro vn-member-id uint32 +--ro src | +--ro src? -> /actn/ap/access-point- list/access-point-id Lee, et al. Expires December 2018 [Page 14] Internet-Draft ACTN VN YANG Model June 2018 | +--ro src-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | +--ro multi-src? boolean {multi-src-dest}? +--ro dest | +--ro dest? -> /actn/ap/access-point- list/access-point-id | +--ro dest-vn-ap-id? -> /actn/ap/access-point- list/vn-ap/vn-ap-id | +--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" module ietf-actn-vn { namespace "urn:ietf:params:xml:ns:yang:ietf-actn-vn"; prefix "vn"; /* Import network */ import ietf-network { prefix "nw"; } /* Import TE generic types */ import ietf-te-types { prefix "te-types"; } /* Import Abstract TE Topology */ import ietf-te-topology { prefix "tet"; } organization Lee, et al. Expires December 2018 [Page 15] Internet-Draft ACTN VN YANG Model June 2018 "IETF Traffic Engineering Architecture and Signaling (TEAS) 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 { description "initial version."; reference "TBD"; } /* * Features */ feature multi-src-dest { description "Support for selection of one src or destination among multiple."; } /*identity path-metric-delay { base te-types:path-metric-type; description "delay path metric"; } identity path-metric-delay-variation { base te-types:path-metric-type; description "delay-variation path metric"; } identity path-metric-loss { base te-types:path-metric-type; description "loss path metric"; }*/ identity vn-state-type { description "Base identity for VN state"; Lee, et al. Expires December 2018 [Page 16] Internet-Draft ACTN VN YANG Model June 2018 } identity vn-state-up { base vn-state-type; description "VN state up"; } identity vn-state-down { base vn-state-type; description "VN state down"; } identity vn-admin-state-type { description "Base identity for VN admin states"; } identity vn-admin-state-up { base vn-admin-state-type; description "VN administratively state up"; } identity vn-admin-state-down { base vn-admin-state-type; description "VN administratively state down"; } identity vn-compute-state-type { description "Base identity for compute states"; } identity vn-compute-state-computing { base vn-compute-state-type; description "State path compute in progress"; } identity vn-compute-state-computation-ok { base vn-compute-state-type; description "State path compute successful"; } identity vn-compute-state-computatione-failed { base vn-compute-state-type; description "State path compute failed"; } /* * Groupings */ typedef vn-disjointness { Lee, et al. Expires December 2018 [Page 17] Internet-Draft ACTN VN YANG Model June 2018 type bits { bit node { position 0; description "node disjoint"; } bit link { position 1; description "link disjoint"; } bit srlg { position 2; description "srlg disjoint"; } } description "type of the resource disjointness for VN level applied across all VN members in a VN"; } grouping vn-ap { description "VNAP related information"; leaf vn-ap-id { type uint32; description "unique identifier for the referred VNAP"; } leaf vn { type leafref { path "/actn/vn/vn-list/vn-id"; } description "reference to the VN"; } leaf abstract-node { type leafref { path "/nw:networks/nw:network/nw:node/" + "tet:te-node-id"; } description "a reference to the abstract node in TE Topology"; } Lee, et al. Expires December 2018 [Page 18] Internet-Draft ACTN VN YANG Model June 2018 leaf ltp { type te-types:te-tp-id; description "Reference LTP in the TE-topology"; } } grouping access-point{ description "AP related information"; leaf access-point-id { type uint32; description "unique identifier for the referred access point"; } leaf access-point-name { type string; description "ap name"; } leaf max-bandwidth { type te-types:te-bandwidth; description "max bandwidth of the AP"; } leaf avl-bandwidth { type te-types:te-bandwidth; description "available bandwidth of the AP"; } /*add details and any other properties of AP, not associated by a VN CE port, PE port etc. */ list vn-ap { key vn-ap-id; uses vn-ap; description "list of VNAP in this AP"; } }//access-point grouping vn-member { description "vn-member is described by this container"; Lee, et al. Expires December 2018 [Page 19] Internet-Draft ACTN VN YANG Model June 2018 leaf vn-member-id { type uint32; description "vn-member identifier"; } container src { description "the source of VN Member"; leaf src { type leafref { path "/actn/ap/access-point-list/access-point-id"; } description "reference to source AP"; } leaf src-vn-ap-id{ type leafref { path "/actn/ap/access-point-list/vn-ap/vn-ap-id"; } description "reference to source VNAP"; } leaf multi-src { if-feature multi-src-dest; type boolean; description "Is source part of multi-source, where only one of the source is enabled"; } } container dest { description "the destination of VN Member"; leaf dest { type leafref { path "/actn/ap/access-point-list/access-point-id"; } description "reference to destination AP"; } leaf dest-vn-ap-id{ type leafref { path "/actn/ap/access-point-list/vn-ap/vn-ap-id"; Lee, et al. Expires December 2018 [Page 20] Internet-Draft ACTN VN YANG Model June 2018 } description "reference to dest VNAP"; } leaf multi-dest { if-feature multi-src-dest; type boolean; description "Is destination part of multi-destination, where only one of the destination is enabled"; } } leaf connetivity-matrix-id{ type leafref { path "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/" + "tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:id"; } description "reference to connetivity-matrix"; } }//vn-member /* grouping policy { description "policy related to vn-member-id"; leaf local-reroute { type boolean; description "Policy to state if reroute can be done locally"; } leaf push-allowed { type boolean; description "Policy to state if changes can be pushed to the customer"; } leaf incremental-update { type boolean; description "Policy to allow only the changes to be reported"; } Lee, et al. Expires December 2018 [Page 21] Internet-Draft ACTN VN YANG Model June 2018 }//policy */ grouping vn-policy { description "policy for VN-level diverisity"; leaf vn-level-diversity { type vn-disjointness; description "the type of disjointness on the VN level (i.e., across all VN members)"; } } /* grouping metrics-op { description "metric related information"; list metric{ key "metric-type"; config false; description "The list of metrics for VN"; leaf metric-type { type identityref { base te-types:path-metric-type; } description "The VN metric type."; } leaf value{ type uint32; description "The limit value"; } } } */ /* grouping metrics { description "metric related information"; list metric{ key "metric-type"; description "The list of metrics for VN"; uses te:path-metrics-bounds_config; Lee, et al. Expires December 2018 [Page 22] Internet-Draft ACTN VN YANG Model June 2018 container optimize{ description "optimizing constraints"; leaf enabled{ type boolean; description "Metric to optimize"; } leaf value{ type uint32; description "The computed value"; } } } } */ /* grouping service-metric { description "service-metric"; uses te:path-objective-function_config; uses metrics; uses te-types:common-constraints_config; uses te:protection-restoration-params_config; uses policy; }//service-metric */ /* * Configuration data nodes */ container actn { description "actn is described by this container"; container ap { description "AP configurations"; list access-point-list { key "access-point-id"; description "access-point identifier"; uses access-point{ description "access-point information"; } Lee, et al. Expires December 2018 [Page 23] Internet-Draft ACTN VN YANG Model June 2018 } } container vn { description "VN configurations"; list vn-list { key "vn-id"; description "a virtual network is identified by a vn-id"; leaf vn-id { type uint32; description "a unique vn identifier"; } leaf vn-name { type string; description "vn name"; } leaf vn-topology-id{ type te-types:te-topology-id; description "An optional identifier to the TE Topology Model where the abstract nodes and links of the Topology can be found for Type 2 VNS"; } leaf abstract-node { type leafref { path "/nw:networks/nw:network/nw:node/" + "tet:te-node-id"; } description "a reference to the abstract node in TE Topology"; } list vn-member-list{ key "vn-member-id"; description "List of VN-members in a VN"; uses vn-member; /*uses metrics-op;*/ leaf oper-status { type identityref { base vn-state-type; } Lee, et al. Expires December 2018 [Page 24] Internet-Draft ACTN VN YANG Model June 2018 config false; description "VN-member operational state."; } } leaf if-selected{ if-feature multi-src-dest; type boolean; default false; config false; description "Is the vn-member is selected among the multi-src/dest options"; } /* container multi-src-dest{ if-feature multi-src-dest; config false; description "The selected VN Member when multi-src and/or mult-destination is enabled."; leaf selected-vn-member{ type leafref { path "/actn/vn/vn-list/vn-member-list" + "/vn-member-id"; } description "The selected VN Member along the set of source and destination configured with multi-source and/or multi-destination"; } } */ /*uses service-metric;*/ leaf admin-status { type identityref { base vn-admin-state-type; } default vn-admin-state-up; description "VN administrative state."; } leaf oper-status { type identityref { base vn-state-type; Lee, et al. Expires December 2018 [Page 25] Internet-Draft ACTN VN YANG Model June 2018 } config false; description "VN operational state."; } uses vn-policy; }//vn-list }//vn }//actn /* * Notifications - TBD */ /* * RPC */ rpc vn-compute{ description "The VN computation without actual instantiation"; input { leaf abstract-node { type leafref { path "/nw:networks/nw:network/nw:node/" + "tet:te-node-id"; } description "a reference to the abstract node in TE Topology"; } list vn-member-list{ key "vn-member-id"; description "List of VN-members in a VN"; uses vn-member; } uses vn-policy; /*uses service-metric;*/ } output { list vn-member-list{ key "vn-member-id"; description "List of VN-members in a VN"; uses vn-member; leaf if-selected{ if-feature multi-src-dest; Lee, et al. Expires December 2018 [Page 26] Internet-Draft ACTN VN YANG Model June 2018 type boolean; default false; description "Is the vn-member is selected among the multi-src/dest options"; } /*uses metrics-op;*/ leaf compute-status { type identityref { base vn-compute-state-type; } description "VN-member compute state."; } } /* container multi-src-dest{ if-feature multi-src-dest; description "The selected VN Member when multi-src and/or mult-destination is enabled."; leaf selected-vn-member-id{ type uint32; description "The selected VN Member-id from the input"; } }*/ } } } 7. JSON Example This section provides json implementation examples as to how ACTN VN YANG model and TE topology model are used together to instantiate virtual networks. Lee, et al. Expires December 2018 [Page 27] Internet-Draft ACTN VN YANG Model June 2018 The example in this section includes following VN o VN1 (Type 1): Which maps to the single node topology abstract1 (node D1) and consist of VN Members 104 (L1 to L4), 107 (L1 to L7), 204 (L2 to L4), 308 (L3 to L8) and 108 (L1 to L8). We also show how disjointness (node, link, srlg) is supported in the example on the global level (i.e., connectivity matrices level). o VN2 (Type 2): Which maps to the single node topology abstract2 (node D2), this topology has an underlay topology (absolute) (see 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 { "actn":{ "ap":{ "access-point-list": [ { "access-point-id": 101, "access-point-name": "101", "vn-ap": [ { "vn-ap-id": 10101, "vn": 1, "abstract-node": "D1", "ltp": "1-0-1" }, { "vn-ap-id": 10102, "vn": 2, "abstract-node": "D2", "ltp": "1-0-1" }, { "vn-ap-id": 10103, "vn": 3, "abstract-node": "D3", Lee, et al. Expires December 2018 [Page 28] Internet-Draft ACTN VN YANG Model June 2018 "ltp": "1-0-1" }, ] }, { "access-point-id": 202, "access-point-name": "202", "vn-ap": [ { "vn-ap-id": 20201, "vn": 1, "abstract-node": "D1", "ltp": "2-0-2" } ] }, { "access-point-id": 303, "access-point-name": "303", "vn-ap": [ { "vn-ap-id": 30301, "vn": 1, "abstract-node": "D1", "ltp": "3-0-3" }, { "vn-ap-id": 30303, "vn": 3, "abstract-node": "D3", "ltp": "3-0-3" } ] }, { "access-point-id": 440, "access-point-name": "440", "vn-ap": [ { "vn-ap-id": 44001, "vn": 1, "abstract-node": "D1", "ltp": "4-4-0" } ] }, { "access-point-id": 550, "access-point-name": "550", Lee, et al. Expires December 2018 [Page 29] Internet-Draft ACTN VN YANG Model June 2018 "vn-ap": [ { "vn-ap-id": 55002, "vn": 2, "abstract-node": "D2", "ltp": "5-5-0" } ] }, { "access-point-id": 770, "access-point-name": "770", "vn-ap": [ { "vn-ap-id": 77001, "vn": 1, "abstract-node": "D1", "ltp": "7-7-0" }, { "vn-ap-id": 77003, "vn": 3, "abstract-node": "D3", "ltp": "7-7-0" } ] }, { "access-point-id": 880, "access-point-name": "880", "vn-ap": [ { "vn-ap-id": 88001, "vn": 1, "abstract-node": "D1", "ltp": "8-8-0" }, { "vn-ap-id": 88003, "vn": 3, "abstract-node": "D3", "ltp": "8-8-0" } ] } ] }, "vn":{ "vn-list": [ Lee, et al. Expires December 2018 [Page 30] Internet-Draft ACTN VN YANG Model June 2018 { "vn-id": 1, "vn-name": "vn1", "vn-topology-id": "te-topology:abstract1", "abstract-node": "D1", "vn-member-list": [ { "vn-member-id": 104, "src": { "src": 101, "src-vn-ap-id": 10101, }, "dest": { "dest": 440, "dest-vn-ap-id": 44001, }, "connectivity-matrix-id": 104 }, { "vn-member-id": 107, "src": { "src": 101, "src-vn-ap-id": 10101, }, "dest": { "dest": 770, "dest-vn-ap-id": 77001, }, "connectivity-matrix-id": 107 }, { "vn-member-id": 204, "src": { "src": 202, "dest-vn-ap-id": 20401, }, "dest": { "dest": 440, "dest-vn-ap-id": 44001, }, "connectivity-matrix-id": 204 }, { "vn-member-id": 308, "src": { "src": 303, "src-vn-ap-id": 30301, }, "dest": { Lee, et al. Expires December 2018 [Page 31] Internet-Draft ACTN VN YANG Model June 2018 "dest": 880, "src-vn-ap-id": 88001, }, "connectivity-matrix-id": 308 }, { "vn-member-id": 108, "src": { "src": 101, "src-vn-ap-id": 10101, }, "dest": { "dest": 880, "dest-vn-ap-id": 88001, }, "connectivity-matrix-id": 108 } ] }, { "vn-id": 2, "vn-name": "vn2", "vn-topology-id": "te-topology:abstract2", "abstract-node": "D2", "vn-member-list": [ { "vn-member-id": 105, "src": { "src": 101, "src-vn-ap-id": 10102, }, "dest": { "dest": 550, "dest-vn-ap-id": 55002, }, "connectivity-matrix-id": 105 } ] }, { "vn-id": 3, "vn-name": "vn3", "vn-topology-id": "te-topology:abstract3", "abstract-node": "D3", "vn-member-list": [ { "vn-member-id": 104, "src": { "src": 101, Lee, et al. Expires December 2018 [Page 32] Internet-Draft ACTN VN YANG Model June 2018 }, "dest": { "dest": 440, "multi-dest": true } }, { "vn-member-id": 107, "src": { "src": 101, "src-vn-ap-id": 10103, }, "dest": { "dest": 770, "dest-vn-ap-id": 77003, "multi-dest": true }, "connectivity-matrix-id": 107, "if-selected":true, }, { "vn-member-id": 204, "src": { "src": 202, "multi-src": true, }, "dest": { "dest": 440, }, }, { "vn-member-id": 304, "src": { "src": 303, "src-vn-ap-id": 30303, "multi-src": true, }, "dest": { "dest": 440, "src-vn-ap-id": 44003, }, "connectivity-matrix-id": 304, "if-selected":true, }, ] }, ] } Lee, et al. Expires December 2018 [Page 33] Internet-Draft ACTN VN YANG Model June 2018 } } 7.2. TE-topology JSON { "networks": { "network": [ { "network-types": { "te-topology": {} }, "network-id": "abstract1", "provider-id": 201, "client-id": 600, "te-topology-id": "te-topology:abstract1", "node": [ { "node-id": "D1", "te-node-id": "2.0.1.1", "te": { "te-node-attributes": { "domain-id" : 1, "is-abstract": [null], "connectivity-matrices": { "is-allowed": true, "path-constraints": { "bandwidth-generic": { "te-bandwidth": { "generic": [ { "generic": "0x1p10", } ] } } "disjointness": "node link srlg", }, "connectivity-matrix": [ { "id": 104, "from": "1-0-1", "to": "4-4-0" }, { "id": 107, "from": "1-0-1", Lee, et al. Expires December 2018 [Page 34] Internet-Draft ACTN VN YANG Model June 2018 "to": "7-7-0" }, { "id": 204, "from": "2-0-2", "to": "4-4-0" }, { "id": 308, "from": "3-0-3", "to": "8-8-0" }, { "id": 108, "from": "1-0-1", "to": "8-8-0" }, ] } } }, "termination-point": [ { "tp-id": "1-0-1", "te-tp-id": 10001, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "1-1-0", "te-tp-id": 10100, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-0-2", "te-tp-id": 20002, Lee, et al. Expires December 2018 [Page 35] Internet-Draft ACTN VN YANG Model June 2018 "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-2-0", "te-tp-id": 20200, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "3-0-3", "te-tp-id": 30003, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "3-3-0", "te-tp-id": 30300, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-0-4", "te-tp-id": 40004, "te": { Lee, et al. Expires December 2018 [Page 36] Internet-Draft ACTN VN YANG Model June 2018 "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-4-0", "te-tp-id": 40400, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "5-0-5", "te-tp-id": 50005, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "5-5-0", "te-tp-id": 50500, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-0-6", "te-tp-id": 60006, "te": { "interface-switching-capability": [ Lee, et al. Expires December 2018 [Page 37] Internet-Draft ACTN VN YANG Model June 2018 { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-6-0", "te-tp-id": 60600, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "7-0-7", "te-tp-id": 70007, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "7-7-0", "te-tp-id": 70700, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-0-8", "te-tp-id": 80008, "te": { "interface-switching-capability": [ { Lee, et al. Expires December 2018 [Page 38] Internet-Draft ACTN VN YANG Model June 2018 "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-8-0", "te-tp-id": 80800, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } } ] } ] }, { "network-types": { "te-topology": {} }, "network-id": "abstract2", "provider-id": 201, "client-id": 600, "te-topology-id": "te-topology:abstract2", "node": [ { "node-id": "D2", "te-node-id": "2.0.1.2", "te": { "te-node-attributes": { "domain-id" : 1, "is-abstract": [null], "connectivity-matrices": { "is-allowed": true, "underlay": { "enabled": true }, "path-constraints": { "bandwidth-generic": { "te-bandwidth": { "generic": [ { "generic": "0x1p10" Lee, et al. Expires December 2018 [Page 39] Internet-Draft ACTN VN YANG Model June 2018 } ] } } }, "optimizations": { "objective-function": { "objective-function-type": "of-maximize-residual- bandwidth" } }, "connectivity-matrix": [ { "id": 105, "from": "1-0-1", "to": "5-5-0", "underlay": { "enabled": true, "primary-path": { "network-ref": "absolute", "path-element": [ { "path-element-id": 1, "index": 1, "numbered-hop": { "address": "4.4.4.4", "hop-type": "STRICT" } }, { "path-element-id": 2, "index": 2, "numbered-hop": { "address": "7.7.7.7", "hop-type": "STRICT" } } ] } } } ] } } }, "termination-point": [ { "tp-id": "1-0-1", "te-tp-id": 10001, Lee, et al. Expires December 2018 [Page 40] Internet-Draft ACTN VN YANG Model June 2018 "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "1-1-0", "te-tp-id": 10100, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-0-2", "te-tp-id": 20002, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-2-0", "te-tp-id": 20200, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "3-0-3", "te-tp-id": 30003, "te": { Lee, et al. Expires December 2018 [Page 41] Internet-Draft ACTN VN YANG Model June 2018 "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "3-3-0", "te-tp-id": 30300, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-0-4", "te-tp-id": 40004, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-4-0", "te-tp-id": 40400, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "5-0-5", "te-tp-id": 50005, "te": { "interface-switching-capability": [ Lee, et al. Expires December 2018 [Page 42] Internet-Draft ACTN VN YANG Model June 2018 { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "5-5-0", "te-tp-id": 50500, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-0-6", "te-tp-id": 60006, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-6-0", "te-tp-id": 60600, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "7-0-7", "te-tp-id": 70007, "te": { "interface-switching-capability": [ { Lee, et al. Expires December 2018 [Page 43] Internet-Draft ACTN VN YANG Model June 2018 "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "7-7-0", "te-tp-id": 70700, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-0-8", "te-tp-id": 80008, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-8-0", "te-tp-id": 80800, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } } ] } ] }, { "network-types": { "te-topology": {} Lee, et al. Expires December 2018 [Page 44] Internet-Draft ACTN VN YANG Model June 2018 }, "network-id": "abstract3", "provider-id": 201, "client-id": 600, "te-topology-id": "te-topology:abstract3", "node": [ { "node-id": "D3", "te-node-id": "3.0.1.1", "te": { "te-node-attributes": { "domain-id" : 3, "is-abstract": [null], "connectivity-matrices": { "is-allowed": true, "path-constraints": { "bandwidth-generic": { "te-bandwidth": { "generic": [ { "generic": "0x1p10", } ] } } }, "connectivity-matrix": [ { "id": 107, "from": "1-0-1", "to": "7-7-0" }, { "id": 308, "from": "3-0-3", "to": "8-8-0" }, ] } } }, "termination-point": [ { "tp-id": "1-0-1", "te-tp-id": 10001, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", Lee, et al. Expires December 2018 [Page 45] Internet-Draft ACTN VN YANG Model June 2018 "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "1-1-0", "te-tp-id": 10100, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-0-2", "te-tp-id": 20002, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "2-2-0", "te-tp-id": 20200, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "3-0-3", "te-tp-id": 30003, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" Lee, et al. Expires December 2018 [Page 46] Internet-Draft ACTN VN YANG Model June 2018 } ] } }, { "tp-id": "3-3-0", "te-tp-id": 30300, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-0-4", "te-tp-id": 40004, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "4-4-0", "te-tp-id": 40400, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "5-0-5", "te-tp-id": 50005, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } Lee, et al. Expires December 2018 [Page 47] Internet-Draft ACTN VN YANG Model June 2018 ] } }, { "tp-id": "5-5-0", "te-tp-id": 50500, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-0-6", "te-tp-id": 60006, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "6-6-0", "te-tp-id": 60600, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "7-0-7", "te-tp-id": 70007, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] Lee, et al. Expires December 2018 [Page 48] Internet-Draft ACTN VN YANG Model June 2018 } }, { "tp-id": "7-7-0", "te-tp-id": 70700, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-0-8", "te-tp-id": 80008, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } }, { "tp-id": "8-8-0", "te-tp-id": 80800, "te": { "interface-switching-capability": [ { "switching-capability": "switching-otn", "encoding": "lsp-encoding-oduk" } ] } } ] } ] }, ] } } Lee, et al. Expires December 2018 [Page 49] Internet-Draft ACTN VN YANG Model June 2018 8. Security Considerations TDB 9. IANA Considerations TDB 10. Acknowledgments The authors would like to thank Xufeng Liu for his helpful comments and valuable suggestions. Lee, et al. Expires December 2018 [Page 50] Internet-Draft ACTN VN YANG Model June 2018 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: draft-ietf-teas-yang-te. 11.2. Informative References [RFC7926] A. Farrel (Ed.), "Problem Statement and Architecture for Information Exchange between Interconnected Traffic- Engineered Networks", RFC 7926, July 2016. [ACTN-REQ] Lee, et al., "Requirements for Abstraction and Control of TE Networks", draft-ietf-teas-actn-requirements, work in progress. [ACTN-FWK] D. Ceccarelli, Y. Lee [Editors], "Framework for Abstraction and Control of Traffic Engineered Networks", draft-ceccarelli-teas-actn-framework, work in progress. [TE-MAP] Y. Lee, D. Dhody, and D. Ceccarelli, "Traffic Engineering and Service Mapping Yang Model", draft-lee-teas-te- service-mapping-yang, work in progress. [SERVICE-YANG] Q. Wu, W. Liu and A. Farrel, "Service Models Explained", draft-wu-opsawg-service-model-explained, work in progress. [ACTN-PM] Y. Lee, et al., "YANG models for ACTN TE Performance Monitoring Telemetry and Network Autonomics", draft-lee- teas-actn-pm-telemetry-autonomics, work in progress. [OIF-VTNS] Virtual Transport Network Services 1.0 Specification, IA OIF-VTNS-1.0, April 2017. [L1CSM] G. Fioccola, Ed. & Y. Lee, Ed., "A Yang Data Model for L1 Connectivity Service Model (L1CSM)", draft-ietf-ccamp- l1csm-yang, work in progress. Lee, et al. Expires December 2018 [Page 51] Internet-Draft ACTN VN YANG Model June 2018 [L2SM] G. Fioccola, Ed., "A YANG Data Model for L2VPN Service Delivery", draft-ietf-l2sm-l2vpn-service-model, work in progress. [RFC8299] Q. Wu, Ed., S. Litkowski, L. Tomotaki, and K. Ogaki, "YANG Data Model for L3VPN Service Delivery", RFC 8299, January 2018. [RFC8309] Q. Wu, W. Cheng, and A. Farrel. "Service Models Explained", RFC 8309, January 2018. 12. Contributors Contributor's Addresses Haomian Zheng Huawei Technologies Email: zhenghaomian@huawei.com Xian Zhang Huawei Technologies Email: zhang.xian@huawei.com Sergio Belotti Nokia Email: sergio.belotti@nokia.com Takuya Miyasaka KDDI Email: ta-miyasaka@kddi.com Authors' Addresses Young Lee (ed.) Huawei Technologies Email: leeyoung@huawei.com Dhruv Dhody Huawei Technologies Lee, et al. Expires December 2018 [Page 52] Internet-Draft ACTN VN YANG Model June 2018 Email: dhruv.ietf@gmail.com Daniele Ceccarelli Ericsson Torshamnsgatan,48 Stockholm, Sweden Email: daniele.ceccarelli@ericsson.com Igor Bryskin Huawei Email: Igor.Bryskin@huawei.com Bin Yeong Yoon ETRI Email: byyun@etri.re.kr Qin Wu Huawei Technologies Email: bill.wu@huawei.com Peter Park KT Email: peter.park@kt.com Lee, et al. Expires December 2018 [Page 53]