[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 draft-ietf-teas-actn-requirements

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

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

                                                     Daniele Ceccarelli
                                                               Ericsson



                                                          July 27, 2015



     Requirements for Abstraction and Control of Transport Networks

                  draft-lee-teas-actn-requirements-01.txt


Abstract

   This draft provides a set of requirements for abstraction and
   control of transport networks.



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




Lee, et. al.           Expires October 27, 2016                [Page 1]


Internet-Draft             ACTN Requirement                  April 2015


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

   This Internet-Draft will expire on October 27, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   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
   2. High-level ACTN requirements...................................3
   3. ACTN Use-Cases.................................................7
      3.1. Two categories of requirements...........................10
   4. ACTN interfaces requirements..................................14
      4.1. CMI Interface Requirements...............................15
      4.2. MPI (MDSC-PNC Interface).................................17
   5. References....................................................20
      5.1. Informative References...................................20
   6. Contributors..................................................21
   Contributors' Addresses..........................................21
   Authors' Addresses...............................................21

1. Introduction

   This draft provides a set of requirements for ACTN identified in
   various use-cases of ACTN. [ACTN-frame] defines the base reference
   architecture and terminology. [ACTN-PS] provides problem statement
   and gap analysis.






Lee, et, al.           Expires January 27, 2016                [Page 2]


Internet-Draft             ACTN Requirement                  April 2015


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

2. High-level ACTN requirements



     1. Requirement 1: Single Virtualized Network Topology

      Ability 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 to provide service requirement/policy (Between Customer
      and Network) and mechanism to enforce service level agreement.

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

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



     3. Requirement 3: 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
               disjoint)

            - VN Topology type: path, graph



Lee, et, al.           Expires January 27, 2016                [Page 3]


Internet-Draft             ACTN Requirement                  April 2015


       -  Response includes VN topology

            - Exact

            - Potential

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



     4. Requirement 4: VN Instantiate

      Ability to request/confirm VN Instantiation

       - VN instance ID

       - 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

            - Path  (tunnel), Node/Links (graph)

       - VN instance ID per service  (unique id to identify VNs)

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



     5. Requirement 5: Dynamic VN Control

      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


Lee, et, al.           Expires January 27, 2016                [Page 4]


Internet-Draft             ACTN Requirement                  April 2015


       - 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

       - Update (VN level OAM Monitoring) under policy agreement

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



     7. Requirement 7: VN Service Operation

      Ability to setup and manage end-2-end service on the VN involving
      multi-domain, multi-layer, meeting constraints based on SLAs.

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



     8. Requirement 8: 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 parameters

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



     9. Requirement 9: Multi-domain & Multi-layer Coordination


Lee, et, al.           Expires January 27, 2016                [Page 5]


Internet-Draft             ACTN Requirement                  April 2015


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

       - Computes E2E path across multi-domain (based on abstract
          topology from each domain)

       - Determines the domain sequence

       - Request path signaling to each domain controller

       - Find alternative path if any of the domain controllers cannot
          find its domain path

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



     10. Requirement 10: E2E Path Restoration

      Ability to perform E2E Path Restoration Operation

       - Intra-domain recovery

       - Cross-domain recovery

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



     11. Requirement 11: Dynamicity of network control operations

      The ACTN interfaces should support dynamicity nature of network
      control operations. This includes but not limited 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., ability to query tens of
           thousands of nodes and connectivity) for time-sensitive
           applications.

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

     12. Requirement 12: VN confidentiality/security


Lee, et, al.           Expires January 27, 2016                [Page 6]


Internet-Draft             ACTN Requirement                  April 2015


        - 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



Lee, et, al.           Expires January 27, 2016                [Page 7]


Internet-Draft             ACTN Requirement                  April 2015


          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)


Lee, et, al.           Expires January 27, 2016                [Page 8]


Internet-Draft             ACTN Requirement                  April 2015


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




Lee, et, al.           Expires January 27, 2016                [Page 9]


Internet-Draft             ACTN Requirement                  April 2015


       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




Lee, et, al.           Expires January 27, 2016               [Page 10]


Internet-Draft             ACTN Requirement                  April 2015


   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.











































Lee, et, al.           Expires January 27, 2016               [Page 11]


Internet-Draft             ACTN Requirement                  April 2015


    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


Lee, et, al.           Expires January 27, 2016               [Page 12]


Internet-Draft             ACTN Requirement                  April 2015


                                    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

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


Lee, et, al.           Expires January 27, 2016               [Page 13]


Internet-Draft             ACTN Requirement                  April 2015


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

   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.

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







Lee, et, al.           Expires January 27, 2016               [Page 14]


Internet-Draft             ACTN Requirement                  April 2015


     4.1. CMI Interface Requirements
















































Lee, et, al.           Expires January 27, 2016               [Page 15]


Internet-Draft             ACTN Requirement                  April 2015


   Requirement
   1. Security/Policy Negotiation (Who are you?) (Between CNC and
     MDSC)
   - Configured vs. Discovered
   - Trust domain verification (External Entity vs. Internal
     Service Department)
   - 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


Lee, et, al.           Expires January 27, 2016               [Page 16]


Internet-Draft             ACTN Requirement                  April 2015



   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
   - Create (same as VN instantiate Request)
   - Delete
   - 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 (MDSC-PNC Interface)


























Lee, et, al.           Expires January 27, 2016               [Page 17]


Internet-Draft             ACTN Requirement                  April 2015


   Requirement
   1. Security/Policy negotiation (who are 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
     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)
   - Under policy agreement, topology changes to be pushed to MDSC
     from PNC

   4. VN Path Computation Request (From MDSC to PNC: Please give me
     a path in your 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 the path info per your
     request)
   - Path level abstraction
   - LSP DB
   - LSP ID ??
   - VN ID

   6. Coordination of multi-domain Centralized Signaling (MSDC
     operation) Path Setup Operation
   - 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


Lee, et, al.           Expires January 27, 2016               [Page 18]


Internet-Draft             ACTN Requirement                  April 2015


          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
     restoration is done across MDSC and PNCs.

   10.   Generic Abstract Topology Update per changes due to new
     path setup/connection failure/degradation/restoration
   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






Lee, et, al.           Expires January 27, 2016               [Page 19]


Internet-Draft             ACTN Requirement                  April 2015


5. References

    5.1. Informative References





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

   [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 ", 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.



Lee, et, al.           Expires January 27, 2016               [Page 20]


Internet-Draft             ACTN Requirement                  April 2015


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





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




Lee, et, al.           Expires January 27, 2016               [Page 21]


Internet-Draft             ACTN Requirement                  April 2015



   Sergio Belotti
   Alcatel Lucent
   Via Trento, 30
   Vimercate, Italy
   Email: sergio.belotti@alcatel-lucent.com

   Khuzema Pithewan
   Infinera
   Email: kpithewan@infinera.com


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
































Lee, et, al.           Expires January 27, 2016               [Page 22]


Html markup produced by rfcmarkup 1.127, available from https://tools.ietf.org/tools/rfcmarkup/