draft-ietf-teas-actn-framework-00.txt   draft-ietf-teas-actn-framework-01.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: January 2017 Huawei Expires: January 2017 Huawei
July 6, 2016 October 25, 2016
Framework for Abstraction and Control of Traffic Engineered Networks Framework for Abstraction and Control of Traffic Engineered Networks
draft-ietf-teas-actn-framework-00 draft-ietf-teas-actn-framework-01
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 34 skipping to change at page 1, line 34
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 January 6, 2017. This Internet-Draft will expire on January 25, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 2, line 32 skipping to change at page 2, line 32
operator or the customer of the operator that actually owns operator or the customer of the operator that actually owns
the network resources. the network resources.
This draft provides a framework for Abstraction and Control of This draft provides a framework for Abstraction and Control of
Traffic Engineered Networks (ACTN). Traffic Engineered Networks (ACTN).
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Terminology...............................................5 1.1. Terminology...............................................5
2. Business Model of ACTN.........................................7 2. Business Model of ACTN.........................................8
2.1. Customers.................................................7 2.1. Customers.................................................8
2.2. Service Providers.........................................9 2.2. Service Providers........................................10
2.3. Network Providers........................................11 2.3. Network Providers........................................11
3. ACTN architecture.............................................11 3. ACTN architecture.............................................12
3.1. Customer Network Controller..............................14 3.1. Customer Network Controller..............................14
3.2. Multi Domain Service Coordinator.........................15 3.2. Multi Domain Service Coordinator.........................15
3.3. Physical Network Controller..............................16 3.3. Physical Network Controller..............................16
3.4. ACTN interfaces..........................................17 3.4. ACTN interfaces..........................................17
4. VN creation process...........................................19 4. VN creation process...........................................19
5. Access Points and Virtual Network Access Points...............20 5. Access Points and Virtual Network Access Points...............20
5.1. Dual homing scenario.....................................22 5.1. Dual homing scenario.....................................22
6. End point selection & mobility................................23 6. End point selection & mobility................................23
6.1. End point selection & mobility...........................23 6.1. End point selection & mobility...........................23
6.2. Preplanned end point migration...........................24 6.2. Preplanned end point migration...........................24
skipping to change at page 6, line 18 skipping to change at page 6, line 18
- - __ - - - - __ - -
( PNC )+---+( PNC ) ( PNC )+---+( PNC )
( Domain X ) ( Domain Y ) ( Domain X ) ( Domain Y )
( )+---+( ) ( )+---+( )
- - border- - - - border- -
( ) node ( ) ( ) node ( )
------- ------- ------- -------
Figure 1 : PNC domain borders Figure 1 : PNC domain borders
- Virtual Network: A Virtual Network (VN) is a customer view of the - A Virtual Network is a client view (typically a network slice)
transport network. It is composed by a set of physical of the transport network. It is presented by the provider as a
resources sliced in the provider network and presented to the set of physical and/or abstracted resources. Depending on the
customer as a set of abstract resources i.e. virtual nodes and agreement between client and provider various VN operations and
virtual links. Depending on the agreement between customer and VN views are possible.
provider a VN can be just represented by:
o How the end points can be connected with given SLA (1) VN Creation - VN could be pre-configured and created via
attributes(e.g., re satisfying the customer's objectives) static negotiation between customer and provider. In other
o A pre-configured set of physical resources cases, VN could also be created dynamically based on the
o Or as outcome of a dynamic request from customer. request from the customer with given SLA attributes which
satisfy the customer's objectives.
In the first case the VN can be seen at customer level as an (2) Dynamic Operations - VN could be further modified and
e2e connectivity that can be formed by recursive aggregation of deleted based on customer request to request changes in the
lower layers tunnels within the provider domain. network resources reserved for the customer. The customer can
When the VN is pre-configured, it is provided after a static further act upon the virtual network resources to perform E2E
negotiation between customer and provider while in the third tunnel management (set-up/release/modify). These changes will
case VN can be dynamically created, deleted, or modified in incur subsequent LSP management on the operator's level.
response to requests from the customer. This implies dynamic
changes of network resources reserved for the customer. (3) VN View - (a) VN can be seen as an (or set of) e2e
In the second and third case , once that customer has obtained tunnel(s) from a customer point of view where an e2e tunnel is
his VN, can act upon the virtual network resources to perform referred as a VN member. Each VN member (i.e., e2e tunnel) can
connection management (set-up/release/modify connections). then be formed by recursive aggregation of lower level paths at
a provider level. Such end to end tunnels may comprise of
customer end points, access links, intra domain paths and
inter-domain link. In this view VN is thus a list of VN
members. (b) VN can also be seen as a terms of topology
comprising of physical and abstracted nodes and links. The
nodes in this case include physical customer end points, border
nodes, and internal nodes as well as abstracted nodes.
Similarly the links includes physical access, inter-domain and
intra-domain links as well as abstracted links. The abstracted
nodes and links in this view can be pre-negotiated or created
dynamically.
- Abstraction is the process of applying policy to the available
TE information within a domain, to produce selective
information that represents the potential ability to connect
across the domain. Thus, abstraction does not necessarily
offer all possible connectivity options, but it presents a
general view of potential connectivity according to the
policies that determine how the domain's administrator wants to
allow the domain resources to be used. [RFC7926]
- Abstract Link: An abstract link is the representation of the
characteristics of a path between two nodes in a domain
produced by abstraction. The abstract link is advertised
outside that domain as a TE link for use in signaling in other
domains. Thus, an abstract link represents the potential to
connect between a pair of nodes. [RFC7926]
- Abstract Topology: Every lower controller in the provider - Abstract Topology: Every lower controller in the provider
network, when is representing its network topology to an higher network, when is representing its network topology to an higher
layer, it may want to hide details of the actual network layer, it may want to hide details of the actual network
topology. In such case, an abstract topology may be used for topology. In such case, an abstract topology may be used for
this purpose. Abstract topology enhances scalability for the this purpose. Abstract topology enhances scalability for the
MDSC to operate multi-domain networks MDSC to operate multi-domain networks
- Access link: A link between a customer node and a provider - Access link: A link between a customer node and a provider
node. node.
skipping to change at page 11, line 36 skipping to change at page 12, line 17
This section provides a high-level control and interface model of This section provides a high-level control and interface model of
ACTN. ACTN.
The ACTN architecture, while being aligned with the ONF SDN The ACTN architecture, while being aligned with the ONF SDN
architecture [ONF-ARCH], is presenting a 3-tiers reference model. It architecture [ONF-ARCH], is presenting a 3-tiers reference model. It
allows for hierarchy and recursiveness not only of SDN controllers allows for hierarchy and recursiveness not only of SDN controllers
but also of traditionally controlled domains. It defines three types but also of traditionally controlled domains. It defines three types
of controllers depending on the functionalities they implement. The of controllers depending on the functionalities they implement. The
main functionalities that are identified are: main functionalities that are identified are:
. Multi domain coordination function: With the definition of . Multi domain coordination function: This function oversees the
domain being "everything that is under the control of the same specific aspects of the different domains and builds a single
controller",it is needed to have a control entity that oversees abstracted end-to-end network topology in order to coordinate
the specific aspects of the different domains and to build a end-to-end path computation and path/service provisioning.
single abstracted end-to-end network topology in order to Domain sequence path calculation/determination is also a part
coordinate end-to-end path computation and path/service of this function.
provisioning.
. Virtualization/Abstraction function: To provide an abstracted . Virtualization/Abstraction function: This function provides an
view of the underlying network resources towards customer, abstracted view of the underlying network resources towards
being it the client or a higher level controller entity. It customer, being it the client or a higher level controller
includes computation of customer resource requests into virtual entity. It includes network path computation based on customer
network paths based on the global network-wide abstracted service connectivity request constraints, based on the global
topology and the creation of an abstracted view of network network-wide abstracted topology and the creation of an
slices allocated to each customer, according to customer- abstracted view of network slices allocated to each customer,
specific virtual network objective functions, and to the according to customer-specific network objective functions, and
customer traffic profile. to the customer traffic profile.
. Customer mapping function: In charge of mapping customer VN . Customer mapping/translation function: This function is to map
setup commands into network provisioning requests to the customer intent-like commands into network provisioning
Physical Network Controller (PNC) according to business OSS/NMS requests to the Physical Network Controller (PNC) according to
provisioned static or dynamic policy. Moreover it provides business OSS/NMS provisioned static or dynamic policy.
mapping and translation of customer virtual network slices into Specifically, it provides mapping and translation of customer's
physical network resources service request into a set of parameters that are specific to a
network type and technology such that network configuration
process is made possible.
. Virtual service coordination: Virtual service coordination . Virtual service coordination: This function translates customer
function in ACTN incorporates customer service-related service-related information into the virtual network service
knowledge into the virtual network operations in order to operations in order to seamlessly operate virtual networks
seamlessly operate virtual networks while meeting customer's while meeting customer's service requirements. In the context
service requirements. of ACTN, service/virtual service coordination includes a number
of service orchestration functions such as multi-destination
load balancing, guarantees of service quality, bandwidth and
throughput and notification for service fault and performance
degradation and so forth.
The virtual services that are coordinated under ACTN can be split The virtual services that are coordinated under ACTN can be split
into two categories: into two categories:
. Service-aware Connectivity Services: This category includes all . Service-aware Connectivity Services: This category includes all
the network service operations used to provide connectivity the network service operations used to provide connectivity
between customer end-points while meeting policies and service between customer end-points while meeting policies and service
related constraints. The data model for this category would related constraints. The data model for this category would
include topology entities such as virtual nodes, virtual links, include topology entities such as virtual nodes, virtual links,
adaptation and termination points and service-related entities adaptation and termination points and service-related entities
skipping to change at page 21, line 5 skipping to change at page 21, line 5
( ) ( )
------------- -------------
Figure 8 : APs definition customer view Figure 8 : APs definition customer view
Let's take as example a scenario in which CE1 is connected to the Let's take as example a scenario in which CE1 is connected to the
network via a 10Gb link and CE2 via a 40Gb link. Before the creation network via a 10Gb link and CE2 via a 40Gb link. Before the creation
of any VN between AP1 and AP2 the customer view can be summarized as of any VN between AP1 and AP2 the customer view can be summarized as
follows: follows:
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
|AP id| MaxResBw | AvailableBw | CE,port | |AP id| MaxResBw | AvailableBw | CE,port |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
| AP1 | 10Gb | 10Gb |CE1,portX | | AP1 | 10Gb | 10Gb |CE1,portX |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
| AP2 | 40Gb | 40Gb |CE2,portZ | | AP2 | 40Gb | 40Gb |CE2,portZ |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
Table 1: AP - customer view Table 1: AP - customer view
On the other side what the provider sees is: On the other side what the provider sees is:
------- ------- ------- -------
( ) ( ) ( ) ( )
- - - - - - - -
W (+---+ ) ( +---+) Y W (+---+ ) ( +---+) Y
-+---( |PE1| Dom.X )----( Dom.Y |PE2| )---+- -+---( |PE1| Dom.X )----( Dom.Y |PE2| )---+-
| (+---+ ) ( +---+) | | (+---+ ) ( +---+) |
AP1 - - - - AP2 AP1 - - - - AP2
( ) ( ) ( ) ( )
------- ------- ------- -------
Figure 9 : Provider view of the AP Figure 9 : Provider view of the AP
Which in the example above ends up in a summarization as follows: Which in the example above ends up in a summarization as follows:
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
|AP id| MaxResBw | AvailableBw | PE,port | |AP id| MaxResBw | AvailableBw | PE,port |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
| AP1 | 10Gb | 10Gb |PE1,portW | | AP1 | 10Gb | 10Gb |PE1,portW |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
| AP2 | 40Gb | 40Gb |PE2,portY | | AP2 | 40Gb | 40Gb |PE2,portY |
+-----+----------+-------------+----------+ +-----+----------+-------------+----------+
Table 2: AP - provider view Table 2: AP - provider view
The second entity that needs to be defined is a structure within the The second entity that needs to be defined is a structure within the
AP that is linked to a VN and that is used to allow for different VN AP that is linked to a VN and that is used to allow for different VN
to be provided starting from the same AP. It also allows reserving to be provided starting from the same AP. It also allows reserving
the bandwidth for the VN on the access link. Such entity is called the bandwidth for the VN on the access link. Such entity is called
Virtual Network Access Point. For each virtual network is defined on Virtual Network Access Point. For each virtual network is defined on
an AP, a different VNAP is created. an AP, a different VNAP is created.
In the simple scenario depicted above we suppose to create two In the simple scenario depicted above we suppose to create two
virtual networks. The first one has with VN identifier 9 between AP1 virtual networks. The first one has with VN identifier 9 between AP1
and AP2 with and bandwidth of 1Gbps, while the second one with VN id and AP2 with and bandwidth of 1Gbps, while the second one with VN id
5, again between AP1 and AP2 and bandwidth 2Gbps. 5, again between AP1 and AP2 and bandwidth 2Gbps.
The customer view would evolve as follows: The customer view would evolve as follows:
+---------+----------+-------------+----------+ +---------+----------+-------------+----------+
|AP/VNAPid| MaxResBw | AvailableBw | PE,port | |AP/VNAPid| MaxResBw | AvailableBw | PE,port |
+---------+----------+-------------+----------+ +---------+----------+-------------+----------+
|AP1 | 10Gbps | 7Gbps |PE1,portW | |AP1 | 10Gbps | 7Gbps |PE1,portW |
| -VNAP1.9| 1Gbps | N.A. | | | -VNAP1.9| 1Gbps | N.A. | |
| -VNAP1.5| 2Gbps | N.A | | | -VNAP1.5| 2Gbps | N.A | |
+---------+----------+-------------+----------+ +---------+----------+-------------+----------+
|AP2 | 40Gb | 37Gb |PE2,portY | |AP2 | 40Gb | 37Gb |PE2,portY |
| -VNAP2.9| 1Gbps | N.A. | | | -VNAP2.9| 1Gbps | N.A. | |
| -VNAP2.5| 2Gbps | N.A | | | -VNAP2.5| 2Gbps | N.A | |
+---------+----------+-------------+----------+ +---------+----------+-------------+----------+
Table 3: AP and VNAP - provider view after VN creation Table 3: AP and VNAP - provider view after VN creation
5.1. Dual homing scenario 5.1. Dual homing scenario
Often there is a dual homing relationship between a CE and a pair of Often there is a dual homing relationship between a CE and a pair of
PE. This case needs to be supported also by the definition of VN, AP PE. This case needs to be supported also by the definition of VN, AP
and VNAP. Suppose to have CE1 connected to two different PE in the and VNAP. Suppose to have CE1 connected to two different PE in the
operator domain via AP1 and AP2 and the customer needing 5Gbps of operator domain via AP1 and AP2 and the customer needing 5Gbps of
bandwidth between CE1 and CE2. bandwidth between CE1 and CE2.
AP1 -------------- AP3 AP1 -------------- AP3
-------(PE1) (PE3) ------- -------(PE1) (PE3) -------
W / - - \X W / - - \X
+---+ / ( ) \ +---+ +---+ / ( ) \ +---+
|CE1| ( ) |CE2| |CE1| ( ) |CE2|
+---+ \ ( ) / +---+ +---+ \ ( ) / +---+
Y \ - - /Z Y \ - - /Z
-------(PE2) (PE4) ------- -------(PE2) (PE4) -------
AP2 -------------- AP4 AP2 -------------- AP4
Figure 10 : Dual homing scenario Figure 10 : Dual homing scenario
In this case the customer will request for a VN between AP1, AP2 and In this case the customer will request for a VN between AP1, AP2 and
AP3 specifying a dual homing relationship between AP1 and AP2. As a AP3 specifying a dual homing relationship between AP1 and AP2. As a
consequence no traffic will be flowing between AP1 and AP2. The dual consequence no traffic will be flowing between AP1 and AP2. The dual
homing relationship would then be mapped against the VNAPs (since homing relationship would then be mapped against the VNAPs (since
other independent VNs might have AP1 and AP2 as end points). other independent VNs might have AP1 and AP2 as end points).
The customer view would be as follows: The customer view would be as follows:
+---------+----------+-------------+----------+-----------+ +---------+----------+-------------+----------+-----------+
|AP/VNAPid| MaxResBw | AvailableBw | CE,port |Dual Homing| |AP/VNAPid| MaxResBw | AvailableBw | CE,port |Dual Homing|
+---------+----------+-------------+----------+-----------+ +---------+----------+-------------+----------+-----------+
|AP1 | 10Gbps | 5Gbps |CE1,portW | | |AP1 | 10Gbps | 5Gbps |CE1,portW | |
| -VNAP1.9| 5Gbps | N.A. | | VNAP2.9 | | -VNAP1.9| 5Gbps | N.A. | | VNAP2.9 |
+---------+----------+-------------+----------+-----------+ +---------+----------+-------------+----------+-----------+
|AP2 | 40Gbps | 35Gbps |CE1,portY | | |AP2 | 40Gbps | 35Gbps |CE1,portY | |
| -VNAP2.9| 5Gbps | N.A. | | VNAP1.9 | | -VNAP2.9| 5Gbps | N.A. | | VNAP1.9 |
+---------+----------+-------------+----------+-----------+ +---------+----------+-------------+----------+-----------+
|AP3 | 40Gbps | 35Gbps |CE2,portZ | | |AP3 | 40Gbps | 35Gbps |CE2,portZ | |
| -VNAP3.9| 5Gbps | N.A. | | NONE | | -VNAP3.9| 5Gbps | N.A. | | NONE |
+---------+----------+-------------+----------+-----------+ +---------+----------+-------------+----------+-----------+
Table 4: Dual homing - customer view after VN creation Table 4: Dual homing - customer view after VN creation
6. End point selection & mobility 6. End point selection & mobility
Virtual networks could be used as the infrastructure to connect a Virtual networks could be used as the infrastructure to connect a
number of sites of a customer among them or to provide connectivity number of sites of a customer among them or to provide connectivity
between customer sites and virtualized network functions (VNF) like between customer sites and virtualized network functions (VNF) like
for example virtualized firewall, vBNG, storage, computational for example virtualized firewall, vBNG, storage, computational
functions. functions.
6.1. End point selection & mobility 6.1. End point selection & mobility
skipping to change at page 26, line 11 skipping to change at page 26, line 11
[RFC4026] L. Andersson, T. Madsen, "Provider Provisioned Virtual [RFC4026] L. Andersson, T. Madsen, "Provider Provisioned Virtual
Private Network (VPN) Terminology", RFC 4026, March 2005. Private Network (VPN) Terminology", RFC 4026, March 2005.
[RFC4208] G. Swallow, J. Drake, H.Ishimatsu, Y. Rekhter, [RFC4208] G. Swallow, J. Drake, H.Ishimatsu, Y. Rekhter,
"Generalized Multiprotocol Label Switching (GMPLS) User- "Generalized Multiprotocol Label Switching (GMPLS) User-
Network Interface (UNI): Resource ReserVation Protocol- Network Interface (UNI): Resource ReserVation Protocol-
Traffic Engineering (RSVP-TE) Support for the Overlay Traffic Engineering (RSVP-TE) Support for the Overlay
Model", RFC 4208, October 2005. Model", RFC 4208, October 2005.
[RFC7926] A. Farrel (Ed.), "Problem Statement and Architecture for
Information Exchange between Interconnected Traffic-
Engineered Networks", RFC 7926, July 2016.
[PCE-S] Crabbe, E, et. al., "PCEP extension for stateful [PCE-S] Crabbe, E, et. al., "PCEP extension for stateful
PCE",draft-ietf-pce-stateful-pce, work in progress. PCE",draft-ietf-pce-stateful-pce, work in progress.
[GMPLS] Manning, E., et al., "Generalized Multi-Protocol Label [GMPLS] Manning, E., et al., "Generalized Multi-Protocol Label
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[NFV-AF] "Network Functions Virtualization (NFV); Architectural [NFV-AF] "Network Functions Virtualization (NFV); Architectural
Framework", ETSI GS NFV 002 v1.1.1, October 2013. Framework", ETSI GS NFV 002 v1.1.1, October 2013.
[ACTN-PS] Y. Lee, D. King, M. Boucadair, R. Jing, L. Contreras [ACTN-PS] Y. Lee, D. King, M. Boucadair, R. Jing, L. Contreras
 End of changes. 23 change blocks. 
114 lines changed or deleted 150 lines changed or added

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