idnits 2.17.1 draft-yang-apn-sd-wan-usecase-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 : ---------------------------------------------------------------------------- ** There are 9 instances of too long lines in the document, the longest one being 5 characters in excess of 72. 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 (February 19, 2021) is 1161 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-03) exists of draft-li-6man-app-aware-ipv6-network-02 == Outdated reference: A later version (-07) exists of draft-li-apn-framework-01 == Outdated reference: A later version (-08) exists of draft-li-apn-problem-statement-usecases-01 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Yang 3 Internet-Draft W. Cheng 4 Intended status: Informational China Mobile 5 Expires: August 23, 2021 S. Peng 6 Z. Li 7 Huawei 8 February 19, 2021 10 Usage scenarios of Application-aware Networking (APN) for SD-WAN 11 draft-yang-apn-sd-wan-usecase-01 13 Abstract 15 This document describes the usage of Application-aware Networking 16 (APN) in SD-WAN scenarios. In these scenarios, APN is able to 17 identify a particular application, steer its traffic flows along 18 explicit path across the network, and provide SLA guaranteed network 19 services such as low latency and high reliability. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in RFC 2119 [RFC2119]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on August 23, 2021. 44 Copyright Notice 46 Copyright (c) 2021 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 (https://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 respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Usage Scenarios of APN for SD-WAN . . . . . . . . . . . . . . 3 63 2.1. APN for Traffic Steering into Dedicated WAN . . . . . . . 3 64 2.2. APN for Traffic Steering into Particular Cloud . . . . . 3 65 2.3. APN for Value-added Service Provisioning in SD-WAN . . . 4 66 2.4. APN for Data Processing in SD-WAN . . . . . . . . . . . . 4 67 3. APN with SRv6 . . . . . . . . . . . . . . . . . . . . . . . . 5 68 4. Business Model of APN enhanced SD-WAN . . . . . . . . . . . . 6 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 71 7. Normative References . . . . . . . . . . . . . . . . . . . . 6 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 74 1. Introduction 76 As more and more applications are moved to the cloud, the traditional 77 WAN architecture starts facing challenges. Software-defined Wide 78 Area Network (SD-WAN) provides a cloud-friendly way of 79 interconnecting branch offices and applications in the cloud over any 80 combination of transport services such as MPLS and 4G LTE, which is 81 able to optimising application performance with low costs. 83 Application-aware Networking (APN) is introduced in 84 [I-D.li-apn-framework] and [I-D.li-apn-problem-statement-usecases]. 85 APN conveys application information such as application/user/flow 86 identifiers and SLA/service requirements along data packets into 87 network [I-D.li-6man-app-aware-ipv6-network] and make the network 88 aware of applications and their requirements, so to provide 89 corresponding network services and guarantee their SLA requirements. 90 The ever-emerging network services such as network slicing and iOAM 91 can be further enhanced with the application awareness in the network 92 enabled by APN. 94 This document describes the usage scenarios of APN for SD-WAN. 96 2. Usage Scenarios of APN for SD-WAN 98 This section describes the scenarios that can use APN to meet the 99 fine-granularity service operations in SD-WAN. 101 2.1. APN for Traffic Steering into Dedicated WAN 103 In CPE, different applications can be recognized and their traffic 104 flows can be steered into different WANs that can guarantee their 105 corresponding SLA requirements. 107 +------+ +-----------+ +------+ 108 | APP1 | /------| WAN1 |------\ | APP1 | 109 +------+ / +-----------+ \ +------+ 110 +------+ +-------+ +-----------+ +--------+ +------+ 111 | APP2 |-----| CPE |------| WAN2 |------| CPE |-----| APP2 | 112 +------+ +-------+ +-----------+ +--------+ +------+ 113 +------+ \ +-----------+ / +------+ 114 | APP3 | \------| WAN3 |------/ | APP3 | 115 +------+ +-----------+ +------+ 117 Traffic Steering into WAN 119 2.2. APN for Traffic Steering into Particular Cloud 121 In the multi-cloud scenario, a CPE can be deployed by an enterprise 122 as its gateway to access different clouds. In the CPE (e.g. an 123 universial CPE, called uCPE), different applications can be 124 recogonized and steered into the corresponding cloud where the 125 application servers are running through the corresponding WANs. 127 +------+ +-----------+ +----------+ 128 | APP1 | /---------| WAN1 |-----| Cloud1 | 129 +------+ / +-----------+ +----------+ 130 +------+ +--------+ +-----------+ +----------+ 131 | APP2 |-----| CPE |-----| WAN2 |-----| Cloud2 | 132 +------+ +--------+ +-----------+ +----------+ 133 +------+ \ +-----------+ +----------+ 134 | APP3 | \---------| WAN3 |-----| Cloud3 | 135 +------+ +-----------+ +----------+ 137 Traffic Steering into Cloud 139 2.3. APN for Value-added Service Provisioning in SD-WAN 141 APN can faciliate the value-added service provisioning in SD-WAN, 142 either at the CPE or the POP. 144 At the CPE, network security and application acceleration services 145 can be provided. With APN, certain malicious applications can be 146 recogonized and blocked, while the traffic from the applications that 147 require acceleration can be steered through the acceleration service. 149 At the POP, value-added service can be provisioned for certain 150 applications according to the application information carried in 151 their packets. 153 +------------+ 154 |POP(VAS/SFC)| 155 +------------+ 156 | 157 +-----+ +------------+ +------------+ +------------+ +-----+ 158 | APP |----|CPE(VAS/SFC)|-----| WAN |-----|CPE(VAS/SFC)|-----| APP | 159 +-----+ +------------+ +------------+ +------------+ +-----+ 161 VAS Provisioning 163 2.4. APN for Data Processing in SD-WAN 165 In enterprise, usually important data is kept locally and it is 166 preferred to be processed locally, while other data can be processed 167 with the complex processing capabilities in the cloud. 169 With APN, the traffic can be steered according to the localization 170 characteristics of the data, either being processed locally or in the 171 cloud. 173 +------+ +-------+ +------------+ +------------------+ 174 | Data |-----| CPE |-----| WAN |-----| Cloud (Computing)| 175 +------+ +-------+ +------------+ +------------------+ 176 \ 177 \ +---------------------------+ 178 --- | Local DC (Data Processing)| 179 +---------------------------+ 181 Data Processing 183 3. APN with SRv6 185 By carrying the application identification and demand information 186 through data packets, i.e., the delivery of application information 187 and ensuring the security and reliability of application information, 188 the network senses the application and provides it with high-quality 189 differentiated services according to the demand of the application. 190 And when the network transmits the data packets, it matches the 191 network correspondence policy according to the application 192 information in the data packets and selects the corresponding SRv6 193 path to transmit the data packets (e.g., low latency path) to meet 194 the SLA requirements and service chain in order to improve the 195 service quality. 197 +------+ +-----------+ +------+ 198 | APP1 | /-----| SRv6 path1|-----\ | APP1 | 199 +------+ / +-----------+ \ +------+ 200 +------+ +-------+ +-----------+ +--------+ +------+ 201 | APP2 |---| CPE |----| SRv6 path2|---| CPE |---| APP2 | 202 +------+ +-------+ +-----------+ +--------+ +------+ 203 +------+ \ +-----------+ / +------+ 204 | APP3 | \-----| SRv6 path3|-----/ | APP3 | 205 +------+ +-----------+ +------+ 207 SRv6 enabled SD-WAN 209 4. Business Model of APN enhanced SD-WAN 211 With the digital transformation, the network infrastructure and 212 cloud-based applications are emerging as an integrated service of 213 network operators to provide a complete solution to customer. As an 214 overlay technology, SD-WAN is able to simplify the network and make 215 it more service-focused, which has become the de facto option for the 216 Enterprise WAN Edge. With SD-WAN, the network is not just a pipe any 217 more, and network becomes application aware. It enables the network 218 service providers to reshape their network to provide more complex 219 products to meet customers' various requirements. 221 When SD-WAN is integrated with APN, service providers are able to 222 provide network services together with cloud services in a fine- 223 granularity SaaS-like model. The latest functionalities can be 224 delivered via cloud. Customers benefit from the pay-for-use model in 225 per application granularity and have the agility to adjust the level 226 of functionality, capability, and capacity. According to the 227 application-aware information carried by the important applications, 228 corresponding paths/WANs can be selected, the SLA can be guaranteed, 229 and value-added services can be provisioned. 231 5. Security Considerations 233 The security consideration can refer to [I-D.li-apn-framework] . 235 6. IANA Considerations 237 There are no IANA considerations in this document. 239 7. Normative References 241 [I-D.li-6man-app-aware-ipv6-network] 242 Li, Z., Peng, S., Li, C., Xie, C., Voyer, D., Li, X., Liu, 243 P., Liu, C., and K. Ebisawa, "Application-aware IPv6 244 Networking (APN6) Encapsulation", draft-li-6man-app-aware- 245 ipv6-network-02 (work in progress), July 2020. 247 [I-D.li-apn-framework] 248 Li, Z., Peng, S., Voyer, D., Li, C., Geng, L., Cao, C., 249 Ebisawa, K., Previdi, S., and J. Guichard, "Application- 250 aware Networking (APN) Framework", draft-li-apn- 251 framework-01 (work in progress), September 2020. 253 [I-D.li-apn-problem-statement-usecases] 254 Li, Z., Peng, S., Voyer, D., Xie, C., Liu, P., Qin, Z., 255 Ebisawa, K., Previdi, S., and J. Guichard, "Problem 256 Statement and Use Cases of Application-aware Networking 257 (APN)", draft-li-apn-problem-statement-usecases-01 (work 258 in progress), September 2020. 260 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 261 Requirement Levels", BCP 14, RFC 2119, 262 DOI 10.17487/RFC2119, March 1997, 263 . 265 Authors' Addresses 267 Feng Yang 268 China Mobile 269 Beijing 270 China 272 Email: yangfeng@chinamobile.com 274 Weiqiang Cheng 275 China Mobile 276 Beijing 277 China 279 Email: chengweiqiang@chinamobile.com 281 Shuping Peng 282 Huawei 283 Beijing 284 China 286 Email: pengshuping@huawei.com 288 Zhenbin Li 289 Huawei 290 Beijing 291 China 293 Email: lizhenbin@huawei.com