draft-ietf-bess-evpn-overlay-06.txt   draft-ietf-bess-evpn-overlay-07.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Juniper Juniper
N. Bitar N. Bitar
Nokia Nokia
R. Shekhar R. Shekhar
Juniper Juniper
J. Uttaro J. Uttaro
AT&T AT&T
W. Henderickx W. Henderickx
Nokia Nokia
Expires: May 18, 2017 November 18, 2016 Expires: June 1, 2017 December 1, 2016
A Network Virtualization Overlay Solution using EVPN A Network Virtualization Overlay Solution using EVPN
draft-ietf-bess-evpn-overlay-06 draft-ietf-bess-evpn-overlay-07
Abstract Abstract
This document describes how Ethernet VPN (EVPN) [RFC7432] can be used This document describes how Ethernet VPN (EVPN) [RFC7432] can be used
as an Network Virtualization Overlay (NVO) solution and explores the as an Network Virtualization Overlay (NVO) solution and explores the
various tunnel encapsulation options over IP and their impact on the various tunnel encapsulation options over IP and their impact on the
EVPN control-plane and procedures. In particular, the following EVPN control-plane and procedures. In particular, the following
encapsulation options are analyzed: VXLAN, NVGRE, and MPLS over GRE. encapsulation options are analyzed: VXLAN, NVGRE, and MPLS over GRE.
Status of this Memo Status of this Memo
skipping to change at page 3, line 4 skipping to change at page 3, line 4
8.1 EVPN Multi-Homing Features . . . . . . . . . . . . . . . . 16 8.1 EVPN Multi-Homing Features . . . . . . . . . . . . . . . . 16
8.1.1 Multi-homed Ethernet Segment Auto-Discovery . . . . . . 16 8.1.1 Multi-homed Ethernet Segment Auto-Discovery . . . . . . 16
8.1.2 Fast Convergence and Mass Withdraw . . . . . . . . . . . 16 8.1.2 Fast Convergence and Mass Withdraw . . . . . . . . . . . 16
8.1.3 Split-Horizon . . . . . . . . . . . . . . . . . . . . . 16 8.1.3 Split-Horizon . . . . . . . . . . . . . . . . . . . . . 16
8.1.4 Aliasing and Backup-Path . . . . . . . . . . . . . . . . 16 8.1.4 Aliasing and Backup-Path . . . . . . . . . . . . . . . . 16
8.1.5 DF Election . . . . . . . . . . . . . . . . . . . . . . 17 8.1.5 DF Election . . . . . . . . . . . . . . . . . . . . . . 17
8.2 Impact on EVPN BGP Routes & Attributes . . . . . . . . . . . 18 8.2 Impact on EVPN BGP Routes & Attributes . . . . . . . . . . . 18
8.3 Impact on EVPN Procedures . . . . . . . . . . . . . . . . . 18 8.3 Impact on EVPN Procedures . . . . . . . . . . . . . . . . . 18
8.3.1 Split Horizon . . . . . . . . . . . . . . . . . . . . . 18 8.3.1 Split Horizon . . . . . . . . . . . . . . . . . . . . . 18
8.3.2 Aliasing and Backup-Path . . . . . . . . . . . . . . . . 19 8.3.2 Aliasing and Backup-Path . . . . . . . . . . . . . . . . 19
8.3.3 Unknown Unicast Traffic Designation . . . . . . . . . . 19
9 Support for Multicast . . . . . . . . . . . . . . . . . . . . . 19 9 Support for Multicast . . . . . . . . . . . . . . . . . . . . . 20
10 Data Center Interconnections - DCI . . . . . . . . . . . . . . 20 10 Data Center Interconnections - DCI . . . . . . . . . . . . . . 21
10.1 DCI using GWs . . . . . . . . . . . . . . . . . . . . . . . 21 10.1 DCI using GWs . . . . . . . . . . . . . . . . . . . . . . . 21
10.2 DCI using ASBRs . . . . . . . . . . . . . . . . . . . . . . 21 10.2 DCI using ASBRs . . . . . . . . . . . . . . . . . . . . . . 22
10.2.1 ASBR Functionality with NVEs in Hypervisors . . . . . . 22 10.2.1 ASBR Functionality with NVEs in Hypervisors . . . . . . 23
10.2.2 ASBR Functionality with NVEs in TORs . . . . . . . . . 22 10.2.2 ASBR Functionality with NVEs in TORs . . . . . . . . . 23
11 Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 25 11 Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 25
12 Security Considerations . . . . . . . . . . . . . . . . . . . 25 12 Security Considerations . . . . . . . . . . . . . . . . . . . 25
13 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 13 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
14 References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 14 References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
14.1 Normative References . . . . . . . . . . . . . . . . . . . 26 14.1 Normative References . . . . . . . . . . . . . . . . . . . 26
14.2 Informative References . . . . . . . . . . . . . . . . . . 26 14.2 Informative References . . . . . . . . . . . . . . . . . . 27
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1 Introduction 1 Introduction
In the context of this document, a Network Virtualization Overlay In the context of this document, a Network Virtualization Overlay
(NVO) is a solution to address the requirements of a multi-tenant (NVO) is a solution to address the requirements of a multi-tenant
data center, especially one with virtualized hosts, e.g., Virtual data center, especially one with virtualized hosts, e.g., Virtual
Machines (VMs) or virtual workloads. The key requirements of such a Machines (VMs) or virtual workloads. The key requirements of such a
solution, as described in [Problem-Statement], are: solution, as described in [Problem-Statement], are:
- Isolation of network traffic per tenant - Isolation of network traffic per tenant
skipping to change at page 19, line 48 skipping to change at page 19, line 48
The Aliasing and the Backup-Path procedures for VXLAN/NVGRE The Aliasing and the Backup-Path procedures for VXLAN/NVGRE
encapsulation is very similar to the ones for MPLS. In case of MPLS, encapsulation is very similar to the ones for MPLS. In case of MPLS,
Ethernet A-D route per EVI is used for Aliasing when the Ethernet A-D route per EVI is used for Aliasing when the
corresponding Ethernet Segment operates in All-Active multi-homing, corresponding Ethernet Segment operates in All-Active multi-homing,
and the same route is used for Backup-Path when the corresponding and the same route is used for Backup-Path when the corresponding
Ethernet Segment operates in Single-Active multi-homing. In case of Ethernet Segment operates in Single-Active multi-homing. In case of
VxLAN/NVGRE, the same route is used for the Aliasing and the Backup- VxLAN/NVGRE, the same route is used for the Aliasing and the Backup-
Path with the difference that the Ethernet Tag and VNI fields in Path with the difference that the Ethernet Tag and VNI fields in
Ethernet A-D per EVI route is set as described in section 5.1.3. Ethernet A-D per EVI route is set as described in section 5.1.3.
8.3.3 Unknown Unicast Traffic Designation
In EVPN, when an ingress PE uses ingress replication to flood unknown
unicast traffic to egress PEs, the ingress PE uses a different EVPN
MPLS label (from the one used for known unicast traffic) to identify
such BUM traffic. The egress PEs use this label to identify such BUM
traffic and thus apply DF filtering for All-Active multi-homed sites.
In absence of unknown unicast traffic designation and in presence of
enabling unknown unicast flooding, there can be transient duplicate
traffic to All-Active multi-homed sites under the following
condition: the host MAC address is learned by the egress PE(s) and
advertised to the ingress PE; however, the MAC advertisement has not
been received or processed by the ingress PE, resulting in the host
MAC address to be unknown on the ingress PE but be known on the
egress PE(s). Therefore, when a packet destined to that host MAC
address arrives on the ingress PE, it floods it via ingress
replication to all the egress PE(s) and since they are known to the
egress PE(s), multiple copies is sent to the All-Active multi-homed
site. It should be noted that such transient packet duplication only
happens when a) the destination host is multi-homed via All-Active
redundancy mode, b) flooding of unknown unicast is enabled in the
network, c) ingress replication is used, and d) traffic for the
destination host is arrived on the ingress PE before it learns the
host MAC address via BGP EVPN advertisement. In order to prevent such
occurrence of packet duplication (however low probability that may
be), the ingress PE MAY use a flag-bit in the VxLAN header to
indicate BUM traffic type. Bit 6 of flag field in the VxLAN header is
used for this purpose per section 3.1 of [VXLAN-GPE].
9 Support for Multicast 9 Support for Multicast
The E-VPN Inclusive Multicast BGP route is used to discover the The E-VPN Inclusive Multicast BGP route is used to discover the
multicast tunnels among the endpoints associated with a given EVI multicast tunnels among the endpoints associated with a given EVI
(e.g., given VNI) for VLAN-based service and a given <EVI,VLAN> for (e.g., given VNI) for VLAN-based service and a given <EVI,VLAN> for
VLAN-aware bundle service. All fields of this route is set as VLAN-aware bundle service. All fields of this route is set as
described in section 5.1.3. The Originating router's IP address field described in section 5.1.3. The Originating router's IP address field
is set to the NVE's IP address. This route is tagged with the PMSI is set to the NVE's IP address. This route is tagged with the PMSI
Tunnel attribute, which is used to encode the type of multicast Tunnel attribute, which is used to encode the type of multicast
tunnel to be used as well as the multicast tunnel identifier. The tunnel to be used as well as the multicast tunnel identifier. The
skipping to change at page 27, line 19 skipping to change at page 27, line 45
October 2012. October 2012.
[DCI-EVPN-OVERLAY] Rabadan et al., "Interconnect Solution for EVPN [DCI-EVPN-OVERLAY] Rabadan et al., "Interconnect Solution for EVPN
Overlay networks", draft-ietf-bess-dci-evpn-overlay-02, work in Overlay networks", draft-ietf-bess-dci-evpn-overlay-02, work in
progress, February 29, 2016. progress, February 29, 2016.
[TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation [TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation
Attribute", draft-ietf-idr-tunnel-encaps-02, work in progress, May Attribute", draft-ietf-idr-tunnel-encaps-02, work in progress, May
31, 2016. 31, 2016.
[VXLAN-GPE] Maino et al., "Generic Protocol Extension for VXLAN",
draft-ietf-nvo3-vxlan-gpe-03, work in progress October 25, 2016.
Contributors Contributors
S. Salam K. Patel D. Rao S. Thoria D. Cai Cisco S. Salam K. Patel D. Rao S. Thoria D. Cai Cisco
Y. Rekhter A. Issac Wen Lin Nischal Sheth Juniper
Y. Rekhter R. Shekhar Wen Lin Nischal Sheth Juniper
L. Yong Huawei L. Yong Huawei
Authors' Addresses Authors' Addresses
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
John Drake John Drake
 End of changes. 10 change blocks. 
13 lines changed or deleted 44 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/