idnits 2.17.1 draft-contreras-bmwg-5g-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 8, 2019) is 1753 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-01 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Benchmarking Methodology Working Group LM. Contreras 3 Internet-Draft J. Rodriguez 4 Intended status: Experimental L. Luque 5 Expires: January 9, 2020 Telefonica 6 July 8, 2019 8 5G transport network benchmarking 9 draft-contreras-bmwg-5g-00 11 Abstract 13 New 5G services are starting to be deployed in operational networks, 14 leveraging in a number of novel technologies and architectural 15 concepts. The purpose of this document is to overview the 16 implications of 5G services in transport networks and to provide 17 guidance on bechmarking of the infratructures supporting those 18 services. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on January 9, 2020. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions used in this document . . . . . . . . . . . . . . 2 56 3. 5G services . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 4. Benchmarking aspects of transport networks in 5G . . . . . . 3 58 5. Guidance on 5G transport benchmarking . . . . . . . . . . . . 4 59 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 61 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 9.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 9.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 5G services are starting to be introduced in real operational 70 networks. The challenges of 5G are multiple, impacting in different 71 technological areas such as radio access, mobile core and transport 72 network. From all those technological areas, the transport network 73 is the focus of this document. 75 It is important for operators to have a good basis of benchmarking 76 solutions, technologies and architectures before moving them into 77 production. With such aim, this document intends to overview 78 available guidelines to assist on the benchmarking of 5G transport 79 networks, identifying gaps that could require further work and 80 details. 82 As result, it is expected to provide guidance on benchmarking of 5G 83 transport network infrastructures ready for experimentation in lab 84 environments or real deployment in operational networks. 86 2. Conventions used in this document 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in RFC2119 [RFC2119]. 92 3. 5G services 94 5G transport networks will need to accommodate different kind of 95 services with very distinct needs and requirements leveraging on the 96 same infrastructure. 5G services can be grouped in three main 97 categories, namely enhanced Mobile Broadband (eMBB), ultra-Reliable 98 and Low Latency Communications (URLLC), and massive Machine Type 99 Communications (mMTC). Each of them presents different inherent 100 characteristics spanning from ultra-low latency to high bandwidth and 101 high reliability. For instance, eMMB services are expected to 102 provide peak bit rates of up to 1 Gbps, uRRLC services will require 103 latencies as lower as below microsecond delays, and mMTC will demand 104 to support up to 100 times the number of current sessions. All these 105 features impose great constraints to the networks deployed today in 106 backhaul and aggregation, in terms of not only network capacity but 107 also in terms of data processing, especially for guaranteeing very 108 low latencies. 110 The impact in the transport network of those challenges is increased 111 by some other additional challenges introduced by the emergence of 112 two new technological paradigms: the network virtualization and the 113 network programmability. 115 In one hand, virtualization will introduce uncertainty on the traffic 116 patterns due to the flexibility and scalability in the deployment 117 traffic sources in the transport network. On the other hand, 118 programmability will potentially enable automated reconfiguration of 119 the transport network which requires coordination mechanisms to avoid 120 misconfigurations. 122 A final consideration is the introduction of the network slicing 123 concept in 5G networks. According to that, the objective is to 124 provide customized and tailored logical networks to different 125 customers, allocating resources for the specific customer service 126 request. 128 4. Benchmarking aspects of transport networks in 5G 130 The benchmarking aspects of 5G transport networks can be then 131 structured in the following manner: 133 Data plane benchmarking: aspects to consider in data plane 134 benchmarking refer to both hardware capabilities as well as to 135 transport encapsulations. Examples of hardware capabilities are 136 recent developments such as IEEE TSN, and example of encapsulation 137 is SRv6 [I-D.ietf-spring-srv6-network-programming]. 139 Control plane benchmarking: aspects to consider for control plane 140 relates to transport infrastructure programmability. In this case 141 some previous works exists such as RFC8456 [RFC8456]. 143 Management plane benchmarking: one specific aspect of management 144 benchmarking in 5G refers to the capability of managing the 145 transport network slice lifecycle. 147 Architecture benchmarking: new architectural frameworks are being 148 conceived to support advanced services like 5G. An example of 149 these architectures is [I-D.ietf-detnet-architecture]. 151 5. Guidance on 5G transport benchmarking 153 To be completed. 155 6. Security Considerations 157 This draft does not include any security considerations. 159 7. IANA Considerations 161 This draft does not include any IANA considerations 163 8. Acknowledgements 165 This work has been partly funded by the European Commission through 166 the H2020 project 5G-EVE (Grant Agreement no. 815074). 168 9. References 170 9.1. Normative References 172 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 173 Requirement Levels", BCP 14, RFC 2119, 174 DOI 10.17487/RFC2119, March 1997, 175 . 177 9.2. Informative References 179 [I-D.ietf-detnet-architecture] 180 Finn, N., Thubert, P., Varga, B., and J. Farkas, 181 "Deterministic Networking Architecture", draft-ietf- 182 detnet-architecture-13 (work in progress), May 2019. 184 [I-D.ietf-spring-srv6-network-programming] 185 Filsfils, C., Camarillo, P., Leddy, J., 186 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 187 Network Programming", draft-ietf-spring-srv6-network- 188 programming-01 (work in progress), July 2019. 190 [RFC8456] Bhuvaneswaran, V., Basil, A., Tassinari, M., Manral, V., 191 and S. Banks, "Benchmarking Methodology for Software- 192 Defined Networking (SDN) Controller Performance", 193 RFC 8456, DOI 10.17487/RFC8456, October 2018, 194 . 196 Authors' Addresses 198 Luis M. Contreras 199 Telefonica 200 Ronda de la Comunicacion, s/n 201 Sur-3 building, 3rd floor 202 Madrid 28050 203 Spain 205 Email: luismiguel.contrerasmurillo@telefonica.com 206 URI: http://lmcontreras.com/ 208 Juan Rodriguez 209 Telefonica 210 Zurbaran, 12 211 Madrid 28010 212 Spain 214 Email: juan.rodriguezmartinez@telefonica.com 216 Lourdes Luque 217 Telefonica 218 Zurbaran, 12 219 Madrid 28010 220 Spain 222 Email: lourdes.luquecanto@telefonica.com