draft-ietf-teas-actn-requirements-03.txt   draft-ietf-teas-actn-requirements-04.txt 
Network Working Group Young Lee (Editor) Network Working Group Young Lee (Editor)
Dhruv Dhody Dhruv Dhody
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Sergio Belotti Intended status: Informational Sergio Belotti
Alcatel-Lucent Alcatel-Lucent
Expires: January 2017 Expires: July 2017
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
July 6, 2016 January 3, 2017
Requirements for Abstraction and Control of TE Networks Requirements for Abstraction and Control of TE Networks
draft-ietf-teas-actn-requirements-03.txt draft-ietf-teas-actn-requirements-04.txt
Abstract Abstract
This draft provides a set of requirements for abstraction and This document provides a set of requirements for abstraction and
control of TE networks. control of Traffic Engineering networks to facilitate virtual
network operation via the creation of a single virtualized network
or a seamless service. This supports operators in viewing and
controlling different domains (at any dimension: applied technology,
administrative zones, or vendor-specific technology islands) as a
single virtualized network.
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 2, line 4 skipping to change at page 2, line 9
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 January 6, 2017. This Internet-Draft will expire on July 3, 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
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
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................3
2. High-level ACTN requirements...................................4 2. High-level ACTN requirements...................................4
3. ACTN Use-Cases.................................................8 2.1. Service-Specific Requirements.............................4
3.1. Two categories of requirements...........................11 2.2. Network-Related Requirements..............................7
4. ACTN interfaces requirements..................................15 3. ACTN Interfaces Requirements...................................8
4.1. CMI Requirements.........................................16 3.1. CMI Requirements..........................................9
4.2. MPI Requirements.........................................18 3.2. MPI Requirements.........................................11
5. References....................................................21 4. References....................................................13
5.1. Informative References...................................21 4.1. Normative References.....................................13
6. Contributors..................................................22 4.2. Informative References...................................14
Contributors' Addresses..........................................22 5. Contributors..................................................15
Authors' Addresses...............................................22 Authors' Addresses...............................................15
1. Introduction 1. Introduction
This draft provides a set of requirements for Abstraction and This document provides a set of requirements for Abstraction and
Control of TE Networks (ACTN) identified in various use-cases of Control of Traffic Engineering (TE) Networks (ACTN) identified in
ACTN. [ACTN-frame] defines the base reference architecture and various use-cases. [ACTN-frame] defines the base reference
terminology. [ACTN-PS] provides problem statement and gap analysis. architecture and terminology.
ACTN refers to the set of virtual network operations needed to ACTN refers to the set of virtual network operations needed to
orchestrate, control and manage large-scale multi-domain TE networks orchestrate, control and manage large-scale multi-domain TE networks
so as to facilitate network programmability, automation, efficient so as to facilitate network programmability, automation, efficient
resource sharing, and end-to-end virtual service aware connectivity resource sharing, and end-to-end virtual service aware connectivity
and network function virtualization services. and network function virtualization services.
These operations are summarized as follows: These operations are summarized as follows:
- Abstraction and coordination of underlying network resources - Abstraction and coordination of underlying network resources
to higher-layer applications and customers, independent of how independent of how these resources are managed or controlled,
these resources are managed or controlled, so that these so that higher-layer entities can dynamically control virtual
higher-layer entities can dynamically control virtual networks based on those resources. Control includes creating,
networks. Control includes creating, modifying, modifying, monitoring, and deleting virtual networks.
monitoring, and deleting virtual networks.
- Multi-domain and multi-tenant virtual network operations via - Collation of the resources from multiple TE networks (multiple
hierarchical abstraction of TE domains that facilitates technologies, equipment from multiple vendors, under the
multi-administration, multi-vendor, and multi-technology control of multiple administrations) through a process of
networks as a single virtualized network. This is achieved by hierarchical abstraction to present a customer with a single
presenting the network domain as an abstracted topology to the virtual network. This is chieved by presenting the network
customers via open and programmable interfaces. Hierarchical domain as an abstracted topology to the customer via open and
abstraction allows for the recursion of controllers in a programmable interfaces. Hierarchical abstraction allows for
customer-provider relationship. the recursion of controllers in a customer-provider
relationship.
- Orchestration of end-to-end virtual network services and - Orchestration of end-to-end virtual network services and
applications via allocation of network resources to meet applications via allocation of network resources to meet
specific service, application and customer requirements. specific service, application and customer requirements.
- Adaptation of customer requests (made on virtual resources) to - Adaptation of customer requests (to control virtual resources)
the physical network resources performing the necessary to the physical network resources performing the necessary
mapping, translation, isolation and, policy that allows mapping, translation, isolation and, policy that allows
conveying, managing and enforcing customer policies with conveying, managing and enforcing customer policies with
respect to the services by the network to said customer. respect to the services and the network of the customer.
- Provision of a computation scheme and virtual control - Provision via a data model of a computation scheme and virtual
capability via a data model to customers who request virtual control capability to customers who request virtual network
network services. Note that these customers could, themselves, services. Note that these customers could, themselves, be
be service providers. service providers.
ACTN solutions will build on, and extend, existing TE constructs and ACTN solutions will build on, and extend, existing TE constructs and
TE mechanisms wherever possible and appropriate. Support for TE mechanisms wherever possible and appropriate. Support for
controller-based approaches is specifically included in the possible controller-based approaches is specifically included in the possible
solution set. solution set.
Section 2 provides high-level ACTN requirements. Sections 3-5 Section 2 provides high-level ACTN requirements. Section 3 provides
provide the list of ACTN use-cases and the detailed requirement ACTN interface requirements.
analysis of these use-cases.
2. High-level ACTN requirements 2. High-level ACTN requirements
1. Requirement 1: Single Virtualized Network Topology This section provides a summary of use-cases in terms of two
categories: (i) service-specific requirements; (ii) network-related
requirements.
Ability to build virtual network operation infrastructure based Service-specific requirements listed below are uniquely applied to
on multi-layer, multi-domain topology abstracted from multiple the work scope of ACTN. Service-specific requirements are related to
physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS, the virtual service coordination function. These requirements are
etc.) related to customer's VNs in terms of service policy associated with
VNs such as service performance objectives, VN endpoint location
information for certain required service specific functions (e.g.,
security and others), VN survivability requirement, or dynamic
service control policy, etc.
Reference: [KLEE], [LOPEZ], [DHODY], [CHENG]. Network-related requirements are related to the virtual network
operation function. These requirements are related to multi-domain
and multi-layer signaling, routing, protection/restoration and
synergy, re-optimization/re-grooming, etc. These requirements are
not inherently unique for the scope of ACTN but some of these
requirements are in scope of ACTN, especially for coherent/seamless
operation aspect of multiple controller hierarchy.
2. Requirement 2: Policy Enforcement 2.1. Service-Specific Requirements
1. Requirement 1: Policy Enforcement
Ability to provide service requirement/policy (between Customer Ability to provide service requirement/policy (between Customer
and Network) and mechanism to enforce service level agreement. and Network) and mechanism to enforce Service Level Agreements
(SLA).
- Endpoint selection policy, routing policy, time-related - Endpoint selection policy, routing policy, time-related
policy, etc. policy, etc.
Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG]. Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG].
3. Requirement 3: VN Query 2. Requirement 2: Virtual Network (VN) Query
Ability to request/respond VN Query (Can you give me VN(s)?)
- Request Input:
- VN end-points (CE end)
- VN Topology Service-specific Multi-Cost Objective
Function
- VN Topology diversity (e.g., VN1 and VN2 must be Ability to request/respond VN Query ("Can you give me these
disjoint) VN(s)?")
- VN Topology type: path, graph Request Input:
- Response includes VN topology - VN end-points (Customer Edge equipment)
- VN Topology Service-specific Multi-Cost Objective Function
- VN constraints requirement
o Latency only, bandwidth guarantee, joint latency and
bandwidth guarantee
- VN Topology diversity (e.g., VN1 and VN2 must be disjoint;
Node/link disjoint from other VNs)
- VN Topology type: path, graph
- Exact Response includes VN topology:
- Potential - Exact
- Potential
Reference: [KUMAKI], [FANG], [CHENG]. Reference: [KUMAKI], [FANG], [CHENG].
4. Requirement 4: VN Instantiate 3. Requirement 3: VN Instantiation ("Please create a VN for me")
Ability to request/confirm VN Instantiation Ability to request/confirm VN Instantiation
- VN instance ID Request Input:
- VN end-points
- VN constraints requirement
- Latency only, B/W guarantee, Latency and B/W guarantee
together
- VN diversity
- Node/Link disjoint from other VNs
- VN level diversity (e.g., VN1 and VN2 must be disjoint)
- VN type - VN instance ID
- VN end-points (Customer Edge equipment)
- VN Topology Service-specific Multi-Cost Objective Function
- VN constraints requirement
o Latency only, bandwidth guarantee, joint latency and
bandwidth guarantee
- VN Topology diversity (e.g., VN1 and VN2 must be disjoint;
Node/link disjoint from other VNs)
- VN Topology type: path, graph
- Path (tunnel), Node/Links (graph) Response includes VN topology:
- VN instance ID per service (unique id to identify VNs) - Exact
- Potential
Reference: [KUMAKI], [FANG], [CHENG]. Reference: [KUMAKI], [FANG], [CHENG].
5. Requirement 5: Dynamic VN Control 4. Requirement 4: VN Lifecycle Management & Operation (M&O)
Dynamic/On-demand VN Modification/Confirmation with feedback loop
to the customer
- Traffic monitoring and control policies sent to the network
- Network states based traffic optimization policies
- Utilization Monitoring (Frequency of report)
- Abstraction of Resource Topology reflecting these service-
related parameters
Reference: [XU], [XU2], [DHODY], [CHENG].
6. Requirement 6: VN Lifecycle M&O
VN lifecycle management/operation
- Instantiate
- Delete
- Modify Ability to do the following VN operations:
- Update (VN level OAM Monitoring) under policy agreement - Delete
- Modify
- Update (VN level Operations, Administration and Management
(OAM) Monitoring) under policy agreement
Reference: [FANG], [KUMAKI], [LOPEZ]. Reference: [FANG], [KUMAKI], [LOPEZ].
7. Requirement 7: VN Service Operation 5. Requirement 5: VN Service Operation
Ability to setup and manage end-2-end service on the VN involving Ability to set up and manage end-to-end services on the VN
multi-domain, multi-layer, meeting constraints based on SLAs. involving multi-domain and multi-layer operations of the
underlying network while meeting constraints based on SLAs.
Reference: [LOPEZ], [KUMAKI], [CHENG], [DHODY], [FANG], [KLEE]. Reference: [LOPEZ], [KUMAKI], [CHENG], [DHODY], [FANG], [KLEE].
8. Requirement 8: Multi-destination Coordination 6. Requirement 6: VN Confidentiality/Security
- A VN customer must not be able to control another customer's
virtual network
- A VN customer must not see any routing information (e.g. IGP
database, TE database) relating to another customer's
virtual network
Reference: [KUMAKI], [FANG], [LOPEZ]
7. Requirement 7: Multi-Destination Coordination
Coordination of multi-destination service requirement/policy to Coordination of multi-destination service requirement/policy to
support dynamic applications such as VM migration, disaster support dynamic applications such as VM migration, disaster
recovery, load balancing, etc. recovery, load balancing, etc.
- Service-policy primitives and its parameters - Service-policy primitives and their parameters
Reference: [FANG], [LOPEZ], [SHIN]. Reference: [FANG], [LOPEZ], [SHIN].
9. Requirement 9: Multi-domain & Multi-layer Coordination 2.2. Network-Related Requirements
Ability to Coordinate multi-domain and multi-layer path 1. Requirement 1: Single Virtualized Network Topology
computation and setup operation (network)
- E2E path computation across multi-domain (based on abstract Ability to build virtual network operation infrastructure based
topology from each domain) on multi-layer, multi-domain topology abstracted from multiple
physical network control mechanisms (e.g., GMPLS, OpenFlow, PCE,
NMS, etc.)
- The domain sequence determination Reference: [KLEE], [LOPEZ], [DHODY], [CHENG].
- Request for path signaling to each domain controller 2. Requirement 2: Multi-Domain & Multi-layer Coordination
- Alternative path computation if any of the domain controllers Ability to coordinate multi-domain and multi-layer path
cannot find its domain path computation and path setup operation
Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI]. - End-to-end path computation across multi-domain networks
(based on abstract topology from each domain)
- Domain sequence determination
- Request for path signaling to each domain controller
- Alternative path computation if any of the domain
controllers cannot find its domain path
10. Requirement 10: E2E Path Restoration Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI].
Ability to perform E2E Path Restoration Operation 3. Requirement 3: End-to-End Path Restoration
- Intra-domain recovery Ability to perform end-to-end Path Restoration Operations
- Cross-domain recovery - Intra-domain recovery
- Cross-domain recovery
Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN]. Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN].
11. Requirement 11: Dynamicity of network control operations 4. Requirement 4: Dynamicity of network control operations
The ACTN interfaces should support dynamicity nature of network The ACTN interfaces should support dynamic network control
control operations. This includes but not limited to the operations. This includes, but is not limited to, the following:
following:
- Real-time VN control (e.g., a fast recovery/reroute upon - Real-time VN control (e.g., fast recovery/reroute upon
network failure). network failure).
- Fast convergence of abstracted topologies upon changes due - Fast convergence of abstracted topologies upon changes due
to failure or reconfiguration across the network domain to failure or reconfiguration across the network domain
view, the multi-domain network view and the customer view. view, the multi-domain network view and the customer view.
- Large-scale VN operation (e.g., ability to query tens of - Large-scale VN operation (e.g., the ability to query tens of
thousands of nodes and connectivity) for time-sensitive thousands of nodes, and to examine tens of thousands of
applications. connectivity requests) for time-sensitive applications.
Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI]. Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI].
12. Requirement 12: VN confidentiality/security 5. Requirement 5: Dynamic VN Control
- A VN customer MUST not control other customer's virtual
network
- A VN customer MUST not see any routing information (e.g. IGP
database, TE database) on other customer's virtual network
Reference: [KUMAKI], [FANG], [LOPEZ]
3. ACTN Use-Cases
Listed below is a set of high-level requirements identified by each
of the ACTN use-cases:
- [CHENG] (ACTN Use-cases for Packet Transport Networks in Mobile
Backhaul Networks)
o Faster End-to-End Enterprise Services Provisioning
o Multi-layer coordination in L2/L3 Packet Transport Networks
o Optimizing the network resources utilization (supporting
various performances monitoring matrix, such as traffic flow
statistics, packet delay, delay variation, throughput and
packet-loss rate)
o Virtual Networks Operations for multi-domain Packet Transport
Networks
- [DHODY] (Packet Optical Integration (POI) Use Cases for
Abstraction and Control of Transport Networks (ACTN))
o Packet Optical Integration to support Traffic Planning,
performance Monitoring, automated congestion management and
Automatic Network Adjustments
o Protection and Restoration Synergy in Packet Optical Multi-
layer network.
o Service Awareness and Coordination between Multiple Network
Domains
- [FANG] (ACTN Use Case for Multi-domain Data Center Interconnect)
o Multi-domain Data Center Interconnection to support VM
Migration, Global Load Balancing, Disaster Recovery, On-
demand Virtual Connection/Circuit Services
o The interfaces between the Data Center Operation and each
transport network domain SHOULD support standards-based
abstraction with a common information/data model to support
the following:
. Network Query (Pull Model) from the Data Center
Operation to each transport network domain to collect
potential resource availability (e.g., BW availability,
latency range, etc.) between a few data center
locations.
. Network Path Computation Request from the Data Center
Operation to each transport network domain to estimate
the path availability.
. Network Virtual Connections/Circuits Request from the
Data Center Operation to each transport domain to
establish end-to-end virtual connections/circuits (with
type, concurrency, duration, SLA.QoS parameters,
protection.reroute policy options, policy constraints
such as peering preference, etc.).
. Network Virtual Connections/Circuits Modification
Request
- [KLEE] (ACTN Use-case for On-demand E2E Connectivity Services in
Multiple Vendor Domain Transport Networks)
o Two-stage path computation capability in a hierarchical
control architecture (MDSC-PNC) and a hierarchical
composition of integrated network views
o Coordination of signal flow for E2E connections and
management.
o Abstraction of:
. Inter-connection data between domains
. Customer Endpoint data
. The multiple levels/granularities of the abstraction of
network resource (which is subject to policy and service
need).
. Any physical network constraints (such as SRLG, link Dynamic/On-demand VN Modification/Confirmation with feedback loop
distance, etc.) should be reflected in abstraction. to the customer
. Domain preference and local policy (such as preferred - Traffic monitoring and control policies sent to the network
peering point(s), preferred route, etc.), Domain network - Network states based traffic optimization policies
capability (e.g., support of push/pull model). - Utilization Monitoring (including frequency of reporting)
- Abstraction of Resource Topology reflecting service-related
parameters
- [KUMAKI] (ACTN : Use case for Multi Tenant VNO) Reference: [XU], [XU2], [DHODY], [CHENG]
o On-demand Virtual Network Service Creation 3. ACTN Interfaces Requirements
o Domain Control Plane/Routing Layer Separation
o Independent service Operation for Virtual Services from
control of other domains
o Multiple service level support for each VN (e.g., bandwidth
and latency for each VN service).
o VN diversity/survivability should be met in physical network
mapping.
o VN confidentiality and sharing constraint should be supported.
- [LOPEZ] (ACTN Use-case for Virtual Network Operation for Multiple This section provides detailed ACTN interface requirements for the
Domains in a Single Operator Network) two interfaces that are within the ACTN scope based on [ACTN-Frame]
and the use-cases referenced in this document.
o Creation of a global abstraction of network topology: The VNO The ACTN architecture described in [ACTN-Frame] comprises three
Coordinator assembles each domain level abstraction of functional components:
network topology into a global abstraction of the end-to-end
network.
o End-to-end connection lifecycle management
o Invocation of path provisioning request to each domain
(including optimization requests)
o Invocation of path protection/reroute to the affected
domain(s)
o End-to-end network monitoring and fault management. This could
imply potential KPIs and alarm correlation capabilities.
o End-to-end accounting and generation of detailed records for
resource usage
o End-to-end policy enforcement
- [SHIN] (ACTN Use-case for Mobile Virtual Network Operation for - CNC: Customer Network Controller
Multiple Domains in a Single Operator Network) - MDSC: Multi Domain Service Coordinator
- PNC: Physical Network Controller
o Resource abstraction: operational mechanisms in mobile The architecture gives rise to two interfaces between components:
backhaul network to give the current network usage
information for dynamic and elastic applications to be
provisioned dynamically with QoS guarantee.
o Load balancing or for recovery, the selection of core DC - CMI: CNC-MDSC Interface
location from edge constitutes a data center selection - MPI: MDSC-PNC Interface
problem.
o Multi-layer routing and optimization, coordination between 3.1. CMI Requirements
these two layers.
- [SUZUKI] (Use-case and Requirements for Multi-domain Operation 1. Security/Policy Negotiation ("Who are you?") between CNC and
Plane Change) MDSC
o Operational state data synchronization between multi-domain
controllers
- [XU] (Use Cases and Requirements of Dynamic Service Control based - Trust domain verification (External Entity versus Internal
on Performance Monitoring in ACTN Architecture) Service Department)
- Push/Pull support (for policy)
o Dynamic Service Control Policy enforcement and Traffic/SLA 2. VN Topology Query ("Can you give me VN?") from CNC to MDSC
Monitoring:
. Customer service performance monitoring strategy,
including the traffic monitoring object (the service
need to be monitored)
. monitoring parameters (e.g., transmitted and received
bytes per unit time),
. traffic monitoring cycle (e.g., 15 minutes, 24 hours),
. threshold of traffic monitoring (e.g., high and low
threshold), etc.
- [XU2] (Requirements of Abstract Alarm Report in ACTN architecture - VN end-points (CE end)
- VN Topology Service-specific Multi-Cost Objective Function
o Latency Map
o Available Bandwidth Map
o Latency Map and Available Bandwidth Map together
o Other types
- VN Topology diversity
o Node/Link disjoint from other VNs
o VN Topology level diversity (e.g., VN1 and VN2 must be
disjoint)
- VN Topology type
o Path vector (tunnel)
o Node/Links (graph)
o Dynamic abstract alarm report 3. VN Topology Query Response from MDSC to CNC: "Here's the VN
Topology that can be given to you if you request it"
3.1. Two categories of requirements - For VN Topology,
o This is what can be reserved for you
o This is what is available beyond what you asked for
(potential)
This section provides a summary of use-cases in terms of two 4. Basic VN Instantiation Request/Confirmation between CNC and
categories: (i) service-specific requirements; (ii) network-related MDSC: "I need a VN for my service, please instantiate my VN"
requirements. - VN instance ID
- VN end-points
- VN service requirement
o Latency only
o B/W guarantee
o Latency and B/W guarantee together
- VN diversity
o Node/Link disjoint from other VNs
- VN level diversity (e.g., VN1 and VN2 must be disjoint)
- VN type
o Path vector (tunnel)
o Node/Links (graph)
- VN instance ID per service (unique id to identify VNs)
- If failed to instantiate the requested VN, say why
Service-specific requirements listed below are uniquely applied to 5. Dynamic/On-demand VN Instantiation/Modification and
the work scope of ACTN. Service-specific requirements are related to Confirmation with feedback loop (This is to be differentiated
virtual service coordination function defined in Section 3. These from Basic VN Instantiation)
requirements are related to customer's VNs in terms of service
policy associated with VNs such as service performance objectives,
VN endpoint location information for certain required service-
specific functions (e.g., security and others), VN survivability
requirement, or dynamic service control policy, etc.
Network-related requirements are related to virtual network - Performance/Fault Monitoring
operation function defined in Section 3. These requirements are - Utilization Monitoring (Frequency of report)
related to multi-domain and multi-layer signaling, routing, - Abstraction of Resource Topology reflecting these service-
protection/restoration and synergy, re-optimization/re-grooming, related parameters
etc. These requirements are not inherently unique for the scope of - Dynamic Policy enforcement
ACTN but some of these requirements are in scope of ACTN, especially
for coherent/seamless operation aspect of multiple controller
hierarchy.
The following table gives an overview of service-specific 6. VN lifecycle management/operation
requirements and network-related requirements respectively for each
ACTN use-case and identifies the work in scope of ACTN.
Use-case Service- Network-related Control - Create (same as VN instantiate Request)
specific Requirements Functions/Data - Delete
Requirements Models to be - Modify
supported - Update (VN level OAM Monitoring) under policy agreement
------- -------------- --------------- -------------- 7. Coordination of multi-destination service requirement/policy
[CHENG] - E2E service - Multi-layer - Dynamic to support dynamic applications such as VM migration,
provisioning (L2/L2.5) multi-layer disaster recovery, load balancing, etc.
- Performance coordination coordination
monitoring - VNO for multi- function based
- Resource domain transport on utilization
utilization networks
abstraction - YANG for
utilization
abstraction
------- -------------- ---------------- -------------- - Service-policy primitives and its parameters
[DHODY] - Service - POI - Customer's
awareness/ Performance VN
coordination monitoring survivability
between P/O. - Protection/ policy
Restoration enforcement
synergy for
protection/res
toration
- YANG for 3.2. MPI Requirements
Performance
Monitoring
------- -------------- ---------------- --------------
[FANG] - Dynamic VM - On-demand - Multi-
migration virtual circuit destination
(service), request service
Global load - Network Path selection
balancing Connection policy
(utilization request enforcement
efficiency), function
Disaster
recovery - YANG for
- Service- Service-aware
aware network policy
query enforcement
- Service
Policy
Enforcement
------- -------------- ---------------- --------------
[KLEE] - Two stage path - Multi-domain
computation service policy
E2E signaling coordination
coordination to network
primitives
- Abstraction of
inter-domain - YANG for
info Abstraction of
- Enforcement of peering/
network policy boundary data
(peering, domain
preference)
- Network
capability
exchange
(pull/push,
abstraction
level, etc.)
- on-demand and
long-lived end-
to-end service
provisioning and
monitoring
------- -------------- ---------------- --------------
[KUMAKI] - On-demand VN - Dynamic VN
creation creation,
- Multi- survivability
service level with security/
for VN confi-
- VN dentiality
survivability
/diversity/con
fidentiality
------- -------------- ---------------- -------------- 1. Security/Policy negotiation ("Who are you?")
[LOPEZ] - E2E - E2E connection - Escalation
accounting and management, path of performance
resource usage provisioning and fault
data - E2E network management
- E2E service monitoring and data to CNC
policy fault management and the policy
enforcement enforcement
- YANG for
performance
and fault
management
------- -------------- ---------------- -------------- - Exchange of key, etc.
- Domain preference + local policy exchange
- Push/Pull support
- Preferred peering points
- Preferred route
- Reroute policy
- End-point mobility (for multi-destination)
[SHIN] - Current - LB for - Multi-layer 2. Topology Query /Response (Pull Model from MDSC to PNC: "Please
network recovery routing and give me your domain topology")
resource - Multi-layer optimization
abstraction routing and - VN's dynamic
Endpoint/DC optimization endpoint
dynamic coordination selection
selection (for policy.
VM migration)
------- -------------- ---------------- -------------- - TED Abstraction level negotiation
[SUZUKI] - Operational - Operations - Abstract topology (per policy)
Data/State DB sync o Node/Link metrics
between multi- function o Node/Link Type (Border/Gateway, etc.)
domain across o All TE metrics (SRLG, etc.)
controllers controllers o Topology Metrics (latency, B/W available, etc.)
- YANG for 3. Topology Update (Push Model from PNC to MDSC: "The topology
operational has been updated")
data/state
model
------- -------------- ---------------- --------------
[XU]/ - Dynamic - Traffic - Dynamic
[XU2] service monitoring service
control policy - SLA monitoring control policy
enforcement enforcement
- Dynamic control
service
control - YANG for
traffic
monitoring
abstraction,
alarm
abstraction.
4. ACTN interfaces requirements - Under policy agreement, topology changes to be pushed to
MDSC from PNC
This section provides detailed ACTN interface requirements for the 4. VN Path Computation Request (From MDSC to PNC: "Please give me
two interfaces that are within the ACTN scope based on [ACTN-Frame] a path in your domain")
and the use-cases referenced in this document.
. CMI: CNC-MDSC Interface - VN Instance ID (Note: this is passed from CNC to MDSC)
. MPI: MDSC-PNC Interface - End-point information
4.1. CMI Requirements - CE ends
- Border points (if applicable)
- All other PCE request info (PCEP)
Requirement 5. VN Path Computation Reply ("Here's the path info per your
1. Security/Policy Negotiation (Who are you?) (Between CNC and Request")
MDSC) - Path level abstraction
- Configured vs. Discovered - LSP DB
- Trust domain verification (External Entity vs. Internal - LSP ID
Service Department) - VN ID
- Push/Pull support (for policy)
2. VN Topology Query (Can you give me VN?) (From CNC to MDSC)
- VN end-points (CE end)
- VN Topology Service-specific Multi-Cost Objective Function
o Latency Map
o Available B/W Map
o Latency Map and Available B/W Map together
o Other types
- VN Topology diversity
o Node/Link disjoint from other VNs
o VN Topology level diversity (e.g., VN1 and VN2 must be
disjoint)
- VN Topology type
o Path vector (tunnel)
o Node/Links (graph)
3. VN Topology Query Response (From MDSC to CNC: Here's the VN
Topology that can be given to you if you accept)
- For VN Topology,
o This is what can be reserved for you
o This is what is available beyond what is given to you
(potential)
4. VN Topology Abstraction Model (generic network model)
5. VN Topology Abstraction Model (Service-specific model that
include customer endpoints)
6. Basic VN Instantiation Request/Confirmation (Between CNC and
MDSC: I need VN for my service, please instantiate my VN)
- VN instance ID
- VN end-points
- VN service requirement
o Latency only
o B/W guarantee
o Latency and B/W guarantee together
- VN diversity
o Node/Link disjoint from other VNs
- VN level diversity (e.g., VN1 and VN2 must be disjoint)
- VN type
o Path vector (tunnel)
o Node/Links (graph)
- VN instance ID per service (unique id to identify VNs)
- If failed to instantiate the requested VN, say why
7. Dynamic/On-demand VN Instantiation/Modification and
Confirmation with feedback loop (This is to be differentiated
from Basic VN Instantiation)
- Performance/Fault Monitoring
- Utilization Monitoring (Frequency of report)
- Abstraction of Resource Topology reflecting these service-
related parameters
- Dynamic Policy enforcement
8. VN lifecycle management/operation 6. Coordination of multi-domain Centralized Signaling Path Setup
- Create (same as VN instantiate Request) Operation (From MDSC to PNC: "Please give me your domain path
- Delete if you can; otherwise, let me know if that is not possible."
- Modify
- Update (VN level OAM Monitoring) under policy agreement
9. Coordination of multi-destination service requirement/policy
to support dynamic applications such as VM migration,
disaster recovery, load balancing, etc.
- Service-policy primitives and its parameters
4.2. MPI Requirements - MSDC computes E2E path across multi-domain (based on abstract
topology from each PNC)
- MDSC determines the domain sequence
- MDSC request path signaling to each PNC (domain)
- MDSC finds alternative path if any of the PNCs cannot find
its domain path
o PNC will crankback to MDSC if it cannot find its domain
path
o PNC will confirm to MDSC if it finds its domain path
Requirement 7. Path Restoration Operation after an E2E path is setup
1. Security/Policy negotiation (who are you?) successfully, some domain had a failure that cannot be restored
- Exchange of key, etc. by the PNC domain (From PNC to MDSC: "My domain path failed and
- Domain preference + local policy exchange I cannot restore it."; From MDSC to PNC: "OK. Please set up a
- Push/Pull support new domain path with this ingress/egress nodes."
- Preferred peering points
- Preferred route
- Reroute policy
- End-point mobility (for multi-destination)
2. Topology Query /Response (Pull Model from MDSC to PNC: Please
give me your domain topology)
- TED Abstraction level negotiation
- Abstract topology (per policy)
o Node/Link metrics
o Node/Link Type (Border/Gateway, etc.)
o All TE metrics (SRLG, etc.)
o Topology Metrics (latency, B/W available, etc.)
3. Topology Update (Push Model from PNC to MDSC) - The problem PNC will send this notification with changed
- Under policy agreement, topology changes to be pushed to MDSC abstract topology (computed after resource changes due to
from PNC failure/other factors)
- MDSC will find an alternate E2E path based on the changes
reported from PNC. It will need to update the E2E abstract
topology and the affected CN's VN topology in real-time (This
refers to dynamic synchronization of topology from Physical
topology to abstract topology to VN topology)
- MDSC will perform the path restoration signaling to the
affected PNCs.
4. VN Path Computation Request (From MDSC to PNC: Please give me 8. Coordination of Multi-destination service restoration
a path in your domain) operation: the CNC may have, for example, multiple endpoints
- VN Instance ID (Note: this is passed from CNC to MDSC) where the source can send its data to either one of the
- End-point information endpoints. (From PNC to MDSC, "I lost my connectivity to the
- CE ends endpoint. Please help to find alternative endpoint."; From MDSC
- Border points (if applicable) to PNC, "Please use this alternative endpoint.")
- All other PCE request info (PCEP)
5. VN Path Computation Reply (here's the path info per your - When PNC reports domain problem that cannot be resolved at
request) PNC level because of there is no network restoration path to
- Path level abstraction a given destination, then MDSC has customers' profile in
- LSP DB which to find the customer has "multi-destination"
- LSP ID ?? application.
- VN ID - Under policy A, MDSC will be allowed to reroute the customer
traffic to one of the pre-negotiated destinations and
proceed with restoration of this particular customer's
traffic.
- Under policy B, CNC may reroute on its VN topology level and
push this to MDSC and MDSC maps this into its abstract
topology and proceed with restoration of this customer's
traffic.
- In either case, the MDSC will proceed its restoration
operation (as explained in Req. 7) to the corresponding
PNCs.
6. Coordination of multi-domain Centralized Signaling (MSDC 9. MDSC-PNC policy negotiation is also needed as to how
operation) Path Setup Operation restoration is done across MDSC and PNCs. (From MDSC to PNC:
- MSDC computes E2E path across multi-domain (based on abstract "Please resolve at your domain for restoration of LSP."
topology from each PNC)
- MDSC determines the domain sequence
- MDSC request path signaling to each PNC (domain)
- MDSC finds alternative path if any of the PNCs cannot find its
domain path
o PNC will crankback to MDSC if it cannot find its domain
path
o PNC will confirm to MDSC if it finds its domain path
7. Path Restoration Operation (after an E2E path is setup
successfully, some domain had a failure that cannot be
restored by the PNC domain)
- The problem PNC will send this notification with changed
abstract topology (computed after resource changes due to
failure/other factors)
- MDSC will find an alternate E2E path based on the changes
reported from PNC. It will need to update the E2E abstract
topology and the affected CN's VN topology in real-time (This
refers to dynamic synchronization of topology from Physical
topology to abstract topology to VN topology)
- MDSC will perform the path restoration signaling to the
affected PNCs.
8. Coordination of Multi-destination service restoration
operation (CNC have, for example, multiple endpoints where the
source endpoint can send its data to either one of the
endpoints)
- When PNC reports domain problem that cannot be resolved at
MDSC level because of there is no network restoration path to
a given destination.
- Then MDSC has Customers' profile in which to find the customer
has "multi-destination" application.
- Under policy A, MDSC will be allowed to reroute the customer
traffic to one of the pre-negotiated destinations and proceed
with restoration of this particular customer's traffic.
- Under policy B, CNC may reroute on its VN topology level and
push this to MDSC and MDSC maps this into its abstract
topology and proceed with restoration of this customer's
traffic.
- In either case, the MDSC will proceed its restoration
operation (as explained in Req. 6) to the corresponding PNCs.
9. MDSC-PNC policy negotiation is also needed as to how 10. Generic Abstract Topology Update per changes due to new path
restoration is done across MDSC and PNCs. setup/connection failure/degradation/restoration (From PNC to
MDSC: "Here's an updated topology")
10. Generic Abstract Topology Update per changes due to new 11. Service-specific Abstract Topology Update per changes due
path setup/connection failure/degradation/restoration to new path setup/connection failure/degradation/restoration
11. Service-specific Abstract Topology Update per changes due (From PNC to MDSC: "Here's an updated service-specific
to new path setup/connection failure/degradation/restoration topology")
12. Abstraction model of technology-specific topology element
5. References 4. References
5.1. Informative References 4.1. Normative References
[ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and
Control of Transport Networks", draft-ietf-teas-actn- Control of Transport Networks", draft-ietf-teas-actn-
framework, work in progress. framework, work in progress.
4.2. Informative References
[CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport [CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport
Networks in Mobile Backhaul Networks", draft-cheng-actn- Networks in Mobile Backhaul Networks", draft-cheng-actn-
ptn-requirements, work in progress. ptn-requirements, work in progress.
[DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use [DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use
Cases for Abstraction and Control of Transport Networks Cases for Abstraction and Control of Transport Networks
(ACTN)", draft-dhody-actn-poi-use-case, work in progress. (ACTN)", draft-dhody-actn-poi-use-case, work in progress.
[FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center [FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center
Interconnect", draft-fang-actn-multidomain-dci, work in Interconnect", draft-fang-actn-multidomain-dci, work in
progress. progress.
[KLEE] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for E2E [KLEE] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for E2E
Network Services in Multiple Vendor Domain Transport Network Services in Multiple Vendor Domain Transport
Networks", draft-klee-teas-actn-connectivity-multi-domain, Networks", draft-klee-teas-actn-connectivity-multi-domain,
work-in-progress. work-in-progress.
[KUMAKI] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant [KUMAKI] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant
VNO ", draft-kumaki-teas-actn-multitenant-vno, work in VNO", draft-kumaki-teas-actn-multitenant-vno, work in
progress. progress.
[LOPEZ] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation [LOPEZ] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation
for Multiple Domains in a Single Operator Network", draft- for Multiple Domains in a Single Operator Network", draft-
lopez-actn-vno-multidomains, work in progress. lopez-actn-vno-multidomains, work in progress.
[SHIN] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual [SHIN] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual
Network Operation for Multiple Domains in a Single Network Operation for Multiple Domains in a Single
Operator Network", draft-shin-actn-mvno-multi-domain, work Operator Network", draft-shin-actn-mvno-multi-domain, work
in progress. in progress.
skipping to change at page 22, line 13 skipping to change at page 15, line 9
work in progress. work in progress.
[XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN [XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN
architecture", draft-xu-teas-actn-abstract-alarm-report, architecture", draft-xu-teas-actn-abstract-alarm-report,
work-in-progress. work-in-progress.
[SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi- [SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi-
domain Operation Plane Change", draft-suzuki-teas-actn- domain Operation Plane Change", draft-suzuki-teas-actn-
multidomain-opc, work-in-progress. multidomain-opc, work-in-progress.
6. Contributors 5. Contributors
Contributors' Addresses
Kwangkook Lee Kwangkook Lee
KT KT
Email: kwangkooglee@gmail.com Email: kwangkooglee@gmail.com
Takuya Miyasaka Takuya Miyasaka
KDDI KDDI
Email: ta-miyasaka@kddi.com Email: ta-miyasaka@kddi.com
Yunbin Xu Yunbin Xu
 End of changes. 104 change blocks. 
586 lines changed or deleted 333 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/