draft-ietf-bess-dci-evpn-overlay-09.txt   draft-ietf-bess-dci-evpn-overlay-10.txt 
BESS Workgroup J. Rabadan (Ed.) BESS Workgroup J. Rabadan (Ed.)
Internet Draft S. Sathappan Internet Draft S. Sathappan
Intended status: Standards Track W. Henderickx Intended status: Standards Track W. Henderickx
Updates: 7432 Nokia Nokia
A. Sajassi A. Sajassi
Cisco Cisco
J. Drake J. Drake
Juniper Juniper
Expires: August 24, 2018 February 20, 2018 Expires: September 3, 2018 March 2, 2018
Interconnect Solution for EVPN Overlay networks Interconnect Solution for EVPN Overlay networks
draft-ietf-bess-dci-evpn-overlay-09 draft-ietf-bess-dci-evpn-overlay-10
Abstract Abstract
This document describes how Network Virtualization Overlays (NVO) can This document describes how Network Virtualization Overlays (NVO) can
be connected to a Wide Area Network (WAN) in order to extend the be connected to a Wide Area Network (WAN) in order to extend the
layer-2 connectivity required for some tenants. The solution analyzes layer-2 connectivity required for some tenants. The solution analyzes
the interaction between NVO networks running Ethernet Virtual Private the interaction between NVO networks running Ethernet Virtual Private
Networks (EVPN) and other L2VPN technologies used in the WAN, such as Networks (EVPN) and other L2VPN technologies used in the WAN, such as
Virtual Private LAN Services (VPLS), VPLS extensions for Provider Virtual Private LAN Services (VPLS), VPLS extensions for Provider
Backbone Bridging (PBB-VPLS), EVPN or PBB-EVPN. It also describes how Backbone Bridging (PBB-VPLS), EVPN or PBB-EVPN. It also describes how
the existing technical specifications apply to the Interconnection the existing technical specifications apply to the Interconnection
and extends the EVPN procedures needed in some cases. In particular, and extends the EVPN procedures needed in some cases. In particular,
this document describes how EVPN routes are processed on Gateways this document describes how EVPN routes are processed on Gateways
(GWs) that interconnect EVPN-Overlay and EVPN-MPLS networks, as well (GWs) that interconnect EVPN-Overlay and EVPN-MPLS networks, as well
as the Interconnect Ethernet Segment (I-ES) to provide multi-homing, as the Interconnect Ethernet Segment (I-ES) to provide multi-homing,
and the use of the Unknown MAC route to avoid MAC scale issues on and the use of the Unknown MAC route to avoid MAC scale issues on
Data Center Network Virtualization Edge (NVE) devices. The document Data Center Network Virtualization Edge (NVE) devices.
updates [RFC7432].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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 August 24, 2018. This Internet-Draft will expire on September 3, 2018.
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
Table of Contents Table of Contents
1. Conventions and Terminology . . . . . . . . . . . . . . . . . . 3 1. Conventions and Terminology . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Decoupled Interconnect solution for EVPN overlay networks . . . 6 3. Decoupled Interconnect solution for EVPN overlay networks . . . 6
3.1. Interconnect requirements . . . . . . . . . . . . . . . . . 7 3.1. Interconnect requirements . . . . . . . . . . . . . . . . . 7
3.2. VLAN-based hand-off . . . . . . . . . . . . . . . . . . . . 8 3.2. VLAN-based hand-off . . . . . . . . . . . . . . . . . . . . 8
3.3. PW-based (Pseudowire-based) hand-off . . . . . . . . . . . 8 3.3. PW-based (Pseudowire-based) hand-off . . . . . . . . . . . 8
3.4. Multi-homing solution on the GWs . . . . . . . . . . . . . 9 3.4. Multi-homing solution on the GWs . . . . . . . . . . . . . 9
3.5. Gateway Optimizations . . . . . . . . . . . . . . . . . . . 10 3.5. Gateway Optimizations . . . . . . . . . . . . . . . . . . . 9
3.5.1. MAC Address Advertisement Control . . . . . . . . . . . 10 3.5.1. MAC Address Advertisement Control . . . . . . . . . . . 9
3.5.2. ARP/ND flooding control . . . . . . . . . . . . . . . . 11 3.5.2. ARP/ND flooding control . . . . . . . . . . . . . . . . 10
3.5.3. Handling failures between GW and WAN Edge routers . . . 11 3.5.3. Handling failures between GW and WAN Edge routers . . . 11
4. Integrated Interconnect solution for EVPN overlay networks . . 12 4. Integrated Interconnect solution for EVPN overlay networks . . 11
4.1. Interconnect requirements . . . . . . . . . . . . . . . . . 12 4.1. Interconnect requirements . . . . . . . . . . . . . . . . . 12
4.2. VPLS Interconnect for EVPN-Overlay networks . . . . . . . . 13 4.2. VPLS Interconnect for EVPN-Overlay networks . . . . . . . . 13
4.2.1. Control/Data Plane setup procedures on the GWs . . . . 13 4.2.1. Control/Data Plane setup procedures on the GWs . . . . 13
4.2.2. Multi-homing procedures on the GWs . . . . . . . . . . 14 4.2.2. Multi-homing procedures on the GWs . . . . . . . . . . 14
4.3. PBB-VPLS Interconnect for EVPN-Overlay networks . . . . . . 14 4.3. PBB-VPLS Interconnect for EVPN-Overlay networks . . . . . . 14
4.3.1. Control/Data Plane setup procedures on the GWs . . . . 14 4.3.1. Control/Data Plane setup procedures on the GWs . . . . 14
4.3.2. Multi-homing procedures on the GWs . . . . . . . . . . 15 4.3.2. Multi-homing procedures on the GWs . . . . . . . . . . 15
4.4. EVPN-MPLS Interconnect for EVPN-Overlay networks . . . . . 15 4.4. EVPN-MPLS Interconnect for EVPN-Overlay networks . . . . . 15
4.4.1. Control Plane setup procedures on the GWs . . . . . . . 15 4.4.1. Control Plane setup procedures on the GWs . . . . . . . 15
4.4.2. Data Plane setup procedures on the GWs . . . . . . . . 17 4.4.2. Data Plane setup procedures on the GWs . . . . . . . . 17
4.4.3. Multi-homing procedure extensions on the GWs . . . . . 18 4.4.3. Multi-homing procedure extensions on the GWs . . . . . 18
4.4.4. Impact on MAC Mobility procedures . . . . . . . . . . . 20 4.4.4. Impact on MAC Mobility procedures . . . . . . . . . . . 20
4.4.5. Gateway optimizations . . . . . . . . . . . . . . . . . 21 4.4.5. Gateway optimizations . . . . . . . . . . . . . . . . . 20
4.4.6. Benefits of the EVPN-MPLS Interconnect solution . . . . 21 4.4.6. Benefits of the EVPN-MPLS Interconnect solution . . . . 21
4.5. PBB-EVPN Interconnect for EVPN-Overlay networks . . . . . . 22 4.5. PBB-EVPN Interconnect for EVPN-Overlay networks . . . . . . 22
4.5.1. Control/Data Plane setup procedures on the GWs . . . . 22 4.5.1. Control/Data Plane setup procedures on the GWs . . . . 22
4.5.2. Multi-homing procedures on the GWs . . . . . . . . . . 23 4.5.2. Multi-homing procedures on the GWs . . . . . . . . . . 22
4.5.3. Impact on MAC Mobility procedures . . . . . . . . . . . 23 4.5.3. Impact on MAC Mobility procedures . . . . . . . . . . . 23
4.5.4. Gateway optimizations . . . . . . . . . . . . . . . . . 23 4.5.4. Gateway optimizations . . . . . . . . . . . . . . . . . 23
4.6. EVPN-VXLAN Interconnect for EVPN-Overlay networks . . . . . 23 4.6. EVPN-VXLAN Interconnect for EVPN-Overlay networks . . . . . 23
4.6.1. Globally unique VNIs in the Interconnect network . . . 24 4.6.1. Globally unique VNIs in the Interconnect network . . . 24
4.6.2. Downstream assigned VNIs in the Interconnect network . 25 4.6.2. Downstream assigned VNIs in the Interconnect network . 24
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 25 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 25
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 26 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 26
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1. Normative References . . . . . . . . . . . . . . . . . . . 26 7.1. Normative References . . . . . . . . . . . . . . . . . . . 26
7.2. Informative References . . . . . . . . . . . . . . . . . . 27 7.2. Informative References . . . . . . . . . . . . . . . . . . 27
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 28 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 28
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28
10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 29 10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 29
1. Conventions and Terminology 1. Conventions and Terminology
skipping to change at page 3, line 42 skipping to change at page 3, line 42
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
AC: Attachment Circuit. AC: Attachment Circuit.
ARP: Address Resolution Protocol. ARP: Address Resolution Protocol.
BUM: it refers to the Broadcast, Unknown unicast and Multicast BUM: refers to Broadcast, Unknown unicast and Multicast traffic.
traffic.
CE: Customer Equipment. CE: Customer Equipment.
CFM: Connectivity Fault Management. CFM: Connectivity Fault Management.
DC and DCI: Data Center and Data Center Interconnect. DC and DCI: Data Center and Data Center Interconnect.
DC RR(s) and WAN RR(s): it refers to the Data Center and Wide Area DC RR(s) and WAN RR(s): refers to the Data Center and Wide Area
Network Route Reflectors, respectively. Network Route Reflectors, respectively.
DF and NDF: Designated Forwarder and Non-Designated Forwarder. DF and NDF: Designated Forwarder and Non-Designated Forwarder.
EVPN: Ethernet Virtual Private Network, as in [RFC7432]. EVPN: Ethernet Virtual Private Network, as in [RFC7432].
EVI: EVPN Instance. EVI: EVPN Instance.
EVPN Tunnel binding: it refers to a tunnel to a remote PE/NVE for a EVPN Tunnel binding: refers to a tunnel to a remote PE/NVE for a
given EVI. Ethernet packets in these bindings are encapsulated with given EVI. Ethernet packets in these bindings are encapsulated with
the Overlay or MPLS encapsulation and the EVPN label at the bottom of the Overlay or MPLS encapsulation and the EVPN label at the bottom of
the stack. the stack.
ES: Ethernet Segment. ES and vES: Ethernet Segment and virtual Ethernet Segment.
ESI: Ethernet Segment Identifier. ESI: Ethernet Segment Identifier.
GW: Gateway or Data Center Gateway. GW: Gateway or Data Center Gateway.
I-ES and I-ESI: Interconnect Ethernet Segment and Interconnect I-ES and I-ESI: Interconnect Ethernet Segment and Interconnect
Ethernet Segment Identifier. An I-ES is defined on the GWs for multi- Ethernet Segment Identifier. An I-ES is defined on the GWs for multi-
homing to/from the WAN. homing to/from the WAN.
MAC-VRF: it refers to an EVI instance in a particular node. MAC-VRF: refers to an EVI instance in a particular node.
MP2P and LSM tunnels: it refers to Multi-Point to Point and Label MP2P and LSM tunnels: refer to Multi-Point to Point and Label
Switched Multicast tunnels. Switched Multicast tunnels.
ND: Neighbor Discovery protocol. ND: Neighbor Discovery protocol.
NVE: Network Virtualization Edge. NVE: Network Virtualization Edge.
NVGRE: Network Virtualization using Generic Routing Encapsulation. NVGRE: Network Virtualization using Generic Routing Encapsulation.
NVO: refers to Network Virtualization Overlays. NVO: refers to Network Virtualization Overlays.
skipping to change at page 5, line 5 skipping to change at page 5, line 5
PBB: Provider Backbone Bridging. PBB: Provider Backbone Bridging.
PE: Provider Edge. PE: Provider Edge.
PW: Pseudowire. PW: Pseudowire.
RD: Route-Distinguisher. RD: Route-Distinguisher.
RT: Route-Target. RT: Route-Target.
S/C-TAG: It refers to a combination of Service Tag and Customer Tag S/C-TAG: refers to a combination of Service Tag and Customer Tag in a
in a 802.1Q frame. 802.1Q frame.
TOR: Top-Of-Rack switch. TOR: Top-Of-Rack switch.
UMR: Unknown MAC Route. UMR: Unknown MAC Route.
VNI/VSID: refers to VXLAN/NVGRE virtual identifiers. VNI/VSID: refers to VXLAN/NVGRE virtual identifiers.
VPLS: Virtual Private LAN Service. VPLS: Virtual Private LAN Service.
VSI: Virtual Switch Instance or VPLS instance in a particular PE. VSI: Virtual Switch Instance or VPLS instance in a particular PE.
skipping to change at page 5, line 41 skipping to change at page 5, line 41
existing deployed technologies. For instance, a Service Provider existing deployed technologies. For instance, a Service Provider
might have an already deployed Virtual Private LAN Service (VPLS) might have an already deployed Virtual Private LAN Service (VPLS)
[RFC4761][RFC4762], VPLS extensions for Provider Backbone Bridging [RFC4761][RFC4762], VPLS extensions for Provider Backbone Bridging
(PBB-VPLS) [RFC7041], EVPN [RFC7432] or PBB-EVPN [RFC7623] network (PBB-VPLS) [RFC7041], EVPN [RFC7432] or PBB-EVPN [RFC7623] network
that has to be used to interconnect Data Centers and WAN VPN users. A that has to be used to interconnect Data Centers and WAN VPN users. A
Gateway (GW) function is required in these cases. In fact, [EVPN- Gateway (GW) function is required in these cases. In fact, [EVPN-
Overlays] discusses two main Data Center Interconnect solution Overlays] discusses two main Data Center Interconnect solution
groups: "DCI using GWs" and "DCI using ASBRs". This document groups: "DCI using GWs" and "DCI using ASBRs". This document
specifies the solutions that correspond to the "DCI using GWs" group. specifies the solutions that correspond to the "DCI using GWs" group.
This document describes a Interconnect solution for EVPN overlay It is assumed that the NVO Gateway (GW) and the WAN Edge functions
networks, assuming that the NVO Gateway (GW) and the WAN Edge can be decoupled in two separate systems or integrated into the same
functions can be decoupled in two separate systems or integrated into system. The former option will be referred as "Decoupled Interconnect
the same system. The former option will be referred as "Decoupled solution" throughout the document, whereas the latter one will be
Interconnect solution" throughout the document, whereas the latter referred as "Integrated Interconnect solution".
one will be referred as "Integrated Interconnect solution".
The specified procedures are local to the redundant GWs connecting a The specified procedures are local to the redundant GWs connecting a
DC to the WAN. The document does not preclude any combination across DC to the WAN. The document does not preclude any combination across
different DCs for the same tenant. For instance, a "Decoupled" different DCs for the same tenant. For instance, a "Decoupled"
solution can be used in GW1 and GW2 (for DC1) and an "Integrated" solution can be used in GW1 and GW2 (for DC1) and an "Integrated"
solution can be used in GW3 and GW4 (for DC2). solution can be used in GW3 and GW4 (for DC2).
While the Gateways and WAN PEs use existing specifications in some While the Gateways and WAN PEs use existing specifications in some
cases, the document also defines extensions so that the requirements cases, the document also defines extensions that are specific to DCI.
of the Interconnection can be met. In particular, the document In particular, those extensions are:
updates [RFC7432] on several aspects:
o The Interconnect Ethernet Segment (I-ES), an Ethernet Segment that o The Interconnect Ethernet Segment (I-ES), an Ethernet Segment that
can be associated not only to a set of Ethernet links, as in can be associated to a set of PWs or other tunnels. I-ES defined in
[RFC7432], but also to a set of PWs or other tunnels. this document is not associated with a set of Ethernet links, as
per [RFC7432], but rather with a set of virtual tunnels (e.g., a
set of PWs). This set of virtual tunnels is referred to as vES
[VIRTUAL-ES].
o The use of the Unknown MAC route in a DCI scenario. o The use of the Unknown MAC route in a DCI scenario.
o The processing of EVPN routes on Gateways with MAC-VRFs connecting o The processing of EVPN routes on Gateways with MAC-VRFs connecting
EVPN-Overlay and EVPN-MPLS networks, or EVPN-Overlay and EVPN- EVPN-Overlay and EVPN-MPLS networks, or EVPN-Overlay and EVPN-
Overlay networks. Overlay networks.
3. Decoupled Interconnect solution for EVPN overlay networks 3. Decoupled Interconnect solution for EVPN overlay networks
This section describes the interconnect solution when the GW and WAN This section describes the interconnect solution when the GW and WAN
skipping to change at page 9, line 17 skipping to change at page 9, line 17
o If a FEC128-based PW is used between the MAC-VRF (GW) and the VSI o If a FEC128-based PW is used between the MAC-VRF (GW) and the VSI
(WAN Edge), the corresponding VCID MUST be provisioned on the MAC- (WAN Edge), the corresponding VCID MUST be provisioned on the MAC-
VRF and match the VCID used in the peer VSI at the WAN Edge router. VRF and match the VCID used in the peer VSI at the WAN Edge router.
o If BGP Auto-discovery [RFC6074] and FEC129-based PWs are used o If BGP Auto-discovery [RFC6074] and FEC129-based PWs are used
between the GW MAC-VRF and the WAN Edge VSI, the provisioning of between the GW MAC-VRF and the WAN Edge VSI, the provisioning of
the VPLS-ID MUST be supported on the MAC-VRF and MUST match the the VPLS-ID MUST be supported on the MAC-VRF and MUST match the
VPLS-ID used in the WAN Edge VSI. VPLS-ID used in the WAN Edge VSI.
If a PW-based handoff is used, the GW's AC (or point of attachment to If a PW-based handoff is used, the GW's AC (or point of attachment to
the EVPN Instance) uses a combination of a PW label and VLAN IDs, as the EVPN Instance) uses a combination of a PW label and VLAN IDs. PWs
opposed to only VLAN IDs as in [RFC7432]. Therefore the [RFC7432] are treated as service interfaces defined in [RFC7432].
mapping definitions of VLAN-based, VLAN-bundle or VLAN-aware bundle
service interfaces are updated in this document to include the PW
label as follows:
o VLAN-Based Service Interface: the AC mapping to the MAC-VRF is
given by a unique combination of (PW label, optional inner VLAN
ID). In this context "optional VLAN ID" means a unique combination
of S/C-TAG or no tag at all. In case of no-tag, the point of
attachment to the MAC-VRF is strictly based on the PW label and the
service interface may be referred to as PW-Based Service Interface.
The rest of the VLAN-Based service characteristics are as per
[RFC7432].
o VLAN-Bundle Service Interface: the AC mapping to the MAC-VRF is
given by a unique combination of (PW label, VLAN ID range), where
VLAN ID range represents the S/C-TAG values included in a range.
The rest of the VLAN-Bundle service characteristics are as per
[RFC7432].
o VLAN-Aware Bundle Service Interface: the AC mapping to the Bridge
Table is given by a unique combination of (PW VC label, VLAN ID).
In this service interface, there are multiple Bridge Tables per
MAC-VRF, and each point of attachment to a Bridge Table has a
different (PW label, VLAN ID) combination. The rest of the VLAN-
Aware Bundle service characteristics are as per [RFC7432].
3.4. Multi-homing solution on the GWs 3.4. Multi-homing solution on the GWs
EVPN single-active multi-homing, i.e. per-service load-balancing EVPN single-active multi-homing, i.e. per-service load-balancing
multi-homing is required in this type of interconnect. multi-homing is required in this type of interconnect.
The GWs will be provisioned with a unique ES per WAN interconnect, The GWs will be provisioned with a unique ES per WAN interconnect,
and the hand-off attachment circuits or PWs between the GW and the and the hand-off attachment circuits or PWs between the GW and the
WAN Edge router will be assigned an ESI for such ES. The ESI will be WAN Edge router will be assigned an ESI for such ES. The ESI will be
administratively configured on the GWs according to the procedures in administratively configured on the GWs according to the procedures in
skipping to change at page 27, line 34 skipping to change at page 27, line 17
[TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation [TUNNEL-ENCAP] Rosen et al., "The BGP Tunnel Encapsulation
Attribute", draft-ietf-idr-tunnel-encaps-08, work in progress, Attribute", draft-ietf-idr-tunnel-encaps-08, work in progress,
January 11, 2018. January 11, 2018.
[RFC7623] Sajassi et al., "Provider Backbone Bridging Combined with [RFC7623] Sajassi et al., "Provider Backbone Bridging Combined with
Ethernet VPN (PBB-EVPN)", RFC 7623, September, 2015, <http://www.rfc- Ethernet VPN (PBB-EVPN)", RFC 7623, September, 2015, <http://www.rfc-
editor.org/info/rfc7623>. editor.org/info/rfc7623>.
[EVPN-Overlays] Sajassi-Drake et al., "A Network Virtualization [EVPN-Overlays] Sajassi-Drake et al., "A Network Virtualization
Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-11.txt, Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-11.txt,
work in progress, January, 2018 work in progress, January 2018.
[RFC7543] Jeng, H., Jalil, L., Bonica, R., Patel, K., and L. Yong, [RFC7543] Jeng, H., Jalil, L., Bonica, R., Patel, K., and L. Yong,
"Covering Prefixes Outbound Route Filter for BGP-4", RFC 7543, DOI "Covering Prefixes Outbound Route Filter for BGP-4", RFC 7543, DOI
10.17487/RFC7543, May 2015, <https://www.rfc- 10.17487/RFC7543, May 2015, <https://www.rfc-
editor.org/info/rfc7543>. editor.org/info/rfc7543>.
7.2. Informative References 7.2. Informative References
[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, [RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
R., Patel, K., and J. Guichard, "Constrained Route Distribution for R., Patel, K., and J. Guichard, "Constrained Route Distribution for
skipping to change at page 28, line 36 skipping to change at page 28, line 21
2014. 2014.
[RFC6870] Muley, P., Ed., and M. Aissaoui, Ed., "Pseudowire [RFC6870] Muley, P., Ed., and M. Aissaoui, Ed., "Pseudowire
Preferential Forwarding Status Bit", RFC 6870, DOI 10.17487/RFC6870, Preferential Forwarding Status Bit", RFC 6870, DOI 10.17487/RFC6870,
February 2013, <http://www.rfc-editor.org/info/rfc6870>. February 2013, <http://www.rfc-editor.org/info/rfc6870>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, DOI 10.17487/RFC3031, Label Switching Architecture", RFC 3031, DOI 10.17487/RFC3031,
January 2001, <http://www.rfc-editor.org/info/rfc3031>. January 2001, <http://www.rfc-editor.org/info/rfc3031>.
[VIRTUAL-ES] Sajassi et al., "EVPN Virtual Ethernet Segment", draft-
sajassi-bess-evpn-virtual-eth-segment-03, work in progress, February
2018.
8. Acknowledgments 8. Acknowledgments
The authors would like to thank Neil Hart, Vinod Prabhu and Kiran The authors would like to thank Neil Hart, Vinod Prabhu and Kiran
Nagaraj for their valuable comments and feedback. We would also like Nagaraj for their valuable comments and feedback. We would also like
to thank Martin Vigoureux and Alvaro Retana for his detailed review to thank Martin Vigoureux and Alvaro Retana for his detailed review
and comments. and comments.
9. Contributors 9. Contributors
In addition to the authors listed on the front page, the following In addition to the authors listed on the front page, the following
 End of changes. 23 change blocks. 
61 lines changed or deleted 39 lines changed or added

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