draft-ietf-nvo3-evpn-applicability-00.txt   draft-ietf-nvo3-evpn-applicability-01.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
NVO3 Workgroup J. Rabadan, Ed. NVO3 Workgroup J. Rabadan, Ed.
Internet Draft M. Bocci Internet Draft M. Bocci
Intended status: Informational Nokia Intended status: Informational Nokia
S. Boutros S. Boutros
WMware WMware
A. Sajassi A. Sajassi
Cisco Cisco
Expires: March 15, 2019 September 11, 2018 Expires: April 25, 2019 October 22, 2018
Applicability of EVPN to NVO3 Networks Applicability of EVPN to NVO3 Networks
draft-ietf-nvo3-evpn-applicability-00 draft-ietf-nvo3-evpn-applicability-01
Abstract Abstract
In NVO3 networks, Network Virtualization Edge (NVE) devices sit at In NVO3 networks, Network Virtualization Edge (NVE) devices sit at
the edge of the underlay network and provide Layer-2 and Layer-3 the edge of the underlay network and provide Layer-2 and Layer-3
connectivity among Tenant Systems (TSes) of the same tenant. The NVEs connectivity among Tenant Systems (TSes) of the same tenant. The NVEs
need to build and maintain mapping tables so that they can deliver need to build and maintain mapping tables so that they can deliver
encapsulated packets to their intended destination NVE(s). While encapsulated packets to their intended destination NVE(s). While
there are different options to create and disseminate the mapping there are different options to create and disseminate the mapping
table entries, NVEs may exchange that information directly among table entries, NVEs may exchange that information directly among
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference 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 15, 2019. This Internet-Draft will expire on April 25, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
4. Applicability of EVPN to NVO3 Networks . . . . . . . . . . . . 8 4. Applicability of EVPN to NVO3 Networks . . . . . . . . . . . . 8
4.1. EVPN Route Types used in NVO3 Networks . . . . . . . . . . 8 4.1. EVPN Route Types used in NVO3 Networks . . . . . . . . . . 8
4.2. EVPN Basic Applicability For Layer-2 Services . . . . . . . 9 4.2. EVPN Basic Applicability For Layer-2 Services . . . . . . . 9
4.2.1. Auto-Discovery and Auto-Provisioning of ES, 4.2.1. Auto-Discovery and Auto-Provisioning of ES,
Multi-Homing PEs and NVE services . . . . . . . . . . . 10 Multi-Homing PEs and NVE services . . . . . . . . . . . 10
4.2.2. Remote NVE Auto-Discovery . . . . . . . . . . . . . . . 11 4.2.2. Remote NVE Auto-Discovery . . . . . . . . . . . . . . . 11
4.2.3. Distribution Of Tenant MAC and IP Information . . . . . 12 4.2.3. Distribution Of Tenant MAC and IP Information . . . . . 12
4.3. EVPN Basic Applicability for Layer-3 Services . . . . . . . 13 4.3. EVPN Basic Applicability for Layer-3 Services . . . . . . . 13
4.4. EVPN as a Control Plane for NVO3 Encapsulations and 4.4. EVPN as a Control Plane for NVO3 Encapsulations and
GENEVE . . . . . . . . . . . . . . . . . . . . . . . . . . 15 GENEVE . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5. EVPN OAM and application to NVO3 . . . . . . . . . . . . . 15 4.5. EVPN OAM and application to NVO3 . . . . . . . . . . . . . 16
4.6. EVPN as the control plane for NVO3 security . . . . . . . . 16 4.6. EVPN as the control plane for NVO3 security . . . . . . . . 16
4.7. Advanced EVPN Features For NVO3 Networks . . . . . . . . . 16 4.7. Advanced EVPN Features For NVO3 Networks . . . . . . . . . 16
4.7.1. Virtual Machine (VM) Mobility . . . . . . . . . . . . . 16 4.7.1. Virtual Machine (VM) Mobility . . . . . . . . . . . . . 16
4.7.2. MAC Protection, Duplication Detection and Loop 4.7.2. MAC Protection, Duplication Detection and Loop
Protection . . . . . . . . . . . . . . . . . . . . . . 16 Protection . . . . . . . . . . . . . . . . . . . . . . 17
4.7.3. Reduction/Optimization of BUM Traffic In Layer-2 4.7.3. Reduction/Optimization of BUM Traffic In Layer-2
Services . . . . . . . . . . . . . . . . . . . . . . . 17 Services . . . . . . . . . . . . . . . . . . . . . . . 17
4.7.4. Ingress Replication (IR) Optimization For BUM Traffic . 18 4.7.4. Ingress Replication (IR) Optimization For BUM Traffic . 18
4.7.5. EVPN Multi-homing . . . . . . . . . . . . . . . . . . . 18 4.7.5. EVPN Multi-homing . . . . . . . . . . . . . . . . . . . 19
4.7.6. EVPN Recursive Resolution for Inter-Subnet Unicast 4.7.6. EVPN Recursive Resolution for Inter-Subnet Unicast
Forwarding . . . . . . . . . . . . . . . . . . . . . . 19 Forwarding . . . . . . . . . . . . . . . . . . . . . . 20
4.7.7. EVPN Optimized Inter-Subnet Multicast Forwarding . . . 21 4.7.7. EVPN Optimized Inter-Subnet Multicast Forwarding . . . 21
4.7.8. Data Center Interconnect (DCI) . . . . . . . . . . . . 21 4.7.8. Data Center Interconnect (DCI) . . . . . . . . . . . . 21
5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. Conventions used in this document . . . . . . . . . . . . . . . 22 6. Conventions used in this document . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 22 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 22
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 22 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 23 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 23
9.2 Informative References . . . . . . . . . . . . . . . . . . . 23 9.2 Informative References . . . . . . . . . . . . . . . . . . . 23
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25
skipping to change at page 9, line 46 skipping to change at page 9, line 46
+----+------------------------+-------------------------------------+ +----+------------------------+-------------------------------------+
Table 1 EVPN route types Table 1 EVPN route types
4.2. EVPN Basic Applicability For Layer-2 Services 4.2. EVPN Basic Applicability For Layer-2 Services
Although the applicability of EVPN to NVO3 networks spans multiple Although the applicability of EVPN to NVO3 networks spans multiple
documents, EVPN's baseline specification is [RFC7432]. [RFC7432] documents, EVPN's baseline specification is [RFC7432]. [RFC7432]
allows multipoint layer-2 VPNs to be operated as [RFC4364] IP-VPNs, allows multipoint layer-2 VPNs to be operated as [RFC4364] IP-VPNs,
where MACs and the information to setup flooding trees are where MACs and the information to setup flooding trees are
distributed by MP-BGP. Based on [RFC7432], [EVPN-OVERLAY] describes distributed by MP-BGP. Based on [RFC7432], [RFC8365] describes how to
how to use EVPN to deliver Layer-2 services specifically in NVO3 use EVPN to deliver Layer-2 services specifically in NVO3 Networks.
Networks.
Figure 1 represents a Layer-2 service deployed with an EVPN BD in an Figure 1 represents a Layer-2 service deployed with an EVPN BD in an
NVO3 network. NVO3 network.
+--TS2---+ +--TS2---+
* | Single-Active * | Single-Active
* | ESI-1 * | ESI-1
+----+ +----+ +----+ +----+
|BD1 | |BD1 | |BD1 | |BD1 |
+-------------| |--| |-----------+ +-------------| |--| |-----------+
skipping to change at page 11, line 43 skipping to change at page 11, line 43
o Auto-provisioning of services: when deploying a Layer-2 Service for o Auto-provisioning of services: when deploying a Layer-2 Service for
a tenant in an NVO3 network, all the NVEs attached to the same a tenant in an NVO3 network, all the NVEs attached to the same
subnet must be configured with a MAC-VRF and the BD for the subnet, subnet must be configured with a MAC-VRF and the BD for the subnet,
as well as certain parameters for them. Note that, if the EVPN as well as certain parameters for them. Note that, if the EVPN
service model is VLAN-based or VLAN-bundle, implementations do not service model is VLAN-based or VLAN-bundle, implementations do not
normally have a specific provisioning for the BD (since it is in normally have a specific provisioning for the BD (since it is in
that case the same construct as the MAC-VRF). EVPN allows auto- that case the same construct as the MAC-VRF). EVPN allows auto-
deriving as many MAC-VRF parameters as possible. As an example, the deriving as many MAC-VRF parameters as possible. As an example, the
MAC-VRF's RT and RD for the EVPN routes may be auto-derived. MAC-VRF's RT and RD for the EVPN routes may be auto-derived.
Section 5.1.2.1 in [EVPN-OVERLAY] specifies how to auto-derive a Section 5.1.2.1 in [RFC8365] specifies how to auto-derive a MAC-
MAC-VRF's RT as long as VLAN-based service model is implemented. VRF's RT as long as VLAN-based service model is implemented.
[RFC7432] specifies how to auto-derive the RD. [RFC7432] specifies how to auto-derive the RD.
4.2.2. Remote NVE Auto-Discovery 4.2.2. Remote NVE Auto-Discovery
Auto-discovery via MP-BGP is used to discover the remote NVEs Auto-discovery via MP-BGP is used to discover the remote NVEs
attached to a given BD, NVEs participating in a given redundancy attached to a given BD, NVEs participating in a given redundancy
group, the tunnel encapsulation types supported by an NVE, etc. group, the tunnel encapsulation types supported by an NVE, etc.
In particular, when a new MAC-VRF and BD are enabled, the NVE will In particular, when a new MAC-VRF and BD are enabled, the NVE will
advertise a new RT-3. Besides other fields, the RT-3 will encode the advertise a new RT-3. Besides other fields, the RT-3 will encode the
skipping to change at page 12, line 24 skipping to change at page 12, line 24
the PTA. Assuming Ingress Replication (IR), the RT-3 will include an the PTA. Assuming Ingress Replication (IR), the RT-3 will include an
identification for IR in the PTA and the VNI the NVEs must use to identification for IR in the PTA and the VNI the NVEs must use to
send BUM traffic to the advertising NVE. The other NVEs in the BD, send BUM traffic to the advertising NVE. The other NVEs in the BD,
will import the RT-3 and will add NVE1's IP address to the flooding will import the RT-3 and will add NVE1's IP address to the flooding
list for BD1. Note that the RT-3 is also sent with a BGP list for BD1. Note that the RT-3 is also sent with a BGP
encapsulation attribute [TUNNEL-ENCAP] that indicates what NVO3 encapsulation attribute [TUNNEL-ENCAP] that indicates what NVO3
encapsulation the remote NVEs should use when sending BUM traffic to encapsulation the remote NVEs should use when sending BUM traffic to
NVE1. NVE1.
Refer to [RFC7432] for more information about the RT-3 and forwarding Refer to [RFC7432] for more information about the RT-3 and forwarding
of BUM traffic, and to [EVPN-OVERLAY] for its considerations on NVO3 of BUM traffic, and to [RFC8365] for its considerations on NVO3
networks. networks.
4.2.3. Distribution Of Tenant MAC and IP Information 4.2.3. Distribution Of Tenant MAC and IP Information
Tenant MAC/IP information is advertised to remote NVEs using RT-2s. Tenant MAC/IP information is advertised to remote NVEs using RT-2s.
Following the example of Figure 1: Following the example of Figure 1:
o In a given EVPN BD, TSes' MAC addresses are first learned at the o In a given EVPN BD, TSes' MAC addresses are first learned at the
NVE they are attached to, via data path or management plane NVE they are attached to, via data path or management plane
learning. In Figure 1 we assume NVE1 learns MAC1/IP1 in the learning. In Figure 1 we assume NVE1 learns MAC1/IP1 in the
skipping to change at page 13, line 10 skipping to change at page 13, line 10
L. NVE4 can then encapsulate the frame into an NVO3 tunnel with IP- L. NVE4 can then encapsulate the frame into an NVO3 tunnel with IP-
A as the tunnel IP DA and L as the Virtual Network Identifier. Note A as the tunnel IP DA and L as the Virtual Network Identifier. Note
that the RT-2 may also contain the host's IP address (as in the that the RT-2 may also contain the host's IP address (as in the
example of Figure 1). While the MAC of the received RT-2 is example of Figure 1). While the MAC of the received RT-2 is
installed in the BT, the IP address may be installed in the Proxy- installed in the BT, the IP address may be installed in the Proxy-
ARP/ND table (if enabled) or in the ARP/IP-VRF tables if the BD has ARP/ND table (if enabled) or in the ARP/IP-VRF tables if the BD has
an IRB. See section 4.7.3. to see more information about Proxy- an IRB. See section 4.7.3. to see more information about Proxy-
ARP/ND and section 4.3. for more details about IRB and Layer-3 ARP/ND and section 4.3. for more details about IRB and Layer-3
services. services.
Refer to [RFC7432] and [EVPN-OVERLAY] for more information about the Refer to [RFC7432] and [RFC8365] for more information about the RT-2
RT-2 and forwarding of known unicast traffic. and forwarding of known unicast traffic.
4.3. EVPN Basic Applicability for Layer-3 Services 4.3. EVPN Basic Applicability for Layer-3 Services
[IP-PREFIX] and [INTER-SUBNET] are the reference documents that [IP-PREFIX] and [INTER-SUBNET] are the reference documents that
describe how EVPN can be used for Layer-3 services. Inter Subnet describe how EVPN can be used for Layer-3 services. Inter Subnet
Forwarding in EVPN networks is implemented via IRB interfaces between Forwarding in EVPN networks is implemented via IRB interfaces between
BDs and IP-VRFs. As discussed, an EVPN BD corresponds to an IP BDs and IP-VRFs. As discussed, an EVPN BD corresponds to an IP
subnet. When IP packets generated in a BD are destined to a different subnet. When IP packets generated in a BD are destined to a different
subnet (different BD) of the same tenant, the packets are sent to the subnet (different BD) of the same tenant, the packets are sent to the
IRB attached to local BD in the source NVE. As discussed in [INTER- IRB attached to local BD in the source NVE. As discussed in [INTER-
skipping to change at page 14, line 22 skipping to change at page 14, line 22
| +---+ | | | | | | +---+ | | +---+ | | | | | | +---+ |
| +---+ | | | | | | +---+ | | +---+ | | | | | | +---+ |
| |BD2|----| | | | | |----|BD2|----TS2 | |BD2|----| | | | | |----|BD2|----TS2
| +---+IRB +------+ | | +------+IRB +---+ | | +---+IRB +------+ | | +------+IRB +---+ |
+--------------------+ +--------------------+ +--------------------+ +--------------------+
| | | |
+-------------------------------------+ +-------------------------------------+
Figure 2 EVPN for L3 in an NVO3 Network - Asymmetric model Figure 2 EVPN for L3 in an NVO3 Network - Asymmetric model
In the Symmetric model, depicted in Figure 3, there are the same data In the Symmetric model, depicted in Figure 3, the same number of data
path lookups at the ingress and egress NVEs. For example, if TS1 path lookups is needed at the ingress and egress NVEs. For example,
sends IP packets to TS3, the following data path lookups are if TS1 sends IP packets to TS3, the following data path lookups are
required: a MAC lookup at NVE1's BD1 table, an IP lookup at NVE1's required: a MAC lookup at NVE1's BD1 table, an IP lookup at NVE1's
IP-VRF and then IP lookup and MAC lookup at NVE2's IP-VRF and BD3 IP-VRF and then IP lookup and MAC lookup at NVE2's IP-VRF and BD3
respectively. In the Symmetric model, the Inter Subnet connectivity respectively. In the Symmetric model, the Inter Subnet connectivity
between NVEs is done based on tunnels between the IP-VRFs. between NVEs is done based on tunnels between the IP-VRFs.
+-------------------------------------+ +-------------------------------------+
| EVPN NVO3 | | EVPN NVO3 |
| | | |
NVE1 NVE2 NVE1 NVE2
+--------------------+ +--------------------+ +--------------------+ +--------------------+
skipping to change at page 15, line 14 skipping to change at page 15, line 14
and the exchange of IP Prefixes between the NVEs in the control and the exchange of IP Prefixes between the NVEs in the control
plane. EVPN uses RT-2 and RT-5 routes for the exchange of host IP plane. EVPN uses RT-2 and RT-5 routes for the exchange of host IP
routes (in the case of RT-2 and RT-5) and IP Prefixes (RT-5s) of any routes (in the case of RT-2 and RT-5) and IP Prefixes (RT-5s) of any
length. As an example, in Figure 3, NVE2 needs to advertise TS3's length. As an example, in Figure 3, NVE2 needs to advertise TS3's
host route and/or TS3's subnet, so that the IP lookup on NVE1's IP- host route and/or TS3's subnet, so that the IP lookup on NVE1's IP-
VRF succeeds. VRF succeeds.
[INTER-SUBNET] specifies the use of RT-2s for the advertisement of [INTER-SUBNET] specifies the use of RT-2s for the advertisement of
host routes. Section 4.4.1 in [IP-PREFIX] specifies the use of RT-5s host routes. Section 4.4.1 in [IP-PREFIX] specifies the use of RT-5s
for the advertisement of IP Prefixes in an "Interface-less IP-VRF-to- for the advertisement of IP Prefixes in an "Interface-less IP-VRF-to-
IP-VRF Model". IP-VRF Model". The Symmetric model for host routes can be implemented
following either approach:
a. [INTER-SUBNET] uses RT-2s to convey the information to populate
L2, ARP/ND and L3 FIB tables in the remote NVE. For instance, in
Figure 3, NVE2 would advertise a RT-2 with TS3's IP and MAC
addresses, and including two labels/VNIs: a label-3/VNI-3 that
identifies BD3 for MAC lookup (that would be used for L2 traffic
in case NVE1 was attached to BD3 too) and a label-1/VNI-1 that
identifies the IP-VRF for IP lookup (and will be used for L3
traffic). NVE1 imports the RT-2 and installs TS3's IP in the IP-
VRF route table with label-1/VNI-1. Traffic from e.g., TS2 to TS3,
will be encapsulated with label-1/VNI-1 and forwarded to NVE2.
b. [IP-PREFIX] uses RT-2s to convey the information to populate the
L2 FIB and ARP/ND tables, and RT-5s to populate the IP-VRF L3 FIB
table. For instance, in Figure 3, NVE2 would advertise a RT-2
including TS3's MAC and IP addresses with a single label-3/VNI-3.
In this example, this RT-2 wouldn't be imported by NVE1 because
NVE1 is not attached to BD3. In addition, NVE2 would advertise a
RT-5 with TS3's IP address and label-1/VNI-1. This RT-5 would be
imported by NVE1's IP-VRF and the host route installed in the L3
FIB associated to label-1/VNI-1. Traffic from TS2 to TS3 would be
encapsulated with label-1/VNI-1.
4.4. EVPN as a Control Plane for NVO3 Encapsulations and GENEVE 4.4. EVPN as a Control Plane for NVO3 Encapsulations and GENEVE
[EVPN-OVERLAY] describes how to use EVPN for NVO3 encapsulations, [RFC8365] describes how to use EVPN for NVO3 encapsulations, such us
such us VXLAN, nvGRE or MPLSoGRE. The procedures can be easily VXLAN, nvGRE or MPLSoGRE. The procedures can be easily applicable to
applicable to any other NVO3 encapsulation, in particular GENEVE. any other NVO3 encapsulation, in particular GENEVE.
The NVO3 working group has been working on different data plane The NVO3 working group has been working on different data plane
encapsulations. The Generic Network Virtualization Encapsulation encapsulations. The Generic Network Virtualization Encapsulation
[GENEVE] has been recommended to be the proposed standard for NVO3 [GENEVE] has been recommended to be the proposed standard for NVO3
Encapsulation. The EVPN control plane can signal the GENEVE Encapsulation. The EVPN control plane can signal the GENEVE
encapsulation type in the BGP Tunnel Encapsulation Extended Community encapsulation type in the BGP Tunnel Encapsulation Extended Community
(see [TUNNEL-ENCAP]). (see [TUNNEL-ENCAP]).
The NVO3 encapsulation design team has made a recommendation in The NVO3 encapsulation design team has made a recommendation in
[NVO3-ENCAP] for a control plane to: [NVO3-ENCAP] for a control plane to:
skipping to change at page 19, line 35 skipping to change at page 20, line 7
and then the TS. As an example, in Figure 1, assuming NVE4 is the and then the TS. As an example, in Figure 1, assuming NVE4 is the
DF for ES-2 in BD1, BUM frames sent from TS3 to NVE5 will be DF for ES-2 in BD1, BUM frames sent from TS3 to NVE5 will be
received at NVE4 and, since NVE4 is the DF for DB1, it will received at NVE4 and, since NVE4 is the DF for DB1, it will
forward them back to TS3. Split-horizon allows NVE4 (and any forward them back to TS3. Split-horizon allows NVE4 (and any
multi-homed NVE for that matter) to identify if an EVPN BUM frame multi-homed NVE for that matter) to identify if an EVPN BUM frame
is coming from the same ES or different, and if the frame belongs is coming from the same ES or different, and if the frame belongs
to the same ES2, NVE4 will not forward the BUM frame to TS3, in to the same ES2, NVE4 will not forward the BUM frame to TS3, in
spite of being the DF. spite of being the DF.
While [RFC7432] describes the default algorithm for the DF Election, While [RFC7432] describes the default algorithm for the DF Election,
[HRW-DF], [PREF-DF] and [AC-DF] specify other algorithms and [DF] and [PREF-DF] specify other algorithms and procedures that
procedures that optimize the DF Election. optimize the DF Election.
The Split-horizon function is specified in [RFC7432] and it is The Split-horizon function is specified in [RFC7432] and it is
carried out by using a special ESI-label that it identifies in the carried out by using a special ESI-label that it identifies in the
data path, all the BUM frames being originated from a given NVE and data path, all the BUM frames being originated from a given NVE and
ES. Since the ESI-label is an MPLS label, it cannot be used in all ES. Since the ESI-label is an MPLS label, it cannot be used in all
the non-MPLS NVO3 encapsulations, therefore [EVPN-OVERLAY] defines a the non-MPLS NVO3 encapsulations, therefore [RFC8365] defines a
modified Split-horizon procedure that is based on the IP SA of the modified Split-horizon procedure that is based on the IP SA of the
NVO3 tunnel, known as "Local-Bias". It is worth noting that Local- NVO3 tunnel, known as "Local-Bias". It is worth noting that Local-
Bias only works for all-active multi-homing, and not for single- Bias only works for all-active multi-homing, and not for single-
active multi-homing. active multi-homing.
4.7.6. EVPN Recursive Resolution for Inter-Subnet Unicast Forwarding 4.7.6. EVPN Recursive Resolution for Inter-Subnet Unicast Forwarding
Section 4.3. describes how EVPN can be used for Inter Subnet Section 4.3. describes how EVPN can be used for Inter Subnet
Forwarding among subnets of the same tenant. RT-2s and RT-5s allow Forwarding among subnets of the same tenant. RT-2s and RT-5s allow
the advertisement of host routes and IP Prefixes (RT-5) of any the advertisement of host routes and IP Prefixes (RT-5) of any
length. The procedures outlined by section 4.3. are similar to the length. The procedures outlined by section 4.3. are similar to the
ones in [RFC4364], only for NVO3 tunnels. However, [EVPN-PREFIX] also ones in [RFC4364], only for NVO3 tunnels. However, [EVPN-PREFIX] also
defines advanced Inter Subnet Forwarding procedures that allow the defines advanced Inter Subnet Forwarding procedures that allow the
resolution of RT-5s to not only BGP next-hops but also "overlay resolution of RT-5s to not only BGP next-hops but also "overlay
indexes" that can be a MAC, a GW IP or an ESI, all of them in the indexes" that can be a MAC, a GW IP or an ESI, all of them in the
tenant space. tenant space.
skipping to change at page 23, line 39 skipping to change at page 23, line 39
9.2 Informative References 9.2 Informative References
[IP-PREFIX] Rabadan et al., "IP Prefix Advertisement in EVPN", [IP-PREFIX] Rabadan et al., "IP Prefix Advertisement in EVPN",
draft-ietf-bess-evpn-prefix-advertisement-11, work in progress, May, draft-ietf-bess-evpn-prefix-advertisement-11, work in progress, May,
2018 2018
[INTER-SUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in EVPN", [INTER-SUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in EVPN",
draft-ietf-bess-evpn-inter-subnet-forwarding-05, work in progress, draft-ietf-bess-evpn-inter-subnet-forwarding-05, work in progress,
July, 2018 July, 2018
[EVPN-USAGE] Rabadan et al., "Usage and applicability of BGP MPLS [RFC8365] Sajassi-Drake et al., "A Network Virtualization Overlay
based Ethernet VPN", work in progress, draft-ietf-bess-evpn-usage-06, Solution using EVPN", RFC 8365, March 2017, <http://www.rfc-
August 2017 editor.org/info/rfc8365>
[EVPN-OVERLAY] Sajassi-Drake et al., "A Network Virtualization
Overlay Solution using EVPN", work in progress, draft-ietf-bess-
evpn-overlay-08, March 2017
[GENEVE] Gross et al., "Geneve: Generic Network Virtualization [GENEVE] Gross et al., "Geneve: Generic Network Virtualization
Encapsulation", draft-ietf-nvo3-geneve-05, work in progress, Encapsulation", draft-ietf-nvo3-geneve-08, work in progress, October
September 2017 2018
[NVO3-ENCAP] Boutros et al., "NVO3 Encapsulation Considerations", [NVO3-ENCAP] Boutros et al., "NVO3 Encapsulation Considerations",
draft-ietf-nvo3-encap-01, work in progress, October 2017 draft-ietf-nvo3-encap-02, work in progress, September 2018
[TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation [TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation
Attribute", draft-ietf-idr-tunnel-encaps-03, work in progress, May Attribute", draft-ietf-idr-tunnel-encaps-10, work in progress, August
31, 2016. 2018
[EVPN-LSP-PING] Jain et al., "LSP-Ping Mechanisms for EVPN and PBB- [EVPN-LSP-PING] Jain et al., "LSP-Ping Mechanisms for EVPN and PBB-
EVPN", draft-jain-bess-evpn-lsp-ping-05, work in progress, July 2017 EVPN", draft-jain-bess-evpn-lsp-ping-07, work in progress, June 2018
[LOOP] Rabadan et al., "Loop Protection in EVPN networks", draft- [LOOP] Rabadan et al., "Loop Protection in EVPN networks", draft-
snr-bess-evpn-loop-protect-00, work in progress, July 2017 snr-bess-evpn-loop-protect-02, work in progress, August 2018
[PROXY-ARP-ND] Rabadan et al., "Operational Aspects of Proxy-ARP/ND [PROXY-ARP-ND] Rabadan et al., "Operational Aspects of Proxy-ARP/ND
in EVPN Networks", draft-ietf-bess-evpn-proxy-arp-nd-03, work in in EVPN Networks", draft-ietf-bess-evpn-proxy-arp-nd-05, work in
progress, October 2017 progress, October 2018
[IGMP-MLD-PROXY] Sajassi et al., "IGMP and MLD Proxy for EVPN", [IGMP-MLD-PROXY] Sajassi et al., "IGMP and MLD Proxy for EVPN",
draft-ietf-bess-evpn-igmp-mld-proxy-00, work in progress, March 2017 draft-ietf-bess-evpn-igmp-mld-proxy-02, work in progress, June 2018
[PIM-PROXY] Rabadan et al., "PIM Proxy in EVPN Networks", draft-skr- [PIM-PROXY] Rabadan et al., "PIM Proxy in EVPN Networks", draft-skr-
bess-evpn-pim-proxy-01, work in progress, October 2017 bess-evpn-pim-proxy-01, work in progress, October 2017
[OPT-IR] Rabadan et al., "Optimized Ingress Replication solution for [OPT-IR] Rabadan et al., "Optimized Ingress Replication solution for
EVPN", draft-ietf-bess-evpn-optimized-ir-02, work in progress, August EVPN", draft-ietf-bess-evpn-optimized-ir-06, work in progress,
2017 October 2018
[HRW-DF] Mohanty et al., "A new Designated Forwarder Election for [DF] Rabadan-Mohanty et al., "Framework for EVPN Designated
the EVPN", draft-ietf-bess-evpn-df-election-03, work in progress, Forwarder Election Extensibility", draft-ietf-bess-evpn-df-election-
October 2017 04, work in progress, October 2018
[PREF-DF] Rabadan et al., "Preference-based EVPN DF Election", [PREF-DF] Rabadan et al., "Preference-based EVPN DF Election",
draft-ietf-bess-evpn-pref-df-00, work in progress, June 2017 draft-ietf-bess-evpn-pref-df-02, work in progress, October 2018
[AC-DF] Rabadan et al., "AC-Influenced Designated Forwarder Election
for EVPN", draft-ietf-bess-evpn-ac-df-02, work in progress, October
2017
[OISM] Lin at al., "EVPN Optimized Inter-Subnet Multicast (OISM) [OISM] Lin at al., "EVPN Optimized Inter-Subnet Multicast (OISM)
Forwarding", draft-lin-bess-evpn-irb-mcast-04, work in progress, Forwarding", draft-ietf-bess-evpn-irb-mcast-01, work in progress,
October 2017 July 2018
[EVPN-DCI] Rabadan et al., "Interconnect Solution for EVPN Overlay [EVPN-DCI] Rabadan et al., "Interconnect Solution for EVPN Overlay
networks", draft-ietf-bess-dci-evpn-overlay-10, work in progress, networks", draft-ietf-bess-dci-evpn-overlay-10, work in progress,
March 2018 March 2018
[BUM-UPDATE] Zhang et al., "Updates on EVPN BUM Procedures", draft- [BUM-UPDATE] Zhang et al., "Updates on EVPN BUM Procedures", draft-
ietf-bess-evpn-bum-procedure-updates-02, work in progress, September ietf-bess-evpn-bum-procedure-updates-04, work in progress, June 2018
2017
[EVPN-IPVPN] Rabadan-Sajassi et al., "EVPN Interworking with IPVPN", [EVPN-IPVPN] Rabadan-Sajassi et al., "EVPN Interworking with IPVPN",
draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-00, work in draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-01, work in
progress, October 2017 progress, July 2018
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
L., Sridhar, T., Bursell, M., and C. Wright, "Virtual eXtensible L., Sridhar, T., Bursell, M., and C. Wright, "Virtual eXtensible
Local Area Network (VXLAN): A Framework for Overlaying Virtualized Local Area Network (VXLAN): A Framework for Overlaying Virtualized
Layer 2 Networks over Layer 3 Networks", RFC 7348, DOI Layer 2 Networks over Layer 3 Networks", RFC 7348, DOI
10.17487/RFC7348, August 2014, <http://www.rfc- 10.17487/RFC7348, August 2014, <http://www.rfc-
editor.org/info/rfc7348>. editor.org/info/rfc7348>.
[RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black, [RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black,
"Encapsulating MPLS in UDP", RFC 7510, DOI 10.17487/RFC7510, April "Encapsulating MPLS in UDP", RFC 7510, DOI 10.17487/RFC7510, April
skipping to change at page 25, line 31 skipping to change at page 25, line 22
[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, DOI 10.17487/RFC4364, February 2006, Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006,
<http://www.rfc-editor.org/info/rfc4364>. <http://www.rfc-editor.org/info/rfc4364>.
[CLOS1953] Clos, C., "A Study of Non-Blocking Switching Networks", [CLOS1953] Clos, C., "A Study of Non-Blocking Switching Networks",
The Bell System Technical Journal, Vol. 32(2), DOI 10.1002/j.1538- The Bell System Technical Journal, Vol. 32(2), DOI 10.1002/j.1538-
7305.1953.tb01433.x, March 1953. 7305.1953.tb01433.x, March 1953.
[EVPN-GENEVE] Boutros et al., "EVPN control plane for Geneve", [EVPN-GENEVE] Boutros et al., "EVPN control plane for Geneve",
draft-boutros-bess-evpn-geneve-01, work in progress, February 2018. draft-boutros-bess-evpn-geneve-03, work in progress, September 2018.
[EVPN-MVPN] Sajassi et al., "Seamless Multicast Interoperability [EVPN-MVPN] Sajassi et al., "Seamless Multicast Interoperability
between EVPN and MVPN PEs", draft-sajassi-bess-evpn-mvpn-seamless- between EVPN and MVPN PEs", draft-sajassi-bess-evpn-mvpn-seamless-
interop-00, work in progress, July 2017. interop-02, work in progress, July 2018.
10. Acknowledgments 10. Acknowledgments
The authors want to thank Aldrin Isaac for his comments.
11. Contributors 11. Contributors
12. Authors' Addresses 12. Authors' Addresses
Jorge Rabadan (Editor) Jorge Rabadan (Editor)
Nokia Nokia
777 E. Middlefield Road 777 E. Middlefield Road
Mountain View, CA 94043 USA Mountain View, CA 94043 USA
Email: jorge.rabadan@nokia.com Email: jorge.rabadan@nokia.com
 End of changes. 34 change blocks. 
60 lines changed or deleted 76 lines changed or added

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