< draft-king-teas-applicability-actn-slicing-00.txt   draft-king-teas-applicability-actn-slicing-01.txt >
TEAS Working Group D. King TEAS Working Group D. King (Ed.)
Internet-Draft Old Dog Consulting Internet-Draft Old Dog Consulting
Intended status: Informational June 13, 2017 Intended status: Informational Y. Lee (Ed.)
Expires: December 15, 2017 Expires: January 3, 2018 Huawei
July 3, 2017
Applicability of Abstraction and Control Applicability of Abstraction and Control
of TE Networks (ACTN) to Network Slicing of Traffic Engineered Networks (ACTN) to Network Slicing
draft-king-teas-applicability-actn-slicing-00 draft-king-teas-applicability-actn-slicing-01
Abstract Abstract
Network abstraction is a technique that can be applied to a network Network abstraction is a technique that can be applied to a network
domain to manage network resources to create a virtualized network domain to select network resources by policy to obtain a view of
that is under the control of a network operator (or perhaps the potential connectivity
customer).
Network slicing is an approach to network operations that builds on Network slicing is an approach to network operations that builds on
the concept of network abstraction to provide programmability, the concept of network abstraction to provide programmability,
flexibility, and modularity. It uses techniques such as Software flexibility, and modularity. It may use techniques such as Software
Defined Networking (SDN) and Network Function Virtualization (NFV) Defined Networking (SDN) and Network Function Virtualization (NFV)
to create multiple logical (virtual) networks, each tailored for a to create multiple logical (virtual) networks, each tailored for a
given use case, on top of a common network. set of services that are sharing the same set of requirements, on
top of a common network.
These logical networks are referred to as network slices. A network These logical networks are referred to as transport network slices.
slice does not necessarily represent dedicated resources in the A transport network slice does not necessarily represent dedicated
server network, but does constitute a commitment by the service resources in the network, but does constitute a commitment by the
provider to provide a specific level of service. network provider to provide a specific level of service.
The Abstraction and Control of Traffic Engineered Networks (ACTN) The Abstraction and Control of Traffic Engineered Networks (ACTN)
defines an SDN-based architecture that relies on the concepts of defines an SDN-based architecture that relies on the concepts of
network and service abstraction to detach network and service network and service abstraction to detach network and service
control from the underlying data plane. control from the underlying data plane.
This document outlines the applicability of ACTN to network This document outlines the applicability of ACTN to transport
slicing in an IETF technology network. It also identifies the network slicing in an IETF technology network. It also identifies
features of network slicing not currently within the scope of ACTN, the features of network slicing not currently within the scope of
and indicates where ACTN might be extended. ACTN, and indicates where ACTN might be extended.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 15, 2017. This Internet-Draft will expire on January 3, 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 2, line 32 skipping to change at page 2, line 32
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. 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. Requirements for Network Slicing................................4 2. Requirements for Network Slicing................................4
2.1. Resource Management........................................5 2.1. Resource Slicing...........................................4
2.2. Network and Function Virtualization........................5 2.2. Network and Function Virtualization........................5
2.3. Resource Isolation.........................................5 2.3. Resource Isolation.........................................5
2.4. Control and Orchestration..................................5 2.4. Control and Orchestration..................................6
3. Abstraction and Control of Traffic Engineered (TE) 3. Abstraction and Control of Traffic Engineered (TE)
Networks (ACTN).................................................6 Networks (ACTN).................................................6
3.1. ACTN Virtual Network as a "Network Slice"..................7 3.1. ACTN Virtual Network as a "Network Slice"..................8
3.2. Examples of ACTN Delivering Types of Network Slices........8 3.2. Examples of ACTN Delivering Types of Network Slices........8
3.2.1. ACTN Used for Virtual Private Line Model...............8 3.2.1. ACTN Used for Virtual Private Line Model...............9
3.2.2. ACTN Used for VPN Delivery Model.......................9 3.2.2. ACTN Used for VPN Delivery Model.......................10
3.2.3. ACTN Used to Deliver a Virtual Customer Network........10 3.2.3. ACTN Used to Deliver a Virtual Customer Network........10
3.3. Network Slice Service Mapping from TE to ACTN VN Models....11 3.3. Network Slice Service Mapping from TE to ACTN VN Models....11
4. IANA Considerations.............................................12 3.4 ACTN VN KPI Telemetry Models................................12
5. Security Considerations.........................................12 4. IANA Considerations.............................................13
6. Informative References..........................................13 5. Security Considerations.........................................13
Authors' Addresses.................................................14 6. Acknowledgements................................................13
7. Contributors....................................................13
8. References......................................................14
Authors' Addresses.................................................15
1. Introduction 1. Introduction
The principles of network resource separation are not new. For The principles of network resource separation are not new. For
years, separated overlay and logical (virtual) networking have years, separated overlay and logical (virtual) networking have
existed, allowing multiple connectivity and bandwidth services to be existed, allowing multiple connectivity services to be deployed over
deployed over a single physical network comprised of single or a single physical network comprised of single or multiple layers.
multiple layers. However, several key differences exist that However, several key differences exist that differentiate overlay and
differentiate overlay and virtual networking from network slicing. virtual networking from network slicing.
A network slice construct provides an end-to-end logical network, A transport network slice construct provides an end-to-end logical
often with compute functions and utilising shared underlying network, often with compute functions and utilising shared underlying
(physical or virtual) network resources. This logical network is (physical or virtual) network resources. This logical network is
separated from other, often concurrent, logical networks each with separated from other, often concurrent, logical networks each with
independent control and management, and each of which can be created independent control and management, and each of which can be created
or modified on demand. or modified on demand.
At one end of the spectrum, a virtual private wire or a virtual At one end of the spectrum, a virtual private wire or a virtual
private network (VPN) is a network slice. In these cases, the network private network (VPN) may be used to build a network slice. In these
slices do not require the service provider to isolate network cases, the network slices do not require the service provider to
resources for the provision of the service - the service is isolate network resources for the provision of the service - the
"virtual". service is "virtual".
At the other end of the spectrum there may be a detailed description At the other end of the spectrum there may be a detailed description
of a complex service that will meet the needs of a set of of a complex service that will meet the needs of a set of
applications with connectivity, bandwidth, and function requirements applications with connectivity and service function requirements that
that include compute resource, storage capability, and access to may include compute resource, storage capability, and access to
content. Such a service may be requested dynamically (that is, content.Such a service may be requested dynamically (that is,
instantiated when an application needs it, and released when the instantiated when an application needs it, and released when the
application no longer needs it), and modified as the needs of the application no longer needs it), and modified as the needs of the
application change. application change.
Each example represents a self-contained network that must be Each example represents a self-contained network that must be
flexible enough to simultaneously accommodate diverse business-driven flexible enough to simultaneously accommodate diverse business-driven
use cases from multiple players on a common network infrastructure. use cases from multiple players on a common network infrastructure.
This document outlines the application of the ACTN architecture and This document outlines the application of the ACTN architecture
enabling technologies to network slicing in an IETF technology [actn-framework] and enabling technologies to provide transport
network. It describes how the ACTN functional components can be used network slicing in an IETF technology network. It describes how the
to support model-driven partitioning of variable-sized bandwidth to ACTN functional components can be used to support model-driven
facilitate network sharing and virtualization. Furthermore, the use partitioning of variable-sized bandwidth to facilitate network
of model-based interfaces to dynamically request the instantiation of sharing and virtualization. Furthermore, the use of model-based
virtual networks could be extended to encompass requesting and interfaces to dynamically request the instantiation of virtual
instantiation of specific Network Functions (which may be both networks could be extended to encompass requesting and instantiation
physical and/or virtual), and to partition network resources such as of specific service functions (which may be both physical and/or
compute resource, storage capability, and access to content. virtual), and to partition network resources such as compute
resource, storage capability, and access to content.
This document highlights how the ACTN approach might be extended to This document highlights how the ACTN approach might be extended to
address these other requirements of network slicing. address these other requirements of network slicing where TE is
required.
1.1 Terminology 1.1 Terminology
Resource: Any features or functions that can be delivered by a server Resource: Any features that can be delivered, including connectivity,
network. Includes connectivity, compute resources, storage, and compute, storage, and content delivery.
content delivery.
Network Functions (NFs): Components that provide specific function Service Functions (SFs): Components that provide specific function
within a network. NFs are often combined in a specific sequence to within a network. SFs are often combined in a specific sequence,
deliver services. service function chain, to deliver services.
Infrastructure Resources: The hardware and necessary software for Infrastructure Resources: The hardware and necessary software for
hosting and connecting NFs. These resources may include computing hosting and connecting SFs. These resources may include computing
hardware, storage capacity, network resources (e.g. links and hardware, storage capacity, network resources (e.g. links and
switching/routing devices enabling network connectivity), and switching/routing devices enabling network connectivity), and
physical assets for radio access. physical assets for radio access.
Service Provider: A server network or collection of server Service Provider: A server network or collection of server
networks. networks.
Consumer: Any application, client network, or customer of a service Consumer: Any application, client network, or customer of a network
provider provider.
Service Level Agreement (SLA): An agreement between a consumer and Service Level Agreement (SLA): An agreement between a consumer and
service provider that describes the quality with which features network provider that describes the quality with which features
and functions are to be delivered. It may include measures of and functions are to be delivered. It may include measures of
bandwidth, latency, and jitter; the types of service (such as the bandwidth, latency, and jitter; the types of service (such as the
network service functions or billing) to be executed; the location, network service functions or billing) to be executed; the location,
nature, and quantities of services (such as the amount and location nature, and quantities of services (such as the amount and location
of compute resources and the accelerators require). of compute resources and the accelerators require).
Network Slice: An agreement between a consumer and a service Network Slice: An agreement between a consumer and a service
provider to deliver network resources according to a specific service provider to deliver network resources according to a specific service
level agreement. level agreement. A slice could span multiple technology (e.g., radio,
transport and cloud) and administrative domains.
IETF Technology: A TE network slice or transport network slice.
2. Requirements for Network Slicing 2. Requirements for Network Slicing
The concept of network slicing is considered a key capability for The concept of network slicing is considered a key capability for
future networks and, to serve customers with a wide variety of future networks and, to serve customers with a wide variety of
different service needs, in term of latency, reliability, capacity, different service needs, in term of latency, reliability, capacity,
and function specific capabilities. and service function specific capabilities.
This section outlines the key capabilities required, and further This section outlines the key capabilities required, and further
discussed in [ngmn-network-slicing], [network-slice-5g], discussed in [ngmn-network-slicing], [network-slice-5g],
[3gpp.28.801] and [onf-tr526], to realise network slicing in an IETF [3gpp.28.801] and [onf-tr526], to realise network slicing in an IETF
technology network. technology network.
2.1 Resource Slicing 2.1 Resource Slicing
For network slicing, it is important to consider both infrastructure For network slicing, it is important to consider both infrastructure
resources and network functions. This allows a flexible approach to resources and servic functions. This allows a flexible approach to
deliver a range of services both by partitioning (slicing) the deliver a range of services both by partitioning (slicing) the
available network resources to present them for use by a consumer, available network resources to present them for use by a consumer,
but also by providing instances of NFs at the right locations and but also by providing instances of SFs at the right locations and in
with access to the necessary hardware, including specific compute and the correct chaining logic, with access to the necessary hardware,
storage resources. including specific compute and storage resources.
Mapping of resources to slices may 1-to-1, or resources may be shared
among multiple slices.
2.2 Network and Function Virtualization 2.2 Network and Function Virtualization
Virtualization is the abstraction of resources where the abstraction Virtualization is the abstraction of resources where the abstraction
is made available for use by an operations entity, for example, by is made available for use by an operations entity, for example, by
the Network Management Station (NMS) of a consumer network. The the Network Management Station (NMS) of a consumer network. The
resources to be virtualized can be physical or already virtualized, resources to be virtualized can be physical or already virtualized,
supporting a recursive pattern with different abstraction layers. supporting a recursive pattern with different abstraction layers.
Therefore, Virtualization is critical for network slicing as it Therefore, Virtualization is critical for network slicing as it
enables effective resource sharing between network slices. enables effective resource sharing between network slices.
Just as server Virtualization makes virtual machines (VMs) Just as server virtualization makes virtual machines (VMs)
independent of the underlying physical hardware, network independent of the underlying physical hardware, network
Virtualization enables the creation of multiple isolated virtual Virtualization enables the creation of multiple isolated virtual
networks that are completely decoupled from the underlying physical networks that are completely decoupled from the underlying physical
network, and can safely run on top of it. network, and can safely run on top of it.
2.3 Resource Isolation 2.3 Resource Isolation
Isolation of data and traffic is a major requirement that must be Isolation of data and traffic is a major requirement that must be
satisfied for certain applications to operate in concurrent network satisfied for certain applications to operate in concurrent network
slices on a common shared underlying infrastructure. Therefore, slices on a common shared underlying infrastructure. Therefore,
isolation must be understood in terms of: isolation must be understood in terms of:
o Performance: Each slice is defined to meet specific service o Performance: Each slice is defined to meet specific service
requirements, usually expressed in the form of Key Performance requirements, usually expressed in the form of Key Performance
Indicators (KPIs). Performance isolation requires that service Indicators (KPIs). Performance isolation requires that service
delivery on one network slice is not adversely impacted by delivery on one network slice is not adversely impacted by
congestion and performance levels of other slices; congestion and performance levels of other slices;
o Security: Attacks or faults occurring in one slice must not have an o Security: Attacks or faults occurring in one slice must not have an
impact on other slices. Moreover, each slice must have independent impact on other slices, or customer flows are not only isolated on
network edge, but multiple customer traffic is not mixed across the
core of the network. Moreover, each slice must have independent
security functions that prevent unauthorised entities to have read security functions that prevent unauthorised entities to have read
or write access to slice-specific configuration, management, or write access to slice-specific configuration, management,
accounting information, and able to record any of these attempts, accounting information, and able to record any of these attempts,
whether authorised or not; whether authorised or not;
o Management: Each slice must be independently viewed, utilised and o Management: Each slice must be independently viewed, utilised and
managed as a separate network. managed as a separate network.
2.4 Control and Orchestration 2.4 Control and Orchestration
Orchestration is the overriding control method for network slicing. Orchestration is the overriding control method for network slicing.
We may define orchestration as combining and coordinating multiple We may define orchestration as combining and coordinating multiple
control methods to provide an operational mechanism that can deliver control methods to provide an operational mechanism that can deliver
services and control underlying resources. In a network slicing services and control underlying resources. In a network slicing
environment, an orchestrator is needed to coordinate disparate environment, an orchestrator is needed to coordinate disparate
processes and resources for creating, managing, and deploying the processes and resources for creating, managing, and deploying the
end-to-end service. end-to-end service. Two scenarios are outlined below where
orchestration would be required:
1. Multi-domain Orchestration: Managing connectivity setup of the
transport service, across multiple administrative domains;
2. End-to-end Orchestration: Combining resources for an "end-to-end
service (e.g., transport connectivity with firewalling and
guaranteed bandwidth and minimum delay for premium radio users
(spanning multiple domains).
In addition, 3GPP has also developed Release 14 "Study on In addition, 3GPP has also developed Release 14 "Study on
management and orchestration of network slicing for next generation management and orchestration of network slicing for next generation
network" [3gpp.28.801], which defines an information model where the network" [3gpp.28.801], which defines an information model where the
network slice as well as physical and virtualized network functions network slice as well as physical and virtualized network functions
belong to the network operator domain, while the virtualized belong to the network operator domain, while the virtualized
resources belong to another domain operated by a Virtualization resources belong to another domain operated by a Virtualization
infrastructure service provider. infrastructure service provider.
3. Abstraction and Control of Traffic Engineered (TE) Networks (ACTN) 3. Abstraction and Control of Traffic Engineered (TE) Networks (ACTN)
skipping to change at page 6, line 43 skipping to change at page 7, line 14
--------- --------- --------- --------- --------- ---------
| CNC-A | | CNC-B | | CNC-C | | CNC-A | | CNC-B | | CNC-C |
--------- --------- --------- --------- --------- ---------
\ | / \ | /
\__________ |-CMI I/F __________/ \__________ |-CMI I/F __________/
\ | / \ | /
------------------------- -------------------------
| MDSC | | MDSC |
------------------------- -------------------------
/ | \ / / | \
_________/ |-MMI I/F \__________ / / |-MPI I/F \
/ | \ / / | \
------------ ------------ ---------- ------- ------- ------- -------
| MDSC | | MDSC | | MDSC | | PNC | | PNC | | PNC | | PNC |
------------ ------------ ---------- ------- ------- ------- -------
| / |-MPI I/F / \
| / | / \
------- ------- ------- ------- -------
| PNC | | PNC | | PNC | | PNC | | PNC |
------- ------- ------- ------- -------
CMI - (CNC-MDSC Interface ) CMI - (CNC-MDSC Interface )
MMI - (MDSC-MDSC Interface)
MPI - (MDSC-PNC Interface) MPI - (MDSC-PNC Interface)
Figure 1: ACTN Hierarchy Figure 1: ACTN Hierarchy
ACTN facilitates end-to-end connections and provides them to the ACTN facilitates end-to-end connections and provides them to the
user. The ACTN framework highlights how: user. The ACTN framework highlights how:
o Abstraction of the underlying network resources are provided to o Abstraction of the underlying network resources are provided to
higher-layer applications and customers; higher-layer applications and customers;
skipping to change at page 7, line 37 skipping to change at page 7, line 52
The ACTN managed infrastructure are traffic engineered network The ACTN managed infrastructure are traffic engineered network
resources, which may include: resources, which may include:
o Statistical packet bandwidth; o Statistical packet bandwidth;
o Physical forwarding plane sources, such as: wavelengths and o Physical forwarding plane sources, such as: wavelengths and
time slots; time slots;
o Forwarding and cross connect capabilities. o Forwarding and cross connect capabilities.
The ACTN type of network Virtualization provides customers and The ACTN type of network virtualization provides customers and
applications (tenants) to utilise and independently control applications (tenants) to utilise and independently control
allocated virtual network resources as if resources as if they allocated virtual network resources as if resources as if they
were physically their own resource. The ACTN network is "sliced"", were physically their own resource. The ACTN network is "sliced",
with tenants being given a different partial and abstracted with tenants being given a different partial and abstracted
topology view of the physical underlying network. The capabilities topology view of the physical underlying network. The capabilities
that ACTN provides to enable slicing are outlined in Section 2 that ACTN provides to enable slicing are outlined in Section 2
(Requirements for Network Slicing). (Requirements for Network Slicing).
3.1 ACTN Virtual Network as a "Network Slice" 3.1 ACTN Virtual Network as a "Network Slice"
To support multiple clients each with its own view of and control To support multiple clients each with its own view of and control
of the server network, a network operator needs to partition (or of the server network, a network operator needs to partition (or
"slice") the network resources. The resulting slices can be "slice") the network resources. The resulting slices can be
skipping to change at page 8, line 25 skipping to change at page 8, line 36
o Network Slice Creation: A VN could be pre-configured and created o Network Slice Creation: A VN could be pre-configured and created
via static or dynamic request and negotiation between customer and via static or dynamic request and negotiation between customer and
provider. It must meet the specified SLA attributes which satisfy provider. It must meet the specified SLA attributes which satisfy
the customer's objectives. the customer's objectives.
o Network Slice Operations: The network slice may be further modified o Network Slice Operations: The network slice may be further modified
and deleted based on customer request to request changes in the and deleted based on customer request to request changes in the
network resources reserved for the customer, and used to construct network resources reserved for the customer, and used to construct
the network slice. The customer can further act upon the network the network slice. The customer can further act upon the network
slice to manager traffic flow across the network slice. slice to manage traffic flow across the network slice.
o Network Slice View: The VN topology from a customer point of view. o Network Slice View: The VN topology from a customer point of view.
These may be a variety of tunnels, or an entire VN topology. Such These may be a variety of tunnels, or an entire VN topology. Such
connections may comprise of customer end points, access links, connections may comprise of customer end points, access links,
intra domain paths and inter-domain links. intra domain paths and inter-domain links.
Primitives (capabilities and messages) have been provided to support Primitives (capabilities and messages) have been provided to support
the different ACTN network control functions that will enable network the different ACTN network control functions that will enable network
slicing. These include: topology request/query, VN service request, slicing. These include: topology request/query, VN service request,
path computation and connection control, VN service policy path computation and connection control, VN service policy
negotiation, enforcement, routing options. [actn-info] negotiation, enforcement, routing options. [actn-info]
3.2 Examples of ACTN Delivering Types of Network Slices 3.2 Examples of ACTN Delivering Types of Network Slices
In all the examples below ACTN is the framework used to provide In examples below the ACTN framework is used to provide
control, management and orchestration for the network slice control, management and orchestration for the network slice
life-cycle. These dynamic and highly flexible, end-to-end and life-cycle, the connectivity . These dynamic and highly flexible,
dedicated network slices utilising common physical infrastructure, end-to-end and dedicated network slices utilising common physical
and according to vertical-specific requirements. The following infrastructure, and according to vertical-specific requirements.
example provides three examples of using ACTN to achieve different
scenarios of ACTN for network slicing g. All three scenarios can be The rest of this section provides three examples of using ACTN to
scaled up capacity and topology changes, customer requirements achieve different scenarios of ACTN for network slicing. All three
change. scenarios can be scaled up in capacity or be subject to topology
changes as well as changes from customer requirements perspective.
3.2.1 ACTN Used for Virtual Private Line Model 3.2.1 ACTN Used for Virtual Private Line Model
ACTN Provides virtual connections between multiple customer ACTN Provides virtual connections between multiple customer
locations, requested via Virtual Private Line (VPL) requester locations, requested via Virtual Private Line (VPL) requester
(CNC-A), are provided. Benefits of this model include: (CNC-A). Benefits of this model include:
o Automated: the service set-up and operation is network provider o Automated: the service set-up and operation is network provider
managed; managed;
o Virtual: the private line is seamlessly extended from customers o Virtual: the private line is seamlessly extended from customers
Site A (vCE1 to vCE2) and Site B (vCE2 to vCE2) across the Site A (vCE1 to vCE2) and Site B (vCE2 to vCE3) across the
ACTN-managed WAN to Site C; ACTN-managed WAN to Site C;
o Agile: on-demand where the customer needs connectivity and o Agile: on-demand where the customer needs connectivity and
fully adjustable bandwidth. fully adjustable bandwidth.
(Customer VPL Request) (Customer VPL Request)
| |
--------- ---------
| CNC-A | | CNC-A |
Boundary --------- Boundary ---------
skipping to change at page 10, line 46 skipping to change at page 11, line 9
Figure 3: VPN Model Figure 3: VPN Model
3.2.3 ACTN Used to Deliver a Virtual Customer Network 3.2.3 ACTN Used to Deliver a Virtual Customer Network
In this example ACTN provides a virtual network resource to the In this example ACTN provides a virtual network resource to the
customer. This resource is customer managed. Empowering the tenant customer. This resource is customer managed. Empowering the tenant
to control allocated slice (recursively). Benefits of this model to control allocated slice (recursively). Benefits of this model
include: include:
o The MDSC provides the topology as part of the customer view so o The MDSC provides the topology as part of the customer view so
that the the customer can control their network slice to fit their that the customer can control their network slice to fit their
needs; needs;
o Resource isolation, each customer network slice is fixed and will o Resource isolation, each customer network slice is fixed and will
not be affected by changes to other customer network slices; not be affected by changes to other customer network slices;
o Applications can interact with their assigned network slice o Applications can interact with their assigned network slice
directly, the customer may implement their own network control directly, the customer may implement their own network control
method and traffic prioritization, manage their own addressing method and traffic prioritization, manage their own addressing
scheme, and further slice their assigned network resource; scheme, and further slice their assigned network resource;
skipping to change at page 12, line 28 skipping to change at page 12, line 37
| L2SM | <------> | | <-----> | ACTN VN | | L2SM | <------> | | <-----> | ACTN VN |
----------- --------------- | Model | ----------- --------------- | Model |
------------ ------------
Figure 5: TE-Service Mapping ([te-service-mapping]) Figure 5: TE-Service Mapping ([te-service-mapping])
Editors note - We plan to provide a list of models available and Editors note - We plan to provide a list of models available and
their relationships/dependencies. We will also provide a vertical their relationships/dependencies. We will also provide a vertical
hierarchy of how these models may be used between functional hierarchy of how these models may be used between functional
components in ACTN. components in ACTN.
3.4 ACTN VN KPI telemetry Models
The role of ACTN VN KPI telemetry model [actn-pm-telemetry] is
to provide YANG models so that customer can define key
performance monitoring data relevant for its VN/network slicing
via the YANG subscription model.
Key characteristics of [actn-pm-telemetry] include:
o an ability to provide scalable VN-level telemetry aggregation
based on customer-subscription model for key performance
parameters defined by the customer;
o an ability to facilitate proactive re-optimization and
reconfiguration of VNs/Netork Slices based on network
autonomic traffic engineering scaling configuration
mechanism.
4. IANA Considerations 4. IANA Considerations
This document makes no requests for action by IANA. This document makes no requests for action by IANA.
5. Security Considerations 5. Security Considerations
Network slicing involves the control of network resources in order Network slicing involves the control of network resources in order
to meet the service requirements of consumers. In some deployment to meet the service requirements of consumers. In some deployment
models, the consumer is able to directly request modification in models, the consumer is able to directly request modification in
the behaviour of resources owned and operated by a service provider. the behaviour of resources owned and operated by a service provider.
skipping to change at page 13, line 19 skipping to change at page 13, line 43
physical connectivity. physical connectivity.
ACTN operates using the [netconf] or [restconf] protocols and ACTN operates using the [netconf] or [restconf] protocols and
assumes the security characteristics of those protocols. assumes the security characteristics of those protocols.
Deployment models for ACTN should fully explore the authentication Deployment models for ACTN should fully explore the authentication
and other security aspects before networks start to carry live and other security aspects before networks start to carry live
traffic. traffic.
6. Acknowledgements 6. Acknowledgements
Thanks to Qin Wu, Andy Jones and Ramon Casellas for their insight Thanks to Qin Wu, Andy Jones, Ramon Casellas, and Gert Grammel for
and useful discussions about network slicing. their insight and useful discussions about network slicing.
7. Contributors 7. Contributors
The following people contributed text to this document. The following people contributed text to this document.
Adrian Farrel Adrian Farrel
Email: afarrel@juniper.net Email: afarrel@juniper.net
Mohamed Boucadair
Email: mohamed.boucadair@orange.com
Young Lee Sergio Belotti
Email: ylee@huawei.com Email: sergio.belotti@nokia.com
Daniele Ceccarelli
Email: daniele.ceccarelli@ericsson.com
Haomian Zheng
Email: zhenghaomian@huawei.com
8. References 8. References
8.1. Normative References 8.1. Normative References
8.2. Informative References 8.2. Informative References
[ngmn-network-slicing] [ngmn-network-slicing]
NGMN, "Description of Network Slicing Concept", 1 2016, NGMN, "Description of Network Slicing Concept", 1 2016,
<https://www.ngmn.org/uploads/ <https://www.ngmn.org/uploads/
skipping to change at page 14, line 30 skipping to change at page 15, line 8
[te-service-mapping] [te-service-mapping]
Y. Lee, D. Dhody, and D. Ceccarelli, "Traffic Engineering Y. Lee, D. Dhody, and D. Ceccarelli, "Traffic Engineering
and Service Mapping Yang Model", and Service Mapping Yang Model",
draft-lee-teas-te-service-mapping-yang-00 draft-lee-teas-te-service-mapping-yang-00
(work in progress), March 2017. (work in progress), March 2017.
[actn-vn] Y. Lee (Editor), "A Yang Data Model for ACTN VN [actn-vn] Y. Lee (Editor), "A Yang Data Model for ACTN VN
Operation", draft-lee-teas-actn-vn-yang, work in progress. Operation", draft-lee-teas-actn-vn-yang, work in progress.
[actn-info] [actn-info] Y. Lee, S. Belotti (Editors), "Information Model for
"Information Model for Abstraction and Control of TE Abstraction and Control of TE Networks (ACTN)", draft-ietf-
Networks (ACTN)", <https://datatracker.ietf.org/doc/html/ teas-actn-info-model, work in progress.
draft-ietf-teas-actn-info-model>.
[l3sm] Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data [actn-pm-elemetry] Y. Lee, et al, "YANG models for ACTN TE
Model for L3VPN Service Delivery", RFC 8049, Performance Monitoring Telemetry and Network Autonomics",
DOI 10.17487/RFC8049, February 2017, draft-lee- teas-actn-pm-telemetry-autonomics, work in
<http://www.rfc-editor.org/info/rfc8049>. progress.
[l3sm] Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data
Model for L3VPN Service Delivery", RFC 8049,
DOI 10.17487/RFC8049, February 2017,
<http://www.rfc-editor.org/info/rfc8049>.
[netconf] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [netconf] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241. (NETCONF)", RFC 6241.
[restconf] A. Bierman, M. Bjorklund, and K. Watsen, "RESTCONF [restconf] A. Bierman, M. Bjorklund, and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf, work in progress. Protocol", draft-ietf-netconf-restconf, work in progress.
Authors' Addresses Authors' Addresses
Daniel King Daniel King
Email: daniel@olddog.co.uk Email: daniel@olddog.co.uk
Young Lee
Email: ylee@huawei.com
 End of changes. 51 change blocks. 
109 lines changed or deleted 158 lines changed or added

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