< draft-ietf-nvo3-use-case-09.txt   draft-ietf-nvo3-use-case-10.txt >
Network Working Group L. Yong Network Working Group L. Yong
Internet Draft L. Dunbar Internet Draft L. Dunbar
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: March 2017 September 1, 2016 Expires: March 2017 September 22, 2016
Use Cases for Data Center Network Virtualization Overlays Use Cases for Data Center Network Virtualization Overlays
draft-ietf-nvo3-use-case-09 draft-ietf-nvo3-use-case-10
Abstract Abstract
This document describes Data Center (DC) Network Virtualization over This document describes Data Center (DC) Network Virtualization over
Layer 3 (NVO3) use cases that can be deployed in various data Layer 3 (NVO3) use cases that can be deployed in various data
centers and serve different applications. centers and serve 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 45 skipping to change at page 1, line 45
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 March 3, 2017. This Internet-Draft will expire on March 22, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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. Terminology...............................................4 1.1. Terminology...............................................4
2. Basic Virtual Networks in a Data Center........................4 2. Basic Virtual Networks in a Data Center........................5
3. DC Virtual Network and External Network Interconnection........6 3. DC Virtual Network and External Network Interconnection........6
3.1. DC Virtual Network Access via the Internet................6 3.1. DC Virtual Network Access via the Internet................6
3.2. DC VN and SP WAN VPN Interconnection......................7 3.2. DC VN and SP WAN VPN Interconnection......................8
4. DC Applications Using NVO3.....................................8 4. DC Applications Using NVO3.....................................9
4.1. Supporting Multiple Technologies..........................9 4.1. Supporting Multiple Technologies..........................9
4.2. DC Application with Multiple Virtual Networks.............9 4.2. DC Application with Multiple Virtual Networks.............9
4.3. Virtualized Data Center (vDC)............................10 4.3. Virtual Data Center (vDC)................................10
5. Summary.......................................................11 5. Summary.......................................................11
6. Security Considerations.......................................12 6. Security Considerations.......................................12
7. IANA Considerations...........................................12 7. IANA Considerations...........................................12
8. References....................................................12 8. References....................................................12
8.1. Normative References.....................................12 8.1. Normative References.....................................12
8.2. Informative References...................................12 8.2. Informative References...................................12
Contributors.....................................................13 Contributors.....................................................13
Acknowledgements.................................................14 Acknowledgements.................................................14
Authors' Addresses...............................................14 Authors' Addresses...............................................14
skipping to change at page 3, line 43 skipping to change at page 3, line 43
NVO3 network is over), via a gateway. The use case examples for the NVO3 network is over), via a gateway. The use case examples for the
latter are: 1) DCs that migrate toward an NVO3 solution will be done latter are: 1) DCs that migrate toward an NVO3 solution will be done
in steps, where a portion of tenant systems in a VN is on in steps, where a portion of tenant systems in a VN is on
virtualized servers while others exist on a LAN. 2) many DC virtualized servers while others exist on a LAN. 2) many DC
applications serve to Internet users who are on physical networks; 3) applications serve to Internet users who are on physical networks; 3)
some applications are CPU bound, such as Big Data analytics, and may some applications are CPU bound, such as Big Data analytics, and may
not run on virtualized resources. Some inter-VN policies can be not run on virtualized resources. Some inter-VN policies can be
enforced at the gateway. enforced at the gateway.
This document describes general NVO3 use cases that apply to various This document describes general NVO3 use cases that apply to various
data centers. Three types of the use cases described in this data centers. The use cases described here represent DC provider's
document are: interests and vision for their cloud services. The document groups
the use cases into three categories from simple to advance in term
of implementation. However the implementations of these use cases
are outside the scope of this document. These three categories are
highlighted below:
o Basic NVO3 virtual networks in a DC (Section 2). All Tenant o Basic NVO3 virtual networks in a DC (Section 2). All Tenant
Systems (TS) in the virtual network are located within the same Systems (TS) in the virtual network are located within the same
DC. The individual virtual networks can be either Layer 2 (L2) or DC. The individual virtual networks can be either Layer 2 (L2) or
Layer 3 (L3). The number of NVO3 virtual networks in a DC is much Layer 3 (L3). The number of NVO3 virtual networks in a DC is much
higher than what traditional VLAN based virtual networks [IEEE higher than what traditional VLAN based virtual networks [IEEE
802.1Q] can support. This case is often referred as to the DC 802.1Q] can support. This case is often referred as to the DC
East-West traffic. East-West traffic.
o Virtual networks that span across multiple Data Centers and/or to o Virtual networks that span across multiple Data Centers and/or to
customer premises, i.e., an NVO3 virtual network where some customer premises, i.e., an NVO3 virtual network where some
tenant systems in a DC attach to interconnect another virtual or tenant systems in a DC attach to interconnect another virtual or
physical network outside the data center. An enterprise customer physical network outside the data center. An enterprise customer
may use a traditional carrier VPN or an IPsec tunnel over the may use a traditional carrier VPN or an IPsec tunnel over the
Internet to communicate with its systems in the DC. This is Internet to communicate with its systems in the DC. This is
described in Section 3. described in Section 3.
o DC applications or services require an advanced network that o DC applications or services require an advanced network that
contains several NVO3 virtual networks that are interconnected by contains several NVO3 virtual networks that are interconnected by
the gateways. Three scenarios are described in Section 4: 1) the gateways. Three scenarios are described in Section 4: 1)
using NVO3 and other network technologies to build a tenant supporting multiple technologies; 2) constructing several virtual
network; 2) constructing several virtual networks as a tenant networks as a tenant network; 3) applying NVO3 to a virtual Data
network; 3) applying NVO3 to a virtualized DC (vDC). Center (vDC).
The document uses the architecture reference model defined in The document uses the architecture reference model defined in
[RFC7365] to describe the use cases. [RFC7365] to describe the use cases.
1.1. Terminology 1.1. Terminology
This document uses the terminologies defined in [RFC7365] and This document uses the terminologies defined in [RFC7365] and
[RFC4364]. Some additional terms used in the document are listed [RFC4364]. Some additional terms used in the document are listed
here. here.
DMZ: Demilitarized Zone. A computer or small sub-network that sits DMZ: Demilitarized Zone. A computer or small sub-network that sits
between a trusted internal network, such as a corporate private LAN, between a trusted internal network, such as a corporate private LAN,
and an un-trusted external network, such as the public Internet. and an un-trusted external network, such as the public Internet.
DNS: Domain Name Service [RFC1035] DNS: Domain Name Service [RFC1035]
NAT: Network Address Translation [RFC1631] DC Operator: A role who is responsible to construct and manage cloud
service instances in their life-cycle and manage DC infrastructure
that runs these cloud instances.
DC Provider: A company that uses its DC infrastructure to offer
cloud services to its customers.
NAT: Network Address Translation [RFC3022]
vGW: virtual Gateway; a gateway component used for an NVO3 virtual
network to interconnect with another virtual/physical network.
Note that a virtual network in this document refers to an NVO3 Note that a virtual network in this document refers to an NVO3
virtual network in a DC [RFC7365]. virtual network in a DC [RFC7365].
2. Basic Virtual Networks in a Data Center 2. Basic Virtual Networks in a Data Center
A virtual network in a DC enables communications among Tenant A virtual network in a DC enables communications among Tenant
Systems (TS). A TS can be a physical server/device or a virtual Systems (TS). A TS can be a physical server/device or a virtual
machine (VM) on a server, i.e., end-device [RFC7365]. A Network machine (VM) on a server, i.e., end-device [RFC7365]. A Network
Virtual Edge (NVE) can be co-located with a TS, i.e., on the same Virtual Edge (NVE) can be co-located with a TS, i.e., on the same
skipping to change at page 8, line 43 skipping to change at page 9, line 9
assigned to the enterprise from one sever to another in the DC assigned to the enterprise from one sever to another in the DC
without the enterprise customer being aware, i.e., with no impact on without the enterprise customer being aware, i.e., with no impact on
the enterprise's 'live' applications. Such advanced technologies the enterprise's 'live' applications. Such advanced technologies
bring DC providers great benefits in offering cloud services, but bring DC providers great benefits in offering cloud services, but
add some requirements for NVO3 [RFC7364] as well. add some requirements for NVO3 [RFC7364] as well.
4. DC Applications Using NVO3 4. DC Applications Using NVO3
NVO3 technology provides DC operators with the flexibility in NVO3 technology provides DC operators with the flexibility in
designing and deploying different applications in an end-to-end designing and deploying different applications in an end-to-end
virtualization overlay environment. Operators no longer need to virtualization overlay environment. The operators no longer need to
worry about the constraints of the DC physical network configuration worry about the constraints of the DC physical network configuration
when creating VMs and configuring a virtual network. A DC provider when creating VMs and configuring a virtual network. A DC provider
may use NVO3 in various ways, in conjunction with other physical may use NVO3 in various ways, in conjunction with other physical
networks and/or virtual networks in the DC for a reason. This networks and/or virtual networks in the DC for a reason. This
section highlights some use cases for this goal. section highlights some use cases for this goal.
4.1. Supporting Multiple Technologies 4.1. Supporting Multiple Technologies
Servers deployed in a large data center are often installed at Servers deployed in a large data center are often installed at
different times, and may have different capabilities/features. Some different times, and may have different capabilities/features. Some
skipping to change at page 10, line 5 skipping to change at page 10, line 8
booking run, and a back zone (database tier) with Data. External booking run, and a back zone (database tier) with Data. External
users are only able to communicate with the Web application in the users are only able to communicate with the Web application in the
front zone; the back zone can only receive traffic from the front zone; the back zone can only receive traffic from the
application zone. In this case, communications between the zones application zone. In this case, communications between the zones
must pass through a GW/firewall. Each zone can be implemented by one must pass through a GW/firewall. Each zone can be implemented by one
virtual network and a GW/firewall can be used to between two virtual virtual network and a GW/firewall can be used to between two virtual
networks, i.e., two zones. A tunnel carrying virtual network traffic networks, i.e., two zones. A tunnel carrying virtual network traffic
has to be terminated at the GW/firewall where overlay traffic is has to be terminated at the GW/firewall where overlay traffic is
processed. processed.
4.3. Virtualized Data Center (vDC) 4.3. Virtual Data Center (vDC)
An Enterprise Data Center today may deploy routers, switches, and An Enterprise Data Center today may deploy routers, switches, and
network appliance devices to construct its internal network, DMZ, network appliance devices to construct its internal network, DMZ,
and external network access; it may have many servers and storage and external network access; it may have many servers and storage
running various applications. With NVO3 technology, a DC Provider running various applications. With NVO3 technology, a DC Provider
can construct a virtualized DC over its physical DC infrastructure can construct a virtual Data Center (vDC) over its physical DC
and offer a virtual DC service to enterprise customers. A vDC at the infrastructure and offer a virtual Data Center service to enterprise
DC Provider site provides the same capability as the physical DC at customers. A vDC at the DC Provider site provides the same
the customer site. A customer manages their own applications running capability as the physical DC at a customer site. A customer manages
in their vDC. A DC Provider can further offer different network its own applications running in its vDC. A DC Provider can further
service functions to the customer. The network service functions may offer different network service functions to the customer. The
include firewall, DNS, load balancer, gateway, etc. network service functions may include firewall, DNS, load balancer,
gateway, etc.
Figure 3 below illustrates one such scenario. For simplicity, it Figure 2 below illustrates one such scenario at service abstraction
only shows the L3 VN or L2 VN in abstraction. In this example, the level. In this example, the vDC contains several L2 VNs (L2VNx,
DC Provider operators create several L2 VNs (L2VNx, L2VNy, L2VNz) to L2VNy, L2VNz) to group the tenant systems together on a per-
group the tenant systems together on a per-application basis, and application basis, and one L3 VN (L3VNa) for the internal routing. A
one L3 VN (L3VNa) for the internal routing. A network firewall and network firewall and gateway runs on a VM or server that connects to
gateway runs on a VM or server that connects to L3VNa and is used L3VNa and is used for inbound and outbound traffic processing. A
for inbound and outbound traffic processing. A load balancer (LB) is load balancer (LB) is used in L2VNx. A VPN is also built between the
used in L2VNx. A VPN is also built between the gateway and gateway and enterprise router. An Enterprise customer runs
enterprise router. The Enterprise customer runs Web/Mail/Voice Web/Mail/Voice applications on VMs within the vDC. The users at the
applications on VMs at the provider DC site which may be spread Enterprise site access the applications running in the vDC via the
across many servers. The users at the Enterprise site access the VPN; Internet users access these applications via the
applications running in the provider DC site via the VPN; Internet gateway/firewall at the provider DC site.
users access these applications via the gateway/firewall at the
provider DC.
The Enterprise customer decides which applications should be The Enterprise customer decides which applications should be
accessible only via the intranet and which should be assessable via accessible only via the intranet and which should be assessable via
both the intranet and Internet, and configures the proper security both the intranet and Internet, and configures the proper security
policy and gateway function at the firewall/gateway. Furthermore, an policy and gateway function at the firewall/gateway. Furthermore, an
enterprise customer may want multi-zones in a vDC (See section 4.1) enterprise customer may want multi-zones in a vDC (See section 4.2)
for the security and/or the ability to set different QoS levels for for the security and/or the ability to set different QoS levels for
the different applications. the different applications.
The vDC use case requires the NVO3 solution to provide DC operators The vDC use case requires an NVO3 solution to provide DC operators
with an easy and quick way to create a VN and NVEs for any vDC with an easy and quick way to create a VN and NVEs for any vDC
design, to allocate TSs and assign TSs to the corresponding VN, and design, to allocate TSs and assign TSs to the corresponding VN, and
to illustrate vDC topology and manage/configure individual elements to illustrate vDC topology and manage/configure individual elements
in the vDC in a secure way. in the vDC in a secure way.
Internet ^ Internet Internet ^ Internet
| |
^ +--+---+ ^ +--+---+
| | GW | | | GW |
| +--+---+ | +--+---+
| | | |
+-------+--------+ +--+---+ +-------+--------+ +--+---+
|Firewall/Gateway+--- VPN-----+router| |Firewall/Gateway+--- VPN-----+router|
+-------+--------+ +-+--+-+ +-------+--------+ +-+--+-+
| | | | | |
...+.... |..| ...+.... |..|
+-------: L3 VNa :---------+ LANs +-------: L3 VNa :---------+ LANs
skipping to change at page 11, line 27 skipping to change at page 11, line 29
+-+-+ | | +-+-+ | |
...+... ...+... ...+... ...+... ...+... ...+...
: L2VNx : : L2VNy : : L2VNz : : L2VNx : : L2VNy : : L2VNz :
....... ....... ....... ....... ....... .......
|..| |..| |..| |..| |..| |..|
| | | | | | | | | | | |
Web App. Mail App. VoIP App. Web App. Mail App. VoIP App.
Provider DC Site Provider DC Site
Figure 2 - Virtual Data Center (vDC) Figure 2 - Virtual Data Center Abstraction View
5. Summary 5. Summary
This document describes some general and potential NVO3 use cases in This document describes some general and potential NVO3 use cases in
DCs. The combination of these cases will give operators the DCs. The combination of these cases will give operators the
flexibility and capability to design more sophisticated cases for flexibility and capability to design more sophisticated cases for
various cloud applications. various cloud applications.
DC services may vary, from infrastructure as a service (IaaS), to DC services may vary, from infrastructure as a service (IaaS), to
platform as a service (PaaS), to software as a service (SaaS). platform as a service (PaaS), to software as a service (SaaS).
skipping to change at page 12, line 43 skipping to change at page 12, line 48
8.1. Normative References 8.1. Normative References
[RFC7364] Narten, T., et al "Problem Statement: Overlays for Network [RFC7364] Narten, T., et al "Problem Statement: Overlays for Network
Virtualization", RFC7364, October 2014. Virtualization", RFC7364, October 2014.
[RFC7365] Lasserre, M., Motin, T., and et al, "Framework for DC [RFC7365] Lasserre, M., Motin, T., and et al, "Framework for DC
Network Virtualization", RFC7365, October 2014. Network Virtualization", RFC7365, October 2014.
8.2. Informative References 8.2. Informative References
[IEEE 802.1Q] IEEE, "IEEE Standard for Local and metropolitan area [IEEE802.1Q] IEEE, "IEEE Standard for Local and metropolitan area
networks -- Media Access Control (MAC) Bridges and Virtual networks -- Media Access Control (MAC) Bridges and Virtual
Bridged Local Area", IEEE Std 802.1Q, 2011. Bridged Local Area", IEEE Std 802.1Q, 2011.
[NVO3HYVR2NVE] Li, Y., et al, "Hypervisor to NVE Control Plane [NVO3HYVR2NVE] Li, Y., et al, "Hypervisor to NVE Control Plane
Requirements", draft-ietf-nvo3-hpvr2nve-cp-req-01, work in Requirements", draft-ietf-nvo3-hpvr2nve-cp-req-05, work in
progress. progress.
[NVO3ARCH] Black, D., et al, "An Architecture for Overlay Networks [NVO3ARCH] Black, D., et al, "An Architecture for Overlay Networks
(NVO3)", draft-ietf-nvo3-arch-02, work in progress. (NVO3)", draft-ietf-nvo3-arch-08, work in progress.
[NVO3MCAST] Ghanwani, A., "Framework of Supporting Applications [NVO3MCAST] Ghanwani, A., "Framework of Supporting Applications
Specific Multicast in NVO3", draft-ghanwani-nvo3-app- Specific Multicast in NVO3", draft-ghanwani-nvo3-app-
mcast-framework-02, work in progress. mcast-framework-02, work in progress.
[RFC1035] Mockapetris, P., "DOMAIN NAMES - Implementation and [RFC1035] Mockapetris, P., "DOMAIN NAMES - Implementation and
Specification", RFC1035, November 1987. Specification", RFC1035, November 1987.
[RFC1631] Egevang, K., Francis, P., "The IP network Address [RFC3022] Srisuresh, P. and Egevang, K., "Traditional IP Network
Translator (NAT)", RFC1631, May 1994. Address Translator (Traditional NAT)", RFC3022, January
2001.
[RFC4301] Kent, S., "Security Architecture for the Internet [RFC4301] Kent, S., "Security Architecture for the Internet
Protocol", rfc4301, December 2005 Protocol", rfc4301, December 2005
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006. Networks (VPNs)", RFC 4364, February 2006.
[RFC7348] Mahalingam,M., Dutt, D., ific Multicast in etc "VXLAN: A [RFC7348] Mahalingam,M., Dutt, D., ific Multicast in etc "VXLAN: A
Framework for Overlaying Virtualized Layer 2 Networks over Framework for Overlaying Virtualized Layer 2 Networks over
Layer 3 Networks", RFC7348 August 2014. Layer 3 Networks", RFC7348 August 2014.
skipping to change at page 13, line 45 skipping to change at page 14, line 4
[VRF-LITE] Cisco, "Configuring VRF-lite", http://www.cisco.com [VRF-LITE] Cisco, "Configuring VRF-lite", http://www.cisco.com
Contributors Contributors
Vinay Bannai Vinay Bannai
PayPal PayPal
2211 N. First St, 2211 N. First St,
San Jose, CA 95131 San Jose, CA 95131
Phone: +1-408-967-7784 Phone: +1-408-967-7784
Email: vbannai@paypal.com Email: vbannai@paypal.com
Ram Krishnan Ram Krishnan
Brocade Communications Brocade Communications
San Jose, CA 95134 San Jose, CA 95134
Phone: +1-408-406-7890 Phone: +1-408-406-7890
Email: ramk@brocade.com Email: ramk@brocade.com
Kieran Milne Kieran Milne
Juniper Networks Juniper Networks
1133 Innovation Way 1133 Innovation Way
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Phone: +1-408-745-2000 Phone: +1-408-745-2000
Email: kmilne@juniper.net Email: kmilne@juniper.net
Acknowledgements Acknowledgements
Authors like to thank Sue Hares, Young Lee, David Black, Pedro Authors like to thank Sue Hares, Young Lee, David Black, Pedro
Marques, Mike McBride, David McDysan, Randy Bush, Uma Chunduri, Eric Marques, Mike McBride, David McDysan, Randy Bush, Uma Chunduri, Eric
Gray, David Allan, and Joe Touch for the review, comments, and Gray, David Allan, Joe Touch, and Olufemi Komolafe for the review,
suggestions. comments, and suggestions.
Authors' Addresses Authors' Addresses
Lucy Yong Lucy Yong
Huawei Technologies Huawei Technologies
Phone: +1-918-808-1918 Phone: +1-918-808-1918
Email: lucy.yong@huawei.com Email: lucy.yong@huawei.com
Linda Dunbar Linda Dunbar
 End of changes. 24 change blocks. 
49 lines changed or deleted 60 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/