draft-ietf-nvo3-use-case-16.txt   draft-ietf-nvo3-use-case-17.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
Verizon Verizon
A. Isaac A. Isaac
Juniper Networks Juniper Networks
V. Manral V. Manral
Ionos Networks Ionos Networks
Expires: July 2017 February 10, 2017 Expires: July 2017 February 20, 2017
Use Cases for Data Center Network Virtualization Overlay Networks Use Cases for Data Center Network Virtualization Overlay Networks
draft-ietf-nvo3-use-case-16 draft-ietf-nvo3-use-case-17
Abstract Abstract
This document describes data center network virtualization overlay This document describes data center network virtualization overlay
(NVO3) network use cases that can be deployed in various data (NVO3) network use cases that can be deployed in various data
centers and serve different data center 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
skipping to change at page 4, line 36 skipping to change at page 4, line 36
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 terminology defined in [RFC7365] and This document uses the terminology 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.
ASBR: Autonomous System Boarder Routers (ASBR) ASBR: Autonomous System Border Routers (ASBR)
DMZ: Demilitarized Zone. A computer or small sub-network that sits DMZ: Demilitarized Zone. A computer or small sub-network that sits
between a more trusted internal network, such as a corporate private between a more trusted internal network, such as a corporate private
LAN, and an un-trusted or less trusted external network, such as the LAN, and an un-trusted or less trusted external network, such as the
public Internet. public Internet.
DNS: Domain Name Service [RFC1035] DNS: Domain Name Service [RFC1035]
DC Operator: An entity that is responsible for constructing and DC Operator: An entity that is responsible for constructing and
managing all resources in data centers, including, but not limited managing all resources in data centers, including, but not limited
skipping to change at page 6, line 14 skipping to change at page 6, line 14
2. DC with Large Number of Virtual Networks 2. DC with Large Number of Virtual Networks
A DC provider often uses NVO3 virtual networks for internal A DC provider often uses NVO3 virtual networks for internal
applications where each application runs on many VMs or physical applications where each application runs on many VMs or physical
servers and the provider requires applications to be segregated from servers and the provider requires applications to be segregated from
each other. A DC may run a larger number of NVO3 virtual networks to each other. A DC may run a larger number of NVO3 virtual networks to
support many applications concurrently, where traditional IEEE802.1Q support many applications concurrently, where traditional IEEE802.1Q
based VLAN solution is limited to 4094 VLANs. based VLAN solution is limited to 4094 VLANs.
Applications running on VMs may require different quantity of Applications running on VMs may require different quantity of
computing resource, which may result in computing resource shortage computing resource, which may result in computing resource shortage
on some servers and other servers being nearly idle. Shortage of on some servers and other servers being nearly idle. Shortage of
computing resource may impact application performance. DC operators computing resource may impact application performance. DC operators
desire VM or workload movement for resource usage optimization. VM desire VM or workload movement for resource usage optimization. VM
dynamic placement and mobility results in frequent changes of the dynamic placement and mobility results in frequent changes of the
binding between a TS and an NVE. The TS reachability update binding between a TS and an NVE. The TS reachability update
mechanisms should take significantly less time than the typical mechanisms should take significantly less time than the typical re-
TCP/SCTP re-transmission Time-out window, so that end points' transmission Time-out window of a reliable transport protocol such
TCP/SCTP connections won't be impacted by a TS becoming bound to a as TCP and SCTP, so that end points' transport connections won't be
different NVE. The capability of supporting many TSs in a virtual impacted by a TS becoming bound to a different NVE. The capability
network and many virtual networks in a DC is critical for an NVO3 of supporting many TSs in a virtual network and many virtual
solution. networks in a DC is critical for an NVO3 solution.
When NVO3 virtual networks segregate VMs belonging to different When NVO3 virtual networks segregate VMs belonging to different
applications, DC operators can independently assign MAC and/or IP applications, DC operators can independently assign MAC and/or IP
address space to each virtual network. This addressing is more address space to each virtual network. This addressing is more
flexible than requiring all hosts in all NVO3 virtual networks to flexible than requiring all hosts in all NVO3 virtual networks to
share one address space. In contrast, typical use of IEEE 802.1Q share one address space. In contrast, typical use of IEEE 802.1Q
VLANs requires a single common MAC address space. VLANs requires a single common MAC address space.
3. DC NVO3 virtual network and External Network Interconnection 3. DC NVO3 virtual network and External Network Interconnection
skipping to change at page 8, line 41 skipping to change at page 8, line 41
In this case, an Enterprise customer wants to use a Service Provider In this case, an Enterprise customer wants to use a Service Provider
(SP) WAN VPN [RFC4364] [RFC7432] to interconnect its sites with an (SP) WAN VPN [RFC4364] [RFC7432] to interconnect its sites with an
NVO3 virtual network in a DC site. The Service Provider constructs a NVO3 virtual network in a DC site. The Service Provider constructs a
VPN for the enterprise customer. Each enterprise site peers with an VPN for the enterprise customer. Each enterprise site peers with an
SP PE. The DC Provider and VPN Service Provider can build an NVO3 SP PE. The DC Provider and VPN Service Provider can build an NVO3
virtual network and a WAN VPN independently, and then interconnect virtual network and a WAN VPN independently, and then interconnect
them via a local link, or a tunnel between the DC GW and WAN them via a local link, or a tunnel between the DC GW and WAN
Provider Edge (PE) devices. The control plane interconnection Provider Edge (PE) devices. The control plane interconnection
options between the DC and WAN are described in [RFC4364]. Using the options between the DC and WAN are described in [RFC4364]. Using the
option A specified in [RFC4364] with VRF-LITE [VRF-LITE], both option A specified in [RFC4364] with VRF-LITE [VRF-LITE], both
Autonomous System Boarder Routers (ASBR), i.e., DC GW and SP PE, Autonomous System Border Routers (ASBR), i.e., DC GW and SP PE,
maintain a routing/forwarding table (VRF). Using the option B maintain a routing/forwarding table (VRF). Using the option B
specified in [RFC4364], the DC ASBR and SP ASBR do not maintain the specified in [RFC4364], the DC ASBR and SP ASBR do not maintain the
VRF table; they only maintain the NVO3 virtual network and VPN VRF table; they only maintain the NVO3 virtual network and VPN
identifier mappings, i.e., label mapping, and swap the label on the identifier mappings, i.e., label mapping, and swap the label on the
packets in the forwarding process. Both option A and B allow the packets in the forwarding process. Both option A and B allow the
NVO3 virtual network and VPN using their own identifiers and two NVO3 virtual network and VPN using their own identifiers and two
identifiers are mapped at DC GW. With the option C in [RFC4364], the identifiers are mapped at DC GW. With the option C in [RFC4364], the
VN and VPN use the same identifier and both ASBRs perform the tunnel VN and VPN use the same identifier and both ASBRs perform the tunnel
stitching, i.e., tunnel segment mapping. Each option has pros/cons stitching, i.e., tunnel segment mapping. Each option has pros/cons
[RFC4364] and has been deployed in SP networks depending on the [RFC4364] and has been deployed in SP networks depending on the
 End of changes. 5 change blocks. 
17 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/