idnits 2.17.1 draft-ceccarelli-teas-actn-framework-00.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 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 15, 2015) is 3238 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'ONF-ARCH' is mentioned on line 575, but not defined == Unused Reference: 'PCE-S' is defined on line 701, but no explicit reference was found in the text == Unused Reference: 'NFV-AF' is defined on line 707, but no explicit reference was found in the text == Unused Reference: 'ONF' is defined on line 715, but no explicit reference was found in the text == Unused Reference: 'ACTN-Info' is defined on line 727, but no explicit reference was found in the text == Unused Reference: 'Cheng' is defined on line 731, but no explicit reference was found in the text == Unused Reference: 'Dhody' is defined on line 735, but no explicit reference was found in the text == Unused Reference: 'Fang' is defined on line 739, but no explicit reference was found in the text == Unused Reference: 'Klee' is defined on line 743, but no explicit reference was found in the text == Unused Reference: 'Kumaki' is defined on line 748, but no explicit reference was found in the text == Unused Reference: 'Lopez' is defined on line 752, but no explicit reference was found in the text == Unused Reference: 'Shin' is defined on line 756, but no explicit reference was found in the text == Unused Reference: 'Xu' is defined on line 761, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 14 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 TEAS Working Group Daniele Ceccarelli (Ed) 2 Internet Draft Ericsson 3 Intended status: Informational Young Lee (Ed) 4 Expires: November 2015 Huawei 6 June 15, 2015 8 Framework for Abstraction and Control of Transport Networks 10 draft-ceccarelli-teas-actn-framework-00.txt 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with 15 the provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on December 15, 2015. 35 Copyright Notice 37 Copyright (c) 2015 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with 45 respect to this document. Code Components extracted from this 46 document must include Simplified BSD License text as described in 47 Section 4.e of the Trust Legal Provisions and are provided without 48 warranty as described in the Simplified BSD License. 50 Abstract 52 Transport networks have a variety of mechanisms to facilitate the 53 separation of the data plane and control plane. They also have a 54 range of management and provisioning protocols to configure and 55 activate network resources. These mechanisms represent key 56 technologies for enabling flexible and dynamic networking. 58 Abstraction of network resources is a technique that can be applied 59 to a single network domain or across multiple domains to create a 60 single virtualized network that is under the control of a network 61 operator that may be the customer of the operator that actually owns 62 the network resources. 64 This draft provides a framework for Abstraction and Control of 65 Transport Networks (ACTN). 67 Table of Contents 69 1. Introduction...................................................2 70 2. Business Model of ACTN.........................................5 71 2.1. Customers.................................................5 72 2.2. Service Providers.........................................7 73 2.3. Network Providers.........................................9 74 3. ACTN architecture..............................................9 75 3.1. Customer Network Controller..............................12 76 3.2. Multi Domain Service Coordinator.........................13 77 3.3. Physical Network Controller..............................14 78 3.4. ACTN interfaces..........................................15 79 4. References....................................................17 80 4.1. Informative References...................................17 81 5. Contributors..................................................20 82 Authors' Addresses...............................................20 84 1. Introduction 86 Transport networks have a variety of mechanisms to facilitate 87 separation of data plane and control plane including distributed 88 signaling for path setup and protection, centralized path 89 computation for planning and traffic engineering, and a range of 90 management and provisioning protocols to configure and activate 91 network resources. These mechanisms represent key technologies for 92 enabling flexible and dynamic networking. 94 The term Transport Network in this draft refers to any connection- 95 oriented network that has the ability of dynamic provisioning and 96 traffic engineering such that resource guarantees can be provided to 97 the network's clients. Some examples of networks that are in scope 98 of this definition are optical networks, MPLS Transport Profile 99 (MPLS-TP), MPLS Traffic Engineering (MPLS-TE), and other emerging 100 technologies with connection-oriented behavior. 102 One of the main drivers for Software Defined Networking (SDN) is a 103 decoupling of the network control plane from the data plane. This 104 separation of the control plane from the data plane has been already 105 achieved with the development of MPLS/GMPLS [GMPLS] and PCE [PCE] 106 for TE-based transport networks. One of the advantages of SDN is its 107 logically centralized control regime that allows a global view of 108 the underlying network under its control. Centralized control in SDN 109 helps improve network resources utilization compared with 110 distributed network control. For TE-based transport network control, 111 PCE is essentially equivalent to a logically centralized control for 112 path computation function. 114 Two key aspects that need to be solved by SDN are: 116 . Network and service abstraction 118 . Coordination of resources across multiple domains to provide 119 end-to-end services regardless of whether the domains use SDN 120 or not. 122 As transport networks evolve, the need to provide network and 123 service abstraction has emerged as a key requirement for operators; 124 this implies in effect the virtualization of network resources so 125 that the network is "sliced" for different tenants shown as a 126 dedicated portion of the network resources 128 Particular attention needs to be paid to the multi-domain case, 129 where Abstraction and Control of Transport Networks (ACTN) can 130 facilitate virtual network operation via the creation of a single 131 virtualized network or a seamless service. This supports operators 132 in viewing and controlling different domains (at any dimension: 134 applied technology, administrative zones, or vendor-specific 135 technology islands) as a single virtualized network. 137 Network virtualization refers to allowing the customers of network 138 operators (see Section 2.1) to utilize a certain amount of network 139 resources as if they own them and thus control their allocated 140 resources with higher layer or application processes that enables 141 the resources to be used in the most optimal way. This empowerment 142 of customer control facilitates introduction of new services and 143 applications as the customers are permitted to create, modify, and 144 delete their virtual network services. More flexible, dynamic 145 customer control capabilities are added to the traditional VPN along 146 with a customer specific virtual network view. Customers control a 147 view of virtual network resources, specifically allocated to each 148 one of them. This view is called an abstracted network topology. 149 Such a view may be specific to a specific service, the set of 150 consumed resources or to a particular customer. Customer controller 151 of the virtual network is envisioned to support a plethora of 152 distinct applications. This means that there may be a further level 153 of virtualization that provides a view of resources in the 154 customer's virtual network for use by an individual application. 156 The framework described in this draft is named Abstraction and 157 Control of Transport Network (ACTN) and facilitates: 159 - Abstraction of the underlying network resources to higher-layer 160 applications and users (customers); abstraction for a specific 161 application or customer is referred to as virtualization in the 162 Optical Networking Foundation (ONF) SDN architecture. [ONF- 163 ARCH] 165 - Slicing infrastructure to connect multiple customers to meet 166 specific customer's service requirements; 168 - Creation of a virtualized environment allowing operators to 169 view and control multi-subnet multi-technology networks into a 170 single virtualized network; 172 - Possibility of providing a customer with abstracted network or 173 abstracted services (totally hiding the network). 175 - A virtualization/mapping network function that adapts customer 176 requests to the virtual resources (allocated to them) to the 177 supporting physical network control and performs the necessary 178 mapping, translation, isolation and security/policy 179 enforcement, etc.; This function is often referred to as 180 orchestration. 182 - The multi-domain coordination of the underlying transport 183 domains, presenting it as an abstracted topology to the 184 customers via open and programmable interfaces. This allows for 185 the recursion of controllers in a customer-provider 186 relationship. 188 A further discussion of the term "abstraction" can be found in 189 [TE-INFO]. 191 2. Business Model of ACTN 193 The Virtual Private Network (VPN) [RFC4026] and Overlay Network (ON) 194 models [RFC4208] are built on the premise that one single network 195 provider provides all virtual private or overlay networks to its 196 customers. These models are simple to operate but have some 197 disadvantages in accommodating the increasing need for flexible and 198 dynamic network virtualization capabilities. 200 The ACTN model is built upon entities that reflect the current 201 landscape of network virtualization environments. There are three 202 key entities in the ACTN model [ACTN-PS]: 204 - Customers 205 - Service Providers 206 - Network Providers 208 2.1. Customers 210 Within the ACTN framework, different types of customers may be taken 211 into account depending on the type of their resource needs, on their 212 number and type of access. As example, it is possible to group them 213 into two main categories: 215 Basic Customer: Basic customers include fixed residential users, 216 mobile users and small enterprises. Usually the number of basic 217 customers is high; they require small amounts of resources and are 218 characterized by steady requests (relatively time invariant). A 219 typical request for a basic customer is for a bundle of voice 220 services and internet access. Moreover basic customers do not modify 221 their services themselves; if a service change is needed, it is 222 performed by the provider as proxy and they generally have very few 223 dedicated resources (subscriber drop), with everything else shared 224 on the basis of some SLA, which is usually best-efforts. 226 Advanced Customer: Advanced customers typically include enterprises, 227 governments and utilities. Such customers can ask for both point to 228 point and multipoint connectivity with high resource demand 229 significantly varying in time and from customer to customer. This is 230 one of the reasons why a bundled service offering is not enough and 231 it is desirable to provide each of them with a customized virtual 232 network service. 234 Advanced customers may own dedicated virtual resources, or share 235 resources. They may also have the ability to modify their service 236 parameters within the scope of their virtualized environments. 238 As customers are geographically spread over multiple network 239 provider domains, they have to interface multiple providers and may 240 have to support multiple virtual network services with different 241 underlying objectives set by the network providers. To enable these 242 customers to support flexible and dynamic applications they need to 243 control their allocated virtual network resources in a dynamic 244 fashion, and that means that they need an abstracted view of the 245 topology that spans all of the network providers. 247 ACTN's primary focus is Advanced Customers. 249 Customers of a given service provider can in turn offer a service to 250 other customers in a recursive way. An example of recursiveness with 251 2 service providers is shown below. 253 - Customer (of service B) 254 - Customer (of service A) & Service Provider (of service B) 255 - Service Provider (of service A) 256 - Network Provider 258 +------------------------------------------------------------+ --- 259 | | ^ 260 | Customer (of service B)| . 261 | +--------------------------------------------------------+ | B 262 | | | |--- . 263 | |Customer (of service A) & Service Provider(of service B)| | ^ . 264 | | +---------------------------------------------------+ | | . . 265 | | | | | | . . 266 | | | Service Provider (of service A)| | | A . 267 | | |+------------------------------------------+ | | | . . 268 | | || | | | | . . 269 | | || Network provider| | | | v v 270 | | |+------------------------------------------+ | | |------ 271 | | +---------------------------------------------------+ | | 272 | +--------------------------------------------------------+ | 273 +------------------------------------------------------------+ 275 Figure 1: Network Recursiveness. 277 2.2. Service Providers 279 Service providers are the providers of virtual network services to 280 their customers. Service providers may or may not own physical 281 network resources. When a service provider is the same as the 282 network provider, this is similar to traditional VPN models. This 283 model works well when the customer maintains a single interface with 284 a single provider. When customer location spans across multiple 285 independent network provider domains, then it becomes hard to 286 facilitate the creation of end-to-end virtual network services with 287 this model. 289 A more interesting case arises when network providers only provide 290 infrastructure while service providers directly interface their 291 customers. In this case, service providers themselves are customers 292 of the network infrastructure providers. One service provider may 293 need to keep multiple independent network providers as its end-users 294 span geographically across multiple network provider domains as 295 shown in Figure 2 where Service Provider A uses resources from 296 Network Provider A and Network Provider B to offer a virtualized 297 network to its customer. 299 Customer X -----------------------------------X 301 Service Provider A X -----------------------------------X 303 Network Provider B X-----------------X 305 Network Provider A X------------------X 307 Figure 2: A service Provider as Customer of Two Network Providers. 309 The ACTN network model is predicated upon this three tier model and 310 is summarized in Figure 3: 312 +----------------------+ 313 | customer | 314 +----------------------+ 315 | 316 | /\ Service/Customer specific 317 | || Abstract Topology 318 | || 319 +----------------------+ E2E abstract 320 | Service Provider | topology creation 321 +----------------------+ 322 / | \ 323 / | \ Network Topology 324 / | \ (raw or abstract) 325 / | \ 326 +------------------+ +------------------+ +------------------+ 327 |Network Provider 1| |Network Provider 2| |Network Provider 3| 328 +------------------+ +------------------+ +------------------+ 330 Figure 3: Three tier model. 332 There can be multiple types of service providers. 334 . Data Center providers: can be viewed as a service provider type 335 as they own and operate data center resources to various WAN 336 clients, they can lease physical network resources from network 337 providers. 338 . Internet Service Providers (ISP): can be a service provider of 339 internet services to their customers while leasing physical 340 network resources from network providers. 341 . Mobile Virtual Network Operators (MVNO): provide mobile 342 services to their end-users without owning the physical network 343 infrastructure. 345 The network provider space is the one where recursiveness occurs. A 346 customer-provider relationship between multiple service providers 347 can be established leading to a hierarchical architecture of 348 controllers within service provider network. 350 2.3. Network Providers 352 Network Providers are the infrastructure providers that own the 353 physical network resources and provide network resources to their 354 customers. The layered model proposed by this draft separates the 355 concerns of network providers and customers, with service providers 356 acting as aggregators of customer requests. 358 3. ACTN architecture 360 This section provides a high-level control and interface model of 361 ACTN. 363 The ACTN architecture, while being aligned with the ONF SDN 364 architecture [ONF-ARCH], is presenting a 3-tiers reference model. It 365 allows for hierarchy and recursiveness not only of SDN controllers 366 but also of traditionally controlled domains. It defines three types 367 of controllers depending on the functionalities they implement. The 368 main functionalities that are identified are: 370 . Multi domain coordination function: With the definition of 371 domain being "everything that is under the control of the same 372 controller",it is needed to have a control entity that oversees 373 the specific aspects of the different domains and to build a 374 single abstracted end-to-end network topology in order to 375 coordinate end-to-end path computation and path/service 376 provisioning. 378 . Virtualization/Abstraction function: To provide an abstracted 379 view of the underlying network resources towards customer, 380 being it the client or a higher level controller entity. It 381 includes computation of customer resource requests into virtual 382 network paths based on the global network-wide abstracted 383 topology and the creation of an abstracted view of network 384 slices allocated to each customer, according to customer- 385 specific virtual network objective functions, and to the 386 customer traffic profile. 388 . Customer mapping function: In charge of mapping customer VN 389 setup commands into network provisioning requests to the 390 Physical Network Controller (PNC) according to business OSS/NMS 391 provisioned static or dynamic policy. Moreover it provides 392 mapping and translation of customer virtual network slices into 393 physical network resources 395 . Virtual service coordination: Virtual service coordination 396 function in ACTN incorporates customer service-related 397 knowledge into the virtual network operations in order to 398 seamlessly operate virtual networks while meeting customer's 399 service requirements. 401 The virtual services that are coordinated under ACTN can be split 402 into two categories: 404 . Service-aware Connectivity Services: This category includes all 405 the network service operations used to provide connectivity 406 between customer end-points while meeting policies and service 407 related constraints. The data model for this category would 408 include topology entities such as virtual nodes, virtual links, 409 adaptation and termination points and service-related entities 410 such as policies and service related constraints. (See Section 411 4.2.2) 413 . Network Function Virtualization Services: These kinds of 414 services are usually setup between customers' premises and 415 service provider premises and are provided mostly by cloud 416 providers or content delivery providers. The context may 417 include, but not limited to a security function like firewall, 418 a traffic optimizer, the provisioning of storage or computation 419 capacity where the customer does not care whether the service 420 is implemented in a given data center or another. These 421 services may be hosted virtually by the provider or physically 422 part of the network. This allows the service provider to hide 423 his own resources (both network and data centers) and divert 424 customer requests where most suitable. This is also known as 425 "end points mobility" case and introduces new concepts of 426 traffic and service provisioning and resiliency. (e.g. Virtual 427 Machine mobility)." (See Section 4.2.3) 429 About the Customer service-related knowledge it includes: 431 - VN Service Requirements: The end customer would have 432 specific service requirements for the VN including the 433 customer endpoints access profile as well as the E2E 434 customer service objectives. The ACTN framework 435 architectural "entities" would monitor the E2E service 436 during the lifetime of VN by focusing on both the 437 connectivity provided by the network as well as the customer 438 service objectives. These E2E service requirements go beyond 439 the VN service requirements and include customer 440 infrastructure as well. 442 - Application Service Policy: Apart for network connectivity, 443 the customer may also require some policies for application 444 specific features or services. The ACTN framework would take 445 these application service policies and requirements into 446 consideration while coordinating the virtual network 447 operations, which require end customer connectivity for 448 these advanced services. 450 While the "types" of controller defined are shown in Figure 4 below 451 and are the following: 453 . CNC - Customer Network Controller 454 . MDSC - Multi Domain Service Coordinator 455 . PNC - Physical Network Controller 457 VPN customer NW Mobile Customer ISP NW service Customer 458 | | | 459 +-------+ +-------+ +-------+ 460 | CNC-A | | CNC-B | | CNC-C | 461 +-------+ +-------+ +-------+ 462 \___________ | _____________/ 463 ---------- | ------------ 464 \ | / 465 +-----------------------+ 466 | MDSC | 467 +-----------------------+ 468 __________/ | \_________ 469 ---------- | ------------____ 470 / | \ 471 +-------+ +-------+ +-------+ 472 | PNC | | PNC | | PNC | 473 +-------+ +-------+ +-------+ 474 | GMPLS / | / \ 475 | trigger / | / \ 476 -------- __---- +-----+ __ +-----+ \ 477 ( ) ( )_ | PNC |__ | PCE | \ 478 - - ( Phys ) +-----+ +-----+ ----- 479 ( GMPLS ) (Netw) | / ( ) 480 ( Physical ) ---- | / ( Phys. ) 481 ( Network ) ----- ----- ( Net ) 482 - - ( ) ( ) ----- 483 ( ) ( Phys. ) ( Phys ) 484 -------- ( Net ) ( Net ) 485 ----- ----- 487 Figure 4: ACTN Control Hierarchy 489 3.1. Customer Network Controller 491 A Virtual Network Service is instantiated by the Customer Network 492 Controller via the CMI (CNC-MDSC Interface). As the Customer Network 493 Controller directly interfaces the application stratum, it 494 understands multiple application requirements and their service 495 needs. It is assumed that the Customer Network Controller and the 496 MDSC have a common knowledge on the end-point interfaces based on 497 their business negotiation prior to service instantiation. End-point 498 interfaces refer to customer-network physical interfaces that 499 connect customer premise equipment to network provider equipment. 501 In addition to abstract networks, ACTN allows to provide the CNC 502 with services. Example of services include connectivity between one 503 of the customer's end points with a given set of resources in a data 504 center from the service provider. 506 3.2. Multi Domain Service Coordinator 508 The MDSC (Multi Domain Service Coordinator) sits between the CNC 509 (the one issuing connectivity requests) and the PNCs (Physical 510 Network Controllersr - the ones managing the physical network 511 resources). The MDSC can be collocated with the PNC, especially in 512 those cases where the service provider and the network provider are 513 the same entity. 515 The internal system architecture and building blocks of the MDSC are 516 out of the scope of ACTN. Some examples can be found in the 517 Application Based Network Operations (ABNO) architecture [ABNO] and 518 the ONF SDN architecture [ONF-ARCH]. 520 The MDSC is the only building block of the architecture that is able 521 to implement all the four ACTN main functionalities, i.e. multi 522 domain coordination function, virtualization/abstraction function, 523 customer mapping function and virtual service coordination. 524 A hierarchy of MDSCs can be foreseen for scalability and 525 administrative choices. In order to allow for a hierarchy of MDSC, 526 the interface between the parent MDSC and a child MDSC must be the 527 same as the interface between the MDSC and the PNC. This does not 528 introduce any complexity as it is transparent from the perspective 529 of the CNCs and the PNCs and it makes use of the same interface 530 model and its primitives as the CMI and MPI. 532 +-------+ +-------+ +-------+ 533 | CNC-A | | CNC-B | | CNC-C | 534 +-------+ +-------+ +-------+ 535 \___________ | ___________/ 536 ---------- | ---------- 537 \ | / 538 +-----------------------+ 539 | MDSC | 540 +-----------------------+ 541 __________/ | \_________ 542 ---------- | -----------____ 543 / | \ 544 +----------+ +----------+ +--------+ 545 | MDSC | | MDSC | | MDSC | 546 +----------+ +----------+ +--------+ 547 | / | / \ 548 | / | / \ 549 +-----+ +-----+ +-----+ +-----+ +-----+ 550 | PNC | | PNC | | PNC | | PNC | | PNC | 551 +-----+ +-----+ +-----+ +-----+ +-----+ 553 Figure 5: Controller recursiveness 555 A key requirement for allowing recursion of MDSCs is that a single 556 interface needs to be defined both for the north and the south 557 bounds. 558 In order to allow for multi-domain coordination a 1:N relationship 559 must be allowed between MDSCs and between MDSCs and PNCs (i.e. 1 560 parent MDSC and N child MDSC or 1 MDSC and N PNCs). In addition to 561 that it could be possible to have also a M:1 relationship between 562 MDSC and PNC to allow for network resource partitioning/sharing 563 among different customers not necessarily connected to the same MDSC 564 (e.g. different service providers). 566 3.3. Physical Network Controller 568 The Physical Network Controller is the one in charge of configuring 569 the network elements, monitoring the physical topology of the 570 network and passing it, either raw or abstracted, to the MDSC. 572 The internal architecture of the PNC, his building blocks and the 573 way it controls its domain, are out of the scope of ACTN. Some 574 examples can be found in the Application Based Network Operations 575 (ABNO) architecture [ABNO] and the ONF SDN architecture [ONF-ARCH] 576 The PNC, in addition to being in charge of controlling the physical 577 network, is able to implement two of the four ACTN main 578 functionalities: multi domain coordination function and 579 virtualization/abstraction function 580 A hierarchy of PNCs can be foreseen for scalability and 581 administrative choices. 583 3.4. ACTN interfaces 585 To allow virtualization and multi domain coordination, the network 586 has to provide open, programmable interfaces, in which customer 587 applications can create, replace and modify virtual network 588 resources and services in an interactive, flexible and dynamic 589 fashion while having no impact on other customers. Direct customer 590 control of transport network elements and virtualized services is 591 not perceived as a viable proposition for transport network 592 providers due to security and policy concerns among other reasons. 593 In addition, as discussed in the previous section, the network 594 control plane for transport networks has been separated from data 595 plane and as such it is not viable for the customer to directly 596 interface with transport network elements. 598 While the current network control plane is well suited for control 599 of physical network resources via dynamic provisioning, path 600 computation, etc., a multi service domain controller needs to be 601 built on top of physical network controller to support network 602 virtualization. 604 Figure 5 depicts a high-level control and interface architecture for 605 ACTN. A number of key ACTN interfaces exist for deployment and 606 operation of ACTN-based networks. These are highlighted in Figure 5 607 (ACTN Interfaces) below: 609 .-------------- 610 ------------- | 611 | Application |-- 612 ------------- 613 ^ 614 | I/F A -------- 615 v ( ) 616 -------------- - - 617 | Customer | ( Customer ) 618 | Network |--------->( Network ) 619 | Controller | ( ) 620 -------------- - - 621 ^ ( ) 622 | I/F B -------- 623 v ^ ^ 624 -------------- : : 625 | MultiDomain | : . 626 | Service | : . 627 | Coordinator| -------- . I/F E 628 -------------- ( ) . 629 ^ - - . 630 | I/F C ( Physical ) . 631 v ( Network ) . 632 --------------- ( ) -------- 633 | |<----> - - ( ) 634 -------------- | ( ) - - 635 | Physical |-- -------- ( Physical ) 636 | Network |<---------------------->( Network ) 637 | Controller | I/F D ( ) 638 -------------- - - 639 ( ) 640 -------- 642 Figure 5: ACTN Interfaces 644 The interfaces and functions are described below: 646 . Interface A: A north-bound interface (NBI) that will 647 communicate the service request or application demand. A 648 request will include specific service properties, including: 649 services, topology, bandwidth and constraint information. 651 . Interface B: The CNC-MDSC Interface (CMI) is an interface 652 between a Customer Network Controller and a Multi Service 653 Domain Controller. It requests the creation of the network 654 resources, topology or services for the applications. The 655 Virtual Network Controller may also report potential network 656 topology availability if queried for current capability from 657 the Customer Network Controller. 659 . Interface C: The MDSC-PNC Interface (MPI) is an interface 660 between a Multi Domain Service Coordinator and a Physical 661 Network Controller. It communicates the creation request, if 662 required, of new connectivity of bandwidth changes in the 663 physical network, via the PNC. In multi-domain environments, 664 the MDSC needs to establish multiple MPIs, one for each PNC, as 665 there are multiple PNCs responsible for its domain control. 667 . Interface D: The provisioning interface for creating forwarding 668 state in the physical network, requested via the Physical 669 Network Controller. 671 . Interface E: A mapping of physical resources to overlay 672 resources. 674 The interfaces within the ACTN scope are B and C. 676 4. Manageability 678 TBD 680 5. Security 682 TBD 684 6. References 686 6.1. Informative References 688 [PCE] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path 689 Computation Element (PCE)-Based Architecture", IETF RFC 690 4655, August 2006. 692 [RFC4026] L. Andersson, T. Madsen, "Provider Provisioned Virtual 693 Private Network (VPN) Terminology", RFC 4026, March 2005. 695 [RFC4208] G. Swallow, J. Drake, H.Ishimatsu, Y. Rekhter, 696 "Generalized Multiprotocol Label Switching (GMPLS) User- 697 Network Interface (UNI): Resource ReserVation Protocol- 698 Traffic Engineering (RSVP-TE) Support for the Overlay 699 Model", RFC 4208, October 2005. 701 [PCE-S] Crabbe, E, et. al., "PCEP extension for stateful 702 PCE",draft-ietf-pce-stateful-pce, work in progress. 704 [GMPLS] Manning, E., et al., "Generalized Multi-Protocol Label 705 Switching (GMPLS) Architecture", RFC 3945, October 2004. 707 [NFV-AF] "Network Functions Virtualization (NFV); Architectural 708 Framework", ETSI GS NFV 002 v1.1.1, October 2013. 710 [ACTN-PS] Y. Lee, D. King, M. Boucadair, R. Jing, L. Contreras 711 Murillo, "Problem Statement for Abstraction and Control of 712 Transport Networks", draft-leeking-actn-problem-statement, 713 work in progress. 715 [ONF] Open Networking Foundation, "OpenFlow Switch Specification 716 Version 1.4.0 (Wire Protocol 0x05)", October 2013. 718 [TE-INFO] A. Farrel, Editor, "Problem Statement and Architecture for 719 Information Exchange Between Interconnected Traffic 720 Engineered Networks", draft-ietf-teas-interconnected-te- 721 info-exchange, work in progress. 723 [ABNO] King, D., and Farrel, A., "A PCE-based Architecture for 724 Application-based Network Operations", draft-farrkingel- 725 pce-abno-architecture, work in progress. 727 [ACTN-Info] Y. Lee, S. Belotti, D. Dhody, "Information Model for 728 Abstraction and Control of Transport Networks", draft- 729 leebelotti-teas-actn-info, work in progress. 731 [Cheng] W. Cheng, et. al., "ACTN Use-cases for Packet Transport 732 Networks in Mobile Backhaul Networks", draft-cheng-actn- 733 ptn-requirements, work in progress. 735 [Dhody] D. Dhody, et. al., "Packet Optical Integration (POI) Use 736 Cases for Abstraction and Control of Transport Networks 737 (ACTN)", draft-dhody-actn-poi-use-case, work in progress. 739 [Fang] L. Fang, "ACTN Use Case for Multi-domain Data Center 740 Interconnect", draft-fang-actn-multidomain-dci, work in 741 progress. 743 [Klee] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for On- 744 demand E2E Connectivity Services in Multiple Vendor Domain 745 Transport Networks", draft-klee-actn-connectivity-multi- 746 vendor-domains, work in progress. 748 [Kumaki] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant 749 VNO ", draft-kumaki-actn-multitenant-vno, work in 750 progress. 752 [Lopez] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation 753 for Multiple Domains in a Single Operator Network", draft- 754 lopez-actn-vno-multidomains, work in progress. 756 [Shin] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual 757 Network Operation for Multiple Domains in a Single 758 Operator Network", draft-shin-actn-mvno-multi-domain, work 759 in progress. 761 [Xu] Y. Xu, et. al., "Use Cases and Requirements of Dynamic Service 762 Control based on Performance Monitoring in ACTN 763 Architecture", draft-xu-actn-perf-dynamic-service-control, 764 work in progress. 766 7. Contributors 768 Authors' Addresses 770 Daniele Ceccarelli (Editor) 771 Ericsson 772 Torshamnsgatan,48 773 Stockholm, Sweden 774 Email: daniele.ceccarelli@ericsson.com 776 Young Lee (Editor) 777 Huawei Technologies 778 5340 Legacy Drive 779 Plano, TX 75023, USA 780 Phone: (469)277-5838 781 Email: leeyoung@huawei.com 783 Luyuan Fang 784 Email: luyuanf@gmail.com 786 Diego Lopez 787 Telefonica I+D 788 Don Ramon de la Cruz, 82 789 28006 Madrid, Spain 790 Email: diego@tid.es 792 Sergio Belotti 793 Alcatel Lucent 794 Via Trento, 30 795 Vimercate, Italy 796 Email: sergio.belotti@alcatel-lucent.com 798 Daniel King 799 Lancaster University 800 Email: d.king@lancaster.ac.uk 802 Dhruv Dhoddy 803 Huawei Technologies 804 dhruv.ietf@gmail.com