draft-ietf-teas-actn-framework-09.txt   draft-ietf-teas-actn-framework-10.txt 
TEAS Working Group Daniele Ceccarelli (Ed) TEAS Working Group Daniele Ceccarelli (Ed)
Internet Draft Ericsson Internet Draft Ericsson
Intended status: Informational Young Lee (Ed) Intended status: Informational Young Lee (Ed)
Expires: April 16, 2018 Huawei Expires: April 18, 2018 Huawei
October 16, 2017 October 18, 2017
Framework for Abstraction and Control of Traffic Engineered Networks Framework for Abstraction and Control of Traffic Engineered Networks
draft-ietf-teas-actn-framework-09 draft-ietf-teas-actn-framework-10
Abstract Abstract
Traffic Engineered networks have a variety of mechanisms to Traffic Engineered networks have a variety of mechanisms to
facilitate the separation of the data plane and control plane. They facilitate the separation of the data plane and control plane. They
also have a range of management and provisioning protocols to also have a range of management and provisioning protocols to
configure and activate network resources. These mechanisms configure and activate network resources. These mechanisms
represent key technologies for enabling flexible and dynamic represent key technologies for enabling flexible and dynamic
networking. networking.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 April 16, 2018. This Internet-Draft will expire on April 18, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 3, line 7 skipping to change at page 3, line 7
5.2. Abstraction Types........................................18 5.2. Abstraction Types........................................18
5.2.1. Native/White Topology...............................18 5.2.1. Native/White Topology...............................18
5.2.2. Black Topology......................................18 5.2.2. Black Topology......................................18
5.2.3. Grey Topology.......................................19 5.2.3. Grey Topology.......................................19
5.3. Methods of Building Grey Topologies......................20 5.3. Methods of Building Grey Topologies......................20
5.3.1. Automatic Generation of Abstract Topology by 5.3.1. Automatic Generation of Abstract Topology by
Configuration..............................................21 Configuration..............................................21
5.3.2. On-demand Generation of Supplementary Topology via Path 5.3.2. On-demand Generation of Supplementary Topology via Path
Compute Request/Reply......................................21 Compute Request/Reply......................................21
5.4. Hierarchical Topology Abstraction Example................22 5.4. Hierarchical Topology Abstraction Example................22
6. Access Points and Virtual Network Access Points...............23 5.5. VN Recursion with Network Layers.........................23
6.1. Dual-Homing Scenario.....................................25 6. Access Points and Virtual Network Access Points...............25
7. Advanced ACTN Application: Multi-Destination Service..........26 6.1. Dual-Homing Scenario.....................................27
7.1. Pre-Planned End Point Migration..........................27 7. Advanced ACTN Application: Multi-Destination Service..........28
7.2. On the Fly End-Point Migration...........................28 7.1. Pre-Planned End Point Migration..........................29
8. Manageability Considerations..................................28 7.2. On the Fly End-Point Migration...........................30
8.1. Policy...................................................29 8. Manageability Considerations..................................30
8.2. Policy Applied to the Customer Network Controller........30 8.1. Policy...................................................30
8.3. Policy Applied to the Multi Domain Service Coordinator...30 8.2. Policy Applied to the Customer Network Controller........31
8.4. Policy Applied to the Provisioning Network Controller....31 8.3. Policy Applied to the Multi Domain Service Coordinator...31
9. Security Considerations.......................................31 8.4. Policy Applied to the Provisioning Network Controller....32
9.1. CNC-MDSC Interface (CMI).................................32 9. Security Considerations.......................................32
9.2. MDSC-PNC Interface (MPI).................................32 9.1. CNC-MDSC Interface (CMI).................................33
10. IANA Considerations..........................................32 9.2. MDSC-PNC Interface (MPI).................................34
11. References...................................................33 10. IANA Considerations..........................................34
11.1. Informative References..................................33 11. References...................................................34
12. Contributors.................................................34 11.1. Informative References..................................34
Authors' Addresses...............................................35 12. Contributors.................................................35
Authors' Addresses...............................................36
APPENDIX A - Example of MDSC and PNC Functions Integrated in A APPENDIX A - Example of MDSC and PNC Functions Integrated in A
Service/Network Orchestrator.....................................35 Service/Network Orchestrator.....................................37
1. Introduction 1. Introduction
The term "Traffic Engineered network" refers to a network that uses The term "Traffic Engineered network" refers to a network that uses
any connection-oriented technology under the control of a any connection-oriented technology under the control of a
distributed or centralized control plane to support dynamic distributed or centralized control plane to support dynamic
provisioning of end-to-end connectivity. Traffic Engineered (TE) provisioning of end-to-end connectivity. Traffic Engineered (TE)
networks have a variety of mechanisms to facilitate separation of networks have a variety of mechanisms to facilitate separation of
data plane and control plane including distributed signaling for data plane and control plane including distributed signaling for
path setup and protection, centralized path computation for planning path setup and protection, centralized path computation for planning
skipping to change at page 23, line 46 skipping to change at page 23, line 46
and links across and outside the domain. The abstract topology and links across and outside the domain. The abstract topology
MDSC-L1 that operates is a combination of the two topologies from MDSC-L1 that operates is a combination of the two topologies from
PNC1 and PNC2. Likewise, the abstract topology that MDSC-L2 PNC1 and PNC2. Likewise, the abstract topology that MDSC-L2
operates is shown in Figure 9. Both MDSC-L1 and MDSC-L2 provide a operates is shown in Figure 9. Both MDSC-L1 and MDSC-L2 provide a
black topology abstraction to MSDC-H in which each PNC domain is black topology abstraction to MSDC-H in which each PNC domain is
presented as a single virtual node. MDSC-H combines these two presented as a single virtual node. MDSC-H combines these two
topologies to create the abstraction topology on which it operates. topologies to create the abstraction topology on which it operates.
MDSC-H sees the whole four domain networks as four virtual nodes MDSC-H sees the whole four domain networks as four virtual nodes
connected via virtual links. connected via virtual links.
5.5. VN Recursion with Network Layers
In some cases the VN supplied to a customer may be built using
resources from different technology layers operated by different
providers. For example, one provider may run a packet TE network
and use optical connectivity provided by another provider.
As shown in Figure 10, a customer asks for end-to-end connectivity
between CE A and CE B, a virtual network. The customer's CNC makes a
request to Provider 1's MDSC. The MDSC works out which network
resources need to be configured and sends instructions to the
appropriate PNCs. However, the link between Q and R is a virtual
link supplied by Provider 2: Provider 1 is a customer of Provider 2.
To support this, Provider 1 has a CNC that communicates to Provider
2's MDSC. Note that Provider 1's CNC in Figure 10 is a functional
component that does not dictate implementation: it may be embedded
in a PNC.
Virtual CE A o===============================o CE B
Network
----- CNC wants to create a VN
Customer | CNC | between CE A and CE B
-----
:
***********************************************
:
Provider 1 ---------------------------
| MDSC |
---------------------------
: : :
: : :
----- ------------- -----
| PNC | | PNC | | PNC |
----- ------------- -----
: : : : :
Higher v v : v v
Layer CE A o---P-----Q===========R-----S---o CE B
Network | : |
| : |
| ----- |
| | CNC | |
| ----- |
| : |
***********************************************
| : |
Provider 2 | ------ |
| | MSDC | |
| ------ |
| : |
| ------- |
| | PNC | |
| ------- |
\ : : : /
Lower \v v v/
Layer X--Y--Z
Network
Figure 10: VN Recursion with Network Layers
6. Access Points and Virtual Network Access Points 6. Access Points and Virtual Network Access Points
In order to map identification of connections between the customer's In order to map identification of connections between the customer's
sites and the TE networks and to scope the connectivity requested in sites and the TE networks and to scope the connectivity requested in
the VNS, the CNC and the MDSC refer to the connections using the the VNS, the CNC and the MDSC refer to the connections using the
Access Point (AP) construct as shown in Figure 10. Access Point (AP) construct as shown in Figure 11.
------------- -------------
( ) ( )
- - - -
+---+ X ( ) Z +---+ +---+ X ( ) Z +---+
|CE1|---+----( )---+---|CE2| |CE1|---+----( )---+---|CE2|
+---+ | ( ) | +---+ +---+ | ( ) | +---+
AP1 - - AP2 AP1 - - AP2
( ) ( )
------------- -------------
Figure 10: Customer View of APs Figure 11: Customer View of APs
Let's take as an example a scenario shown in Figure 10. CE1 is Let's take as an example a scenario shown in Figure 11. CE1 is
connected to the network via a 10Gb link and CE2 via a 40Gb link. connected to the network via a 10Gb link and CE2 via a 40Gb link.
Before the creation of any VN between AP1 and AP2 the customer view Before the creation of any VN between AP1 and AP2 the customer view
can be summarized as shown in Table 1. can be summarized as shown in Table 1.
+----------+------------------------+ +----------+------------------------+
|End Point | Access Link Bandwidth | |End Point | Access Link Bandwidth |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
|AP id| CE,port | MaxResBw | AvailableBw | |AP id| CE,port | MaxResBw | AvailableBw |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
| AP1 |CE1,portX | 10Gb | 10Gb | | AP1 |CE1,portX | 10Gb | 10Gb |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
| AP2 |CE2,portZ | 40Gb | 40Gb | | AP2 |CE2,portZ | 40Gb | 40Gb |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
Table 1: AP - Customer View Table 1: AP - Customer View
On the other hand, what the provider sees is shown in Figure 11. On the other hand, what the provider sees is shown in Figure 12.
------- ------- ------- -------
( ) ( ) ( ) ( )
- - - - - - - -
W (+---+ ) ( +---+) Y W (+---+ ) ( +---+) Y
-+---( |PE1| Dom.X )---( Dom.Y |PE2| )---+- -+---( |PE1| Dom.X )---( Dom.Y |PE2| )---+-
| (+---+ ) ( +---+) | | (+---+ ) ( +---+) |
AP1 - - - - AP2 AP1 - - - - AP2
( ) ( ) ( ) ( )
------- ------- ------- -------
Figure 11: Provider view of the AP Figure 12: Provider view of the AP
Which results in a summarization as shown in Table 2. Which results in a summarization as shown in Table 2.
+----------+------------------------+ +----------+------------------------+
|End Point | Access Link Bandwidth | |End Point | Access Link Bandwidth |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
|AP id| PE,port | MaxResBw | AvailableBw | |AP id| PE,port | MaxResBw | AvailableBw |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
| AP1 |PE1,portW | 10Gb | 10Gb | | AP1 |PE1,portW | 10Gb | 10Gb |
+-----+----------+----------+-------------+ +-----+----------+----------+-------------+
skipping to change at page 27, line 19 skipping to change at page 28, line 42
source and destination APs is decided by a CNC (or an entity outside source and destination APs is decided by a CNC (or an entity outside
of ACTN) based on certain factors which are outside the scope of of ACTN) based on certain factors which are outside the scope of
ACTN. ACTN.
Based on the AP selection as determined and returned by the network Based on the AP selection as determined and returned by the network
(MDSC), the CNC (or an entity outside of ACTN) should further take (MDSC), the CNC (or an entity outside of ACTN) should further take
care of any subsequent actions such as orchestration or service care of any subsequent actions such as orchestration or service
setup requirements. These further actions are outside the scope of setup requirements. These further actions are outside the scope of
ACTN. ACTN.
Consider a case as shown in Figure 13, where three data centers are Consider a case as shown in Figure 14, where three data centers are
available, but the customer requires the data center selection to be available, but the customer requires the data center selection to be
based on the network status and the connectivity service setup based on the network status and the connectivity service setup
between the AP1 (CE1) and one of the destination APs (AP2 (DC-A), between the AP1 (CE1) and one of the destination APs (AP2 (DC-A),
AP3 (DC-B), and AP4 (DC-C)). The MDSC (in coordination with PNCs) AP3 (DC-B), and AP4 (DC-C)). The MDSC (in coordination with PNCs)
would select the best destination AP based on the constraints, would select the best destination AP based on the constraints,
optimization criteria, policies, etc., and setup the connectivity optimization criteria, policies, etc., and setup the connectivity
service (virtual network). service (virtual network).
------- ------- ------- -------
( ) ( ) ( ) ( )
skipping to change at page 27, line 44 skipping to change at page 29, line 21
AP1 - - - - AP2 AP1 - - - - AP2
( ) ( ) ( ) ( )
---+--- ---+--- ---+--- ---+---
| | | |
AP3-+ AP4-+ AP3-+ AP4-+
| | | |
+----+ +----+ +----+ +----+
|DC-B| |DC-C| |DC-B| |DC-C|
+----+ +----+ +----+ +----+
Figure 13: End-Point Selection Based on Network Status Figure 14: End-Point Selection Based on Network Status
7.1. Pre-Planned End Point Migration 7.1. Pre-Planned End Point Migration
Furthermore, in case of Data Center selection, customer could Furthermore, in case of Data Center selection, customer could
request for a backup DC to be selected, such that in case of request for a backup DC to be selected, such that in case of
failure, another DC site could provide hot stand-by protection. As failure, another DC site could provide hot stand-by protection. As
shown in Figure 14 DC-C is selected as a backup for DC-A. Thus, the shown in Figure 15 DC-C is selected as a backup for DC-A. Thus, the
VN should be setup by the MDSC to include primary connectivity VN should be setup by the MDSC to include primary connectivity
between AP1 (CE1) and AP2 (DC-A) as well as protection connectivity between AP1 (CE1) and AP2 (DC-A) as well as protection connectivity
between AP1 (CE1) and AP4 (DC-C). between AP1 (CE1) and AP4 (DC-C).
------- ------- ------- -------
( ) ( ) ( ) ( )
- - - - - - - -
+---+ ( ) ( ) +----+ +---+ ( ) ( ) +----+
|CE1|---+----( Domain X )----( Domain Y )---+---|DC-A| |CE1|---+----( Domain X )----( Domain Y )---+---|DC-A|
+---+ | ( ) ( ) | +----+ +---+ | ( ) ( ) | +----+
AP1 - - - - AP2 | AP1 - - - - AP2 |
( ) ( ) | ( ) ( ) |
---+--- ---+--- | ---+--- ---+--- |
| | | | | |
AP3-+ AP4-+ HOT STANDBY AP3-+ AP4-+ HOT STANDBY
| | | | | |
+----+ +----+ | +----+ +----+ |
|DC-D| |DC-C|<------------- |DC-D| |DC-C|<-------------
+----+ +----+ +----+ +----+
Figure 14: Pre-planned End-Point Migration Figure 15: Pre-planned End-Point Migration
7.2. On the Fly End-Point Migration 7.2. On the Fly End-Point Migration
Compared to pre-planned end point migration, on the fly end point Compared to pre-planned end point migration, on the fly end point
selection is dynamic in that the migration is not pre-planned but selection is dynamic in that the migration is not pre-planned but
decided based on network condition. Under this scenario, the MDSC decided based on network condition. Under this scenario, the MDSC
would monitor the network (based on the VN SLA) and notify the CNC would monitor the network (based on the VN SLA) and notify the CNC
in case where some other destination AP would be a better choice in case where some other destination AP would be a better choice
based on the network parameters. The CNC should instruct the MDSC based on the network parameters. The CNC should instruct the MDSC
when it is suitable to update the VN with the new AP if it is when it is suitable to update the VN with the new AP if it is
 End of changes. 16 change blocks. 
32 lines changed or deleted 94 lines changed or added

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