idnits 2.17.1 draft-zhang-teas-actn-yang-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 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 (October 4, 2016) is 2753 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC6020' is mentioned on line 114, but not defined == Missing Reference: 'Service-Yang' is mentioned on line 207, but not defined == Missing Reference: 'TE-topology' is mentioned on line 423, but not defined == Missing Reference: 'TE-tunnel' is mentioned on line 450, but not defined -- No information found for draft-lee-tease-actn-abstraction - is the name correct? Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 TEAS WG Young Lee 2 Xian Zhang 3 Internet Draft Huawei 4 Intended status: Informational 5 Daniel Ceccarrelli 6 Expires: February 2017 Ericsson 8 Bin Yeong Yoon 9 ETRI 11 Oscar Gonzalez de Dios 12 Telefonica 14 October 4, 2016 16 Applicability of YANG models for Abstraction and Control of Traffic 17 Engineered Networks 19 draft-zhang-teas-actn-yang-01 21 Status of this Memo 23 This Internet-Draft is submitted to IETF in full conformance with 24 the provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other documents 33 at any time. It is inappropriate to use Internet-Drafts as 34 reference material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 This Internet-Draft will expire on January 4, 2017. 44 Copyright Notice 46 Copyright (c) 2016 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with 54 respect to this document. Code Components extracted from this 55 document must include Simplified BSD License text as described in 56 Section 4.e of the Trust Legal Provisions and are provided without 57 warranty as described in the Simplified BSD License. 59 Abstract 61 Abstraction and Control of TE Networks (ACTN) refers to the set of 62 virtual network operations needed to orchestrate, control and manage 63 large-scale multi-domain TE networks, so as to facilitate network 64 programmability, automation, efficient resource sharing, and end-to- 65 end virtual service aware connectivity and network function 66 virtualization services. 68 This document explains how the different types of YANG models 69 defined in the Operations and Management Area and in the Routing 70 Area are applicable to the ACTN framework. This document also shows 71 how the ACTN architecture can be satisfied using classes of data 72 model that have already been defined, and discusses the 73 applicability of specific data models that are under development. It 74 also highlights where new data models may need to be developed. 76 Table of Contents 78 1. Introduction...................................................3 79 2. Abstraction and Control of TE Networks (ACTN) Architecture.....3 80 3. Service Models.................................................5 81 4. Service Model Mapping to ACTN..................................6 82 4.1. Customer Service Models in the ACTN Architecture (CMI)....9 83 4.2. Service Delivery Models in ACTN Architecture..............9 84 4.3. Network Configuration Models in ACTN Architecture (MPI)...9 85 4.4. Device Models in ACTN Architecture (SBI).................10 86 4.5. Advanced Models..........................................11 88 5. Examples of Using Different Types of YANG Models..............11 89 5.1. Simple Connectivity Examples.............................11 90 5.2. VN service example.......................................12 91 5.3. Data Center-Interconnection Example......................13 92 5.3.1. CMI (CNC-MDSC Interface)............................15 93 5.3.2. MPI (MDSC-PNC Interface)............................15 94 5.3.3. PDI (PNC-Device interface)..........................15 95 6. Security......................................................16 96 7. Acknowledgements..............................................16 97 8. References....................................................16 98 8.1. Informative References...................................16 99 9. Contributors..................................................18 100 Authors' Addresses...............................................19 102 1. Introduction 104 Abstraction and Control of TE Networks (ACTN) describes a method for 105 operating a Traffic Engineered (TE) network (such as an MPLS-TE 106 network or a layer 1 transport network) to provide connectivity and 107 virtual network services for customers of the TE network. The 108 services provided can be tuned to meet the requirements (such as 109 traffic patterns, quality, and reliability) of the applications 110 hosted by the customers. More details about ACTN can be found in 111 Section 2. 113 Data models are a representation of objects that can be configured 114 or monitored within a system. Within the IETF, YANG [RFC6020] is the 115 language of choice for documenting data models, and YANG models have 116 been produced to allow configuration or modelling of a variety of 117 network devices, protocol instances, and network services. YANG data 118 models have been classified in [Netmod-Yang-Model-Classification] 119 and [Service-YANG]. 121 This document shows how the ACTN architecture can be satisfied using 122 classes of data model that have already been defined, and discusses 123 the applicability of specific data models that are under 124 development. It also highlights where new data models may need to be 125 developed. 127 2. Abstraction and Control of TE Networks (ACTN) Architecture 129 [ACTN-Requirements] describes the high-level ACTN requirements. 130 [ACTN-Frame] describes the architecture model for ACTN including the 131 entities (Customer Network Controller (CNC), Multi-domain Service 132 Coordinator (MDSC), and Physical Network Controller (PNC)) and their 133 interfaces. 135 Figure 1 depicts a high-level control and interface architecture for 136 ACTN and is a reproduction of Figure 7 from [ACTN-Frame]. A number 137 of key ACTN interfaces exist for deployment and operation of ACTN- 138 based networks. These are highlighted in Figure 1 (ACTN Interfaces) 139 below: 141 .-------------- 142 ------------- | 143 | Application |-- 144 ------------- 145 ^ 146 | I/F A -------- 147 v ( ) 148 -------------- - - 149 | Customer | ( Customer ) 150 | Network |--------->( Network ) 151 | Controller | ( ) 152 -------------- - - 153 ^ ( ) 154 | I/F B -------- 155 v 156 -------------- 157 | MultiDomain | 158 | Service | 159 | Coordinator| -------- 160 -------------- ( ) 161 ^ - - 162 | I/F C ( Physical ) 163 v ( Network ) 164 --------------- ( ) -------- 165 | |<----> - - ( ) 166 -------------- | ( ) - - 167 | Physical |-- -------- ( Physical ) 168 | Network |<---------------------->( Network ) 169 | Controller | I/F D ( ) 170 -------------- - - 171 ( ) 172 -------- 174 Figure 1 : ACTN Interfaces 176 The interfaces and functions are described below (without modifying 177 the definitions) in [ACTN-Frame]: 179 . Interface A: This is out of scope of this draft. 181 . Interface B: The CNC-MDSC Interface (CMI) is an interface 182 between a Customer Network Controller and a Multi Domain 183 Service Controller. The interface will communicate the service 184 request or application demand. A request will include specific 185 service properties, including: services, bandwidth and 186 constraint information. The CNC can also request the creation 187 of the virtual network based on underlying physical resources 188 to provide network services for the applications. The CNC can 189 provide the end-point information/characteristics, traffic 190 matrix specifying specific customer constraints. The MDSC may 191 also report potential network topology availability if queried 192 for current capability from the Customer Network Controller. 194 . Interface C: The MDSC-PNC Interface (MPI) is an interface 195 between a Multi Domain Service Coordinator and a Physical 196 Network Controller. It allows the MDSC to communicate requests 197 to create connectivity or to modify bandwidth reservations in 198 the physical network. In multi-domain environments, each PNC is 199 responsible for a separate domain and so the MDSC needs to 200 establish multiple MPIs, one for each PNC and perform 201 coordination between them. 203 . Interface D: The provisioning interface for creating forwarding 204 state in the physical network, requested via the Physical 205 Network Controller. Interface D is not in the scope of ACTN, 206 however, it is included in this document so that it can be 207 compared to models in [Service-Yang]. 209 3. Service Models 211 [Service-YANG] introduces a reference architecture to explain the 212 nature and usage of service YANG models in the context of service 213 orchestration. Figure 2 below depicts this relationship and is a 214 reproduction of Figure 2 from [Service-YANG]. Four models depicted 215 in Figure 2 are defined as follows: 217 . Customer Service Model: A customer service model is used to 218 describe a service as offer or delivered to a customer by a 219 network operator. 220 . Service Delivery Model: A service delivery model is used by a 221 network operator to define and configure how a service is 222 provided by the network. 223 . Network Configuration Model: A network configuration model is 224 used by a network orchestrator to provide network-level 225 configuration model to a controller. 227 . Device Configuration Model: A device configuration model is 228 used by a controller to configure physical network elements. 230 Customer 231 ------------------ Service ---------- 232 | | Model | | 233 | Service |<-------->| Customer | 234 | Orchestrator | | | 235 | | ---------- 236 ------------------ 237 . . ----------- 238 . . ......|Application| 239 . . : | BSS/OSS | 240 . . : ----------- 241 . Service Delivery . : 242 . Model . : 243 ------------------ ------------------ 244 | | | | 245 | Network | | Network | 246 | Orchestrator | | Orchestrator | 247 | | | | 248 .------------------ ------------------. 249 . : : . 250 . : Network Configuration : . 251 . : Model : . 252 ------------ ------------ ------------ ------------ 253 | | | | | | | | 254 | Controller | | Controller | | Controller | | Controller | 255 | | | | | | | | 256 ------------ ------------ ------------ ------------ 257 : . . : : 258 : . . Device : : 259 : . . Configuration : : 260 : . . Model : : 261 --------- --------- --------- --------- --------- 262 | Network | | Network | | Network | | Network | | Network | 263 | Element | | Element | | Element | | Element | | Element | 264 --------- --------- --------- --------- --------- 266 Figure 2: An SDN Architecture with a Service Orchestrator 268 4. Service Model Mapping to ACTN 270 YANG models coupled with the RESTCONF/NETCONF protocol 271 [Netconf][Restconf] are solutions for the ACTN framework. This 272 section explains which types of YANG models apply to each of the 273 ACTN interfaces. 275 +-------------------------------------------------------------+ 276 | | 277 | +-----------+ +-------+ | 278 | | Customer | | CNC | | 279 | +-----------+ +-------+ | 280 | /|\ /|\ | 281 +---------|-------------------------------------------|-------+ 282 | Customer Service Model | CMI 283 | | 284 +------ --|-------------------------------------------|--------+ 285 | \|/ | | 286 | +------------+ | | 287 | | Service | \|/ | 288 | |Orchestrator| +----------+ | 289 | +------------+ | | | 290 | /|\ | MDSC | | 291 | | Service Delivery Model | | | 292 | \|/ | | | 293 | +------------+ +----------+ | 294 | | Network | /|\ | 295 | |Orchestrator| | | 296 | +------------+ | | 297 | /|\ | | 298 | | | | 299 +---------|-------------------------------------------|--------+ 300 | | MPI 301 | Network Configuration Model | 302 +---------|-------------------------------------------|--------+ 303 | \|/ \|/ | 304 | +----------+ +-----------+ | 305 | | Domain | | PNC | | 306 | |Controller| +-----------+ | 307 | +----------+ /|\ /|\ | 308 | /|\ /|\ | | | 309 | | | | | | 310 +------|-----|-------------------------------------|-----|-----+ 311 | | Device Configuration Model | | SBI 312 \|/ \|/ \|/ \|/ 313 --- --- --- --- 314 / \ / \ / \ / \ 315 \ / \ / \ / \ / 316 --- --- --- --- 318 Figure 3 : Mapping between Service Model and ACTN Architecture 320 As shown in Figure 3, the architecture described in [Service-YANG] 321 can be mapped to the ACTN architecture well. A point worth noting is 322 that here the functions of the MDSC can include: 324 A. Customer mapping/translation 326 This function is to map customer intent-like commands into network 327 provisioning requests to the Physical Network Controller (PNC) 328 according to business OSS/NMS provisioned static or dynamic policy. 329 Specifically, it provides mapping and translation of customer's 330 service request into a set of parameters that are specific to a 331 network type and technology such that network configuration process 332 is made possible. 334 B. Service/Virtual service coordination 336 This function translates customer service-related information into 337 the virtual network service operations in order to seamlessly 338 operate virtual networks while meeting customer's service 339 requirements. In the context of ACTN, service/virtual service 340 coordination includes a number of service orchestration functions 341 such as multi-destination load balancing, guarantees of service 342 quality, bandwidth and throughput and notification for service fault 343 and performance degradation and so forth. 345 C. Multi domain coordination 347 This function oversees the specific aspects of the different domains 348 and builds a single abstracted end-to-end network topology in order 349 to coordinate end-to-end path computation and path/service 350 provisioning. Domain sequence path calculation/determination is also 351 a part of this function. 353 D. Virtualization/Abstraction 355 This function provides an abstracted view of the underlying network 356 resources towards customer, being it the client or a higher level 357 controller entity. It includes network path computation based on 358 customer service connectivity request constraints, based on the 359 global network-wide abstracted topology and the creation of an 360 abstracted view of network slices allocated to each customer, 361 according to customer-specific network objective functions, and to 362 the customer traffic profile. 364 The first two of these functions (A and B) are related to service 365 orchestration while function C is related to network orchestration 366 and function D is related to both service and network orchestration. 368 4.1. Customer Service Models in the ACTN Architecture (CMI) 370 Customer Service Models, which are used between a customer and a 371 service orchestrator as in [Service-YANG], should be used between 372 the CNC and MDSC (e.g., CMI) serving as providing a simple intent- 373 like model/interface. 375 Among the key functions of Customer Service Models on the CMI is the 376 service request. A request will include specific service properties, 377 including: service type and its characteristics, bandwidth, 378 constraint information, and end-point characteristics. 380 The following table provides a list of functions needed to build the 381 CMI. They are mapped with Customer Service Models. 383 Function Yang Models 384 ----------------------------------------------------------- 385 Transport Service Request [Transport-Service-Model] 386 VN Service Request [ACTN-VN-YANG] 387 Path Computation Request* [PATH-COMPUTATION-API] 389 *Path computation request in the CMI context means network path 390 computation request based on customer service connectivity request 391 constraints. 393 4.2. Service Delivery Models in ACTN Architecture 395 The Service Delivery Models (as shown in Figure 3) where the service 396 orchestration and the network orchestration could be implemented as 397 separate components as seen in [Service-YANG]. This is also known as 398 Network Service Models. On the other hand, from an ACTN architecture 399 point of view, the service delivery model between the service 400 orchestrator and the network orchestrator is an internal interface 401 between sub-components of the MDSC. 403 4.3. Network Configuration Models in ACTN Architecture (MPI) 405 The Network Configuration Models is used between the network 406 orchestrator and the controller in [Service-YANG]. In ACTN, this 407 model is used primarily between a MDSC and a PNC. The Network 408 Configuration Model can be also used for the foundation of more 409 advanced models, like hierarchical MDSCs (see Section 4.5) 410 The Network Configuration Model captures the parameters which are 411 network wide information. 413 The following table provides a list of mandatory and optional 414 functions needed to build the MPI. They are mapped with Network 415 Configuration Yang Models. Note that various Yang models are work in 416 progress. 418 Function Yang Models 419 ------------------------------------------ 420 Configuration Scheduling [Schedule] 421 Path computation [PATH_COMPUTATION-API]* 422 Path Provisioning [TE-Tunnel]** 423 Topology Abstraction [TE-topology] 424 Telemetry TBD 425 Service Provisioning TBD*** 427 * Related draft is presenting use cases for path computation API, 428 and Yang related model is foreseen to be added. 430 ** Note that path provisioning function is provided by ietf-te 431 module in [TE-Tunnel]. 433 *** This function needs to be investigated further. This can be a 434 part of [TE-Tunnel] which is to be determined. Service provisioning 435 is an optional function that builds on top the path provisioning 436 one. 438 Path provisioning and Topology abstraction functions are mandatory 439 in any case, while Path Computation may be mandatory or optional 440 depending on the type of topology abstraction used. Details of this 441 topic are discussed in [ACTN-Abstraction]. 443 Telemetry may also be an optional function. 445 4.4. Device Models in ACTN Architecture (SBI) 447 For the device YANG models are used for per-device configuration 448 purpose, they can be used between the PNC and the physical 449 network/devices. An example of Device Models is ietf-te-device yang 450 module defined in [TE-tunnel]. Note that SBI is not in the scope of 451 ACTN. This section is provided to give some examples of YANG-based 452 Device Models. 454 4.5. Advanced Models 456 There may be some variation of interface C whereby there may be 457 MDSC-MDSC interface (MMI) in case where there may be a recursive 458 hierarchy among the MDSCs. This is a variation of ACTN architecture. 459 See Figure 4 for this. 461 +-------+ +-------+ +-------+ 462 | CNC-A | | CNC-B | | CNC-C | 463 +-------+ +-------+ +-------+ 464 \ | / 465 ---------- | ---------- 466 \ | / 467 +-----------------------+ 468 | MDSC | 469 +-----------------------+ 470 / | \ 471 ---------- | ----------- 472 / | \ 473 +----------+ +----------+ +--------+ 474 | MDSC | | MDSC | | MDSC | 475 +----------+ +----------+ +--------+ 476 | / | / \ 477 | / | / \ 478 +-----+ +-----+ +-----+ +-----+ +-----+ 479 | PNC | | PNC | | PNC | | PNC | | PNC | 480 +-----+ +-----+ +-----+ +-----+ +-----+ 482 Figure 4: MDSC Controller Hierarchy 484 The MDSC-MDSC interface can be viewed as a recursive network 485 configuration model which is similar to the MDSC-PNC interface. 487 5. Examples of Using Different Types of YANG Models 489 5.1. Simple Connectivity Examples 491 The data model in [Transport-Service-Model] provides an intent-like 492 connectivity service model which can be used in connection-oriented 493 transport networks. 495 It would be used as follows in the ACTN architecture: 497 . A CNC uses this service model to specify the two client nodes 498 that are to be connected, and also indicates the amount of 499 traffic (i.e., the bandwidth required) and payload type. What 500 may be additionally specified is the SLA that describes the 501 required quality and resilience of the service. 503 . The MDSC uses the information in the request to pick the right 504 network (domain) and also to select the provider edge nodes 505 corresponding to the customer edge nodes. 507 If there are multiple domains, then the MDSC needs to 508 coordinate across domains to set up network tunnels to deliver 509 a service. Thus coordination includes, but is not limited to, 510 picking the right domain sequence to deliver a service. Before 511 it can perform such functions, it needs to get the topology 512 information from each PNC, be it abstract or not, using 513 topology YANG models such as [te-topology]. 515 Additionally, an MDSC can initiate the creation of a tunnel (or 516 tunnel segment) in order to fulfill the service request from 517 CNC based on path computation upon the overall topology 518 information it synthesized from different PNCs. The based model 519 that can cater this purpose is the te-tunnel model specified in 520 [te-tunnel]. 522 . Then, the PNC needs to decide the explicit route of such a 523 tunnel or tunnel segment (in case of multiple domains), and 524 create such a tunnel using protocols such as PCEP and RSVP-TE 525 or using per-hop configuration. 527 5.2. VN service example 529 The service model defined in [ACTN-VN-YANG] describes a virtual 530 network (VN) as a service which is a set of multiple connectivity 531 services: 533 . A CNC will specify to the MDSC a list of VN members. Each VN 534 member specifies either a single connectivity service, or a 535 source with multiple potential destination points in the case 536 that the precise destination sites are to be determined by 537 MDSC. 539 o In the first case, the procedure is the same as the 540 connectivity service, except that in this case, there is a 541 list of connections requested. 543 o In the second case, where the CNC requests the MDSC to 544 select the right destination out of a list of candidates, 545 the MDSC needs to choose the best candidate and reply with 546 the chosen destination for a given VN member. After this 547 is selected, the connectivity request setup procedure is 548 the same as in the connectivity-as-a-service example. 550 5.3. Data Center-Interconnection Example 552 This section describes more concretely how existing YANG models 553 described in Section 4 map to an ACTN data center interconnection 554 use case. Figure 5 shows a use-case which shows service policy- 555 driven Data Center selection and is a reproduction of Figure A.1 556 from [ACTN-Info]. 558 +----------------+ 559 | CNC | 560 | (Global DC | 561 | Operation | 562 | Control) | 563 +--------+-------+ 564 | | VN Requirement/Policy: 565 CMI: | | - Endpoint/DC location info 566 Service model | | - Endpoint/DC dynamic 567 | | selection policy 568 | | (for VM migration, DR, LB) 569 | v 570 +---------+---------+ 571 | Multi-domain | Service policy-driven 572 |Service Coordinator| dynamic DC selection 573 MPI: +-----+---+---+-----+ 574 Network Configuration | | | 575 Model | | | 576 +----------------+ | +---------------+ 577 | | | 578 +-----+-----+ +------+-----+ +------+-----+ 579 | PNC for | | PNC for | | PNC for | 580 | Transport | | Transport | | Transport | 581 | Network A | | Network B | | network C | 582 +-----------+ +------------+ +------------+ 583 Device | | | 584 Model | | | 585 | | | 586 +---+ ------ ------ ------ +---+ 587 |DC1|--//// \\\\ //// \\\\ //// \\\\---+DC5| 588 +---+ | | | | | | +---+ 589 | TN A +-----+ TN B +----+ TN C | 590 / | | | | | 591 / \\\\ //// / \\\\ //// \\\\ //// 592 +---+ ------ / ------ \ ------ \ 593 |DC2| / \ \+---+ 594 +---+ / \ |DC6| 595 +---+ \ +---+ +---+ 596 |DC3| \|DC4| 597 +---+ +---+ 599 DR: Disaster Recovery 600 LB: Load Balancing 602 Figure 5: Service Policy-driven Data Center Selection 604 Figure 5 shows how VN policies from the CNC (Global Data Center 605 Operation) are incorporated by the MDSC to support multi-destination 606 applications. Multi-destination applications refer to applications 607 in which the selection of the destination of a network path for a 608 given source needs to be decided dynamically to support such 609 applications. 611 Data Center selection problems arise for VM mobility, disaster 612 recovery and load balancing cases. VN's policy plays an important 613 role for virtual network operation. Policy can be static or dynamic. 614 Dynamic policy for data center selection may be placed as a result 615 of utilization of data center resources supporting VMs. The MDSC 616 would then incorporate this information to meet the objective of 617 this application. 619 5.3.1. CMI (CNC-MDSC Interface) 621 [ACTN-VN-YANG] is used to express the definition of a VN, its VN 622 creation request, the service objectives (metrics, QoS parameters, 623 etc.), dynamic service policy when VM needs to be moved from one 624 Data Center to another Data Center, etc. This service model is used 625 between the CNC and the MDSC (CMI). The CNC in this use-case is an 626 external entity that wants to create a VN and operates on the VN. 628 5.3.2. MPI (MDSC-PNC Interface) 630 The Network Configuration Model is used between the MDSC and the 631 PNCs. Based on the Customer Service Model's request, the MDSC will 632 need to translate the service model into the network configuration 633 model to instantiate a set of multi-domain connections between the 634 prescribed sources and the destinations. The MDSC will also need to 635 dynamically interact with the CNC for dynamic policy changes 636 initiated by the CNC. Upon the determination of the multi-domain 637 connections, the MDSC will need to use the network configuration 638 model such as [TE-Tunnel] to interact with each PNC involved on the 639 path. [TE-Topology] is used to for the purpose of underlying domain 640 network abstraction from the PNC to the MDSC. 642 5.3.3. PDI (PNC-Device interface) 644 The Device Model can be used between the PNC and its underlying 645 devices that are controlled by the PNC. The PNC will need to trigger 646 signaling using any mechanisms it employees (e.g. [RSVP-TE-YANG]) to 647 provision its domain path segment. There can be a plethora of 648 choices how to control/manage its domain network. The PNC is 649 responsible to abstract its domain network resources and update it 650 to the MDSC. Note that this interface is not in the scope of ACTN. 651 This section is provided just for an illustration purpose. 653 6. Security 655 This document is an informational draft. When the models mentioned 656 in this draft are implemented, detailed security consideration will 657 be given in such work. 659 How security fits into the whole architecture has the following 660 components: 662 - the use of Restconf security between components 664 - the use of authentication and policy to govern which services can 665 be requested by different parties. 667 - how security may be requested as an element of a service and 668 mapped down to protocol security mechanisms as well as separation 669 (slicing) of physical resources) 671 7. Acknowledgements 673 We thank Adrian Farrel for providing useful comments and suggestions 674 for this draft. 676 8. References 678 8.1. Informative References 680 [Service-YANG] Q. Wu, W. Liu and A. Farrel, "Service Models 681 Explained", draft-wu-opsawg-service-model-explained, work 682 in progress. 684 [Netmod-Yang-Model-Classification] D. Bogdanovic, B. Claise, and C. 685 Moberg, "YANG Module Classification", draft-ietf-netmod- 686 yang-model-classification, work in progress. 688 [Netconf] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 690 and A. Bierman, Ed., "Network Configuration Protocol 692 (NETCONF)", RFC 6241. 694 [Restconf] A. Bierman, M. Bjorklund, and K. Watsen, "RESTCONF 695 Protocol", draft-ietf-netconf-restconf, work in progress. 697 [ACTN-Requirements] Y. Lee, et al., "ACTN Requirements for 698 Abstraction and Control of TE Networks", draft-ietf-teas- 699 actn-requirements, work in progress. 701 [ACTN-Frame] D. Cecarelli and Y. Lee, "Framework for Abstraction and 702 Control of Traffic Engineered Networks", draft-ietf-teas- 703 actn-framework, work in progress. 705 [TE-Topology] X. Liu, et. al., "YANG Data Model for TE Topologies", 706 draft-ietf-teas-yang-te-topo, work in progress. 708 [TE-Tunnel] T. Saad (Editor), "A YANG Data Model for Traffic 709 Engineering Tunnels and Interfaces", draft-ietf-teas-yang- 710 te, work in progress. 712 [ACTN-VN-YANG] Y. Lee (Editor), "A Yang Data Model for ACTN VN 713 Operation", draft-lee-teas-actn-vn-yang, work in progress. 715 [ACTN-Info] Y. Lee & S. Belotti, "Information Model for Abstraction 716 and Control of TE Networks (ACTN)", draft-leebelotti-teas- 717 actn-info, work in progress. 719 [Transport-Service-Model] X. Zhang (Editor), "A Service YANG Model 720 for Connection-oriented Transport Networks", draft-zhang- 721 teas-transport-service-model, work in progress. 723 [PATH-COMPUTATION-API] I.Busi/S.Belotti et al. "Path Computation 724 API", draft-busibel-ccamp-path-computation-api-00.txt, 725 work in progress 727 [RSVP-TE-YANG] T. Saad (Editor), "A YANG Data Model for Resource 728 Reservation Protocol (RSVP)", draft-ietf-teas-yang-rsvp, 729 work in progress. 731 [Schedule] X. Liu, et. al., "A YANG Data Model for Configuration 732 Scheduling", draft-liu-netmod-yang-schedule, work in 733 progress. 735 [ACTN-Abstraction] Y. Lee, D. Dhody, and D. Ceccarelli, "ACTN 736 Abstraction Methods", draft-lee-tease-actn-abstraction, 737 work in progress. 739 9. Contributors 741 Contributor's Addresses 743 Dhruv Dhoddy 744 Huawei Technologies 746 Email: dhruv.ietf@gmail.com 748 Haomian Zheng 749 Huawei Technologies 751 Email: zhenghaomian@huawei.com 753 Sergio Belotti 754 Nokia 756 Email: sergio.belotti@nokia.com 758 Authors' Addresses 760 Young Lee 761 Huawei Technologies 762 5340 Legacy Drive 763 Plano, TX 75023, USA 764 Phone: (469)277-5838 766 Email: leeyoung@huawei.com 768 Xian Zhang 769 Huawei Technologies 771 Email: zhang.xian@huawei.com 773 Daniele Ceccarelli 774 Ericsson 775 Torshamnsgatan,48 776 Stockholm, Sweden 778 Email: daniele.ceccarelli@ericsson.com 780 Bin Yeong Yoon 781 ETRI 783 Email: byyun@etri.re.kr 785 Oscar Gonzalez de Dios 786 Telefonica 788 Email: oscar.gonzalezdedios@telefonica.com