idnits 2.17.1 draft-gdmb-netslices-intro-and-ps-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 19, 2017) is 2655 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-05) exists of draft-galis-anima-autonomic-slice-networking-01 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 No Working Group A. Galis 3 Internet-Draft University College London 4 Intended status: Informational J. Dong 5 Expires: July 23, 2017 K. Makhijani 6 S. Bryant 7 Huawei Technologies 8 January 19, 2017 10 Network Slicing - Introductory Document and Revised Problem Statement 11 draft-gdmb-netslices-intro-and-ps-00 13 Abstract 15 This documents represents an introduction to the motivation and 16 Network Slicing problems and work ares. It represents an initial 17 revision of Network Slicing problem statement derived from the 18 analysis of the technical gaps in IETF protocols ecosystem. It 19 complements and it bring together the isolated efforts being carried 20 out in several IETF working groups to achieve certain aspects of 21 network slice functions and operations. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on July 23, 2017. 40 Copyright Notice 42 Copyright (c) 2017 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 1.1. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 2. Suggested Problems and Work Areas . . . . . . . . . . . . . . 4 60 2.1. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 3. Documents . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 8 67 7.2. Informative References . . . . . . . . . . . . . . . . . 9 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 70 1. Introduction 72 Network slicing (NS) refers to the managed partitions of physical 73 and/or virtual network resources, network physical/virtual and 74 service functions that can act as an independent instance of a 75 network and/or as a network cloud. Network resources include 76 connectivity, compute and storage resources. 78 Slices considerably transform the networking perspective by 79 abstracting, isolating, orchestrating, softwarizing and separating 80 logical network components from the underlying physical network 81 resources and as such they enhance Internet architecture. 83 For slice creation, the management plane creates the grouping of 84 physical and virtual network resources, connects with the physical 85 and virtual network and service functions as appropriate and it 86 instantiates all the network and service functions assigned to the 87 slice. On the other hand for slice operations the slice control 88 takes over the control and governing of all the network resources, 89 network functions and service functions assigned to the slice, and 90 (re-) configure them as appropriate and as per elasticity needs in 91 order to provide an end-to-end service. 93 Network operators can exploit NS to significantly reduce operations 94 expenditures, and enable softwarization, programmability and the 95 innovation necessary to enrich the offered services. Network 96 softwarization techniques [IMT2020-2015], [IMT2020-2016] may be used 97 to realised and manage [MANO-2014] network slicing. NS provides the 98 means for the network operators to provide network programmable 99 capabilities to OTT providers and other market players without 100 changing their physical infrastructure. NS enables the concurrent 101 deployment of multiple logical, self-contained and independent, 102 shared or partitioned networks on a common infrastructure. Slices 103 support also dynamic multi-services, multi-tenancy and the 104 integration means for vertical market players. 106 The purpose of NS work in IETF is to develop a set of protocols and/ 107 or protocol extensions that enable efficient slice creation, 108 activation / deactivation, composition, elasticity, orchestration, 109 management, isolation, guaranteed SLA and safe operations within a 110 network or network cloud / data centre environment that assumes an IP 111 and/or MPLS-based underlay. 113 While there are, isolated efforts being carried out in several IETF 114 working groups DETNET, [I-D.leeking-actn-problem-statement], 115 [I-D.dong-network-slicing-problem-statement], 116 [I-D.galis-anima-autonomic-slice-networking], [IETF-Slicing1], 117 [IETF-Slicing2], [IETF-Slicing3], [IETF-Slicing4], [IETF-Slicing5] to 118 achieve certain aspects of network slice functions and operations, 119 there is a clear need to look at complete life-cycle management 120 characteristics of network Slicing solutions though the discussions 121 based on the following architectural tenets: 123 o Underlay tenet: support for an IP/MPLS-based underlay data plane 124 the transport network used to carry that underlay. 126 o Governance tenet: a logically centralized authority for network 127 slices in a domain. 129 o Separation tenet: slices are independent and have appropriate 130 degree of isolation (1) from each other. 132 o Capability exposure tenet: each slice allows third parties to 133 access via APIs information regarding services provided by the slice 134 (e.g. connectivity information, QoS, mobility, autonomicity, etc.) 135 within the limits set by the operator. 137 NS approaches that do not adhere to these tenets are explicitly 138 outside of the scope of the proposed work at IETF. 140 In pursuit of the solutions described above, there is a need to 141 document an architecture for network slicing within both wide area 142 network and a data center environments. 144 Elicitation of requirements ([RFC2119], [RFC4364]) for a network 145 slice control and management planes and will be needed facilitating 146 the selection, extension, and/or development of the protocol for each 147 of the functional interfaces identified to support the architecture. 149 Additionally, documentation on the common use-cases for slice 150 validation for 5G is needed (e.g. mission-critical ultra-low latency 151 communication services; massive-connectivity machine communication 152 services - smart metering, smart grid and sensor networks; extreme 153 QoS; Independent operations and management; Independent cost and/or 154 energy optimisation; Independent multi-topology routing; multi-tenant 155 operations, etc.). 157 The proposed NS work would be co-ordinated with other IETF WGs (e.g. 158 TEAS WG, DETNET WG, ANIMA WG, NETCONF WG, SUPA WG, NVO3 WG, Routing 159 Area WG (RTGWG), Network Management Research Group (NMRG) and NFV 160 Research Group (NFVRG)) to ensure that the commonalities and 161 differences in solutions are properly considered. Where suitable 162 protocols, models or methods exist, they will be preferred over 163 creating new ones. 165 1.1. Notes 167 (1) This issue require efficient interaction between an upper layer 168 in the hierarchy and a lower layer for QoS guaranties and most of the 169 operations on slicing. 171 2. Suggested Problems and Work Areas 173 The goal of this work is to develop one or more protocol 174 specifications (or extensions to existing protocols) to address the 175 following problem areas. These problems were selected according to 176 the analysis of the technical gaps in IETF protocols ecosystem. 178 o Uniform Reference Model for Network Slicing; Describe all elements 179 and instances of a network slice. Describe shared non-sliced network 180 parts. 182 o Slice Templates: Design the slices to different scenarios 183 ([ChinaCom-2009], [GENI-2009], [IMT2020-2016bis], [NGMN-2016], 184 [NGS-3GPP-2016], [ONF-2016]); an appropriate slice template 185 definition that may include capability exposure of managed partitions 186 of physical and/or virtual network resources (i.e. connectivity, 187 compute and storage resources), physical and/or virtual network and 188 service functions that can act as an independent network and/or as a 189 network cloud. 191 o Network slice expected capabilities (i.e. prioritization may be 192 needed): 194 * Four-dimensional efficient slice isolation with guarantees for 195 isolation in Data / Control / Management / Service planes. 196 Enablers for safe and efficient multi-tenancy in slices. 198 * Methods to guarantee the end-to-end QoS of a slice. 200 * Recursion - methods for NS segmentation allowing a slicing 201 hierarchy with parent child relationships. 203 * Efficiency in slicing: realize diverse requirements without 204 re-engineering the infrastructure. 206 * Customized security mechanisms per slice. 208 * Enablers to manage the trade-offs between flexibility and 209 efficiency in slicing. 211 * Optimisation - methods for network resources automatic 212 acquisition, global resource view formed; global energy view 213 formed; Network Slice deployed based on global resource 214 and energy efficiency; Mapping algorithms. 216 * Monitoring status and behaviour of NS in a single and/or 217 muti-domain environment. 219 * Capability exposure for slices; APIs for slices. 221 * Programmability and openness of network slices. 223 o Network slice operations (i.e. prioritization may be needed): 225 * Slice creation: slices in access, core and transport 226 networks; slices in data centres, slices in edge clouds. 228 * Slice life cycle management including creation, 229 activation/ deactivation, protection (2) , elasticity (3), 230 extensibility (4) , safety (5) , Sizing and 231 scalability of the slicing model per network and 232 per network cloud. 234 * Autonomic slice management and operation (i.e. self-configuration, 235 self-composition, self-monitoring, self-optimisation, 236 self-elasticity are carried as part of the slice protocols). 238 * Slice stitching / composition: Enablers for efficient stitching / 239 composition/ decomposition of slices: 241 - vertically (service + management + control planes) and/or 242 - horizontally (between different domains part of access, 243 core, edge segments) and /or 244 - vertically + horizontally. 246 * E2E wireline network segments and network clouds orchestration 247 of slices ([GUERZONI-2016], [KARL-2016]). 249 * Service Mapping: Dynamic Mapping of Services to slices; YANG 250 models for slices. 252 o Efficient enablers for Integration of above capabilities and 253 operations. 255 2.1. Notes 257 (2) Protection refers to the related mechanisms so that events within 258 one slice, such as congestion, do not have a negative impact on 259 another slice. 261 (3) Elasticity refers to the mechanisms and triggers for the growth 262 /shrinking of network resources, network and service functions. 264 (4) Extensibility refers to the ability to expand a NS with 265 additional functionality and/or characteristics or through 266 modification of existing functionality/characteristics, while 267 minimizing impact to existing functions. 269 (5) Safety refers to the conditions of being protected against 270 different types and the consequences of failure, error harm or any 271 other event, which could be considered non-desirable. 273 [GUERZONI-2016] [KARL-2016] 275 3. Documents 277 The following are the proposed / expected / resulting documents with 278 priority (I) or (II) (i.e. revised prioritization may be needed): 280 o Agreed work plan 282 o Slice template and reference model to IESG (Informational) 284 o Slice life-cycle management model to IESG (Informational) 286 o Requirements for a network slice control and management planes. 288 o Common use-cases for slice validation for 5G 290 o (I) Slice template and reference model. 292 o (I) Four dimensional efficient slice isolation with guarantees for 293 isolation in Data/ Control/ Management/ Service planes. 295 o (II) Methods to guarantee the end-to-end QoS of a slice. 297 o (I) YANG data model for slicing. 299 o (I) E2E orchestration of slices. 301 o (II) Customized security mechanisms per slice. 303 o (I) Slice stitching / composition: enablers for efficient stitch / 304 composition / decomposition of slices vertically, horizontally and 305 vertically + horizontally 307 4. Security Considerations 309 Security will be a major part of the design of network slicing. 311 5. IANA Considerations 313 This document requests no IANA actions. 315 6. Acknowledgements 317 Thanks to Sheng Jiang (Huawei Technologies) for reviewing this draft. 319 7. References 321 7.1. Normative References 323 [I-D.dong-network-slicing-problem-statement] 324 Dong, J. and S. Bryant, "Problem Statement of Network 325 Slicing in IP/MPLS Networks", draft-dong-network-slicing- 326 problem-statement-00 (work in progress), October 2016. 328 [I-D.galis-anima-autonomic-slice-networking] 329 Galis, A., Makhijani, K., and D. Yu, "Autonomic Slice 330 Networking-Requirements and Reference Model", draft-galis- 331 anima-autonomic-slice-networking-01 (work in progress), 332 October 2016. 334 [I-D.leeking-actn-problem-statement] 335 Lee, Y., King, D., Boucadair, M., Jing, R., and L. 336 Contreras, "Problem Statement for Abstraction and Control 337 of Transport Networks", draft-leeking-actn-problem- 338 statement-03 (work in progress), September 2014. 340 [IETF-Slicing1] 341 "Presentations - Network Slicing meeting at IETF 97 of 342 15th November 2016", n.d., . 346 [IETF-Slicing2] 347 "Presentations - Network Slicing meeting at IETF 97 of 348 15th November 2016", n.d., . 352 [IETF-Slicing3] 353 "Presentations - Network Slicing meeting at IETF 97 of 354 15th November 2016", n.d., . 357 [IETF-Slicing4] 358 "Presentations - Network Slicing meeting at IETF 97 of 359 15th November 2016", n.d., . 364 [IETF-Slicing5] 365 "Presentations - Network Slicing meeting at IETF 97 of 366 15th November 2016", n.d., . 369 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 370 Requirement Levels", BCP 14, RFC 2119, 371 DOI 10.17487/RFC2119, March 1997, 372 . 374 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 375 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 376 2006, . 378 7.2. Informative References 380 [ChinaCom-2009] 381 "A. Galis et al - Management and Service-aware Networking 382 Architectures (MANA) for Future Internet - Invited paper 383 IEEE 2009 Fourth International Conference on 384 Communications and Networking in China (ChinaCom09) 26-28 385 August 2009, Xi'an, China", n.d., 386 . 388 [GENI-2009] 389 "GENI Key Concepts - Global Environment for Network 390 Innovations (GENI)", n.d., 391 . 393 [GUERZONI-2016] 394 "Guerzoni, R., Vaishnavi,I.,Perez-Caparros, D., Galis, A., 395 et al Analysis of End-to-End Multi Domain Management and 396 Orchestration Frameworks for Software Defined 397 Infrastructures - an Architectural Survey", June 2016, 398 . 400 [IMT2020-2015] 401 "Report on Gap Analysis", ITU-T FG IMT2020 , December 402 2015, . 405 [IMT2020-2016] 406 "Draft Technical Report Application of network 407 softwarization to IMT-2020 (O-041)", ITU-T FG IMT2020 , 408 December 2016, . 411 [IMT2020-2016bis] 412 "Draft Terms and definitions for IMT-2020 in ITU-T 413 (O-040)", ITU-T FG IMT2020 , December 2016, 414 . 417 [KARL-2016] 418 "Karl, H., Peuster, M, Galis, A., et al DevOps for Network 419 Function Virtualization - An Architectural Approach", July 420 2016, 421 . 424 [MANO-2014] 425 "Network Functions Virtualisation (NFV); Management and 426 Orchestration v1.1.1.", ETSI European Telecommunications 427 Standards Institute. , December 2014, 428 . 431 [NGMN-2016] 432 "Hedmar,P., Mschner, K., et al - Description of Network 433 Slicing Concept", NGMN Alliance NGS-3GPP-2016 , January 434 2016, . 437 [NGS-3GPP-2016] 438 "Study on Architecture for Next Generation System - latest 439 version v1.0.2", September 2016, 440 . 443 [ONF-2016] 444 "Paul, M, Schallen, S., Betts, M., Hood, D., Shirazipor, 445 M., Lopes, D., Kaippallimalit, J., - Open Network 446 Fundation document "Applying SDN Architecture to 5G 447 Slicing", Open Network Fundation , April 2016, 448 . 452 Authors' Addresses 454 Alex Galis 455 University College London 457 Email: a.galis@ucl.ac.uk 458 Jie Dong 459 Huawei Technologies 461 Email: jie.dong@huawei.com 463 Kiran Makhijani 464 Huawei Technologies 466 Email: kiran.makhijani@huawei.com 468 Stewart Bryant 469 Huawei Technologies 471 Email: stewart.bryant@gmail.com