wdiff draft-ietf-teas-actn-requirements-03.txt draft-ietf-teas-actn-requirements-04.txt

Network Working Group Young Lee (Editor)
Dhruv Dhody
Internet Draft Huawei

Intended status: Informational Sergio Belotti
Alcatel-Lucent
Expires: January July 2017
Khuzema Pithewan
Infinera

Daniele Ceccarelli
Ericsson

July 6, 2016

January 3, 2017

Requirements for Abstraction and Control of TE Networks

draft-ietf-teas-actn-requirements-03.txt

draft-ietf-teas-actn-requirements-04.txt

Abstract

This draft document provides a set of requirements for abstraction and
control of TE networks. 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

This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on January 6, July 3, 2017.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction...................................................2 Introduction...................................................3
2. High-level ACTN requirements...................................4
2.1. Service-Specific Requirements.............................4
2.2. Network-Related Requirements..............................7
3. ACTN Use-Cases.................................................8 Interfaces Requirements...................................8
3.1. Two categories of requirements...........................11 CMI Requirements..........................................9
3.2. MPI Requirements.........................................11
4. ACTN interfaces requirements..................................15 References....................................................13
4.1. CMI Requirements.........................................16 Normative References.....................................13
4.2. MPI Requirements.........................................18
5. References....................................................21
5.1. Informative References...................................21
6. Contributors..................................................22
Contributors' Addresses..........................................22 References...................................14
5. Contributors..................................................15
Authors' Addresses...............................................22 Addresses...............................................15

1. Introduction

This draft document provides a set of requirements for Abstraction and
Control of TE Traffic Engineering (TE) Networks (ACTN) identified in
various use-cases of
ACTN. use-cases. [ACTN-frame] defines the base reference
architecture and terminology. [ACTN-PS] provides problem statement and gap analysis.

ACTN refers to the set of virtual network operations needed to
orchestrate, control and manage large-scale multi-domain TE networks
so as to facilitate network programmability, automation, efficient
resource sharing, and end-to-end virtual service aware connectivity
and network function virtualization services.

These operations are summarized as follows:

- Abstraction and coordination of underlying network resources
to higher-layer applications and customers,
independent of how these resources are managed or controlled,
so that these higher-layer entities can dynamically control virtual
networks.
networks based on those resources. Control includes creating,
modifying, monitoring, and deleting virtual networks.

- Multi-domain and multi-tenant virtual network operations via
hierarchical abstraction Collation of the resources from multiple TE domains that facilitates
multi-administration, multi-vendor, and multi-technology networks as (multiple
technologies, equipment from multiple vendors, under the
control of multiple administrations) through a process of
hierarchical abstraction to present a customer with a single virtualized
virtual network. This is achieved chieved by presenting the network
domain as an abstracted topology to the
customers customer via open and
programmable interfaces. Hierarchical abstraction allows for
the recursion of controllers in a customer-provider
relationship.

- Orchestration of end-to-end virtual network services and
applications via allocation of network resources to meet
specific service, application and customer requirements.

- Adaptation of customer requests (made on (to control virtual resources)
to the physical network resources performing the necessary
mapping, translation, isolation and, policy that allows
conveying, managing and enforcing customer policies with
respect to the services by and the network to said of the customer.

- Provision via a data model of a computation scheme and virtual
control capability via a data model to customers who request virtual network
services. Note that these customers could, themselves, be
service providers.

ACTN solutions will build on, and extend, existing TE constructs and
TE mechanisms wherever possible and appropriate. Support for
controller-based approaches is specifically included in the possible
solution set.

Section 2 provides high-level ACTN requirements. Sections 3-5
provide the list of Section 3 provides
ACTN use-cases and the detailed requirement
analysis of these use-cases. interface requirements.

2. High-level ACTN requirements

1. Requirement 1: Single Virtualized Network Topology

Ability

This section provides a summary of use-cases in terms of two
categories: (i) service-specific requirements; (ii) network-related
requirements.

Service-specific requirements listed below are uniquely applied to build virtual network operation infrastructure based
on multi-layer, multi-domain topology abstracted from multiple
physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS,
etc.)

Reference: [KLEE], [LOPEZ], [DHODY], [CHENG].

2. Requirement 2: Policy Enforcement

Ability
the work scope of ACTN. Service-specific requirements are related to provide
the virtual service requirement/policy (between Customer
and Network) and mechanism coordination function. These requirements are
related to enforce customer's VNs in terms of service level agreement.

- Endpoint selection policy, routing policy, time-related
policy, etc.

Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG].

3. Requirement 3: VN Query 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 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.1. Service-Specific Requirements

1. Requirement 1: Policy Enforcement

Ability to provide service requirement/policy (between Customer
and Network) and mechanism to enforce Service Level Agreements
(SLA).

- Endpoint selection policy, routing policy, time-related
policy, etc.

Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG].

2. Requirement 2: Virtual Network (VN) Query

Ability to request/respond VN Query (Can ("Can you give me VN(s)?)

- these
VN(s)?")

Request Input:

- VN end-points (CE end) (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) disjoint;
Node/link disjoint from other VNs)
- VN Topology type: path, graph

Response includes VN topology topology:

- Exact
- Potential

Reference: [KUMAKI], [FANG], [CHENG].

3. Requirement 4: 3: VN Instantiate Instantiation ("Please create a VN for me")

Ability to request/confirm VN Instantiation

Request Input:

- VN instance ID
- VN end-points (Customer Edge equipment)
- VN Topology Service-specific Multi-Cost Objective Function
- VN constraints requirement

-
o Latency only, B/W bandwidth guarantee, Latency joint latency and B/W
bandwidth guarantee
together

- VN diversity

- Node/Link disjoint from other VNs
- VN level Topology diversity (e.g., VN1 and VN2 must be disjoint) disjoint;
Node/link disjoint from other VNs)
- VN type Topology type: path, graph

Response includes VN topology:

- Path (tunnel), Node/Links (graph) Exact
- VN instance ID per service (unique id to identify VNs) Potential

Reference: [KUMAKI], [FANG], [CHENG].

4. Requirement 5: Dynamic VN Control

Dynamic/On-demand 4: VN Modification/Confirmation with feedback loop Lifecycle Management & Operation (M&O)

Ability to do the customer following VN operations:

- Traffic monitoring and control policies sent to the network Delete
- 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 Modify
- Update (VN level OAM Operations, Administration and Management
(OAM) Monitoring) under policy agreement

Reference: [FANG], [KUMAKI], [LOPEZ].

5. Requirement 7: 5: VN Service Operation

Ability to setup set up and manage end-2-end service end-to-end services on the VN
involving
multi-domain, multi-layer, multi-domain and multi-layer operations of the
underlying network while meeting constraints based on SLAs.

Reference: [LOPEZ], [KUMAKI], [CHENG], [DHODY], [FANG], [KLEE].

6. Requirement 8: Multi-destination 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
support dynamic applications such as VM migration, disaster
recovery, load balancing, etc.

- Service-policy primitives and its their parameters

Reference: [FANG], [LOPEZ], [SHIN].

2.2. Network-Related Requirements

1. Requirement 9: Multi-domain 1: Single Virtualized Network Topology

Ability to build virtual network operation infrastructure based
on multi-layer, multi-domain topology abstracted from multiple
physical network control mechanisms (e.g., GMPLS, OpenFlow, PCE,
NMS, etc.)

Reference: [KLEE], [LOPEZ], [DHODY], [CHENG].

2. Requirement 2: Multi-Domain & Multi-layer Coordination

Ability to Coordinate coordinate multi-domain and multi-layer path
computation and path setup operation (network)

- E2E End-to-end path computation across multi-domain networks
(based on abstract topology from each domain)
- The 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

Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI].

10.

3. Requirement 10: E2E 3: End-to-End Path Restoration

Ability to perform E2E end-to-end Path Restoration Operation Operations

- Intra-domain recovery
- Cross-domain recovery

Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN].

11.

4. Requirement 11: 4: Dynamicity of network control operations

The ACTN interfaces should support dynamicity nature of dynamic network control
operations. This includes includes, but is not limited to to, the following:

- Real-time VN control (e.g., a fast recovery/reroute upon
network failure).
- Fast convergence of abstracted topologies upon changes due
to failure or reconfiguration across the network domain
view, the multi-domain network view and the customer view.
- Large-scale VN operation (e.g., the ability to query tens of
thousands of nodes nodes, and connectivity) for time-sensitive
applications.

Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI].

12. Requirement 12: VN confidentiality/security

- 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 to examine tens of high-level requirements identified by each thousands 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
distance, etc.) should be reflected in abstraction.

. Domain preference and local policy (such as preferred
peering point(s), preferred route, etc.), Domain network
capability (e.g., support of push/pull model).

- [KUMAKI] (ACTN : Use case for Multi Tenant VNO)

o On-demand Virtual Network Service Creation
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
Domains in a Single Operator Network)

o Creation of a global abstraction of network topology: The VNO
Coordinator assembles each domain level abstraction of
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
Multiple Domains in a Single Operator Network)

o Resource abstraction: operational mechanisms in mobile
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
location from edge constitutes a data center selection
problem.

o Multi-layer routing and optimization, coordination between
these two layers.

- [SUZUKI] (Use-case and Requirements for Multi-domain Operation
Plane Change)
o Operational state data synchronization between multi-domain
controllers

- [XU] (Use Cases and Requirements of Dynamic Service Control based
on Performance Monitoring in ACTN Architecture)

o Dynamic Service Control Policy enforcement and Traffic/SLA
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

o Dynamic abstract alarm report

3.1. Two categories of requirements

This section provides a summary of use-cases in terms of two
categories: (i) service-specific requirements; (ii) network-related
requirements.

Service-specific requirements listed below are uniquely applied to
the work scope of ACTN. Service-specific requirements are related to
virtual service coordination function defined in Section 3. These
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
operation function defined in Section 3. 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.

The following table gives an overview of service-specific
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
specific Requirements Functions/Data
Requirements Models to be
supported

------- -------------- --------------- --------------
[CHENG] - E2E service - Multi-layer - Dynamic
provisioning (L2/L2.5) multi-layer
- Performance coordination coordination
monitoring - VNO for multi- function based
- Resource domain transport on utilization
utilization networks
abstraction - YANG for
utilization
abstraction

------- -------------- ---------------- --------------
[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
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

------- -------------- ---------------- --------------
[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

------- -------------- ---------------- --------------

[SHIN] - Current - LB for - Multi-layer
network recovery routing and
resource - Multi-layer optimization
abstraction routing and - VN's dynamic
Endpoint/DC optimization endpoint
dynamic coordination selection
selection (for policy.
VM migration)

------- -------------- ---------------- --------------
[SUZUKI] - Operational - Operations
Data/State DB sync
between multi- function
domain across
controllers controllers

- YANG
connectivity requests) for
operational
data/state
model
------- -------------- ---------------- --------------
[XU]/ - time-sensitive applications.

Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI].

5. Requirement 5: Dynamic VN Control

Dynamic/On-demand VN Modification/Confirmation with feedback loop
to the customer

- Traffic - Dynamic
[XU2] service monitoring service and control policy policies sent to the network
- SLA monitoring control policy
enforcement enforcement Network states based traffic optimization policies
- Dynamic control
service
control Utilization Monitoring (including frequency of reporting)
- YANG for
traffic
monitoring
abstraction,
alarm
abstraction.

4. Abstraction of Resource Topology reflecting service-related
parameters

Reference: [XU], [XU2], [DHODY], [CHENG]

3. ACTN interfaces requirements Interfaces Requirements

This section provides detailed ACTN interface requirements for the
two interfaces that are within the ACTN scope based on [ACTN-Frame]
and the use-cases referenced in this document.

The ACTN architecture described in [ACTN-Frame] comprises three
functional components:

- CNC: Customer Network Controller
- MDSC: Multi Domain Service Coordinator
- PNC: Physical Network Controller

The architecture gives rise to two interfaces between components:

- CMI: CNC-MDSC Interface
.
- MPI: MDSC-PNC Interface
4.1.

3.1. CMI Requirements

Requirement

1. Security/Policy Negotiation (Who ("Who are you?) (Between you?") between CNC and
MDSC)
- Configured vs. Discovered
MDSC

- Trust domain verification (External Entity vs. versus Internal
Service Department)
- Push/Pull support (for policy)

2. VN Topology Query (Can ("Can you give me VN?) (From VN?") from CNC to MDSC) MDSC

- VN end-points (CE end)
- VN Topology Service-specific Multi-Cost Objective Function
o Latency Map
o Available B/W Bandwidth Map
o Latency Map and Available B/W 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)

3. VN Topology Query Response (From from MDSC to CNC: Here's "Here's the VN
Topology that can be given to you if you accept) request it"

- For VN Topology,
o This is what can be reserved for you
o This is what is available beyond what is given to you asked for
(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 between CNC and
MDSC: I "I need a VN for my service, please instantiate my VN) 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.

5. 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

6. VN lifecycle management/operation

- Create (same as VN instantiate Request)
- Delete
- Modify
- Update (VN level OAM Monitoring) under policy agreement
9.

7. 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.

3.2. MPI Requirements

Requirement

1. Security/Policy negotiation (who ("Who are you?) you?")

- 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)

2. Topology Query /Response (Pull Model from MDSC to PNC: Please "Please
give me your domain topology) 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) MDSC: "The topology
has been updated")

- Under policy agreement, topology changes to be pushed to
MDSC from PNC

4. VN Path Computation Request (From MDSC to PNC: Please "Please give me
a path in your domain) domain")

- VN Instance ID (Note: this is passed from CNC to MDSC)
- End-point information
- CE ends
- Border points (if applicable)
- All other PCE request info (PCEP)

5. VN Path Computation Reply (here's ("Here's the path info per your
request)
Request")
- Path level abstraction
- LSP DB
- LSP ID ??
- VN ID

6. Coordination of multi-domain Centralized Signaling (MSDC
operation) Path Setup
Operation (From MDSC to PNC: "Please give me your domain path
if you can; otherwise, let me know if that is not possible."

- 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

7. Path Restoration Operation (after after an E2E path is setup
successfully, some domain had a failure that cannot be restored
by the PNC domain) domain (From PNC to MDSC: "My domain path failed and
I cannot restore it."; From MDSC to PNC: "OK. Please set up a
new domain path with this ingress/egress nodes."

- 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
operation: the CNC may have, for example, multiple endpoints
where the source endpoint can send its data to either one of the
endpoints)
endpoints. (From PNC to MDSC, "I lost my connectivity to the
endpoint. Please help to find alternative endpoint."; From MDSC
to PNC, "Please use this alternative endpoint.")

- When PNC reports domain problem that cannot be resolved at
MDSC
PNC level because of there is no network restoration path to
a given destination.
- Then destination, then MDSC has Customers' 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) 7) to the corresponding
PNCs.

9. MDSC-PNC policy negotiation is also needed as to how
restoration is done across MDSC and PNCs. (From MDSC to PNC:
"Please resolve at your domain for restoration of LSP."

10. Generic Abstract Topology Update per changes due to new path
setup/connection failure/degradation/restoration (From PNC to
MDSC: "Here's an updated topology")

11. Service-specific Abstract Topology Update per changes due
to new path setup/connection failure/degradation/restoration
12. Abstraction model of technology-specific topology element

5.
(From PNC to MDSC: "Here's an updated service-specific
topology")

4. References

5.1. Informative

4.1. Normative References

[ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and
Control of Transport Networks", draft-ietf-teas-actn-
framework, work in progress.

4.2. Informative References

[CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport
Networks in Mobile Backhaul Networks", draft-cheng-actn-
ptn-requirements, work in progress.

[DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use
Cases for Abstraction and Control of Transport Networks
(ACTN)", draft-dhody-actn-poi-use-case, work in progress.

[FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center
Interconnect", draft-fang-actn-multidomain-dci, work in
progress.

[KLEE] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for E2E
Network Services in Multiple Vendor Domain Transport
Networks", draft-klee-teas-actn-connectivity-multi-domain,
work-in-progress.

[KUMAKI] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant
VNO ",
VNO", draft-kumaki-teas-actn-multitenant-vno, work in
progress.

[LOPEZ] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation
for Multiple Domains in a Single Operator Network", draft-
lopez-actn-vno-multidomains, work in progress.

[SHIN] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual
Network Operation for Multiple Domains in a Single
Operator Network", draft-shin-actn-mvno-multi-domain, work
in progress.

[XU] Y. Xu, et. al., "Use Cases and Requirements of Dynamic Service
Control based on Performance Monitoring in ACTN
Architecture", draft-xu-actn-perf-dynamic-service-control,
work in progress.

[XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN
architecture", draft-xu-teas-actn-abstract-alarm-report,
work-in-progress.

[SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi-
domain Operation Plane Change", draft-suzuki-teas-actn-
multidomain-opc, work-in-progress.

5. Contributors

Contributors' Addresses

Kwangkook Lee
KT
Email: kwangkooglee@gmail.com

Takuya Miyasaka
KDDI
Email: ta-miyasaka@kddi.com

Yunbin Xu
CATR
Email: xuyunbin@mail.ritt.com.cn

Toshiaki Suzuki
Hitachi
Email: toshiaki.suzuki.cs@hitachi.com

Authors' Addresses

Young Lee (Editor)
Huawei Technologies
5340 Legacy Drive
Plano, TX 75023, USA
Phone: (469)277-5838
Email: leeyoung@huawei.com

Dhruv Dhody
Huawei Technologies
Email: dhruv.ietf@gmail.com

Sergio Belotti
Nokia
Via Trento, 30
Vimercate, Italy
Email: sergio.belotti@nokia.com

Khuzema Pithewan
Infinera
Email: kpithewan@infinera.com

Daniele Ceccarelli
Ericsson
Torshamnsgatan,48
Stockholm, Sweden
Email: daniele.ceccarelli@ericsson.com