idnits 2.17.1 draft-liu-coinrg-requirement-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 : ---------------------------------------------------------------------------- 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 (November 3, 2019) is 1607 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Computing in Network Research Group P. Liu 3 Internet-Draft L. Geng 4 Intended status: Informational China Mobile 5 Expires: May 6, 2020 November 3, 2019 7 Requirement of Computing in network 8 draft-liu-coinrg-requirement-01 10 Abstract 12 New technology such as IOT, edge computing,etc. propose the 13 requirement of computing in network, so convergence of network and 14 computing has become a trend. This document points out the 15 requirements of computing in network according to the development of 16 new Industry, including the performance, function and management 17 requirements. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on May 6, 2020. 42 Copyright Notice 44 Copyright (c) 2019 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Requirements of Network . . . . . . . . . . . . . . . . . . . 2 61 2.1. Performance requirement . . . . . . . . . . . . . . . . . 3 62 2.1.1. Precision . . . . . . . . . . . . . . . . . . . . . . 3 63 2.1.2. Concurrent . . . . . . . . . . . . . . . . . . . . . 3 64 2.1.3. Security . . . . . . . . . . . . . . . . . . . . . . 4 65 2.2. Function requirement . . . . . . . . . . . . . . . . . . 4 66 2.2.1. Computing aware scheduling . . . . . . . . . . . . . 4 67 2.2.2. Function based addressing . . . . . . . . . . . . . . 4 68 2.2.3. Network programmability . . . . . . . . . . . . . . . 4 69 2.3. Management requirement . . . . . . . . . . . . . . . . . 5 70 2.3.1. Cross domain management . . . . . . . . . . . . . . . 5 71 2.3.2. Simple management . . . . . . . . . . . . . . . . . . 5 72 3. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 75 6. Normative References . . . . . . . . . . . . . . . . . . . . 6 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 78 1. Overview 80 Intelligence in the whole industry has a huge demand for computing, 81 which put forwards immense challenges to cloud computing and network. 82 Network Architecture is undergoing a transformation towards cloud and 83 service, providing rapid response and flexible deployment for 84 different industries. The perfomance, function and management 85 requirements of network's development need to be considered. 87 2. Requirements of Network 89 Computing in the network has some requirements of performance, 90 function and management, to ensure the operation of future business 91 and user experience. 93 2.1. Performance requirement 95 2.1.1. Precision 97 Precision of the network refers to the deterministic of latency, 98 packet loss rate and computing resource. 100 The traditional network's best-effort forwarding mode can no longer 101 meet the demand of such services for network latency. The 102 deterministic latency brings forward a new measure latitude for 103 network, which changes from in-time to on-time. 105 Packet loss rate is another factor to evaluate the precision of the 106 network. Utilizing the ubiquitous computing capability of the 107 network, network prediction and segment-by-segment path 108 retransmitting are realized based on AI, network transmission can be 109 optimized and service QoS can be ensured. 111 Besides those, how to precisely distribute network computing power to 112 meet the requirements of business requests is also a challenge to the 113 network. It considers the network status and the performance status 114 of computing resources to dynamic match the computing power. So the 115 user experience, utilization rate of computing resources and the 116 network efficiency can be optimum. 118 Some technologies such as time-sensitive network TSN, deterministic 119 network DETNET, etc., have proposed corresponding technical means to 120 provide network bearers with deterministic latency(IEEE802.1Qbv, 121 IEEE802.1Qbu) and packet loss rate and guarantee the user's business 122 experience. However, it also needs to consider how to guarantee the 123 service's end-to-end latency, packet loss rate and resource 124 utilization rate. 126 2.1.2. Concurrent 128 In the network computing system, the number of computing nodes 129 increases, so there is a lot of parallel computing needs between 130 nodes, coupled with the trend of interconnection of everything in the 131 future, it will bring great challenges to the network connection. 133 Therefore, how to build and deploy these distributed computing nodes, 134 ensure the processing capacity of the network element, and the 135 storage and call capacity of the database are worth studying. 137 2.1.3. Security 139 Computing In network has brought the trend of network convergence in 140 different regions. For example, 5g network of operators can go deep 141 into the vertical industry user site to provide users with higher 142 quality network services, which will bring the convergence of 143 operator's network and user site network. Besides, industrial 144 Internet brings the trend of integration of industrial OT network and 145 IT network to further improve the production efficiency of the 146 industry. It need to ensure the security of the network, including 147 the mutual trust and non aggression of information among regions, 148 which may require further protection and detection measures. 150 2.2. Function requirement 152 2.2.1. Computing aware scheduling 154 Computing in network needs a reasonable scheduling strategy, which 155 means computing aware scheduling. According to the business 156 requests, dynamicly computing power matching is carried out based on 157 network status and performance of computing resources to achieve 158 optimal user experience, optimal utilization of computing resources 159 and optimal network efficiency. In computing aware scheduling, 160 computing is seen as "link state" and the computing resource 161 information should be exposed. 163 2.2.2. Function based addressing 165 Traditional application-based addressing can not accurately grasp the 166 network performance in real time. The comprehensive performance of 167 addressing results based on application layer may not be the best, 168 resulting in poor business experience. In the function based 169 addressing, the application deconstruction components on the server 170 side are distributed on the cloud platform, and the business logic in 171 the server is transferred to the client side. So the client only 172 needs to care about the computing function itself, not about the 173 computing resources such as server, virtual machine, container and so 174 on, so as to realize the function as a service. 176 2.2.3. Network programmability 178 Network programmability requires the network to configure parameters 179 according to users' needs, such as the network requirements including 180 bandwidth, latency and jitter , and computing requirements, such as 181 CPU, storage and memory. Users can transfer requirements based on 182 network capabilities or states, like network resources and computing 183 resources. Thus it can effectively support future business 184 requirements requiring high quality of service. 186 2.3. Management requirement 188 2.3.1. Cross domain management 190 Computing in the network should guarantee the end-to-end network 191 management to meet the needs of different network topology, 192 performance and function, which involves cross domain network 193 arrangement. In the process of network data transmission, different 194 services will be forwarded by different ways or different network 195 protocols. For example, in cross enterprise network construction, 196 business requests from branches to headquarters may go through the 197 VPN protocol of layer 2, and the routing protocol of layer 3. The 198 branches send business requests to the cloud, may go through the 199 conversion from passive optical network to wavelength division 200 multiplexing, etc. It is necessary to realize the seamless 201 connection of all levels of network transformation, ensure the end- 202 to-end identifiability of business data flow, and provide a dedicated 203 network for carrying and forwarding. 205 2.3.2. Simple management 207 Compared with the traditional network, computing in the network is a 208 new architecture and system. Scheduling and cooperation among 209 different network domains, different operators and different users 210 are very complex problems. However, an effective management system 211 is still needed to make the network capability and computing 212 capability to cooperate with each other, and distribute the computing 213 power reasonably. 215 3. Conclusion 217 In the new business requirements, the existing network technology can 218 not meet the needs of transmission, computing and efficiency. It 219 need to meet the new network system requirements from the 220 performance, function and management aspects, to ensure that the 221 connectivity is everywhere, computing is everywhere, and intelligent 222 support is everywhere. 224 4. Security Considerations 226 TBD. 228 5. IANA Considerations 230 TBD. 232 6. Normative References 234 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 235 Requirement Levels", BCP 14, RFC 2119, 236 DOI 10.17487/RFC2119, March 1997, 237 . 239 Authors' Addresses 241 Peng Liu 242 China Mobile 243 Beijing 100053 244 China 246 Email: liupengyjy@chinamobile.com 248 Liang Geng 249 China Mobile 250 Beijing 100053 251 China 253 Email: gengliang@chinamobile.com