< draft-boutros-l2vpn-vxlan-evpn-03.txt		draft-boutros-l2vpn-vxlan-evpn-04.txt >
	skipping to change at page 1, line 13 ¶		skipping to change at page 1, line 13 ¶
	INTERNET-DRAFT Sami Boutros		INTERNET-DRAFT Sami Boutros
	Intended Status: Informational Ali Sajassi		Intended Status: Informational Ali Sajassi
	Samer Salam		Samer Salam
	Dennis Cai		Dennis Cai
	Samir Thoria		Samir Thoria
	Cisco Systems		Cisco Systems
	Tapraj Singh		Tapraj Singh
	John Drake		John Drake
	Juniper Networks		Juniper Networks
	Expires: August 18, 2014 February 14, 2014
			Jeff Tantsura
			Ericsson
			Expires: January 3, 2015 July 2, 2014
	VXLAN DCI Using EVPN		VXLAN DCI Using EVPN
	draft-boutros-l2vpn-vxlan-evpn-03.txt		draft-boutros-l2vpn-vxlan-evpn-04.txt
	Abstract		Abstract
	This document describes how Ethernet VPN (E-VPN) technology can be		This document describes how Ethernet VPN (E-VPN) technology can be
	used to interconnect VXLAN or NVGRE networks over an MPLS/IP network.		used to interconnect VXLAN or NVGRE networks over an MPLS/IP network.
	This is to provide intra-subnet connectivity at Layer 2 and control-		This is to provide intra-subnet connectivity at Layer 2 and control-
	plane separation among the interconnected VXLAN or NVGRE networks.		plane separation among the interconnected VXLAN or NVGRE networks.
	The scope of the learning of host MAC addresses in VXLAN or NVGRE		The scope of the learning of host MAC addresses in VXLAN or NVGRE
	network is limited to data plane learning in this document.		network is limited to data plane learning in this document.
	skipping to change at page 2, line 43 ¶		skipping to change at page 2, line 45 ¶
	4.2. Ethernet Auto-Discovery Route . . . . . . . . . . . . . . 8		4.2. Ethernet Auto-Discovery Route . . . . . . . . . . . . . . 8
	4.3. Per VPN Route Targets . . . . . . . . . . . . . . . . . . 8		4.3. Per VPN Route Targets . . . . . . . . . . . . . . . . . . 8
	4.4 Inclusive Multicast Route . . . . . . . . . . . . . . . . . 8		4.4 Inclusive Multicast Route . . . . . . . . . . . . . . . . . 8
	4.5. Unicast Forwarding . . . . . . . . . . . . . . . . . . . . 8		4.5. Unicast Forwarding . . . . . . . . . . . . . . . . . . . . 8
	4.6. Handling Multicast . . . . . . . . . . . . . . . . . . . . 9		4.6. Handling Multicast . . . . . . . . . . . . . . . . . . . . 9
	4.6.2. Multicast Stitching with Per-VNI Load Balancing . . . . 9		4.6.2. Multicast Stitching with Per-VNI Load Balancing . . . . 9
	5. NVGRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10		5. NVGRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
	6. Use Cases Overview . . . . . . . . . . . . . . . . . . . . . . 10		6. Use Cases Overview . . . . . . . . . . . . . . . . . . . . . . 10
	6.1. Homogeneous Network DCI interconnect Use cases . . . . . . 10		6.1. Homogeneous Network DCI interconnect Use cases . . . . . . 10
	6.1.1. VNI Base Mode EVPN Service Use Case . . . . . . . . . . 10		6.1.1. VNI Base Mode EVPN Service Use Case . . . . . . . . . . 10
	6.1.2. VNI Bundle Service Use Case Scenario . . . . . . . . . 12		6.1.2. VNI Bundle Service Use Case Scenario . . . . . . . . . 11
	6.1.3. VNI Translation Use Case . . . . . . . . . . . . . . 12		6.1.3. VNI Translation Use Case . . . . . . . . . . . . . . 12
	6.2. Heterogeneous Network DCI Use Cases Scenarios . . . . . . . 12		6.2. Heterogeneous Network DCI Use Cases Scenarios . . . . . . . 12
	6.2.1. VXLAN VLAN Interworking Over EVPN Use Case Scenario . . 12		6.2.1. VXLAN VLAN Interworking Over EVPN Use Case Scenario . . 12
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 13		8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	10.1 Normative References . . . . . . . . . . . . . . . . . . . 13		10.1 Normative References . . . . . . . . . . . . . . . . . . . 13
	10.2 Informative References . . . . . . . . . . . . . . . . . . 13		10.2 Informative References . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
	1 Introduction		1 Introduction
	skipping to change at page 11, line 8 ¶		skipping to change at page 11, line 8 ¶
	6. Use Cases Overview		6. Use Cases Overview
	6.1. Homogeneous Network DCI interconnect Use cases This covers DCI		6.1. Homogeneous Network DCI interconnect Use cases This covers DCI
	interconnect of two or more VXLAN based Data center over MPLS enabled		interconnect of two or more VXLAN based Data center over MPLS enabled
	EVPN core.		EVPN core.
	6.1.1. VNI Base Mode EVPN Service Use Case This use case handles the		6.1.1. VNI Base Mode EVPN Service Use Case This use case handles the
	EVPN service where there is one to one mapping between a VNI and an		EVPN service where there is one to one mapping between a VNI and an
	EVI. Ethernet TAG ID of EVPN BGP NLRI should be set to Zero. BD ID		EVI. Ethernet TAG ID of EVPN BGP NLRI should be set to Zero. BD ID
	can be derived from the RT associated with the EVI/VNI.		can be derived from the RT associated with the EVI/VNI.
	+---+ +---+		+---+ +---+
	| H1| +---+ +-------+ +--+ +---------+ +---+ +-------+ +---+ | H3|		| H1| +---+ +-------+ +--+ +---------+ +---+ +-------+ +---+ | H3|
	| M1|--+ +-+ +-+PE1+-+ +-+PE3+--+ +--+ +--| M3|		| M1|--+ +-+ +-+PE1+-+ +-+PE3+--+ +--+ +--| M3|
	+---+ | | | | +--+ |MPLS Core| +---+ | | | | +---+		+---+ | | | | +--+ |MPLS Core| +---+ | | | | +---+
	+---+ |NVE| | VXLAN | | (EVPN) | | VXLAN | |NVE| +---+		+---+ |NVE| | VXLAN | | (EVPN) | | VXLAN | |NVE| +---+
	| H2| | 1 | | | +--+ | | +---+ | | | 2 | | H4|		| H2| | 1 | | | +--+ | | +---+ | | | 2 | | H4|
	| M2|--+ +-+ +-+PE2+-+ +-+PE4+--+ +--+ +--| M4|		| M2|--+ +-+ +-+PE2+-+ +-+PE4+--+ +--+ +--| M4|
	+---+ +---+ +-------+ +--+ +---------+ +---+ +-------+ +---+ +---+		+---+ +---+ +-------+ +--+ +---------+ +---+ +-------+ +---+ +---+
	+--------+ +------+--------+ +------+--------+ +------+--------++--------+		+--------++------+--------++------+--------++------+--------++--------+
	|Original| |VXLAN |Original| |MPLS |Original| |VXLAN |Original||Original|		|Original||VXLAN |Original||MPLS |Original||VXLAN |Original||Original|
	|Ethernet| |Header|Ethernet| |Header|Ethernet| |Header|Ethernet||Ethernet|		|Ethernet||Header|Ethernet||Header|Ethernet||Header|Ethernet||Ethernet|
	|Frame | | |Frame | | |Frame | | |Frame ||Frame |		|Frame || |Frame || |Frame || |Frame ||Frame |
	+--------+ +------+--------+ +------+--------+ +------+--------++--------+		+--------++------+--------++------+--------++------+--------++--------+
	|<-----Data Center Site1-->|<--------EVPN Core>|<----Data Center Site2-->|		|<----Data Center Site1-->|<------EVPN Core>|<----Data Center Site2-->|
	Figure 2 VNI Base Service Packet Flow.		Figure 2 VNI Base Service Packet Flow.
	VNI base Service(One VNI mapped to one EVI).		VNI base Service(One VNI mapped to one EVI).
	Hosts H1, H2, H3 and H4 are hosts and there associated MAC addresses		Hosts H1, H2, H3 and H4 are hosts and there associated MAC addresses
	are M1, M2, M3 and M4. PE1, PE2, PE3 and PE4 are the VXLAN-EVPN		are M1, M2, M3 and M4. PE1, PE2, PE3 and PE4 are the VXLAN-EVPN
	gateways. NVE1 and NVE2 are the originators of the VXLAN based		gateways. NVE1 and NVE2 are the originators of the VXLAN based
	network.		network.
	skipping to change at page 12, line 29 ¶		skipping to change at page 12, line 18 ¶
	6.1.3. VNI Translation Use Case		6.1.3. VNI Translation Use Case
	+---+ +---+		+---+ +---+
	| H1| +---+ +-------+ +---+ +----------+ +---+ +-------+ +---+ | H3|		| H1| +---+ +-------+ +---+ +----------+ +---+ +-------+ +---+ | H3|
	| M1|-+ +-+ +-+PE1+-+ +-+PE3+-+ +-+ +-| M3|		| M1|-+ +-+ +-+PE1+-+ +-+PE3+-+ +-+ +-| M3|
	+---+ | | | | +---+ |MPLS Core | +---+ | | | | +---+		+---+ | | | | +---+ |MPLS Core | +---+ | | | | +---+
	+---+ |NVE| | VXLAN | | (EVPN) | | VXLAN | |NVE| +---+		+---+ |NVE| | VXLAN | | (EVPN) | | VXLAN | |NVE| +---+
	| H2| | 1 | | | +---+ | | +---+ | | | 2 | | H4|		| H2| | 1 | | | +---+ | | +---+ | | | 2 | | H4|
	| M2|-+ +-+ +-+PE2+-+ +-+PE4+-+ +-+ +-| M4|		| M2|-+ +-+ +-+PE2+-+ +-+PE4+-+ +-+ +-| M4|
	+---+ +---+ +-------+ +---+ +----------+ +---+ +-------+ +---+ +---+		+---+ +---+ +-------+ +---+ +----------+ +---+ +-------+ +---+ +---+
	|<----VNI ID A--->|<-------EVI-A------->|<----VNI_ID_B--->|		|<----VNI ID A--->|<-------EVI-A------->|<----VNI_ID_B--->|
	Figure 3 VNI Translation Use Case Scenarios.		Figure 3 VNI Translation Use Case Scenarios.
	There are two or more Data Center sites. These Data Center sites might use different VNI ID for same service. For example, Service A usage "VNI_ID_A" at data center site1 and "VNI_ID_B" for same service in data center site 2.		There are two or more Data Center sites. These Data Center sites
	VNI ID A is terminated at ingress EVPN PE and VNI ID B is encapsulated at the egress EVPN PE.		might use different VNI ID for same service. For example, Service A
			usage "VNI_ID_A" at data center site1 and "VNI_ID_B" for same service
			in data center site 2. VNI ID A is terminated at ingress EVPN PE and
			VNI ID B is encapsulated at the egress EVPN PE.
	6.2. Heterogeneous Network DCI Use Cases Scenarios		6.2. Heterogeneous Network DCI Use Cases Scenarios
	Data Center sites are upgraded slowly; so heterogeneous network DCI solution is required from the perspective of migration approach from traditional data center to VXLAN based data center. For Example Data Center Site1 is upgrade to VXLAN but Data Center Site 2 and 3 are still layer2/VLAN based data centers. For these use cases, it is required to provide VXLAN VLAN interworking over EVPN core.		Data Center sites are upgraded slowly; so heterogeneous network DCI
			solution is required from the perspective of migration approach from
			traditional data center to VXLAN based data center. For Example Data
			Center Site1 is upgrade to VXLAN but Data Center Site 2 and 3 are
			still layer2/VLAN based data centers. For these use cases, it is
			required to provide VXLAN VLAN interworking over EVPN core.
	6.2.1. VXLAN VLAN Interworking Over EVPN Use Case Scenario		6.2.1. VXLAN VLAN Interworking Over EVPN Use Case Scenario
	The new data center site is VXLAN based data center site. But the older data center sites are still based on the VLAN.		The new data center site is VXLAN based data center site. But the
			older data center sites are still based on the VLAN.
	+---+ +---+		+---+ +---+
	| H1| +---+ +------+ +---+ +---------+ +---+ +-------+ +---+ | H3|		| H1| +---+ +------+ +---+ +---------+ +---+ +-------+ +---+ | H3|
	| M1|-+ +-+ +-+PE1+-+ +-+PE3+-+ +-+ +-| M3|		| M1|-+ +-+ +-+PE1+-+ +-+PE3+-+ +-+ +-| M3|
	+---+ | | | | +---+ |MPLS Core| +---+ | | | | +---+		+---+ | | | | +---+ |MPLS Core| +---+ | | | | +---+
	+---+ |NVE| |VXLAN | | (EVPN) | | L2 | |NVE| +---+		+---+ |NVE| |VXLAN | | (EVPN) | | L2 | |NVE| +---+
	| H2| | 1 | | | +---+ | | +---+ |Network| | 2 | | H4|		| H2| | 1 | | | +---+ | | +---+ |Network| | 2 | | H4|
	| M2|-+ +-+ +-+PE2+-+ +-+PE4+-+ +-+ +-| M4|		| M2|-+ +-+ +-+PE2+-+ +-+PE4+-+ +-+ +-| M4|
	+---+ +---+ +------+ +---+ +---------+ +---+ +-------+ +---+ +---+		+---+ +---+ +------+ +---+ +---------+ +---+ +-------+ +---+ +---+
	|<--Data Center Site1->|<---EVPN Core--->|<--Data Center Site2-->|		|<--Data Center Site1->|<---EVPN Core--->|<--Data Center Site2-->|
	skipping to change at page 13, line 33 ¶		skipping to change at page 13, line 31 ¶
	The authors would like to acknowledge Wen Lin contributions to this		The authors would like to acknowledge Wen Lin contributions to this
	document.		document.
	8. Security Considerations		8. Security Considerations
	There are no additional security aspects that need to be discussed		There are no additional security aspects that need to be discussed
	here.		here.
	9. IANA Considerations		9. IANA Considerations
	TBD.		TBD
	10. References		10. References
	10.1 Normative References		10.1 Normative References
	[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate		[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	10.2 Informative References		10.2 Informative References
	skipping to change at line 600 ¶		skipping to change at page 14, line 40 ¶
	Juniper Networks		Juniper Networks
	Email: tsingh@juniper.net		Email: tsingh@juniper.net
	John Drake		John Drake
	Juniper Networks		Juniper Networks
	Email: jdrake@juniper.net		Email: jdrake@juniper.net
	Samir Thoria		Samir Thoria
	Cisco		Cisco
	EMail: sthoria@cisco.com		EMail: sthoria@cisco.com
			Jeff Tantsura
			Ericsson
			Email: jeff.tantsura@ericsson.com
End of changes. 11 change blocks.
	23 lines changed or deleted		37 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/