< draft-ietf-nvo3-use-case-03.txt   draft-ietf-nvo3-use-case-04.txt >
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Internet Draft Huawei Internet Draft Huawei
Category: Informational M. Toy Category: Informational M. Toy
Comcast Comcast
A. Isaac A. Isaac
Bloomberg Bloomberg
V. Manral V. Manral
Hewlett-Packard Hewlett-Packard
L. Dunbar L. Dunbar
Huawei Huawei
Expires: July 2014 January 8, 2014 Expires: January 2015 July 1, 2014
Use Cases for DC Network Virtualization Overlays Use Cases for DC Network Virtualization Overlays
draft-ietf-nvo3-use-case-03 draft-ietf-nvo3-use-case-04
Abstract Abstract
This document describes DC Network Virtualization (NVO3) use cases This document describes DC Network Virtualization (NVO3) use cases
that may be potentially deployed in various data centers and apply that may be potentially deployed in various data centers and apply
to different applications. to different 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
skipping to change at page 1, line 46 skipping to change at page 1, line 46
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July, 2014. This Internet-Draft will expire on January, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction ................................................ 3
1.1. Contributors..............................................4 1.1. Contributors ........................................... 4
1.2. Terminology...............................................4 1.2. Terminology ............................................ 4
2. Basic Virtual Networks in a Data Center........................5 2. Basic Virtual Networks in a Data Center ..................... 4
3. Interconnecting DC Virtual Network and External Networks.......6 3. Interconnecting DC Virtual Network and External Networks .... 6
3.1. DC Virtual Network Access via Internet....................6 3.1. DC Virtual Network Access via Internet ................. 6
3.2. DC VN and Enterprise Sites interconnected via SP WAN......7 3.2. DC VN and Enterprise Sites interconnected via SP WAN ... 7
4. DC Applications Using NVO3.....................................9 4. DC Applications Using NVO3 .................................. 8
4.1. Supporting Multi Technologies and Applications in a DC....9 4.1. Supporting Multi Technologies and Applications in a DC . 9
4.2. Tenant Network with Multi-Subnets or across multi DCs.....9 4.2. Tenant Network with Multi-Subnets or across multi DCs .. 9
4.3. Virtualized Data Center (vDC)............................11 4.3. Virtualized Data Center (vDC) ......................... 11
5. OAM Considerations............................................13 5. OAM Considerations ......................................... 12
6. Summary.......................................................13 6. Summary .................................................... 13
7. Security Considerations.......................................14 7. Security Considerations .................................... 14
8. IANA Considerations...........................................14 8. IANA Considerations ........................................ 14
9. Acknowledgements..............................................14 9. Acknowledgements ........................................... 14
10. References...................................................14 10. References ................................................ 14
10.1. Normative References....................................14 10.1. Normative References ................................. 14
10.2. Informative References..................................15 10.2. Informative References ............................... 15
Authors' Addresses...............................................15 Authors' Addresses ............................................ 15
1. Introduction 1. Introduction
Server Virtualization has changed IT industry in terms of efficiency, Server Virtualization has changed IT industry in terms of efficiency,
cost, and the speed in providing a new applications and/or services. cost, and the speed in providing a new applications and/or services.
However, today's data center networks have limited support for cloud However, today's data center networks have limited support for cloud
applications and multi tenant networks.[NVO3PRBM] The goal of DC applications and multi tenant networks.[NVO3PRBM] The goal of DC
Network Virtualization Overlays, i.e. NVO3, is to decouple the Network Virtualization Overlays, i.e. NVO3, is to decouple the
communication among tenant systems from DC physical networks and to communication among tenant systems from DC physical networks and to
allow one physical network infrastructure to provide: 1) multi- allow one physical network infrastructure to provide: 1) multi-
tenant virtual networks and traffic isolation among the virtual tenant virtual networks and traffic isolation among the virtual
networks over the same physical network; 2) independent address networks over the same physical network; 2) independent address
spaces in individual virtual networks such as MAC, IP, TCP/UDP etc; spaces in individual virtual networks such as MAC, IP, TCP/UDP etc;
3) Flexible VM placement including the ability to move from one 3) Flexible VMs or workload placement including the ability to move
server to another without requiring VM address and configuration them from servers to other servers without requiring VM address and
change and the ability doing a hot move in which no disruption to configuration change and the ability doing a hot move in which no
the live application on the VM. These characteristics will help disruption to the live application on VM. These characteristics will
address the issues in today's cloud applications [NVO3PRBM]. help address the issues in today's cloud applications [NVO3PRBM].
Although NVO3 enables a true network virtualization environment, the An NVO3 network is necessary to interconnect with a physical network,
NVO3 solution has to address the communication between a virtual where tenant systems attach to the both networks. For examples: 1)
network and a physical network. This is because 1) many DCs that DCs that migrates toward NVO3 solution will be done in steps; 2) a
need to provide network virtualization are currently running over lot of DC applications are served to Internet users which exist on
physical networks, the migration will be in steps; 2) a lot of DC
applications are served to Internet users which run directly on
physical networks; 3) some applications are CPU bound like Big Data physical networks; 3) some applications are CPU bound like Big Data
analytics and may not need the virtualization capability. analytics and may not run on virtualized resources.
This document is to describe general NVO3 use cases that apply to This document is to describe general NVO3 use cases that apply to
various data centers. Three types of the use cases described here various data centers. Three types of the use cases described here
are: are:
o Basic virtual networks in DC. A virtual network connects many o Basic virtual networks in DC. All TS of the virtual networks are
tenant systems in a Data Center site (or more) and forms one L2 located within one DC. The Virtual networks can be either L2 or
or L3 communication domain. Many virtual networks are over same L3. The number of Virtual Networks to be supported in NVO3 is
DC physical network. The case may be used for DC internal usually more than what traditional VLAN can support. The case is
applications that constitute the DC East-West traffic. often referred as to the DC East-West traffic.
o DC virtual network access from external. A DC provider offers a o Virtual networks that span across multiple Data Centers or
secure DC service to an enterprise customer and/or Internet users. customer premises, i.e. a Virtual Network that has some nodes in
An enterprise customer may use a traditional VPN provided by a a DC and other nodes in other places. An enterprise customer may
carrier or an IPsec tunnel over Internet connecting to a virtual use a traditional VPN provided by a carrier or an IPsec tunnel
network within a provider DC site. This mainly constitutes DC over Internet to connect the TSs across multiple DCs and customer
North-South traffic. premises.
o DC applications or services that may use NVO3. Three scenarios o DC applications or services that may use NVO3. Three scenarios
are described: 1) use NVO3 and other network technologies to are described: 1) use NVO3 and other network technologies to
build a tenant network; 2) construct several virtual networks as build a tenant network; 2) construct several virtual networks as
a tenant network; 3) apply NVO3 to a virtualized DC (vDC). a tenant network; 3) apply NVO3 to a virtualized DC (vDC).
The document uses the architecture reference model defined in The document uses the architecture reference model defined in
[NVO3FRWK] to describe the use cases. [NVO3FRWK] to describe the use cases.
1.1. Contributors 1.1. Contributors
skipping to change at page 7, line 41 skipping to change at page 7, line 34
| +--------+ | Tunnel | +--------+ | Tunnel
+----------------+ +----------------+
DC Provider Site DC Provider Site
Figure 1 DC Virtual Network Access via Internet Figure 1 DC Virtual Network Access via Internet
3.2. DC VN and Enterprise Sites interconnected via SP WAN 3.2. DC VN and Enterprise Sites interconnected via SP WAN
An enterprise company may lease the VM and storage resources hosted An enterprise company may lease the VM and storage resources hosted
in the 3rd party DC to run its applications. For example, the rd company may run its web applications at 3 party sites but run in the 3rd party DC to run its applications. For example, the
backend applications in own DCs. The Web applications and backend rd applications need to communicate privately. The 3 party DC may company may run its web applications at 3 party sites but run
backend applications in own DCs. The Web applications and backend
applications need to communicate privately. The 3 party DC may
construct one or more virtual networks to connect all VMs and construct one or more virtual networks to connect all VMs and
storage running the Enterprise Web applications. The company may buy storage running the Enterprise Web applications. The company may buy
a p2p private tunnel such as VPWS from a SP to interconnect its site a p2p private tunnel such as VPWS from a SP to interconnect its site
and the virtual network at the 3rd party site. A protocol is and the virtual network at the 3rd party site. A protocol is
necessary for exchanging the reachability between two peering points necessary for exchanging the reachability between two peering points
and the traffic are carried over the tunnel. If an enterprise has and the traffic are carried over the tunnel. If an enterprise has
multiple sites, it may buy multiple p2p tunnels to form a mesh multiple sites, it may buy multiple p2p tunnels to form a mesh
interconnection among the sites and the third party site. This interconnection among the sites and the third party site. This
requires each site peering with all other sites for route requires each site peering with all other sites for route
distribution. distribution.
 End of changes. 11 change blocks. 
49 lines changed or deleted 49 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/