draft-ietf-teas-actn-yang-04.txt   draft-ietf-teas-actn-yang-05.txt 
TEAS WG Young Lee TEAS WG Young Lee
Internet Draft Futurewei Internet Draft Samsung
Intended status: Informational Haomian Zheng Intended status: Informational Haomian Zheng
Expires: February 16, 2020 Huawei Expires: August 19, 2020 Huawei Technologies
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Bin Yeong Yoon Bin Yeong Yoon
ETRI ETRI
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Jong Yoon Shin Jong Yoon Shin
SKT SKT
Sergio Belotti Sergio Belotti
Nokia Nokia
August 16, 2019 February 19, 2020
Applicability of YANG models for Abstraction and Control of Traffic Applicability of YANG models for Abstraction and Control of Traffic
Engineered Networks Engineered Networks
draft-ietf-teas-actn-yang-04 draft-ietf-teas-actn-yang-05
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
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 February 16, 2020. This Internet-Draft will expire on August 19, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 43 skipping to change at page 2, line 43
model that have already been defined, and discusses the model that have already been defined, and discusses the
applicability of specific data models that are under development. It applicability of specific data models that are under development. It
also highlights where new data models may need to be developed. also highlights where new data models may need to be developed.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
1.1. Conventions Used in This Document ...................... 3 1.1. Conventions Used in This Document ...................... 3
2. Abstraction and Control of TE Networks (ACTN) Architecture... 4 2. Abstraction and Control of TE Networks (ACTN) Architecture... 4
3. Service Models .............................................. 5 3. Service Models .............................................. 5
4. Service Model Mapping to ACTN .............................. 7 4. Service Model Mapping to ACTN ............................... 7
4.1. Customer Service Models in the ACTN Architecture (CMI).. 7 4.1. Customer Service Models in the ACTN Architecture (CMI).. 7
4.2. Service Delivery Models in ACTN Architecture ........... 8 4.2. Service Delivery Models in ACTN Architecture ........... 8
4.3. Network Configuration Models in ACTN Architecture (MPI).. 8 4.3. Network Configuration Models in ACTN Architecture (MPI). 8
4.4. Device Models in ACTN Architecture (SBI) ............... 9 4.4. Device Models in ACTN Architecture (SBI) ............... 9
5. Examples of Using Different Types of YANG Models ............ 10 5. Examples of Using Different Types of YANG Models ............ 10
5.1. Topology Collection ................................... 10 5.1. Topology Collection ................................... 10
5.2. Connectivity over Two Nodes ............................ 10 5.2. Connectivity over Two Nodes ........................... 10
5.3. VN example ............................................. 11 5.3. VN example ............................................ 11
5.4. Data Center-Interconnection Example .................... 12 5.4. Data Center-Interconnection Example ................... 12
5.4.1. CMI (CNC-MDSC Interface) .......................... 14 5.4.1. CMI (CNC-MDSC Interface) ......................... 14
5.4.2. MPI (MDSC-PNC Interface) .......................... 14 5.4.2. MPI (MDSC-PNC Interface) ......................... 14
5.4.3. SBI (Southbound interface between PNC and devices). 14 5.4.3. SBI (Southbound interface between PNC and devices). 14
6. Security ................................................... 15 6. Security ................................................... 15
7. IANA Considerations ........................................ 15 7. IANA Considerations ........................................ 15
8. Acknowledgements ........................................... 15 8. Acknowledgements ........................................... 15
9. References ................................................. 15 9. References ................................................. 15
9.1. Informative References ................................ 15 9.1. Informative References ................................ 15
10. Contributors .............................................. 18 10. Contributors .............................................. 18
Authors' Addresses ............................................ 18 Authors' Addresses ............................................ 18
1. Introduction 1. Introduction
skipping to change at page 4, line 31 skipping to change at page 4, line 31
\ | / \ | /
Business \ | / Business \ | /
Boundary =====\======================|=======================/====== Boundary =====\======================|=======================/======
Between \ | CMI / Between \ | CMI /
Customer & ----------- | -------------- Customer & ----------- | --------------
Network Provider \ | / Network Provider \ | /
+---------------------+ +---------------------+
| MDSC | | MDSC |
+---------------------+ +---------------------+
/ | \ / | \
---------- |MPI -------------- ---------- |MPI -------------
/ | \ / | \
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| PNC | | PNC | | PNC | | PNC | | PNC | | PNC |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| GMPLS / | / \ | GMPLS / | / \
| trigger / |SBI SBI / \ | trigger / |SBI SBI / \
-------- ----- | / \ -------- ----- | / \
( ) ( ) | / \ ( ) ( ) | / \
- - ( Phys. ) | / ----- - - ( Phys. ) | / -----
( GMPLS ) ( Net ) | / ( ) ( GMPLS ) ( Net ) | / ( )
( Physical ) ---- | / ( Phys. ) ( Physical ) ---- | / ( Phys. )
( Network ) ----- ----- ( Net ) ( Network ) ----- ----- ( Net )
- - ( ) ( ) ----- - - ( ) ( ) -----
( ) ( Phys. ) ( Phys. ) ( ) ( Phys. ) ( Phys. )
skipping to change at page 7, line 39 skipping to change at page 7, line 39
Among the key functions of Customer Service Models on the CMI is the Among the key functions of Customer Service Models on the CMI is the
service request. A request will include specific service properties, service request. A request will include specific service properties,
including: service type and its characteristics, bandwidth, including: service type and its characteristics, bandwidth,
constraint information, and end-point characteristics. constraint information, and end-point characteristics.
The following table provides a list of functions needed to build the The following table provides a list of functions needed to build the
CMI. They are mapped with Customer Service Models. CMI. They are mapped with Customer Service Models.
Function Yang Model Function Yang Model
----------------------------------------------------------- -----------------------------------------------------------
VN Service Request [ACTN-VN-YANG] VN Service Request [ACTN-VN-YANG]
VN Computation Request [ACTN-VN-YANG]* VN Computation Request [ACTN-VN-YANG]*
TE & Service Mapping [TE-Service-Mapping]** TE & Service Mapping [TE-Service-Mapping]**
VN Performance Monitoring Telemetry [ACTN-PM-Telemetry]*** VN Performance Monitoring Telemetry [ACTN-PM-Telemetry]***
Topology Abstraction [TE-topology]**** Topology Abstraction [TE-topology]****
Layer 1 Connectivity Service Model [L1CSM] Layer 1 Connectivity Service Model [L1CSM]
Layer 2 VPN Service Model [RFC8466] Layer 2 VPN Service Model [RFC8466]
Layer 3 VPN Service Model [RFC8299] Layer 3 VPN Service Model [RFC8299]
*VN computation request in the CMI context means network path *VN computation request in the CMI context means network path
computation request based on customer service connectivity request computation request based on customer service connectivity request
constraints prior to the instantiation of a VN creation. constraints prior to the instantiation of a VN creation.
**[TE-Service-Mapping] provides a mapping and cross-references **[TE-Service-Mapping] provides a mapping and cross-references
between service models (e.g., L3SM, L2SM, L1CSM) and TE model via between service models (e.g., L3SM, L2SM, L1CSM) and TE model via
skipping to change at page 9, line 14 skipping to change at page 9, line 14
The Network Configuration Model captures the parameters which are The Network Configuration Model captures the parameters which are
network wide information. network wide information.
The following table provides a list of functions needed to build the The following table provides a list of functions needed to build the
MPI. They are mapped with Network Configuration Yang Models. Note MPI. They are mapped with Network Configuration Yang Models. Note
that various Yang models are work in progress. that various Yang models are work in progress.
Function Yang Model Function Yang Model
-------------------------------------------------------- --------------------------------------------------------
Configuration Scheduling [Schedule] Configuration Scheduling [Schedule]
Path computation [PATH_COMPUTATION-API] Path computation [PATH_COMPUTATION-API]
Tunnel/LSP Provisioning [TE-tunnel] Tunnel/LSP Provisioning [TE-tunnel]
Topology Abstraction [TE-topology] Topology Abstraction [TE-topology]
Service Provisioning [Client-signal]&[TE-tunnel]* Service Provisioning [Client-signal]&[TE-tunnel]*
Client Topology Abstraction [Client-topo] Client Topology Abstraction [Client-topo]
OTN Topology Abstraction [OTN-topo] OTN Topology Abstraction [OTN-topo]
WSON Topology Abstraction [WSON-topo] WSON Topology Abstraction [WSON-topo]
Flexi-grid Topology Abstraction [Flexi-topo] Flexi-grid Topology Abstraction [Flexi-topo]
Microwave Topology Abstraction [MW-topo] Microwave Topology Abstraction [MW-topo]
Client Signal Description [Client-signal] Client Signal Description [Client-signal]
OTN Tunnel Model [OTN-Tunnel] OTN Tunnel Model [OTN-Tunnel]
WSON TE Tunnel Model [WSON-Tunnel] WSON TE Tunnel Model [WSON-Tunnel]
Flexi-grid Tunnel Model [Flexigrid-Tunnel] Flexi-grid Tunnel Model [Flexigrid-Tunnel]
* This function is a combination of tunnel set up and client signal * This function is a combination of tunnel set up and client signal
description. Usually a tunnel is setting up first to get prepared to description. Usually a tunnel is setting up first to get prepared to
carry a client signal, in order to do the service provisioning. Then carry a client signal, in order to do the service provisioning. Then
the client signal is adapted to the established tunnel. It is worth the client signal is adapted to the established tunnel. It is worth
noting that various tunnel models such as [OTN-Tunnel] and [WSON- noting that various tunnel models such as [OTN-Tunnel] and [WSON-
Tunnel] can be used together with the [TE-tunnel] model to construct Tunnel] can be used together with the [TE-tunnel] model to construct
technology-specific tunnels, and carry different types of client technology-specific tunnels, and carry different types of client
signals. More details can be found in [Client-signal]. signals. More details can be found in [Client-signal].
skipping to change at page 11, line 50 skipping to change at page 11, line 50
A CNC will request VN to the MDSC by specifying a list of VN A CNC will request VN to the MDSC by specifying a list of VN
members. Each VN member specifies either a single connectivity members. Each VN member specifies either a single connectivity
service, or a source with multiple potential destination points service, or a source with multiple potential destination points
in the case that the precise destination sites are to be in the case that the precise destination sites are to be
determined by MDSC. determined by MDSC.
o In the first case, the procedure is the same as the o In the first case, the procedure is the same as the
connectivity service, except that in this case, there is a connectivity service, except that in this case, there is a
list of connections requested. list of connections requested.
o In the second case, where the CNC requests the MDSC to o In the second case, where the CNC requests the MDSC to
select the right destination out of a list of candidates, select the right destination out of a list of candidates,
the MDSC needs to evaluate each candidate and then choose the MDSC needs to evaluate each candidate and then choose
the best one and reply with the chosen destination for a the best one and reply with the chosen destination for a
given VN member. After this is selected, the connectivity given VN member. After this is selected, the connectivity
request setup procedure is the same as in the connectivity request setup procedure is the same as in the connectivity
example in section 5.2. example in section 5.2.
After the VN is set up, a successful reply message is sent from MDSC After the VN is set up, a successful reply message is sent from MDSC
to CNC, indicating the VN is ready. This message can also be to CNC, indicating the VN is ready. This message can also be
achieved by using the model defined in [ACTN-VN-YANG]. achieved by using the model defined in [ACTN-VN-YANG].
skipping to change at page 13, line 11 skipping to change at page 13, line 11
use case. Figure 3 shows a use-case which shows service policy- use case. Figure 3 shows a use-case which shows service policy-
driven Data Center selection and is a reproduction of Figure A.1 driven Data Center selection and is a reproduction of Figure A.1
from [RFC8454]. from [RFC8454].
+----------------+ +----------------+
| CNC | | CNC |
| (Global DC | | (Global DC |
| Operation | | Operation |
| Control) | | Control) |
+--------+-------+ +--------+-------+
| | VN Requirement/Policy: | | VN Requirement/Policy:
CMI: | |- Endpoint/DC location info CMI: | | - Endpoint/DC location info
Service model | |- Endpoint/DC dynamic Service model | | - Endpoint/DC dynamic
| | selection policy | | selection policy
| | (for VM migration, DR, LB) | | (for VM migration, DR, LB)
| v | v
+---------+---------+ +---------+---------+
| Multi-domain | Service policy-driven | Multi-domain | Service policy-driven
|Service Coordinator| dynamic DC selection |Service Coordinator| dynamic DC selection
MPI: +-----+---+---+-----+ MPI: +-----+---+---+-----+
Network Configuration | | | Network Configuration | | |
Model | | | Model | | |
+----------------+ | +---------------+ +----------------+ | +---------------+
| | | | | |
+-----+-----+ +------+-----+ +------+-----+ +-----+-----+ +------+-----+ +------+-----+
skipping to change at page 18, line 34 skipping to change at page 18, line 30
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Xian Zhang Xian Zhang
Huawei Technologies Huawei Technologies
Email: zhang.xian@huawei.com Email: zhang.xian@huawei.com
Authors' Addresses Authors' Addresses
Young Lee Young Lee
Futurewei Technologies Samsung
5700 Tennyson Parkway, Suite 600 Korea
Plano, TX 75024, USA
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
Email: zhenghaomian@huawei.com Email: zhenghaomian@huawei.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
 End of changes. 18 change blocks. 
40 lines changed or deleted 39 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/