| < draft-ietf-nvo3-use-case-11.txt | draft-ietf-nvo3-use-case-12.txt > | |||
|---|---|---|---|---|
| skipping to change at page 1, line 14 ¶ | skipping to change at page 1, line 14 ¶ | |||
| Category: Informational Huawei | Category: Informational Huawei | |||
| M. Toy | M. Toy | |||
| A. Isaac | A. Isaac | |||
| Juniper Networks | Juniper Networks | |||
| V. Manral | V. Manral | |||
| Ionos Networks | Ionos Networks | |||
| Expires: April 2017 October 3, 2016 | Expires: April 2017 October 3, 2016 | |||
| Use Cases for Data Center Network Virtualization Overlays | Use Cases for Data Center Network Virtualization Overlay Networks | |||
| draft-ietf-nvo3-use-case-11 | draft-ietf-nvo3-use-case-12 | |||
| Abstract | Abstract | |||
| This document describes data center network virtualization over | This document describes data center network virtualization over | |||
| layer (NVO3) use cases that can be deployed in various data centers | layer (NVO3) network use cases that can be deployed in various data | |||
| and serve different applications. | centers and serve different data center applications. | |||
| Status of this Memo | Status of this Memo | |||
| This Internet-Draft is submitted to IETF in full conformance with | This Internet-Draft is submitted to IETF in full conformance with | |||
| the provisions of BCP 78 and BCP 79. | the provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 3, line 12 ¶ | skipping to change at page 3, line 12 ¶ | |||
| Acknowledgements.................................................14 | Acknowledgements.................................................14 | |||
| Authors' Addresses...............................................14 | Authors' Addresses...............................................14 | |||
| 1. Introduction | 1. Introduction | |||
| Server virtualization has changed the Information Technology (IT) | Server virtualization has changed the Information Technology (IT) | |||
| industry in terms of the efficiency, cost, and speed of providing | industry in terms of the efficiency, cost, and speed of providing | |||
| new applications and/or services such as cloud applications. However | new applications and/or services such as cloud applications. However | |||
| traditional data center (DC) networks have some limits in supporting | traditional data center (DC) networks have some limits in supporting | |||
| cloud applications and multi tenant networks [RFC7364]. The goal of | cloud applications and multi tenant networks [RFC7364]. The goal of | |||
| data center network virtualization overlay (NVO3) network is to | data center network virtualization overlay (NVO3) networks is to | |||
| decouple the communication among tenant systems from DC physical | decouple the communication among tenant systems from DC physical | |||
| infrastructure networks and to allow one physical network | infrastructure networks and to allow one physical network | |||
| infrastructure to provide: | infrastructure: | |||
| o Multi-tenant virtual networks and traffic isolation among the | o Carry many NVO3 networks and isolate different NVO3 network | |||
| virtual networks over the same physical network. | traffic on a physical network that carries NVO3 network traffic. | |||
| o Independent address spaces in individual virtual networks such as | o Independent address spaces in individual NVO3 networks such as | |||
| MAC, IP, TCP/UDP etc. | MAC, IP, TCP/UDP etc. | |||
| o Flexible Virtual Machines (VM) and/or workload placement | o Flexible Virtual Machines (VM) and/or workload placement | |||
| including the ability to move them from one server to another | including the ability to move them from one server to another | |||
| without requiring VM address and configuration changes, and the | without requiring VM address changes and physical infrastructure | |||
| ability to perform a "hot move" with no disruption to the live | network configuration changes, and the ability to perform a "hot | |||
| application running on VMs. | move" with no disruption to the live application running on VMs. | |||
| These characteristics of NVO3 help address the issues that cloud | These characteristics of NVO3 networks help address the issues that | |||
| applications face in Data Centers [RFC7364]. | cloud applications face in data centers [RFC7364]. | |||
| An NVO3 network may interconnect with another NVO3 network on the | An NVO3 network may interconnect with another NVO3 network on the | |||
| same physical network, or another physical network (i.e., not the | same physical network, or another physical network (i.e., not the | |||
| physical network that the NVO3 network is over), via a gateway. The | physical network that the NVO3 network is carried over), via a | |||
| use case examples for the latter are: 1) DCs that migrate toward an | gateway. The use case examples for the latter are: 1) DCs that | |||
| NVO3 solution will be done in steps, where a portion of tenant | migrate toward an NVO3 solution will be done in steps, where a | |||
| systems in a VN is on virtualized servers while others exist on a | portion of tenant systems in a VN is on virtualized servers while | |||
| LAN. 2) many DC applications serve to Internet users who are on | others exist on a LAN. 2) many DC applications serve to Internet | |||
| physical networks; 3) some applications are CPU bound, such as Big | users who are on physical networks; 3) some applications are CPU | |||
| Data analytics, and may not run on virtualized resources. Some | bound, such as Big Data analytics, and may not run on virtualized | |||
| inter-VN policies can be enforced at the gateway. | resources. Some inter-VN policies can be enforced at the gateway. | |||
| This document describes general NVO3 use cases that apply to various | This document describes general NVO3 network use cases that apply to | |||
| data centers. The use cases described here represent DC provider's | various data centers. The use cases described here represent DC | |||
| interests and vision for their cloud services. The document groups | provider's interests and vision for their cloud services. The | |||
| the use cases into three categories from simple to advance in term | document groups the use cases into three categories from simple to | |||
| of implementation. However the implementations of these use cases | advance in term of implementation. However the implementations of | |||
| are outside the scope of this document. These three categories are | these use cases are outside the scope of this document. These three | |||
| highlighted below: | categories are highlighted below: | |||
| o Basic NVO3 networks (Section 2). All Tenant Systems (TS) in the | o Basic NVO3 networks (Section 2). All Tenant Systems (TS) in the | |||
| network are located within the same DC. The individual networks | network are located within the same DC. The individual networks | |||
| can be either Layer 2 (L2) or Layer 3 (L3). The number of NVO3 | can be either Layer 2 (L2) or Layer 3 (L3). The number of NVO3 | |||
| networks in a DC is much higher than what traditional VLAN based | networks in a DC is much higher than what traditional VLAN based | |||
| virtual networks [IEEE 802.1Q] can support. This case is often | virtual networks [IEEE 802.1Q] can support. This case is often | |||
| referred as to the DC East-West traffic. | referred as to the DC East-West traffic. | |||
| o A virtual network that spans across multiple Data Centers and/or | o A virtual network that spans across multiple Data Centers and/or | |||
| to customer premises where NVO3 networks are constructed and | to customer premises where NVO3 networks are constructed and | |||
| End of changes. 11 change blocks. | ||||
| 29 lines changed or deleted | 29 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||