idnits 2.17.1 draft-lee-teas-actn-requirements-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 250: '... - A VN customer MUST not control othe...' RFC 2119 keyword, line 252: '... - A VN customer MUST not see any rout...' RFC 2119 keyword, line 291: '...t network domain SHOULD support standa...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 315 has weird spacing: '...NC) and a hie...' == Line 443 has weird spacing: '...ansport on ...' == Line 487 has weird spacing: '...ment of pee...' == Line 515 has weird spacing: '...ing and man...' == Line 516 has weird spacing: '...e usage pro...' == (2 more instances...) == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 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 -- The document date (July 27, 2015) is 3194 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'ACTN-frame' is mentioned on line 80, but not defined == Missing Reference: 'ACTN-PS' is mentioned on line 81, but not defined Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Young Lee (Editor) 2 Dhruv Dhody 3 Internet Draft Huawei 5 Intended status: Informational Sergio Belotti 6 Alcatel-Lucent 7 Expires: January 2016 8 Khuzema Pithewan 9 Infinera 11 Daniele Ceccarelli 12 Ericsson 14 July 27, 2015 16 Requirements for Abstraction and Control of Transport Networks 18 draft-lee-teas-actn-requirements-01.txt 20 Abstract 22 This draft provides a set of requirements for abstraction and 23 control of transport networks. 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with 28 the provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other documents 37 at any time. It is inappropriate to use Internet-Drafts as 38 reference material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html. 45 This Internet-Draft will expire on October 27, 2015. 47 Copyright Notice 49 Copyright (c) 2015 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with 57 respect to this document. Code Components extracted from this 58 document must include Simplified BSD License text as described in 59 Section 4.e of the Trust Legal Provisions and are provided without 60 warranty as described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction...................................................2 65 2. High-level ACTN requirements...................................3 66 3. ACTN Use-Cases.................................................7 67 3.1. Two categories of requirements...........................10 68 4. ACTN interfaces requirements..................................14 69 4.1. CMI Interface Requirements...............................15 70 4.2. MPI (MDSC-PNC Interface).................................17 71 5. References....................................................20 72 5.1. Informative References...................................20 73 6. Contributors..................................................21 74 Contributors' Addresses..........................................21 75 Authors' Addresses...............................................21 77 1. Introduction 79 This draft provides a set of requirements for ACTN identified in 80 various use-cases of ACTN. [ACTN-frame] defines the base reference 81 architecture and terminology. [ACTN-PS] provides problem statement 82 and gap analysis. 84 Section 2 provides high-level ACTN requirements. Sections 3-5 85 provide the list of ACTN use-cases and the detailed requirement 86 analysis of these use-cases. 88 2. High-level ACTN requirements 90 1. Requirement 1: Single Virtualized Network Topology 92 Ability to build virtual network operation infrastructure based 93 on multi-layer, multi-domain topology abstracted from multiple 94 physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS, 95 etc.) 97 Reference: [KLEE], [LOPEZ], [DHODY], [CHENG]. 99 2. Requirement 2: Policy Enforcement 101 Ability to provide service requirement/policy (Between Customer 102 and Network) and mechanism to enforce service level agreement. 104 - Endpoint selection policy, routing policy, time-related 105 policy, etc. 107 Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG]. 109 3. Requirement 3: VN Query 111 Ability to request/respond VN Query (Can you give me VN(s)?) 113 - Request Input: 115 - VN end-points (CE end) 117 - VN Topology Service-specific Multi-Cost Objective 118 Function 120 - VN Topology diversity (e.g., VN1 and VN2 must be 121 disjoint) 123 - VN Topology type: path, graph 125 - Response includes VN topology 127 - Exact 129 - Potential 131 Reference: [KUMAKI], [FANG], [CHENG]. 133 4. Requirement 4: VN Instantiate 135 Ability to request/confirm VN Instantiation 137 - VN instance ID 139 - VN end-points 141 - VN constraints requirement 143 - Latency only, B/W guarantee, Latency and B/W guarantee 144 together 146 - VN diversity 148 - Node/Link disjoint from other VNs 150 - VN level diversity (e.g., VN1 and VN2 must be disjoint) 152 - VN type 154 - Path (tunnel), Node/Links (graph) 156 - VN instance ID per service (unique id to identify VNs) 158 Reference: [KUMAKI], [FANG], [CHENG]. 160 5. Requirement 5: Dynamic VN Control 162 Dynamic/On-demand VN Modification/Confirmation with feedback loop 163 to the customer 165 - Traffic monitoring and control policies sent to the network 167 - Network states based traffic optimization policies 168 - Utilization Monitoring (Frequency of report) 170 - Abstraction of Resource Topology reflecting these service- 171 related parameters 173 Reference: [XU], [XU2], [DHODY], [CHENG]. 175 6. Requirement 6: VN Lifecycle M&O 177 VN lifecycle management/operation 179 - Instantiate 181 - Delete 183 - Modify 185 - Update (VN level OAM Monitoring) under policy agreement 187 Reference: [FANG], [KUMAKI], [LOPEZ]. 189 7. Requirement 7: VN Service Operation 191 Ability to setup and manage end-2-end service on the VN involving 192 multi-domain, multi-layer, meeting constraints based on SLAs. 194 Reference: [LOPEZ], [KUMAKI], [CHENG], [DHODY], [FANG], [KLEE]. 196 8. Requirement 8: Multi-destination Coordination 198 Coordination of multi-destination service requirement/policy to 199 support dynamic applications such as VM migration, disaster 200 recovery, load balancing, etc. 202 - Service-policy primitives and its parameters 204 Reference: [FANG], [LOPEZ], [SHIN]. 206 9. Requirement 9: Multi-domain & Multi-layer Coordination 207 Ability to Coordinate multi-domain and multi-layer path 208 computation and setup operation (network) 210 - Computes E2E path across multi-domain (based on abstract 211 topology from each domain) 213 - Determines the domain sequence 215 - Request path signaling to each domain controller 217 - Find alternative path if any of the domain controllers cannot 218 find its domain path 220 Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI]. 222 10. Requirement 10: E2E Path Restoration 224 Ability to perform E2E Path Restoration Operation 226 - Intra-domain recovery 228 - Cross-domain recovery 230 Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN]. 232 11. Requirement 11: Dynamicity of network control operations 234 The ACTN interfaces should support dynamicity nature of network 235 control operations. This includes but not limited to the 236 following: 238 - Real-time VN control (e.g., a fast recovery/reroute upon 239 network failure). 240 - Fast convergence of abstracted topologies upon changes due 241 to failure or reconfiguration across the network domain 242 view, the multi-domain network view and the customer view. 243 - Large-scale VN operation (e.g., ability to query tens of 244 thousands of nodes and connectivity) for time-sensitive 245 applications. 247 Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI]. 249 12. Requirement 12: VN confidentiality/security 250 - A VN customer MUST not control other customer's virtual 251 network 252 - A VN customer MUST not see any routing information (e.g. IGP 253 database, TE database) on other customer's virtual network 255 Reference: [KUMAKI], [FANG], [LOPEZ] 257 3. ACTN Use-Cases 259 Listed below is a set of high-level requirements identified by each 260 of the ACTN use-cases: 262 - [CHENG] (ACTN Use-cases for Packet Transport Networks in Mobile 263 Backhaul Networks) 265 o Faster End-to-End Enterprise Services Provisioning 266 o Multi-layer coordination in L2/L3 Packet Transport Networks 267 o Optimizing the network resources utilization (supporting 268 various performances monitoring matrix, such as traffic flow 269 statistics, packet delay, delay variation, throughput and 270 packet-loss rate) 271 o Virtual Networks Operations for multi-domain Packet Transport 272 Networks 274 - [DHODY] (Packet Optical Integration (POI) Use Cases for 275 Abstraction and Control of Transport Networks (ACTN)) 277 o Packet Optical Integration to support Traffic Planning, 278 performance Monitoring, automated congestion management and 279 Automatic Network Adjustments 280 o Protection and Restoration Synergy in Packet Optical Multi- 281 layer network. 282 o Service Awareness and Coordination between Multiple Network 283 Domains 285 - [FANG] (ACTN Use Case for Multi-domain Data Center Interconnect) 287 o Multi-domain Data Center Interconnection to support VM 288 Migration, Global Load Balancing, Disaster Recovery, On- 289 demand Virtual Connection/Circuit Services 290 o The interfaces between the Data Center Operation and each 291 transport network domain SHOULD support standards-based 292 abstraction with a common information/data model to support 293 the following: 294 . Network Query (Pull Model) from the Data Center 295 Operation to each transport network domain to collect 296 potential resource availability (e.g., BW availability, 297 latency range, etc.) between a few data center 298 locations. 299 . Network Path Computation Request from the Data Center 300 Operation to each transport network domain to estimate 301 the path availability. 302 . Network Virtual Connections/Circuits Request from the 303 Data Center Operation to each transport domain to 304 establish end-to-end virtual connections/circuits (with 305 type, concurrency, duration, SLA.QoS parameters, 306 protection.reroute policy options, policy constraints 307 such as peering preference, etc.). 308 . Network Virtual Connections/Circuits Modification 309 Request 311 - [KLEE] (ACTN Use-case for On-demand E2E Connectivity Services in 312 Multiple Vendor Domain Transport Networks) 314 o Two-stage path computation capability in a hierarchical 315 control architecture (MDSC-PNC) and a hierarchical 316 composition of integrated network views 318 o Coordination of signal flow for E2E connections and 319 management. 321 o Abstraction of: 323 . Inter-connection data between domains 325 . Customer Endpoint data 327 . The multiple levels/granularities of the abstraction of 328 network resource (which is subject to policy and service 329 need). 331 . Any physical network constraints (such as SRLG, link 332 distance, etc.) should be reflected in abstraction. 334 . Domain preference and local policy (such as preferred 335 peering point(s), preferred route, etc.), Domain network 336 capability (e.g., support of push/pull model). 338 - [KUMAKI] (ACTN : Use case for Multi Tenant VNO) 339 o On-demand Virtual Network Service Creation 340 o Domain Control Plane/Routing Layer Separation 341 o Independent service Operation for Virtual Services from 342 control of other domains 343 o Multiple service level support for each VN (e.g., bandwidth 344 and latency for each VN service). 345 o VN diversity/survivability should be met in physical network 346 mapping. 347 o VN confidentiality and sharing constraint should be supported. 349 - [LOPEZ] (ACTN Use-case for Virtual Network Operation for Multiple 350 Domains in a Single Operator Network) 352 o Creation of a global abstraction of network topology: The VNO 353 Coordinator assembles each domain level abstraction of 354 network topology into a global abstraction of the end-to- 355 endnetwork. 356 o End-to-end connection lifecycle management 357 o Invocation of path provisioning request to each domain 358 (including optimization requests) 359 o Invocation of path protection/reroute to the affected 360 domain(s) 361 o End-to-end network monitoring and fault management. This could 362 imply potential KPIs and alarm correlation capabilities. 363 o End-to-end accounting and generation of detailed records for 364 resource usage 365 o End-to-end policy enforcement 367 - [SHIN] (ACTN Use-case for Mobile Virtual Network Operation for 368 Multiple Domains in a Single Operator Network) 370 o Resource abstraction: operational mechanisms in mobile 371 backhaul network to give the current network usage 372 information for dynamic and elastic applications be 373 provisioned dynamically with QoS guarantee. 375 o Load balancing or for recovery, the selection of core DC 376 location from edge constitutes a data center selection 377 problem. 379 o Multi-layer routing and optimization, coordination between 380 these two layers. 382 - [SUZUKI] (Use-case and Requirements for Multi-domain Operation 383 Plane Change) 384 o Operational state data synchronization between multi-domain 385 controllers 387 - [XU] (Use Cases and Requirements of Dynamic Service Control based 388 on Performance Monitoring in ACTN Architecture) 390 o Dynamic Service Control Policy enforcement and Traffic/SLA 391 Monitoring: 392 . Customer service performance monitoring strategy, 393 including the traffic monitoring object (the service 394 need to be monitored) 395 . monitoring parameters (e.g., transmitted and received 396 bytes per unit time), 397 . traffic monitoring cycle (e.g., 15 minutes, 24 hours), 398 . threshold of traffic monitoring (e.g., high and low 399 threshold), etc. 401 - [XU2] (Requirements of Abstract Alarm Report in ACTN architecture 403 o Dynamic abstract alarm report 405 3.1. Two categories of requirements 407 This section provides a summary of use-cases in terms of two 408 categories: (i) service-specific requirements; (ii) network-related 409 requirements. 411 Service-specific requirements listed below are uniquely applied to 412 the work scope of ACTN. Service-specific requirements are related to 413 virtual service coordination function defined in Section 3. These 414 requirements are related to customer's VNs in terms of service 415 policy associated with VNs such as service performance objectives, 416 VN endpoint location information for certain required service- 417 specific functions (e.g., security and others), VN survivability 418 requirement, or dynamic service control policy, etc. 420 Network-related requirements are related to virtual network 421 operation function defined in Section 3. These requirements are 422 related to multi-domain and multi-layer signaling, routing, 423 protection/restoration and synergy, re-optimization/re-grooming, 424 etc. These requirements are not inherently unique for the scope of 425 ACTN but some of these requirements are in scope of ACTN, especially 426 for coherent/seamless operation aspect of multiple controller 427 hierarchy. 429 The following table gives an overview of service-specific 430 requirements and network-related requirements respectively for each 431 ACTN use-case and identifies the work in scope of ACTN. 433 Use-case Service- Network-related Control 434 specific Requirements Functions/Data 435 Requirements Models to be 436 supported 438 ------- -------------- --------------- -------------- 439 [CHENG] - E2E service - Multi-layer - Dynamic 440 provisioning (L2/L2.5) multi-layer 441 - Performance coordination coordination 442 monitoring - VNO for multi- function based 443 - Resource domain transport on utilization 444 utilization networks 445 abstraction - YANG for 446 utilization 447 abstraction 449 ------- -------------- ---------------- -------------- 450 [DHODY] - Service - POI - Customer's 451 awareness/ Performance VN 452 coordination monitoring survivability 453 between P/O. - Protection/ policy 454 Restoration enforcement 455 synergy for 456 protection/res 457 toration 459 - YANG for 460 Performance 461 Monitoring 462 ------- -------------- ---------------- -------------- 463 [FANG] - Dynamic VM - On-demand - Multi- 464 migration virtual circuit destination 465 (service), request service 466 Global load - Network Path selection 467 balancing Connection policy 468 (utilization request enforcement 469 efficiency), function 470 Disaster 471 recovery - YANG for 472 - Service- Service-aware 473 aware network policy 474 query enforcement 475 - Service 476 Policy 477 Enforcement 478 ------- -------------- ---------------- -------------- 479 [KLEE] - Two stage path - Multi-domain 480 computation service policy 481 E2E signaling coordination 482 coordination to network 483 primitives 484 - Abstraction of 485 inter-domain - YANG for 486 info Abstraction of 487 - Enforcement of peering/ 488 network policy boundary data 489 (peering, domain 490 preference) 491 - Network 492 capability 493 exchange 494 (pull/push, 495 abstraction 496 level, etc.) 497 - on-demand and 498 long-lived end- 499 to-end service 500 provisioning and 501 monitoring 502 ------- -------------- ---------------- -------------- 503 [KUMAKI] - On-demand VN - Dynamic VN 504 creation creation, 505 - Multi- survivability 506 service level with security/ 507 for VN confi- 508 - VN dentiality 509 survivability 510 /diversity/con 511 fidentiality 513 ------- -------------- ---------------- -------------- 514 [LOPEZ] - E2E - E2E connection - Escalation 515 accounting and management, path of performance 516 resource usage provisioning and fault 517 data - E2E network management 518 - E2E service monitoring and data to CNC 519 policy fault management and the policy 520 enforcement enforcement 521 - YANG for 522 performance 523 and fault 524 management 526 ------- -------------- ---------------- -------------- 528 [SHIN] - Current - LB for - Multi-layer 529 network recovery routing and 530 resource - Multi-layer optimization 531 abstraction routing and - VN's dynamic 532 Endpoint/DC optimization endpoint 533 dynamic coordination selection 534 selection (for policy. 535 VM migration) 537 ------- -------------- ---------------- -------------- 538 [SUZUKI] - Operational - Operations 539 Data/State DB sync 540 between multi- function 541 domain across 542 controllers controllers 544 - YANG for 545 operational 546 data/state 547 model 548 ------- -------------- ---------------- -------------- 549 [XU]/ - Dynamic - Traffic - Dynamic 550 [XU2] service monitoring service 551 control policy - SLA monitoring control policy 552 enforcement enforcement 553 - Dynamic control 554 service 555 control - YANG for 556 traffic 557 monitoring 558 abstraction, 559 alarm 560 abstraction. 562 4. ACTN interfaces requirements 564 This section provides detailed ACTN interface requirements for the 565 two interfaces that are within the ACTN scope based on [ACTN-Frame] 566 and the use-cases referenced in this document. 568 . CMI: CNC-MDSC Interface 569 . MPI: MDSC-PNC Interface 570 4.1. CMI Interface Requirements 572 Requirement 573 1. Security/Policy Negotiation (Who are you?) (Between CNC and 574 MDSC) 575 - Configured vs. Discovered 576 - Trust domain verification (External Entity vs. Internal 577 Service Department) 578 - Push/Pull support (for policy) 579 2. VN Topology Query (Can you give me VN?) (From CNC to MDSC) 580 - VN end-points (CE end) 581 - VN Topology Service-specific Multi-Cost Objective Function 582 o Latency Map 583 o Available B/W Map 584 o Latency Map and Available B/W Map together 585 o Other types 586 - VN Topology diversity 587 o Node/Link disjoint from other VNs 588 o VN Topology level diversity (e.g., VN1 and VN2 must be 589 disjoint) 590 - VN Topology type 591 o Path vector (tunnel) 592 o Node/Links (graph) 593 3. VN Topology Query Response (From MDSC to CNC: Here's the VN 594 Topology that can be given to you if you accept) 595 - For VN Topology, 596 o This is what can be reserved for you 597 o This is what is available beyond what is given to you 598 (potential) 599 4. VN Topology Abstraction Model (generic network model) 600 5. VN Topology Abstraction Model (Service-specific model that 601 include customer endpoints) 602 6. Basic VN Instantiation Request/Confirmation (Between CNC and 603 MDSC: I need VN for my service, please instantiate my VN) 604 - VN instance ID 605 - VN end-points 606 - VN service requirement 607 o Latency only 608 o B/W guarantee 609 o Latency and B/W guarantee together 610 - VN diversity 611 o Node/Link disjoint from other VNs 612 - VN level diversity (e.g., VN1 and VN2 must be disjoint) 613 - VN type 614 o Path vector (tunnel) 615 o Node/Links (graph) 616 - VN instance ID per service (unique id to identify VNs) 617 - If failed to instantiate the requested VN, say why 618 7. Dynamic/On-demand VN Instantiation/Modification and 619 Confirmation with feedback loop (This is to be differentiated 620 from Basic VN Instantiation) 621 - Performance/Fault Monitoring 622 - Utilization Monitoring (Frequency of report) 623 - Abstraction of Resource Topology reflecting these service- 624 related parameters 625 - Dynamic Policy enforcement 627 8. VN lifecycle management/operation 628 - Create (same as VN instantiate Request) 629 - Delete 630 - Modify 631 - Update (VN level OAM Monitoring) under policy agreement 632 9. Coordination of multi-destination service requirement/policy 633 to support dynamic applications such as VM migration, 634 disaster recovery, load balancing, etc. 635 - Service-policy primitives and its parameters 637 4.2. MPI (MDSC-PNC Interface) 639 Requirement 640 1. Security/Policy negotiation (who are you?) 641 - Exchange of key, etc. 642 - Domain preference + local policy exchange 643 - Push/Pull support 644 - Preferred peering points 645 - Preferred route 646 - Reroute policy 647 - End-point mobility (for multi-destination) 648 2. Topology Query /Response (Pull Model from MDSC to PNC: Please 649 give me your domain topology) 650 - TED Abstraction level negotiation 651 - Abstract topology (per policy) 652 o Node/Link metrics 653 o Node/Link Type (Border/Gateway, etc.) 654 o All TE metrics (SRLG, etc.) 655 o Topology Metrics (latency, B/W available, etc.) 657 3. Topology Update (Push Model from PNC to MDSC) 658 - Under policy agreement, topology changes to be pushed to MDSC 659 from PNC 661 4. VN Path Computation Request (From MDSC to PNC: Please give me 662 a path in your domain) 663 - VN Instance ID (Note: this is passed from CNC to MDSC) 664 - End-point information 665 - CE ends 666 - Border points (if applicable) 667 - All other PCE request info (PCEP) 669 5. VN Path Computation Reply (here's the path info per your 670 request) 671 - Path level abstraction 672 - LSP DB 673 - LSP ID ?? 674 - VN ID 676 6. Coordination of multi-domain Centralized Signaling (MSDC 677 operation) Path Setup Operation 678 - MSDC computes E2E path across multi-domain (based on abstract 679 topology from each PNC) 680 - MDSC determines the domain sequence 681 - MDSC request path signaling to each PNC (domain) 682 - MDSC finds alternative path if any of the PNCs cannot find its 683 domain path 684 o PNC will crankback to MDSC if it cannot find its domain 685 path 686 o PNC will confirm to MDSC if it finds its domain path 687 7. Path Restoration Operation (after an E2E path is setup 688 successfully, some domain had a failure that cannot be 689 restored by the PNC domain) 690 - The problem PNC will send this notification with changed 691 abstract topology (computed after resource changes due to 692 failure/other factors) 693 - MDSC will find an alternate E2E path based on the changes 694 reported from PNC. It will need to update the E2E abstract 695 topology and the affected CN's VN topology in real-time (This 696 refers to dynamic synchronization of topology from Physical 697 topology to abstract topology to VN topology) 698 - MDSC will perform the path restoration signaling to the 699 affected PNCs. 700 8. Coordination of Multi-destination service restoration 701 operation (CNC have, for example, multiple endpoints where the 702 source endpoint can send its data to either one of the 703 endpoints) 704 - When PNC reports domain problem that cannot be resolved at 705 MDSC level because of there is no network restoration path to 706 a given destination. 707 - Then MDSC has Customers' profile in which to find the customer 708 has "multi-destination" application. 709 - Under policy A, MDSC will be allowed to reroute the customer 710 traffic to one of the pre-negotiated destinations and proceed 711 with restoration of this particular customer's traffic. 712 - Under policy B, CNC may reroute on its VN topology level and 713 push this to MDSC and MDSC maps this into its abstract 714 topology and proceed with restoration of this customer's 715 traffic. 716 - In either case, the MDSC will proceed its restoration 717 operation (as explained in Req. 6) to the corresponding PNCs. 719 9. MDSC-PNC policy negotiation is also needed as to how 720 restoration is done across MDSC and PNCs. 722 10. Generic Abstract Topology Update per changes due to new 723 path setup/connection failure/degradation/restoration 724 11. Service-specific Abstract Topology Update per changes due 725 to new path setup/connection failure/degradation/restoration 726 12. Abstraction model of technology-specific topology element 728 5. References 730 5.1. Informative References 732 [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and 733 Control of Transport Networks", draft-ceccarelli-teas- 734 actn-framework, work in progress. 736 [CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport 737 Networks in Mobile Backhaul Networks", draft-cheng-actn- 738 ptn-requirements, work in progress. 740 [DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use 741 Cases for Abstraction and Control of Transport Networks 742 (ACTN)", draft-dhody-actn-poi-use-case, work in progress. 744 [FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center 745 Interconnect", draft-fang-actn-multidomain-dci, work in 746 progress. 748 [KLEE] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for E2E 749 Network Services in Multiple Vendor Domain Transport 750 Networks", draft-klee-teas-actn-connectivity-multi-domain, 751 work-in-progress. 753 [KUMAKI] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant 754 VNO ", draft-kumaki-teas-actn-multitenant-vno, work in 755 progress. 757 [LOPEZ] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation 758 for Multiple Domains in a Single Operator Network", draft- 759 lopez-actn-vno-multidomains, work in progress. 761 [SHIN] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual 762 Network Operation for Multiple Domains in a Single 763 Operator Network", draft-shin-actn-mvno-multi-domain, work 764 in progress. 766 [XU] Y. Xu, et. al., "Use Cases and Requirements of Dynamic Service 767 Control based on Performance Monitoring in ACTN 768 Architecture", draft-xu-actn-perf-dynamic-service-control, 769 work in progress. 771 [XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN 772 architecture", draft-xu-teas-actn-abstract-alarm-report, 773 work-in-progress. 775 [SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi- 776 domain Operation Plane Change", draft-suzuki-teas-actn- 777 multidomain-opc, work-in-progress. 779 6. Contributors 781 Contributors' Addresses 783 Kwangkook Lee 784 KT 785 Email: kwangkooglee@gmail.com 787 Takuya Miyasaka 788 KDDI 789 Email: ta-miyasaka@kddi.com 791 Yunbin Xu 792 CATR 793 Email: xuyunbin@mail.ritt.com.cn 795 Toshiaki Suzuki 796 Hitachi 797 Email: toshiaki.suzuki.cs@hitachi.com 799 Authors' Addresses 801 Young Lee (Editor) 802 Huawei Technologies 803 5340 Legacy Drive 804 Plano, TX 75023, USA 805 Phone: (469)277-5838 806 Email: leeyoung@huawei.com 808 Dhruv Dhody 809 Huawei Technologies 810 Email: dhruv.ietf@gmail.com 811 Sergio Belotti 812 Alcatel Lucent 813 Via Trento, 30 814 Vimercate, Italy 815 Email: sergio.belotti@alcatel-lucent.com 817 Khuzema Pithewan 818 Infinera 819 Email: kpithewan@infinera.com 821 Daniele Ceccarelli 822 Ericsson 823 Torshamnsgatan,48 824 Stockholm, Sweden 825 Email: daniele.ceccarelli@ericsson.com