idnits 2.17.1 draft-yang-apn-sd-wan-usecase-02.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 (June 4, 2021) is 1055 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.li-6man-app-aware-ipv6-network' is defined on line 242, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-li-apn-framework-02 == 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: December 6, 2021 S. Peng 6 Z. Li 7 Huawei 8 June 4, 2021 10 Usage scenarios of Application-aware Networking (APN) for SD-WAN 11 draft-yang-apn-sd-wan-usecase-02 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 application group, steer its traffic flows along explicit 18 path across the network, and provide SLA guaranteed network services 19 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 December 6, 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-aware information (i.e. APN attribute) along 86 data packets traversing across the APN domain and facilitate fine- 87 granularity network service provisioning and guarantee their SLA 88 requirements. The ever-emerging network services such as network 89 slicing and IOAM can be further enhanced with APN. 91 This document describes the usage scenarios of APN for SD-WAN. 93 2. Usage Scenarios of APN for SD-WAN 95 This section describes the scenarios that can use APN to meet the 96 fine-granularity service operations in SD-WAN. 98 2.1. APN for Traffic Steering into Dedicated WAN 100 In CPE, different application groups are identified based on the 101 existing information in the packet header, and APN attribute is added 102 to the packets along with the tunnel encapsulation. Then the traffic 103 flows can be steered into different WANs that can guarantee their 104 corresponding SLA requirements. 106 +------+ +-----------+ +------+ 107 | APP1 | /------| WAN1 |------\ | APP1 | 108 +------+ / +-----------+ \ +------+ 109 +------+ +-------+ +-----------+ +--------+ +------+ 110 | APP2 |-----| CPE |------| WAN2 |------| CPE |-----| APP2 | 111 +------+ +-------+ +-----------+ +--------+ +------+ 112 +------+ \ +-----------+ / +------+ 113 | APP3 | \------| WAN3 |------/ | APP3 | 114 +------+ +-----------+ +------+ 116 Traffic Steering into WAN 118 2.2. APN for Traffic Steering into Particular Cloud 120 In the multi-cloud scenario, a CPE can be deployed by an enterprise 121 as its gateway to access different clouds. In the CPE (e.g. an 122 universial CPE, called uCPE), different application groups can be 123 identified based on the existing information in the packet header, 124 and APN attribute is added to the packets along with the tunnel 125 encapsulation. The traffic flows are steered into the corresponding 126 cloud where the application servers are running through the 127 corresponding WANs. 129 +------+ +-----------+ +----------+ 130 | APP1 | /---------| WAN1 |-----| Cloud1 | 131 +------+ / +-----------+ +----------+ 132 +------+ +--------+ +-----------+ +----------+ 133 | APP2 |-----| CPE |-----| WAN2 |-----| Cloud2 | 134 +------+ +--------+ +-----------+ +----------+ 135 +------+ \ +-----------+ +----------+ 136 | APP3 | \---------| WAN3 |-----| Cloud3 | 137 +------+ +-----------+ +----------+ 139 Traffic Steering into Cloud 141 2.3. APN for Value-added Service Provisioning in SD-WAN 143 APN can faciliate the value-added service provisioning in SD-WAN, 144 either at the CPE or the POP. 146 At the CPE, network security and application acceleration services 147 can be provided. With APN, certain malicious traffic can be 148 identified and blocked, while the traffic that requires acceleration 149 can be steered through the acceleration service. 151 At the POP, value-added service can be provisioned for certain 152 application groups according to the APN attribute carried in their 153 packets. 155 +------------+ 156 |POP(VAS/SFC)| 157 +------------+ 158 | 159 +-----+ +------------+ +------------+ +------------+ +-----+ 160 | APP |----|CPE(VAS/SFC)|-----| WAN |-----|CPE(VAS/SFC)|-----| APP | 161 +-----+ +------------+ +------------+ +------------+ +-----+ 163 VAS Provisioning 165 2.4. APN for Data Processing in SD-WAN 167 In enterprise, usually important data is kept locally and it is 168 preferred to be processed locally, while other data can be processed 169 with the complex processing capabilities in the cloud. 171 With APN, the traffic can be steered according to the localization 172 characteristics of the data, either being processed locally or in the 173 cloud. 175 +------+ +-------+ +------------+ +------------------+ 176 | Data |-----| CPE |-----| WAN |-----| Cloud (Computing)| 177 +------+ +-------+ +------------+ +------------------+ 178 \ 179 \ +---------------------------+ 180 --- | Local DC (Data Processing)| 181 +---------------------------+ 183 Data Processing 185 3. APN with SRv6 187 By carrying the APN attribute (including APN ID and APN parameters) 188 through data packets, i.e., the delivery of application-aware 189 information and ensuring the security and reliability of application- 190 aware information, the network senses the application groups' 191 requirements and provides high-quality differentiated services 192 according to the demand of the applications. And when the network 193 transmits the data packets, it matches the network correspondence 194 policy according to the APN attribute in the data packets and selects 195 the corresponding SRv6 path to transmit the data packets (e.g., low 196 latency path) to meet the SLA requirements and service chain in order 197 to improve the service quality. 199 +------+ +-----------+ +------+ 200 | APP1 | /-----| SRv6 path1|-----\ | APP1 | 201 +------+ / +-----------+ \ +------+ 202 +------+ +-------+ +-----------+ +--------+ +------+ 203 | APP2 |---| CPE |----| SRv6 path2|---| CPE |---| APP2 | 204 +------+ +-------+ +-----------+ +--------+ +------+ 205 +------+ \ +-----------+ / +------+ 206 | APP3 | \-----| SRv6 path3|-----/ | APP3 | 207 +------+ +-----------+ +------+ 209 SRv6 enabled SD-WAN 211 4. Business Model of APN enhanced SD-WAN 213 With the digital transformation, the network infrastructure and 214 cloud-based applications are emerging as an integrated service of 215 network operators to provide a complete solution to customer. As an 216 overlay technology, SD-WAN is able to simplify the network and make 217 it more service-focused, which has become the de facto option for the 218 Enterprise WAN Edge. SD-WAN enables the network service providers to 219 reshape their network to provide more complex products to meet 220 customers' various requirements. 222 When SD-WAN is integrated with APN, service providers are able to 223 provide network services together with cloud services in a fine- 224 granularity SaaS-like model. The latest functionalities can be 225 delivered via cloud. Customers benefit from the pay-for-use model in 226 per application granularity and have the agility to adjust the level 227 of functionality, capability, and capacity. According to the APN 228 attribute carried by the packets, corresponding paths/WANs can be 229 selected, the SLA can be guaranteed, and value-added services can be 230 provisioned. 232 5. Security Considerations 234 The security consideration can refer to [I-D.li-apn-framework] . 236 6. IANA Considerations 238 There are no IANA considerations in this document. 240 7. Normative References 242 [I-D.li-6man-app-aware-ipv6-network] 243 Li, Z., Peng, S., Li, C., Xie, C., Voyer, D., Li, X., Liu, 244 P., Cao, C., and K. Ebisawa, "Application-aware IPv6 245 Networking (APN6) Encapsulation", draft-li-6man-app-aware- 246 ipv6-network-03 (work in progress), February 2021. 248 [I-D.li-apn-framework] 249 Li, Z., Peng, S., Voyer, D., Li, C., Liu, P., Cao, C., 250 Ebisawa, K., Previdi, S., and J. N. Guichard, 251 "Application-aware Networking (APN) Framework", draft-li- 252 apn-framework-02 (work in progress), February 2021. 254 [I-D.li-apn-problem-statement-usecases] 255 Li, Z., Peng, S., Voyer, D., Xie, C., Liu, P., Qin, Z., 256 Ebisawa, K., Previdi, S., and J. N. Guichard, "Problem 257 Statement and Use Cases of Application-aware Networking 258 (APN)", draft-li-apn-problem-statement-usecases-01 (work 259 in progress), September 2020. 261 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 262 Requirement Levels", BCP 14, RFC 2119, 263 DOI 10.17487/RFC2119, March 1997, 264 . 266 Authors' Addresses 268 Feng Yang 269 China Mobile 270 Beijing 271 China 273 Email: yangfeng@chinamobile.com 275 Weiqiang Cheng 276 China Mobile 277 Beijing 278 China 280 Email: chengweiqiang@chinamobile.com 282 Shuping Peng 283 Huawei 284 Beijing 285 China 287 Email: pengshuping@huawei.com 289 Zhenbin Li 290 Huawei 291 Beijing 292 China 294 Email: lizhenbin@huawei.com