draft-ietf-teas-actn-vn-yang-00.txt   draft-ietf-teas-actn-vn-yang-01.txt 
TEAS Working Group Y. Lee (Editor) TEAS Working Group Y. Lee (Editor)
Internet Draft Dhruv Dhody Internet Draft Dhruv Dhody
Intended Status: Standard Track Huawei Intended Status: Standard Track Huawei
Expires: November 29, 2018 D. Ceccarelli Expires: December 19, 2018 D. Ceccarelli
Ericsson Ericsson
Igor Bryskin Igor Bryskin
Huawei Huawei
Bin Yeong Yoon Bin Yeong Yoon
ETRI ETRI
Qin Wu
Huawei
Peter Park
KT
May 29, 2018 June 19, 2018
A Yang Data Model for ACTN VN Operation A Yang Data Model for ACTN VN Operation
draft-ietf-teas-actn-vn-yang-00 draft-ietf-teas-actn-vn-yang-01
Abstract Abstract
This document provides a YANG data model for the Abstraction and This document provides a YANG data model for the Abstraction and
Control of Traffic Engineered (TE) networks (ACTN) Virtual Network Control of Traffic Engineered (TE) networks (ACTN) Virtual Network
Service (VNS) operation. Service (VNS) operation.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
skipping to change at page 1, line 44 skipping to change at page 2, line 4
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on December 19, 2018.
This Internet-Draft will expire on November 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
skipping to change at page 2, line 24 skipping to change at page 2, line 28
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Terminology...............................................4 1.1. Terminology...............................................4
2. ACTN CMI context...............................................4 2. ACTN CMI context...............................................4
2.1. Type 1 VN.................................................4 2.1. Type 1 VN.................................................4
2.2. Type 2 VN.................................................5 2.2. Type 2 VN.................................................5
3. High-Level Control Flows with Examples.........................6 3. High-Level Control Flows with Examples.........................7
3.1. Type 1 VN Illustration....................................6 3.1. Type 1 VN Illustration....................................7
3.2. Type 2 VN Illustration....................................8 3.2. Type 2 VN Illustration....................................8
4. Justification of the ACTN VN Model on the CMI.................10 4. Justification of the ACTN VN Model on the CMI.................10
4.1. Customer view of VN......................................10 4.1. Customer view of VN......................................10
4.2. Innovative Services......................................10 4.2. Innovative Services......................................11
4.2.1. VN Compute..........................................10 4.2.1. VN Compute..........................................11
4.2.2. Multi-sources and Multi-destinations................11 4.2.2. Multi-sources and Multi-destinations................11
4.2.3. Others..............................................11 4.2.3. Others..............................................12
4.3. Summary..................................................12 4.3. Summary..................................................12
5. ACTN VN YANG Model (Tree Structure)...........................12 5. ACTN VN YANG Model (Tree Structure)...........................13
6. ACTN-VN YANG Code.............................................15 6. ACTN-VN YANG Code.............................................15
7. JSON Example..................................................27 7. JSON Example..................................................27
7.1. ACTN VN JSON.............................................28 7.1. ACTN VN JSON.............................................28
7.2. TE-topology JSON.........................................33 7.2. TE-topology JSON.........................................34
8. Security Considerations.......................................49 8. Security Considerations.......................................50
9. IANA Considerations...........................................50 9. IANA Considerations...........................................50
10. Acknowledgments..............................................50 10. Acknowledgments..............................................50
11. References...................................................51 11. References...................................................51
11.1. Normative References....................................51 11.1. Normative References....................................51
11.2. Informative References..................................51 11.2. Informative References..................................51
12. Contributors.................................................52 12. Contributors.................................................52
Authors' Addresses...............................................52 Authors' Addresses...............................................52
1. Introduction 1. Introduction
This document provides a YANG data model for the Abstraction and This document provides a YANG data model for the Abstraction and
Control of Traffic Engineered (TE) networks (ACTN) Virtual Network Control of Traffic Engineered (TE) networks (ACTN) Virtual Network
Service (VNS) operation that is going to be implemented for the Service (VNS) operation that is going to be implemented for the
Customer Network Controller (CNC)- Multi-Domain Service Coordinator Customer Network Controller (CNC)- Multi-Domain Service Coordinator
(MSDC) interface (CMI). (MSDC) interface (CMI).
The YANG model on the CMI is also known as customer service model in The YANG model on the CMI is also known as customer service model in
[Service-YANG]. The YANG model discussed in this document is used to [RFC8309]. The YANG model discussed in this document is used to
operate customer-driven VNs during the VN computation, VN operate customer-driven VNs during the VN instantiation, VN
instantiation and its life-cycle management and operations. 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 The YANG model discussed in this document basically provides the
following: following:
o Characteristics of Access Points (APs) that describe customer's o Characteristics of Access Points (APs) that describe customer's
end point characteristics; end point characteristics;
o Characteristics of Virtual Network Access Points (VNAP) that o Characteristics of Virtual Network Access Points (VNAP) that
describe How an AP is partitioned for multiple VNs sharing the AP describe How an AP is partitioned for multiple VNs sharing the AP
and its reference to a Link Termination Point (LTP) of the and its reference to a Link Termination Point (LTP) of the
Provider Edge (PE) Node; Provider Edge (PE) Node;
o Characteristics of Virtual Networks (VNs) that describe the o Characteristics of Virtual Networks (VNs) that describe the
customer's VNs in terms of VN Members comprising a VN, multi- customer's VNs in terms of VN Members comprising a VN, multi-
source and/or multi-destination characteristics of VN Member, the source and/or multi-destination characteristics of VN Member, the
VN's reference to TE-topology's Abstract Node; VN's reference to TE-topology's Abstract Node;
The actual VN instantiation is performed with Connectivity Matrices The actual VN instantiation and computation is performed with
sub-module of TE-Topology Model [TE-Topo] which interacts with the Connectivity Matrices sub-module of TE-Topology Model [TE-Topo]
VN YANG module presented in this draft. Once TE-topology Model is which provides TE network topology abstraction and management
used in triggering VN instantiation over the networks, TE-tunnel operation. Once TE-topology Model is used in triggering VN
[TE-tunnel] Model will inevitably interact with TE-Topology model instantiation over the networks, TE-tunnel [TE-tunnel] Model will
for setting up actual tunnels and LSPs under the tunnels. inevitably interact with TE-Topology model for setting up actual
tunnels and LSPs under the tunnels.
The ACTN VN operational state is included in the same tree as the The ACTN VN operational state is included in the same tree as the
configuration consistent with Network Management Datastore configuration consistent with Network Management Datastore
Architecture (NMDA) [NMDA]. The origin of the data is indicated as Architecture (NMDA) [NMDA]. The origin of the data is indicated as
per the origin metadata annotation. per the origin metadata annotation.
1.1. Terminology 1.1. Terminology
Refer to [ACTN-Frame] and [RFC7926] for the key terms used in this Refer to [ACTN-Frame], [RFC7926], and [RFC8309] for the key terms
document. used in this document.
2. ACTN CMI context 2. ACTN CMI context
The model presented in this document has the following ACTN context. The model presented in this document has the following ACTN context.
+-------+ +-------+
| CNC | | CNC |
+-------+ +-------+
| |
| VN YANG + TE-topology YANG | VN YANG + TE-topology YANG
skipping to change at page 4, line 35 skipping to change at page 4, line 40
Both ACTN VN YANG and TE-topology models are used over the CMI to Both ACTN VN YANG and TE-topology models are used over the CMI to
establish a VN over TE networks. establish a VN over TE networks.
2.1. Type 1 VN 2.1. Type 1 VN
As defined in [ACTN-FW], a Virtual Network is a customer view of the 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 TE network. To recapitulate VN types from [ACTN-FW], Type 1 VN is
defined as follows: defined as follows:
The VN can be seen as a set of edge-to-edge links (a Type 1 VN). The VN can be seen as a set of edge-to-edge abstract links (a Type 1
Each link is referred to as a VN member and is formed as an end-to- VN). Each abstract link is referred to as a VN member and is formed
end tunnel across the underlying networks. Such tunnels may be as an end-to-end tunnel across the underlying networks. Such tunnels
constructed by recursive slicing or abstraction of paths in the may be constructed by recursive slicing or abstraction of paths in
underlying networks and can encompass edge points of the customer's the underlying networks and can encompass edge points of the
network, access links, intra-domain paths, and inter-domain links. 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: If we were to create a VN where we have four VN-members as follows:
VN-Member 1 L1-L4 VN-Member 1 L1-L4
VN-Member 2 L1-L7 VN-Member 2 L1-L7
VN-Member 3 L2-L4 VN-Member 3 L2-L4
VN-Member 4 L3-L8 VN-Member 4 L3-L8
Where L1, L2, L3, L4, L7 and L8 correspond to a Customer Where L1, L2, L3, L4, L7 and L8 correspond to a Customer
End-Point, respectively. End-Point, respectively.
skipping to change at page 7, line 18 skipping to change at page 7, line 32
+---------------+ +---------------+
L1 ------| |------ L4 L1 ------| |------ L4
L2 ------| AN 1 |------ L7 L2 ------| AN 1 |------ L7
L3 ------| |------ L8 L3 ------| |------ L8
+---------------+ +---------------+
If this VN is Type 1, the following diagram shows the message flow 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- between CNC and MDSC to instantiate this VN using ACTN VN and TE-
Topology Model. Topology Model.
+--------+ +--------+ +--------+ +--------+
| CNC | | MDSC | | CNC | | MDSC |
+--------+ +--------+ +--------+ +--------+
| | | |
| | | |
CNC POST TE-topo | POST /nw:networks/nw:network/ | CNC POST TE-topo | POST /nw:networks/nw:network/ |
model(with Conn. | nw:node/te-node-id/tet:connectivity- | model(with Conn. | nw:node/te-node-id/tet:connectivity- |
Matrix on one | matrices/tet:connectivity-matrix | Matrix on one | matrices/tet:connectivity-matrix |
Abstract node |---------------------------------------->| Abstract node |---------------------------------------->|
| HTTP 200 | | HTTP 200 |
|<----------------------------------------| |<----------------------------------------|
skipping to change at page 52, line 5 skipping to change at page 51, line 45
Explained", draft-wu-opsawg-service-model-explained, Explained", draft-wu-opsawg-service-model-explained,
work in progress. work in progress.
[ACTN-PM] Y. Lee, et al., "YANG models for ACTN TE Performance [ACTN-PM] Y. Lee, et al., "YANG models for ACTN TE Performance
Monitoring Telemetry and Network Autonomics", draft-lee- Monitoring Telemetry and Network Autonomics", draft-lee-
teas-actn-pm-telemetry-autonomics, work in progress. teas-actn-pm-telemetry-autonomics, work in progress.
[OIF-VTNS] Virtual Transport Network Services 1.0 Specification, IA [OIF-VTNS] Virtual Transport Network Services 1.0 Specification, IA
OIF-VTNS-1.0, April 2017. 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.
[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 12. Contributors
Contributor's Addresses Contributor's Addresses
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
Email: zhenghaomian@huawei.com Email: zhenghaomian@huawei.com
Xian Zhang Xian Zhang
Huawei Technologies Huawei Technologies
Email: zhang.xian@huawei.com Email: zhang.xian@huawei.com
Sergio Belotti Sergio Belotti
Nokia Nokia
Email: sergio.belotti@nokia.com Email: sergio.belotti@nokia.com
Qin Wu
Huawei Technologies
Email: bill.wu@huawei.com
Takuya Miyasaka Takuya Miyasaka
KDDI KDDI
Email: ta-miyasaka@kddi.com Email: ta-miyasaka@kddi.com
Peter Park
KT
Email: peter.park@kt.com
Authors' Addresses Authors' Addresses
Young Lee (ed.) Young Lee (ed.)
Huawei Technologies Huawei Technologies
Email: leeyoung@huawei.com Email: leeyoung@huawei.com
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Torshamnsgatan,48 Torshamnsgatan,48
Stockholm, Sweden Stockholm, Sweden
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
Igor Bryskin Igor Bryskin
Huawei Huawei
Email: Igor.Bryskin@huawei.com Email: Igor.Bryskin@huawei.com
skipping to change at line 2328 skipping to change at page 53, line 19
Stockholm, Sweden Stockholm, Sweden
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
Igor Bryskin Igor Bryskin
Huawei Huawei
Email: Igor.Bryskin@huawei.com Email: Igor.Bryskin@huawei.com
Bin Yeong Yoon Bin Yeong Yoon
ETRI ETRI
Email: byyun@etri.re.kr Email: byyun@etri.re.kr
Qin Wu
Huawei Technologies
Email: bill.wu@huawei.com
Peter Park
KT
Email: peter.park@kt.com
 End of changes. 21 change blocks. 
39 lines changed or deleted 58 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/