idnits 2.17.1 draft-aoch-nvo3-edge-datacenter-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 : ---------------------------------------------------------------------------- ** There are 49 instances of too long lines in the document, the longest one being 21 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 date (October 28, 2016) is 2736 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'I-D.ietf-nvo3-arch' on line 330 looks like a reference -- Missing reference section? 'I-D.ietf-nvo3-use-case' on line 336 looks like a reference -- Missing reference section? 'RFC7365' on line 342 looks like a reference Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NVO3 WG T. Ao 3 Internet-Draft ZTE Corporation 4 Intended status: Standards Track Z. Chen 5 Expires: May 1, 2017 China Telecom 6 October 28, 2016 8 The use case in Edge Datacenter network 9 draft-aoch-nvo3-edge-datacenter-00.txt 11 Abstract 13 This document introduce the Edge Datacentet network, and describe 14 some use cases about Edge Datacenter, discuss an important component 15 in the Edge Datacenter:Service Gateway and its functions. 17 Service Gateway as a flow distribution device in the Edge DC network, 18 it needs to not only play a gateway of the edge Datacenter network, 19 implementing coordination with existing technology,but also meets 20 many new requirements. For example, acts as a traffic distributor to 21 make sure the packets goes into Edge DC or Metro network, SDN 22 forwarding, and as a leaf in the leaf-spin architecture. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on May 1, 2017. 41 Copyright Notice 43 Copyright (c) 2016 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. Edge Datacenter . . . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. Use case of the EDC . . . . . . . . . . . . . . . . . . . 4 62 3.1.1. Future video application . . . . . . . . . . . . . . 5 63 3.1.2. Edge IOT control application . . . . . . . . . . . . 5 64 3.1.3. Home Hybird Cloud . . . . . . . . . . . . . . . . . . 6 65 3.1.4. Light weight lease line based on application . . . . 7 66 4. Service Gateway . . . . . . . . . . . . . . . . . . . . . . . 8 67 4.1. Functions . . . . . . . . . . . . . . . . . . . . . . . . 8 68 4.1.1. PPPoE proxy . . . . . . . . . . . . . . . . . . . . . 8 69 4.1.2. VxLAN encapsulation . . . . . . . . . . . . . . . . . 8 70 4.1.3. C/S VLAN forwarding . . . . . . . . . . . . . . . . . 9 71 4.1.4. Distribution . . . . . . . . . . . . . . . . . . . . 9 72 5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 9 73 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 75 8. Information References . . . . . . . . . . . . . . . . . . . 9 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 78 1. Introduction 80 With the challenge and the chances of the new network SDN/NFV and the 81 development of the Datacenter, the provider is facing many changes 82 from traditional network, which is representive by traditional CO. 83 How to use the resource of the traditinal CO fully and achieve the 84 transition to the SDN/NFV is the problem providers and vendors need 85 to consider. CO re-architection is the attractive to more and more 86 providers and vendors. and getting more and more attention. Using 87 lots of CO resource, the providers can re-architected CO to Edge DC, 88 which is more adaptive in SDN/NFV. 90 In this document, we will present the description of the Edge 91 Datacenter and its main component Service gateway. As a result, some 92 requirements are proposed for Edge DC and Service Gateway. 94 2. Terminology 96 Edge DC: a Datacenter network which is close to user, may by 97 recontructureed from CO, and is SDN/NFV 99 Servie Gateway: flow distribution device in the Edge Datacenter 100 network. 102 CO: Center Office. 104 3. Edge Datacenter 106 There are many communication COs and there are lots of traditional 107 dedicated devices in these COs in providers network. But with the 108 evoluation of SDN/NFV, Edge Datacenter is developed based on CO. 109 Edge Datacenter basic architecture is showed as Figure 1. In the 110 Edge Datacenter, general server can be used as network element. 111 Virtual network elements includes vBNG,vCPE,vOLT,etc. And the Edge 112 Datacenter uses leaf-spin topology. There are three types in leaf: 113 distribution leaf, Server leaf and Board leaf. Server leaf is 114 connecting Server. Board leaf is the DGW providing DC 115 interconnection. Distribution leaf is the SGW in Figure 1. As a key 116 node in the Edge datacenter, Service Gateway will be elaborated in 117 the next clause. 119 ...... 120 ....( ).... 121 . . 122 +->. Metro Network . ..... 123 | ....( ).... ...( )... 124 | ...... . DCI . 125 | ...( )... 126 | ..... 127 | ^ 128 | | 129 ******************************************************************** 130 * | | * 131 * | +---------+ +---------+ | * 132 * | | | | | | * 133 * | | spin | | spin | | * 134 * | +---------+ +---------+ | * 135 * | / \ / \ | * 136 * | / \ / \ | * 137 * | / \ / \ | * 138 * +---------+ +---------+ +---------+ +---------+ * 139 --------------->| SGW |----| |----| |----| DGW | * 140 * | (leaf) | | leaf | | leaf | | (leaf) | * 141 * +---------+ +---------+ +---------+ +---------+ * 142 * | | | | * 143 * +------------------------------------------------------+ * 144 * | | * 145 * | VNF(vCPE, vBNG...) | * 146 * +------------------------------------------------------+ * 147 * Edge Datacenter(EDC) * 148 ******************************************************************** 150 Figure 1 152 3.1. Use case of the EDC 154 EDC is in the place that is closest to user. It may not have a large 155 scale, but because of its "edge" propoerty, it can meet most access 156 requirements from user.These EDC can get realtime data update through 157 WAN and core DC. By the EDC, we can not only avoid to tranmit lots 158 of duplicated data, but also let the users get the same service and 159 data as same as from core DC, but with better experience. 161 In this section, we will list 4 use cases of the EDC to make it 162 clear. 164 3.1.1. Future video application 166 In this use case, all the video traffic are getted from EDC so that 167 the users can get better experience when they play games or watch 168 video,etc. EDC has the capability of abstract for elephant 169 traffic(IPTV), and support the extremely low latency video 170 application. Figure 2 is the diagram of this case. 172 +-------------+ 173 | | 174 | EDC | 175 +-------------+ 176 ^ 177 VR,AR,8K | 178 | 179 +-----------+ 180 VR,AR,8k----------------------->| | 181 Internet----------------------->|Service GW |------------->Internet 182 +-----------+ 184 Figure 2 186 3.1.2. Edge IOT control application 188 EDC has its own computational capbility, and getting more and more 189 intelligent. In the case that UAV( UnmannedAerialVehicle ), it needs 190 to communicate with the apps in EDC so that the UAV can be remote 191 controlled. Similar with other IOT control scenarios. Figure 3 is 192 the diagram of this case. 194 +-------------------+ 195 | | 196 | APP | 197 +-------------------+ 198 / \ Dynamical deploy 199 / \ 200 |/_ _\| 201 +---------------+ +---------------+ 202 | EDC | | EDC | 203 | (App) | | (App) | 204 +---------------+ +---------------+ 205 ^ ^ 206 | Control flow | 207 +---------------+ +---------------+ 208 | Service GW | | Service GW | 209 | |--- | |---+--------->Internet 210 +---------------+ | +---------------+ | 211 ^ | ^ | 212 | +-----------------|-----------+ 213 | | 214 +---+ +---+ 215 |UVA|------------------------->|UVA| 216 +---+ Fly to... +---+ 218 Figure 3 220 3.1.3. Home Hybird Cloud 222 In this case, EDC is an extension of Home Gateway. Some expanded 223 computation or expanded store are extended into EDC instead of on 224 HGW. Even some APPs can also extened into EDC. Users can get more 225 applications, such as OTT white box, remote download, and remote 226 desktop, etc. Figure 4 is the diagram of this case. 228 +------------------------+ 229 | | 230 | EDC | 231 | (Expanded computation) | 232 | (Expaned store) | 233 | | 234 +------------------------+ 235 ^ 236 +--------------+ | 237 APP1------------>| | | 238 APP2------------>| HGW | +-------------+ 239 PC..............>| (Computation)|------------>| | 240 | (store) |............>| Service GW |...............>Internet 241 +--------------+ +-------------+ 243 Figure 4 245 3.1.4. Light weight lease line based on application 247 In this use case, EDC is a control node for user 2/3 layer lease line 248 (VxLAN or MPLS). It can support dynamically setup the tunnel 249 according to application identification; support user private IP 250 address or address management, etc. Figure 5 is the diagram of this 251 case. 253 +-----------+ +------------+ L2/3 lease line +------------------+ 254 | | | |----------------->| | 255 | User GW |------------>| Service GW |-------+ | EDC | 256 +-----------+ +------------+ | | (Authentication) | 257 | | | 258 | | (DHCP) | 259 +-----------+ +------------+ | | | 260 | | | |-------|--------->| (Tunnel | 261 | User GW |------------>| Service GW |-----+ | | management) | 262 +-----------+ +------------+ | | | | 263 | | | (User Apps) | 264 | | | | 265 +-----------+ +------------+ | | | ..... | 266 | | | |-----|-|--------->| | 267 | User GW |------------>| Service GW |---+ | | | | 268 +-----------+ +------------+ | | | +------------------+ 269 | | | 270 | | +-------------------> 271 | +---------------------> Internet 272 +-----------------------> 274 Figure 5 276 4. Service Gateway 278 From those use case above, we know that Service Gateway as a key node 279 in the forwarding plane, is a flow distribution device in Edge DC 280 network. It needs not only to support currently existing protocols, 281 but aslo to meet all kinds of new requirements, ie. SDN forwarding, 282 virtualization,SDN control, and spine-leaf network architecture, 283 dynamic SFC, etc. The main purpose of the Service Gateway is to 284 improve the forwarding, and converge or distribute traffic according 285 to different service. By the Service Gateway, we can avoid the 286 hairpin of the traffic to Metro network, and divide the traffic into 287 north-south traffic and south-east traffic clearly. 289 4.1. Functions 291 4.1.1. PPPoE proxy 293 To terminate PPPoE tunnel. 295 4.1.2. VxLAN encapsulation 297 Encapsulate the packets into Edge DC with VxLAN as VTEP. Provide 298 VxLAN mapping, forwarding, and interconnection with VLAN as a 299 gateway. 301 4.1.3. C/S VLAN forwarding 303 Support QinQ VLAN forwarding, so that be compatible to traditional 304 network, and reduce the capacity of FDB. 306 4.1.4. Distribution 308 Achieve traffic distribution according to service VLAN. The 309 forwarding table on the SGW can be configurated by the SDN controller 310 with NATCONF or OFPCONFIG protocol. 312 Can implement linea forwarding based any field in IP header. 314 5. Conclusion 316 CO being re-architected as Edge DC is a very important step for 317 provider's evolving to SDN/NFV. 319 6. Security Considerations 321 Service Gateway must have the capability of checking the validation 322 of user's address. 324 7. IANA Considerations 326 N/A 328 8. Information References 330 [I-D.ietf-nvo3-arch] 331 Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T. 332 Narten, "An Architecture for Data Center Network 333 Virtualization Overlays (NVO3)", draft-ietf-nvo3-arch-08 334 (work in progress), September 2016. 336 [I-D.ietf-nvo3-use-case] 337 Yong, L., Dunbar, L., Toy, M., Isaac, A., and V. Manral, 338 "Use Cases for Data Center Network Virtualization Overlay 339 Networks", draft-ietf-nvo3-use-case-12 (work in progress), 340 October 2016. 342 [RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y. 343 Rekhter, "Framework for Data Center (DC) Network 344 Virtualization", RFC 7365, DOI 10.17487/RFC7365, October 345 2014, . 347 Authors' Addresses 349 Ting Ao 350 ZTE Corporation 351 No.889, BiBo Road 352 Shanghai 201203 353 China 355 Phone: +86 21 68897642 356 Email: ao.ting@zte.com.cn 358 Zhonghua Chen 359 China Telecom 360 No.1835, South PuDong Road 361 Shanghai 201203 362 China 364 Phone: +86 18918588897 365 Email: 18918588897@189.cn