draft-ietf-bess-evpn-optimized-ir-00.txt   draft-ietf-bess-evpn-optimized-ir-01.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Nokia Nokia
R. Shekhar R. Shekhar
N. Sheth A. Sajassi N. Sheth A. Sajassi
W. Lin Cisco W. Lin Cisco
M. Katiyar M. Katiyar
Juniper A. Isaac Juniper A. Isaac
Juniper Juniper
M. Tufail M. Tufail
Citibank Citibank
Expires: September 1, 2016 February 29, 2016 Expires: August 19, 2017 February 15, 2017
Optimized Ingress Replication solution for EVPN Optimized Ingress Replication solution for EVPN
draft-ietf-bess-evpn-optimized-ir-00 draft-ietf-bess-evpn-optimized-ir-01
Abstract Abstract
Network Virtualization Overlay (NVO) networks using EVPN as control Network Virtualization Overlay (NVO) networks using EVPN as control
plane may use ingress replication (IR) or PIM-based trees to convey plane may use ingress replication (IR) or PIM-based trees to convey
the overlay multicast traffic. PIM provides an efficient solution to the overlay BUM traffic. PIM provides an efficient solution to avoid
avoid sending multiple copies of the same packet over the same sending multiple copies of the same packet over the same physical
physical link, however it may not always be deployed in the NVO core link, however it may not always be deployed in the NVO core network.
network. IR avoids the dependency on PIM in the NVO network core. IR avoids the dependency on PIM in the NVO network core. While IR
While IR provides a simple multicast transport, some NVO networks provides a simple multicast transport, some NVO networks with
with demanding multicast applications require a more efficient demanding multicast applications require a more efficient solution
solution without PIM in the core. This document describes a solution without PIM in the core. This document describes a solution to
to optimize the efficiency of IR in NVO networks. optimize the efficiency of IR in NVO networks.
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 12 skipping to change at page 2, line 12
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 September 1, 2016. This Internet-Draft will expire on August 19, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3 1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3
2. Solution requirements . . . . . . . . . . . . . . . . . . . . . 4 2. Solution requirements . . . . . . . . . . . . . . . . . . . . . 4
3. EVPN BGP Attributes for optimized-IR . . . . . . . . . . . . . 5 3. EVPN BGP Attributes for optimized-IR . . . . . . . . . . . . . 5
4. Non-selective Assisted-Replication (AR) Solution Description . 7 4. Non-selective Assisted-Replication (AR) Solution Description . 7
4.1. Non-selective AR-REPLICATOR procedures . . . . . . . . . . 8 4.1. Non-selective AR-REPLICATOR procedures . . . . . . . . . . 8
4.2. Non-selective AR-LEAF procedures . . . . . . . . . . . . . 9 4.2. Non-selective AR-LEAF procedures . . . . . . . . . . . . . 9
4.3. RNVE procedures . . . . . . . . . . . . . . . . . . . . . . 10 4.3. RNVE procedures . . . . . . . . . . . . . . . . . . . . . . 11
4.4. Forwarding behavior in non-selective AR EVIs . . . . . . . 11 4.4. Forwarding behavior in non-selective AR EVIs . . . . . . . 11
4.4.1. Broadcast and Multicast forwarding behavior . . . . . . 11 4.4.1. Broadcast and Multicast forwarding behavior . . . . . . 11
4.4.1.1. Non-selective AR-REPLICATOR BM forwarding . . . . . 11 4.4.1.1. Non-selective AR-REPLICATOR BM forwarding . . . . . 11
4.4.1.2. Non-selective AR-LEAF BM forwarding . . . . . . . . 12 4.4.1.2. Non-selective AR-LEAF BM forwarding . . . . . . . . 12
4.4.1.3. RNVE BM forwarding . . . . . . . . . . . . . . . . 12 4.4.1.3. RNVE BM forwarding . . . . . . . . . . . . . . . . 12
4.4.2. Unknown unicast forwarding behavior . . . . . . . . . . 12 4.4.2. Unknown unicast forwarding behavior . . . . . . . . . . 13
4.4.2.1. Non-selective AR-REPLICATOR/LEAF Unknown unicast 4.4.2.1. Non-selective AR-REPLICATOR/LEAF Unknown unicast
forwarding . . . . . . . . . . . . . . . . . . . . 13 forwarding . . . . . . . . . . . . . . . . . . . . 13
4.4.2.2. RNVE Unknown unicast forwarding . . . . . . . . . . 13 4.4.2.2. RNVE Unknown unicast forwarding . . . . . . . . . . 13
5. Selective Assisted-Replication (AR) Solution Description . . . 13 5. Selective Assisted-Replication (AR) Solution Description . . . 13
5.1. Selective AR-REPLICATOR procedures . . . . . . . . . . . . 14 5.1. Selective AR-REPLICATOR procedures . . . . . . . . . . . . 14
5.2. Selective AR-LEAF procedures . . . . . . . . . . . . . . . 15 5.2. Selective AR-LEAF procedures . . . . . . . . . . . . . . . 15
5.3. Forwarding behavior in selective AR EVIs . . . . . . . . . 16 5.3. Forwarding behavior in selective AR EVIs . . . . . . . . . 16
5.3.1. Selective AR-REPLICATOR BM forwarding . . . . . . . . . 16 5.3.1. Selective AR-REPLICATOR BM forwarding . . . . . . . . . 16
5.3.2. Selective AR-LEAF BM forwarding . . . . . . . . . . . . 17 5.3.2. Selective AR-LEAF BM forwarding . . . . . . . . . . . . 17
6. Pruned-Flood-Lists (PFL) . . . . . . . . . . . . . . . . . . . 18 6. Pruned-Flood-Lists (PFL) . . . . . . . . . . . . . . . . . . . 18
6.1. A PFL example . . . . . . . . . . . . . . . . . . . . . . . 18 6.1. A PFL example . . . . . . . . . . . . . . . . . . . . . . . 18
7. AR Procedures for single-IP AR-REPLICATORS . . . . . . . . . . 19 7. AR Procedures for single-IP AR-REPLICATORS . . . . . . . . . . 19
8. AR Procedures and EVPN Multi-homing Split-Horizon . . . . . . . 20 8. AR Procedures and EVPN Multi-homing Split-Horizon . . . . . . . 20
9. Out-of-band distribution of Broadcast/Multicast traffic . . . . 20 9. Out-of-band distribution of Broadcast/Multicast traffic . . . . 21
10. Benefits of the optimized-IR solution . . . . . . . . . . . . 20 10. Benefits of the optimized-IR solution . . . . . . . . . . . . 21
11. Conventions used in this document . . . . . . . . . . . . . . 21 11. Conventions used in this document . . . . . . . . . . . . . . 21
12. Security Considerations . . . . . . . . . . . . . . . . . . . 21 12. Security Considerations . . . . . . . . . . . . . . . . . . . 21
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
14. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 21 14. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 22
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
15.1 Normative References . . . . . . . . . . . . . . . . . . . 22 15.1 Normative References . . . . . . . . . . . . . . . . . . . 23
15.2 Informative References . . . . . . . . . . . . . . . . . . 22 15.2 Informative References . . . . . . . . . . . . . . . . . . 23
16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
17. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 17. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23
1. Problem Statement 1. Problem Statement
EVPN may be used as the control plane for a Network Virtualization EVPN may be used as the control plane for a Network Virtualization
Overlay (NVO) network. Network Virtualization Edge (NVE) devices and Overlay (NVO) network. Network Virtualization Edge (NVE) devices and
PEs that are part of the same EVI use Ingress Replication (IR) or PEs that are part of the same EVI use Ingress Replication (IR) or
PIM-based trees to transport the tenant's multicast traffic. In NVO PIM-based trees to transport the tenant's BUM traffic. In NVO
networks where PIM-based trees cannot be used, IR is the only networks where PIM-based trees cannot be used, IR is the only
alternative. Examples of these situations are NVO networks where the alternative. Examples of these situations are NVO networks where the
core nodes don't support PIM or the network operator does not want to core nodes don't support PIM or the network operator does not want to
run PIM in the core. run PIM in the core.
In some use-cases, the amount of replication for BUM (Broadcast, In some use-cases, the amount of replication for BUM (Broadcast,
Unknown unicast and Multicast traffic) is kept under control on the Unknown unicast and Multicast traffic) is kept under control on the
NVEs due to the following fairly common assumptions: NVEs due to the following fairly common assumptions:
a) Broadcast is greatly reduced due to the proxy-ARP and proxy-ND a) Broadcast is greatly reduced due to the proxy-ARP and proxy-ND
skipping to change at page 4, line 22 skipping to change at page 4, line 22
the NVE and impact the application. the NVE and impact the application.
This document describes a solution that makes use of two IR This document describes a solution that makes use of two IR
optimizations: optimizations:
i) Assisted-Replication (AR) i) Assisted-Replication (AR)
ii) Pruned-Flood-Lists (PFL) ii) Pruned-Flood-Lists (PFL)
Both optimizations may be used together or independently so that the Both optimizations may be used together or independently so that the
performance and efficiency of the network to transport multicast can performance and efficiency of the network to transport multicast can
be improved. Both solutions require some extensions to [EVPN] that be improved. Both solutions require some extensions to [RFC7432] that
are described in section 3. are described in section 3.
Section 2 lists the requirements of the combined optimized-IR Section 2 lists the requirements of the combined optimized-IR
solution, whereas sections 4 and 5 describe the Assisted-Replication solution, whereas sections 4 and 5 describe the Assisted-Replication
(AR) solution, and section 6 the Pruned-Flood-Lists (PFL) solution. (AR) solution, and section 6 the Pruned-Flood-Lists (PFL) solution.
2. Solution requirements 2. Solution requirements
The IR optimization solution (optimized-IR hereafter) MUST meet the The IR optimization solution (optimized-IR hereafter) MUST meet the
following requirements: following requirements:
a) The solution MUST provide an IR optimization for BM (Broadcast and a) The solution MUST provide an IR optimization for BM (Broadcast and
Multicast) traffic, while preserving the packet order for unicast Multicast) traffic, while preserving the packet order for unicast
applications, i.e. known and unknown unicast traffic SHALL follow applications, i.e. known and unknown unicast traffic SHALL follow
the same path. the same path.
b) The solution MUST be compatible with [EVPN] and [EVPN-OVERLAY] and b) The solution MUST be compatible with [RFC7432] and [EVPN-OVERLAY]
not have any impact on the EVPN procedures for BM traffic. In and have no impact on the EVPN procedures for BM traffic. In
particular, the solution MUST support the following EVPN particular, the solution SHOULD support the following EVPN
functions: functions:
o All-active multi-homing, including the split-horizon and o All-active multi-homing, including the split-horizon and
Designated Forwarder (DF) functions. Designated Forwarder (DF) functions.
o Single-active multi-homing, including the DF function. o Single-active multi-homing, including the DF function.
o Handling of multi-destination traffic and processing of o Handling of multi-destination traffic and processing of
broadcast and multicast as per [EVPN]. broadcast and multicast as per [RFC7432].
c) The solution MUST be backwards compatible with existing NVEs using c) The solution MUST be backwards compatible with existing NVEs using
a non-optimized version of IR. A given EVI can have NVEs/PEs a non-optimized version of IR. A given EVI can have NVEs/PEs
supporting regular-IR and optimized-IR. supporting regular-IR and optimized-IR.
d) The solution MUST be independent of the NVO specific data plane d) The solution MUST be independent of the NVO specific data plane
encapsulation and the virtual identifiers being used, e.g.: VXLAN encapsulation and the virtual identifiers being used, e.g.: VXLAN
VNIs, NVGRE VSIDs or MPLS labels. VNIs, NVGRE VSIDs or MPLS labels.
3. EVPN BGP Attributes for optimized-IR 3. EVPN BGP Attributes for optimized-IR
This solution proposes some changes to the [EVPN] Inclusive Multicast This solution proposes some changes to the [RFC7432] Inclusive
Ethernet Tag routes and attributes so that an NVE/PE can signal its Multicast Ethernet Tag routes and attributes so that an NVE/PE can
optimized-IR capabilities. signal its optimized-IR capabilities.
The Inclusive Multicast Ethernet Tag route (RT-3) and its PMSI Tunnel The Inclusive Multicast Ethernet Tag route (RT-3) and its PMSI Tunnel
Attribute's (PTA) general format used in [EVPN] are shown below: Attribute's (PTA) general format used in [RFC7432] are shown below:
+---------------------------------+ +---------------------------------+
| RD (8 octets) | | RD (8 octets) |
+---------------------------------+ +---------------------------------+
| Ethernet Tag ID (4 octets) | | Ethernet Tag ID (4 octets) |
+---------------------------------+ +---------------------------------+
| IP Address Length (1 octet) | | IP Address Length (1 octet) |
+---------------------------------+ +---------------------------------+
| Originating Router's IP Addr | | Originating Router's IP Addr |
| (4 or 16 octets) | | (4 or 16 octets) |
skipping to change at page 6, line 14 skipping to change at page 6, line 14
- T is the AR Type field (2 bits) that defines the AR role of the - T is the AR Type field (2 bits) that defines the AR role of the
advertising router: advertising router:
+ 00 (decimal 0) = RNVE (non-AR support) + 00 (decimal 0) = RNVE (non-AR support)
+ 01 (decimal 1) = AR-REPLICATOR + 01 (decimal 1) = AR-REPLICATOR
+ 10 (decimal 2) = AR-LEAF + 10 (decimal 2) = AR-LEAF
+ 11 (decimal 3) = RESERVED
- The PFL (Pruned-Flood-Lists) flags defined the desired behavior of - The PFL (Pruned-Flood-Lists) flags defined the desired behavior of
the advertising router for the different types of traffic: the advertising router for the different types of traffic:
+ BM= Broadcast and Multicast (BM) flag. BM=1 means "prune-me" from + BM= Broadcast and Multicast (BM) flag. BM=1 means "prune-me" from
the BM flooding list. BM=0 means regular behavior. the BM flooding list. BM=0 means regular behavior.
+ U= Unknown flag. U=1 means "prune-me" from the Unknown flooding + U= Unknown flag. U=1 means "prune-me" from the Unknown flooding
list. U=0 means regular behavior. list. U=0 means regular behavior.
- Flag L is an existing flag defined in [RFC6514] (L=Leaf Information - Flag L is an existing flag defined in [RFC6514] (L=Leaf Information
Required) and it will be used only in the Selective AR Solution. Required) and it will be used only in the Selective AR Solution.
Please refer to section 10 for the IANA considerations related to the Please refer to section 10 for the IANA considerations related to the
PTA flags. PTA flags.
In this document, the above RT-3 and PTA can be used in three In this document, the above RT-3 and PTA can be used in two different
different modes for the same EVI/Ethernet Tag: modes for the same EVI/Ethernet Tag:
o Regular-IR route: in this route, Originating Router's IP Address, o Regular-IR route: in this route, Originating Router's IP Address,
Tunnel Type (0x06), MPLS Label, Tunnel Identifier and Flags MUST be Tunnel Type (0x06), MPLS Label, Tunnel Identifier and Flags MUST be
used as described in [EVPN]. The Originating Router's IP Address used as described in [RFC7432]. The Originating Router's IP Address
and Tunnel Identifier are set to an IP address that we denominate and Tunnel Identifier are set to an IP address that we denominate
IR-IP in this document. IR-IP in this document.
o Replicator-AR route: this route is used by the AR-REPLICATOR to o Replicator-AR route: this route is used by the AR-REPLICATOR to
advertise its AR capabilities, with the fields set as follows. advertise its AR capabilities, with the fields set as follows.
+ Originating Router's IP Address as well as the Tunnel Identifier + Originating Router's IP Address as well as the Tunnel Identifier
are set to the same routable IP address that we denominate AR-IP are set to the same routable IP address that we denominate AR-IP
and SHOULD be different than the IR-IP for a given PE/NVE. and SHOULD be different than the IR-IP for a given PE/NVE.
+ Tunnel Type = Assisted-Replication (AR). Section 11 provides the + Tunnel Type = Assisted-Replication (AR). Section 11 provides the
allocated type value. allocated type value.
+ T (AR role type) = 01 (AR-REPLICATOR). + T (AR role type) = 01 (AR-REPLICATOR).
+ L (Leaf Information Required) = 0 (for non-selective AR) or 1 + L (Leaf Information Required) = 0 (for non-selective AR) or 1
(for selective AR). (for selective AR).
o Leaf-AR route: this route MAY be used by the AR-LEAF to advertise In addition, this document also uses the Leaf-AD route (RT-11)
its desire to receive the multicast traffic from a specific AR- defined in [EVPN-BUM] in case the selective AR mode is used. The
REPLICATOR. It is only used for selective AR and its fields are set Leaf-AD route MAY be used by the AR-LEAF in response to a Replicator-
as follows: AR route (with the L flag set) to advertise its desire to receive the
multicast traffic from a specific AR-REPLICATOR. It is only used for
selective AR and its fields are set as follows:
+ Originating Router's IP Address is set to the advertising IR-IP + Originating Router's IP Address is set to the advertising IR-IP
(same IP used by the AR-LEAF in regular-IR routes). (same IP used by the AR-LEAF in regular-IR routes).
+ Tunnel Identifier is set to the AR-IP of the AR-REPLICATOR from + Route Key is the "Route Type Specific" NLRI of the Replicator-AR
which the multicast traffic is requested. route for which this Leaf-AD route is generated.
+ Tunnel Type = Assisted-Replication (AR). Section 11 provides the + The AR-LEAF constructs an IP-address-specific route-target as
allocated type value. indicated in [EVPN-BUM], by placing the IP address carried in the
Next Hop field of the received Replicator-AR route in the Global
Administrator field of the Community, with the Local
Administrator field of this Community set to 0. Note that the
same IP-address-specific import route-target is auto-configured
by the AR-REPLICATOR that sent the Replicator-AR, in order to
control the acceptance of the Leaf-AD routes.
+ T (AR role type) = 02 (AR-LEAF). + The leaf-AD route MUST include the PMSI Tunnel attribute with the
Tunnel Type set to AR, type set to AR-LEAF and the Tunnel
Identifier set to the IR-IP of the advertising AR-LEAF. The PMSI
Tunnel attribute MUST carry a downstream-assigned MPLS label that
is used by the AR-REPLICATOR to send traffic to the AR-LEAF.
Each AR-enabled node MUST understand and process the AR type field in Each AR-enabled node MUST understand and process the AR type field in
the PTA (Flags field) of replicator-AR and leaf-AR routes, and MUST the PTA (Flags field) of the routes, and MUST signal the
signal the corresponding type (1 or 2) according to its corresponding type (1 or 2) according to its administrative choice.
administrative choice for replicator-AR and leaf-AR routes.
Each node, part of the EVI, MAY understand and process the BM/U Each node, part of the EVI, MAY understand and process the BM/U
flags. Note that these BM/U flags may be used to optimize the flags. Note that these BM/U flags may be used to optimize the
delivery of multi-destination traffic and its use SHOULD be an delivery of multi-destination traffic and its use SHOULD be an
administrative choice, and independent of the AR role. administrative choice, and independent of the AR role.
Non-optimized-IR nodes will be unaware of the new PMSI attribute flag Non-optimized-IR nodes will be unaware of the new PMSI attribute flag
definition as well as the new Tunnel Type (AR), i.e. they will ignore definition as well as the new Tunnel Type (AR), i.e. they will ignore
the information contained in the flags field for any RT-3 and will the information contained in the flags field for any RT-3 and will
ignore the RT-3 routes with an unknown Tunnel Type (type AR in this ignore the RT-3 routes with an unknown Tunnel Type (type AR in this
skipping to change at page 8, line 47 skipping to change at page 9, line 6
The AR-REPLICATOR signals its role in the control plane and The AR-REPLICATOR signals its role in the control plane and
understands where the other roles (AR-LEAF nodes, RNVEs and other AR- understands where the other roles (AR-LEAF nodes, RNVEs and other AR-
REPLICATORs) are located. A given AR-enabled EVI service may have REPLICATORs) are located. A given AR-enabled EVI service may have
zero, one or more AR-REPLICATORs. In our example in figure 1, PE1 and zero, one or more AR-REPLICATORs. In our example in figure 1, PE1 and
PE2 are defined as AR-REPLICATORs. The following considerations apply PE2 are defined as AR-REPLICATORs. The following considerations apply
to the AR-REPLICATOR role: to the AR-REPLICATOR role:
a) The AR-REPLICATOR role SHOULD be an administrative choice in any a) The AR-REPLICATOR role SHOULD be an administrative choice in any
NVE/PE that is part of an AR-enabled EVI. This administrative NVE/PE that is part of an AR-enabled EVI. This administrative
option to enable AR-REPLICATOR capabilities MAY be implemented as option to enable AR-REPLICATOR capabilities MAY be implemented as
a system level option as opposed to as a per-EVI option. a system level option as opposed to as a per-MAC-VRF option.
b) An AR-REPLICATOR MUST advertise a Replicator-AR route and MAY b) An AR-REPLICATOR MUST advertise a Replicator-AR route and MAY
advertise a Regular-IR route. The AR-REPLICATOR MUST NOT generate advertise a Regular-IR route. The AR-REPLICATOR MUST NOT generate
a Regular-IR route if it does not have local attachment circuits a Regular-IR route if it does not have local attachment circuits
(AC). (AC).
c) The Replicator-AR and Regular-IR routes will be generated c) The Replicator-AR and Regular-IR routes will be generated
according to section 3. The AR-IP and IR-IP used by the according to section 3. The AR-IP and IR-IP used by the
Replicator-AR will be different routable IP addresses. Replicator-AR will be different routable IP addresses.
d) When a node defined as AR-REPLICATOR receives a packet on an d) When a node defined as AR-REPLICATOR receives a packet on an
overlay tunnel, it will do a tunnel destination IP lookup and overlay tunnel, it will do a tunnel destination IP lookup and
apply the following procedures: apply the following procedures:
o If the destination IP is the AR-REPLICATOR IR-IP Address the o If the destination IP is the AR-REPLICATOR IR-IP Address the
node will process the packet normally as in [EVPN]. node will process the packet normally as in [RFC7432].
o If the destination IP is the AR-REPLICATOR AR-IP Address the o If the destination IP is the AR-REPLICATOR AR-IP Address the
node MUST replicate the packet to local ACs and overlay node MUST replicate the packet to local ACs and overlay
tunnels (excluding the overlay tunnel to the source of the tunnels (excluding the overlay tunnel to the source of the
packet). When replicating to remote AR-REPLICATORs the tunnel packet). When replicating to remote AR-REPLICATORs the tunnel
destination IP will be an IR-IP. That will be an indication destination IP will be an IR-IP. That will be an indication
for the remote AR-REPLICATOR that it MUST NOT replicate to for the remote AR-REPLICATOR that it MUST NOT replicate to
overlay tunnels. The tunnel source IP will be the AR-IP of the overlay tunnels. The tunnel source IP will be the AR-IP of the
AR-REPLICATOR. AR-REPLICATOR.
4.2. Non-selective AR-LEAF procedures 4.2. Non-selective AR-LEAF procedures
AR-LEAF is defined as an NVE/PE that - given its poor replication AR-LEAF is defined as an NVE/PE that - given its poor replication
performance - sends all the BM traffic to an AR-REPLICATOR that can performance - sends all the BM traffic to an AR-REPLICATOR that can
replicate the traffic further on its behalf. It MAY signal its AR- replicate the traffic further on its behalf. It MAY signal its AR-
LEAF capability in the control plane and understands where the other LEAF capability in the control plane and understands where the other
roles are located (AR-REPLICATOR and RNVEs). A given service can have roles are located (AR-REPLICATOR and RNVEs). A given service can have
zero, one or more AR-LEAF nodes. Figure 1 shows NVE1 and NVE2 (both zero, one or more AR-LEAF nodes. Figure 1 shows NVE1 and NVE3 (both
residing in hypervisors) acting as AR-LEAF. The following residing in hypervisors) acting as AR-LEAF. The following
considerations apply to the AR-LEAF role: considerations apply to the AR-LEAF role:
a) The AR-LEAF role SHOULD be an administrative choice in any NVE/PE a) The AR-LEAF role SHOULD be an administrative choice in any NVE/PE
that is part of an AR-enabled EVI. This administrative option to that is part of an AR-enabled EVI. This administrative option to
enable AR-LEAF capabilities MAY be implemented as a system level enable AR-LEAF capabilities MAY be implemented as a system level
option as opposed to as per-EVI option. option as opposed to as per-MAC-VRF option.
b) In this non-selective AR solution, the AR-LEAF MUST advertise a b) In this non-selective AR solution, the AR-LEAF MUST advertise a
single Regular-IR inclusive multicast route as in [EVPN]. The AR- single Regular-IR inclusive multicast route as in [RFC7432]. The
LEAF SHOULD set the AR Type field to AR-LEAF. Note that although AR-LEAF SHOULD set the AR Type field to AR-LEAF. Note that
this flag does not make any difference for the egress nodes when although this flag does not make any difference for the egress
creating an EVPN destination to the the AR-LEAF, it is RECOMMENDED nodes when creating an EVPN destination to the the AR-LEAF, it is
the use of this flag for an easy operation and troubleshooting of RECOMMENDED the use of this flag for an easy operation and
the EVI. troubleshooting of the EVI.
c) In a service where there are no AR-REPLICATORs, the AR-LEAF MUST c) In a service where there are no AR-REPLICATORs, the AR-LEAF MUST
use regular ingress replication. This will happen when a new use regular ingress replication. This will happen when a new
update from the last former AR-REPLICATOR is received and contains update from the last former AR-REPLICATOR is received and contains
a non-REPLICATOR AR type, or when the AR-LEAF detects that the a non-REPLICATOR AR type, or when the AR-LEAF detects that the
last AR-REPLICATOR is down (next-hop tracking in the IGP or any last AR-REPLICATOR is down (next-hop tracking in the IGP or any
other detection mechanism). Ingress replication MUST use the other detection mechanism). Ingress replication MUST use the
forwarding information given by the remote Regular-IR Inclusive forwarding information given by the remote Regular-IR Inclusive
Multicast Routes as described in [EVPN]. Multicast Routes as described in [RFC7432].
d) In a service where there is one or more AR-REPLICATORs (based on d) In a service where there is one or more AR-REPLICATORs (based on
the received Replicator-AR routes for the EVI), the AR-LEAF can the received Replicator-AR routes for the EVI), the AR-LEAF can
locally select which AR-REPLICATOR it sends the BM traffic to: locally select which AR-REPLICATOR it sends the BM traffic to:
o A single AR-REPLICATOR MAY be selected for all the BM packets o A single AR-REPLICATOR MAY be selected for all the BM packets
received on the AR-LEAF attachment circuits (ACs) for a given received on the AR-LEAF attachment circuits (ACs) for a given
EVI. This selection is a local decision and it does not have EVI. This selection is a local decision and it does not have
to match other AR-LEAF's selection within the same EVI. to match other AR-LEAF's selection within the same EVI.
o An AR-LEAF MAY select more than one AR-REPLICATOR and do o An AR-LEAF MAY select more than one AR-REPLICATOR and do
either per-flow or per-EVI load balancing. either per-flow or per-EVI load balancing.
o In case of a failure on the selected AR-REPLICATOR, another o In case of a failure on the selected AR-REPLICATOR, another
AR-REPLICATOR will be selected. AR-REPLICATOR will be selected.
o When an AR-REPLICATOR is selected, the AR-LEAF MUST send all o When an AR-REPLICATOR is selected, the AR-LEAF MUST send all
the BM packets to that AR-REPLICATOR using the forwarding the BM packets to that AR-REPLICATOR using the forwarding
information given by the Replicator-AR route for the chosen information given by the Replicator-AR route for the chosen
AR-REPLICATOR, with tunnel type = TBD (AR tunnel). The AR-REPLICATOR, with tunnel type = 0x0A (AR tunnel). The
underlay destination IP address MUST be the AR-IP advertised underlay destination IP address MUST be the AR-IP advertised
by the AR-REPLICATOR in the Replicator-AR route. by the AR-REPLICATOR in the Replicator-AR route.
o AR-LEAF nodes SHALL send service-level BM control plane o AR-LEAF nodes SHALL send service-level BM control plane
packets following regular IR procedures. An example would be packets following regular IR procedures. An example would be
IGMP, MLD or PIM multicast packets. The AR-REPLICATORs MUST IGMP, MLD or PIM multicast packets. The AR-REPLICATORs MUST
not replicate these control plane packets to other overlay not replicate these control plane packets to other overlay
tunnels since they will use the regular IR-IP Address. tunnels since they will use the regular IR-IP Address.
e) The use of an AR-REPLICATOR-activation-timer (in seconds) on the e) The use of an AR-REPLICATOR-activation-timer (in seconds) on the
AR-LEAF nodes is RECOMMENDED. Upon receiving a new Replicator-AR AR-LEAF nodes is RECOMMENDED. Upon receiving a new Replicator-AR
route where the AR-REPLICATOR is selected, the AR-LEAF will run a route where the AR-REPLICATOR is selected, the AR-LEAF will run a
timer before programming the new AR-REPLICATOR. This will give the timer before programming the new AR-REPLICATOR. This will give the
AR-REPLICATOR some time to program the AR-LEF nodes before the AR- AR-REPLICATOR some time to program the AR-LEAF nodes before the
LEAF sends BM traffic. AR-LEAF sends BM traffic.
4.3. RNVE procedures 4.3. RNVE procedures
RNVE (Regular Network Virtualization Edge node) is defined as an RNVE (Regular Network Virtualization Edge node) is defined as an
NVE/PE without AR-REPLICATOR or AR-LEAF capabilities that does IR as NVE/PE without AR-REPLICATOR or AR-LEAF capabilities that does IR as
described in [EVPN]. The RNVE does not signal any AR role and is described in [RFC7432]. The RNVE does not signal any AR role and is
unaware of the AR-REPLICATOR/LEAF roles in the EVI. The RNVE will unaware of the AR-REPLICATOR/LEAF roles in the EVI. The RNVE will
ignore the Flags in the Regular-IR routes and will ignore the ignore the Flags in the Regular-IR routes and will ignore the
Replicator-AR and Leaf-AR routes entirely (due to an unknown tunnel Replicator-AR routes (due to an unknown tunnel type in the PTA) and
type in the PTA). the Leaf-AD routes (due to the IP-address-specific route-target).
This role provides EVPN with the backwards compatibility required in This role provides EVPN with the backwards compatibility required in
optimized-IR EVIs. Figure 1 shows NVE2 as RNVE. optimized-IR EVIs. Figure 1 shows NVE2 as RNVE.
4.4. Forwarding behavior in non-selective AR EVIs 4.4. Forwarding behavior in non-selective AR EVIs
In AR EVIs, BM (Broadcast and Multicast) traffic between two NVEs may In AR EVIs, BM (Broadcast and Multicast) traffic between two NVEs may
follow a different path than unicast traffic. This solution proposes follow a different path than unicast traffic. This solution proposes
the replication of BM through the AR-REPLICATOR node, whereas the replication of BM through the AR-REPLICATOR node, whereas
unknown/known unicast will be delivered directly from the source node unknown/known unicast will be delivered directly from the source node
skipping to change at page 11, line 51 skipping to change at page 12, line 10
forward the BM packet to its flooding list (including local ACs and forward the BM packet to its flooding list (including local ACs and
remote NVE/PEs), skipping the non-BM overlay tunnels. remote NVE/PEs), skipping the non-BM overlay tunnels.
o When an AR-REPLICATOR receives a BM packet on an overlay tunnel, it o When an AR-REPLICATOR receives a BM packet on an overlay tunnel, it
will check the destination IP of the underlay IP header and: will check the destination IP of the underlay IP header and:
- If the destination IP matches its AR-IP, the AR-REPLICATOR will - If the destination IP matches its AR-IP, the AR-REPLICATOR will
forward the BM packet to its flooding list (ACs and overlay forward the BM packet to its flooding list (ACs and overlay
tunnels) excluding the non-BM overlay tunnels. The AR-REPLICATOR tunnels) excluding the non-BM overlay tunnels. The AR-REPLICATOR
will do source squelching to ensure the traffic is not sent back will do source squelching to ensure the traffic is not sent back
to the originating AR-LEAF. If the overlay encapsulation is MPLS to the originating AR-LEAF. If the encapsulation is MPLSoGRE (or
and the EVI label is not the bottom of the stack, the AR- MPLSoUDP) and the EVI label is not the bottom of the stack, the
REPLICATOR MUST copy the rest of the labels and forward them to AR-REPLICATOR MUST copy the rest of the labels and forward them
the egress overlay tunnels. to the egress overlay tunnels.
- If the destination IP matches its IR-IP, the AR-REPLICATOR will - If the destination IP matches its IR-IP, the AR-REPLICATOR will
skip all the overlay tunnels from the flooding list, i.e. it skip all the overlay tunnels from the flooding list, i.e. it
will only replicate to local ACs. This is the regular IR will only replicate to local ACs. This is the regular IR
behavior described in [EVPN]. behavior described in [RFC7432].
4.4.1.2. Non-selective AR-LEAF BM forwarding 4.4.1.2. Non-selective AR-LEAF BM forwarding
The AR-LEAF nodes will build two flood-lists: The AR-LEAF nodes will build two flood-lists:
1) Flood-list #1 - composed of ACs and an AR-REPLICATOR-set of 1) Flood-list #1 - composed of ACs and an AR-REPLICATOR-set of
overlay tunnels. The AR-REPLICATOR-set is defined as one or more overlay tunnels. The AR-REPLICATOR-set is defined as one or more
overlay tunnels to the AR-IP Addresses of the remote AR- overlay tunnels to the AR-IP Addresses of the remote AR-
REPLICATOR(s) in the EVI. The selection of more than one AR- REPLICATOR(s) in the EVI. The selection of more than one AR-
REPLICATOR is described in section 4.2. and it is a local AR- REPLICATOR is described in section 4.2. and it is a local AR-
skipping to change at page 12, line 39 skipping to change at page 12, line 46
o If the AR-REPLICATOR-set is empty, the AR-LEAF will send the packet o If the AR-REPLICATOR-set is empty, the AR-LEAF will send the packet
to flood-list #2. to flood-list #2.
o If the AR-REPLICATOR-set is NOT empty, the AR-LEAF will send the o If the AR-REPLICATOR-set is NOT empty, the AR-LEAF will send the
packet to flood-list #1, where only one of the overlay tunnels of packet to flood-list #1, where only one of the overlay tunnels of
the AR-REPLICATOR-set is used. the AR-REPLICATOR-set is used.
When an AR-LEAF receives a BM packet on an overlay tunnel, will When an AR-LEAF receives a BM packet on an overlay tunnel, will
forward the BM packet to its local ACs and never to an overlay forward the BM packet to its local ACs and never to an overlay
tunnel. This is the regular IR behavior described in [EVPN]. tunnel. This is the regular IR behavior described in [RFC7432].
4.4.1.3. RNVE BM forwarding 4.4.1.3. RNVE BM forwarding
The RNVE is completely unaware of the AR-REPLICATORs, AR-LEAF nodes The RNVE is completely unaware of the AR-REPLICATORs, AR-LEAF nodes
and BM/U flags (that information is ignored). Its forwarding behavior and BM/U flags (that information is ignored). Its forwarding behavior
is the regular IR behavior described in [EVPN]. Any regular non-AR is the regular IR behavior described in [RFC7432]. Any regular non-AR
node is fully compatible with the RNVE role described in this node is fully compatible with the RNVE role described in this
document. document.
4.4.2. Unknown unicast forwarding behavior 4.4.2. Unknown unicast forwarding behavior
The expected behavior is described in this section. The expected behavior is described in this section.
4.4.2.1. Non-selective AR-REPLICATOR/LEAF Unknown unicast forwarding 4.4.2.1. Non-selective AR-REPLICATOR/LEAF Unknown unicast forwarding
While the forwarding behavior in AR-REPLICATORs and AR-LEAF nodes is While the forwarding behavior in AR-REPLICATORs and AR-LEAF nodes is
different for BM traffic, as far as Unknown unicast traffic different for BM traffic, as far as Unknown unicast traffic
forwarding is concerned, AR-LEAF nodes behave exactly in the same way forwarding is concerned, AR-LEAF nodes behave exactly in the same way
as AR-REPLICATORs do. as AR-REPLICATORs do.
The AR-REPLICATOR/LEAF nodes will build a flood-list composed of ACs The AR-REPLICATOR/LEAF nodes will build a flood-list composed of ACs
skipping to change at page 13, line 26 skipping to change at page 13, line 33
unicast) receivers based on the U flag received from the remote nodes unicast) receivers based on the U flag received from the remote nodes
in the EVI. in the EVI.
o When an AR-REPLICATOR/LEAF receives an unknown packet on an AC, it o When an AR-REPLICATOR/LEAF receives an unknown packet on an AC, it
will forward the unknown packet to its flood-list, skipping the will forward the unknown packet to its flood-list, skipping the
non-U overlay tunnels. non-U overlay tunnels.
o When an AR-REPLICATOR/LEAF receives an unknown packet on an overlay o When an AR-REPLICATOR/LEAF receives an unknown packet on an overlay
tunnel will forward the unknown packet to its local ACs and never tunnel will forward the unknown packet to its local ACs and never
to an overlay tunnel. This is the regular IR behavior described in to an overlay tunnel. This is the regular IR behavior described in
[EVPN]. [RFC7432].
4.4.2.2. RNVE Unknown unicast forwarding 4.4.2.2. RNVE Unknown unicast forwarding
As described for BM traffic, the RNVE is completely unaware of the As described for BM traffic, the RNVE is completely unaware of the
REPLICATORs, LEAF nodes and BM/U flags (that information is ignored). REPLICATORs, LEAF nodes and BM/U flags (that information is ignored).
Its forwarding behavior is the regular IR behavior described in Its forwarding behavior is the regular IR behavior described in
[EVPN], also for Unknown unicast traffic. Any regular non-AR node is [RFC7432], also for Unknown unicast traffic. Any regular non-AR node
fully compatible with the RNVE role described in this document. is fully compatible with the RNVE role described in this document.
5. Selective Assisted-Replication (AR) Solution Description 5. Selective Assisted-Replication (AR) Solution Description
Figure 1 is also used to describe the selective AR solution, however Figure 1 is also used to describe the selective AR solution, however
in this section we consider NVE2 as one more AR-LEAF for EVI-1. The in this section we consider NVE2 as one more AR-LEAF for EVI-1. The
solution is called "selective" because a given AR-REPLICATOR MUST solution is called "selective" because a given AR-REPLICATOR MUST
replicate the BM traffic to only the AR-LEAF that requested the replicate the BM traffic to only the AR-LEAF that requested the
replication (as opposed to all the AR-LEAF nodes) and MAY replicate replication (as opposed to all the AR-LEAF nodes) and MAY replicate
the BM traffic to the RNVEs. The same AR roles defined in section 4 the BM traffic to the RNVEs. The same AR roles defined in section 4
are used here, however the procedures are slightly different. are used here, however the procedures are slightly different.
skipping to change at page 14, line 14 skipping to change at page 14, line 19
5.1. Selective AR-REPLICATOR procedures 5.1. Selective AR-REPLICATOR procedures
In our example in figure 1, PE1 and PE2 are defined as Selective AR- In our example in figure 1, PE1 and PE2 are defined as Selective AR-
REPLICATORs. The following considerations apply to the Selective AR- REPLICATORs. The following considerations apply to the Selective AR-
REPLICATOR role: REPLICATOR role:
a) The Selective AR-REPLICATOR capability SHOULD be an administrative a) The Selective AR-REPLICATOR capability SHOULD be an administrative
choice in any NVE/PE that is part of an AR-enabled EVI, as the AR choice in any NVE/PE that is part of an AR-enabled EVI, as the AR
role itself. This administrative option MAY be implemented as a role itself. This administrative option MAY be implemented as a
system level option as opposed to as a per-EVI option. system level option as opposed to as a per-MAC-VRF option.
b) Each AR-REPLICATOR will build a list of AR-REPLICATOR, AR-LEAF and b) Each AR-REPLICATOR will build a list of AR-REPLICATOR, AR-LEAF and
RNVE nodes (AR-LEAF nodes that sent only a regular-IR route are RNVE nodes (AR-LEAF nodes that sent only a regular-IR route are
accounted as RNVEs by the AR-REPLICATOR). In spite of the accounted as RNVEs by the AR-REPLICATOR). In spite of the
'Selective' administrative option, an AR-REPLICATOR MUST NOT 'Selective' administrative option, an AR-REPLICATOR MUST NOT
behave as a Selective AR-REPLICATOR if at least one of the AR- behave as a Selective AR-REPLICATOR if at least one of the AR-
REPLICATORs has the L flag NOT set. If at least one AR-REPLICATOR REPLICATORs has the L flag NOT set. If at least one AR-REPLICATOR
sends a Replicator-AR route with L=0 (in the EVI context), the sends a Replicator-AR route with L=0 (in the EVI context), the
rest of the AR-REPLICATORs will fall back to non-selective AR rest of the AR-REPLICATORs will fall back to non-selective AR
mode. mode.
b) The Selective AR-REPLICATOR MUST follow the procedures described b) The Selective AR-REPLICATOR MUST follow the procedures described
in section 4.1, except for the following differences: in section 4.1, except for the following differences:
o The Replicator-AR route MUST include L=1 (Leaf Information o The Replicator-AR route MUST include L=1 (Leaf Information
Required) in the Replicator-AR route. This flag is used by the Required) in the Replicator-AR route. This flag is used by the
AR-REPLICATORs to advertise their 'selective' AR-REPLICATOR AR-REPLICATORs to advertise their 'selective' AR-REPLICATOR
capabilities. capabilities. In addition, the AR-REPLICATOR auto-configures
its IP-address-specific import route-target as described in
section 3.
o The AR-REPLICATOR will build a 'selective' AR-LEAF-set with o The AR-REPLICATOR will build a 'selective' AR-LEAF-set with
the list of nodes that requested replication to its own AR-IP. the list of nodes that requested replication to its own AR-IP.
For instance, assuming NVE1 and NVE2 advertise a Leaf-AR route For instance, assuming NVE1 and NVE2 advertise a Leaf-AD route
with PE1's AR-IP (as Tunnel Identifier) and NVE3 advertises a with PE1's IP-address-specific route-target and NVE3
Leaf-AR route with PE2's AR-IP, PE1 MUST only add NVE1/NVE2 in advertises a Leaf-AD route with PE2's IP-address-specific
its selective AR-LEAF-set for EVI-1, and exclude NVE3. route-target, PE1 MUST only add NVE1/NVE2 to its selective AR-
LEAF-set for EVI-1, and exclude NVE3.
o When a node defined and operating as Selective AR-REPLICATOR o When a node defined and operating as Selective AR-REPLICATOR
receives a packet on an overlay tunnel, it will do a tunnel receives a packet on an overlay tunnel, it will do a tunnel
destination IP lookup and if the destination IP is the AR- destination IP lookup and if the destination IP is the AR-
REPLICATOR AR-IP Address, the node MUST replicate the packet REPLICATOR AR-IP Address, the node MUST replicate the packet
to: to:
+ local ACs + local ACs
+ overlay tunnels in the Selective AR-LEAF-set (excluding the + overlay tunnels in the Selective AR-LEAF-set (excluding the
overlay tunnel to the source AR-LEAF). overlay tunnel to the source AR-LEAF).
+ overlay tunnels to the RNVEs if the tunnel source IP is the + overlay tunnels to the RNVEs if the tunnel source IP is the
IR-IP of an AR-LEAF (in any other case, the AR-REPLICATOR IR-IP of an AR-LEAF (in any other case, the AR-REPLICATOR
MUST NOT replicate the BM traffic to remote RNVEs). In other MUST NOT replicate the BM traffic to remote RNVEs). In other
words, the first-hop selective AR-REPLICATOR will replicate words, the first-hop selective AR-REPLICATOR will replicate
to all the RNVEs. to all the RNVEs.
+ overlay tunnels to the remote Selective AR-REPLICATORs if + overlay tunnels to the remote Selective AR-REPLICATORs if
the tunnel source IP is the IR-IP of its own AR-LEAF-set (in the tunnel source IP is an IR-IP of its own AR-LEAF-set (in
any other case, the AR-REPLICATOR MUST NOT replicate the BM any other case, the AR-REPLICATOR MUST NOT replicate the BM
traffic to remote AR-REPLICATORs), where the tunnel traffic to remote AR-REPLICATORs), where the tunnel
destination IP is the AR-IP of the remote Selective AR- destination IP is the AR-IP of the remote Selective AR-
REPLICATOR. The tunnel destination IP AR-IP will be an REPLICATOR. The tunnel destination IP AR-IP will be an
indication for the remote Selective AR-REPLICATOR that the indication for the remote Selective AR-REPLICATOR that the
packet needs further replication to its AR-LEAFs. packet needs further replication to its AR-LEAFs.
5.2. Selective AR-LEAF procedures 5.2. Selective AR-LEAF procedures
A Selective AR-LEAF chooses a single Selective AR-REPLICATOR per EVI A Selective AR-LEAF chooses a single Selective AR-REPLICATOR per EVI
and: and:
o Sends all the EVI BM traffic to that AR-REPLICATOR and o Sends all the EVI BM traffic to that AR-REPLICATOR and
o Expects to receive the BM traffic for a given EVI from the same AR- o Expects to receive the BM traffic for a given EVI from the same AR-
REPLICATOR. REPLICATOR.
In the example of Figure 1, we consider that NVE1/NVE2/NVE3 as In the example of Figure 1, we consider NVE1/NVE2/NVE3 as Selective
Selective AR-LEAFs. NVE1 selects PE1 as its Selective AR-REPLICATOR. AR-LEAFs. NVE1 selects PE1 as its Selective AR-REPLICATOR. If that is
If that is so, NVE1 will send all its BM traffic for EVI-1 to PE1. If so, NVE1 will send all its BM traffic for EVI-1 to PE1. If other AR-
other AR-LEAF/REPLICATORs send BM traffic, NVE1 will receive that LEAF/REPLICATORs send BM traffic, NVE1 will receive that traffic from
traffic from PE1. These are the differences in the behavior of a PE1. These are the differences in the behavior of a Selective AR-LEAF
Selective AR-LEAF compared to a non-selective AR-LEAF: compared to a non-selective AR-LEAF:
a) The AR-LEAF role selective capability SHOULD be an administrative a) The AR-LEAF role selective capability SHOULD be an administrative
choice in any NVE/PE that is part of an AR-enabled EVI. This choice in any NVE/PE that is part of an AR-enabled EVI. This
administrative option to enable AR-LEAF capabilities MAY be administrative option to enable AR-LEAF capabilities MAY be
implemented as a system level option as opposed to as per-EVI implemented as a system level option as opposed to as per-MAC-VRF
option. option.
b) The AR-LEAF MAY advertise a Regular-IR route if there are RNVEs or b) The AR-LEAF MAY advertise a Regular-IR route if there are RNVEs in
non-selective AR-LEAFs in the EVI. The Selective AR-LEAF MUST the EVI. The Selective AR-LEAF MUST advertise a Leaf-AD route
advertise a Leaf-AR route after receiving a Replicator-AR route after receiving a Replicator-AR route with L=1. It is recommended
with L=1. It is recommended that the Selective AR-LEAF waits for a that the Selective AR-LEAF waits for a timer t before sending the
timer t before sending the Leaf-AR route, so that the AR-LEAF Leaf-AD route, so that the AR-LEAF receives all the Replicator-AR
receives all the Replicator-AR routes for the EVI. routes for the EVI.
c) In a service where there is more than one Selective AR-REPLICATORs c) In a service where there is more than one Selective AR-REPLICATORs
the Selective AR-LEAF MUST locally select a single Selective AR- the Selective AR-LEAF MUST locally select a single Selective AR-
REPLICATOR for the EVI. Once selected: REPLICATOR for the EVI. Once selected:
o The Selective AR-LEAF will send a Leaf-AR route including the o The Selective AR-LEAF will send a Leaf-AD route including the
AR-IP of the selected AR-REPLICATOR. Route-key and IP-address-specific route-target of the selected
AR-REPLICATOR.
o The Selective AR-LEAF will send all the BM packets received on o The Selective AR-LEAF will send all the BM packets received on
the attachment circuits (ACs) for a given EVI to that AR- the attachment circuits (ACs) for a given EVI to that AR-
REPLICATOR. REPLICATOR.
o In case of a failure on the selected AR-REPLICATOR, another o In case of a failure on the selected AR-REPLICATOR, another
AR-REPLICATOR will be selected and a new Leaf-AR update will AR-REPLICATOR will be selected and a new Leaf-AD update will
be issued, including the new AR-IP. This new route will update be issued for the new AR-REPLICATOR. This new route will
the selective list in the new Selective AR-REPLICATOR. In case update the selective list in the new Selective AR-REPLICATOR.
of failure on the active Selective AR-REPLICATOR, it is In case of failure on the active Selective AR-REPLICATOR, it
recommended for the Selective AR-LEAF to revert to IR behavior is recommended for the Selective AR-LEAF to revert to IR
for a timer t to speed up the convergence. When the timer behavior for a timer t to speed up the convergence. When the
expires, the Selective AR-LEAF will resume its AR mode with timer expires, the Selective AR-LEAF will resume its AR mode
the new Selective AR-REPLICATOR. with the new Selective AR-REPLICATOR.
All the AR-LEAFs in an EVI are expected to be configured as either
selective or non-selective. A mix of selective and non-selective AR-
LEAFs SHOULD NOT coexist in the same EVI. In case there is a non-
selective AR-LEAF, its BM traffic sent to a selective AR-REPLICATOR
will not be replicated to other AR-LEAFs that are not in its
Selective AR-LEAF-set.
5.3. Forwarding behavior in selective AR EVIs 5.3. Forwarding behavior in selective AR EVIs
This section describes the differences of the selective AR forwarding This section describes the differences of the selective AR forwarding
mode compared to the non-selective mode. Compared to section 4.4, mode compared to the non-selective mode. Compared to section 4.4,
there are no changes for the forwarding behavior in RNVEs or for there are no changes for the forwarding behavior in RNVEs or for
unknown unicast traffic. unknown unicast traffic.
5.3.1. Selective AR-REPLICATOR BM forwarding 5.3.1. Selective AR-REPLICATOR BM forwarding
skipping to change at page 16, line 40 skipping to change at page 17, line 9
1) Flood-list #1 - composed of ACs and overlay tunnels to the 1) Flood-list #1 - composed of ACs and overlay tunnels to the
remote nodes in the EVI, always using the IR-IPs in the tunnel remote nodes in the EVI, always using the IR-IPs in the tunnel
destination IP addresses. Some of those overlay tunnels MAY be destination IP addresses. Some of those overlay tunnels MAY be
flagged as non-BM receivers based on the BM flag received from flagged as non-BM receivers based on the BM flag received from
the remote nodes in the EVI. the remote nodes in the EVI.
2) Flood-list #2 - composed of ACs, a Selective AR-LEAF-set and a 2) Flood-list #2 - composed of ACs, a Selective AR-LEAF-set and a
Selective AR-REPLICATOR-set, where: Selective AR-REPLICATOR-set, where:
o The Selective AR-LEAF-set is composed of the overlay tunnels o The Selective AR-LEAF-set is composed of the overlay tunnels
to the AR-LEAFs that advertise a Leaf-AR route with the AR-IP to the AR-LEAFs that advertise a Leaf-AD route for the local
of the local AR-REPLICATOR. This set is updated with every AR-REPLICATOR. This set is updated with every Leaf-AD route
Leaf-AR route received with a change in the AR-IP included in received/withdrawn from a new AR-LEAF.
the PTA's Tunnel Identifier.
o The Selective AR-REPLICATOR-set is composed of the overlay o The Selective AR-REPLICATOR-set is composed of the overlay
tunnels to all the AR-REPLICATORs that send a Replicator-AR tunnels to all the AR-REPLICATORs that send a Replicator-AR
route with L=1. The AR-IP addresses are used as tunnel route with L=1. The AR-IP addresses are used as tunnel
destination IP. destination IP.
When a Selective AR-REPLICATOR receives a BM packet on an AC, it will When a Selective AR-REPLICATOR receives a BM packet on an AC, it will
forward the BM packet to its flood-list #1, skipping the non-BM forward the BM packet to its flood-list #1, skipping the non-BM
overlay tunnels. overlay tunnels.
skipping to change at page 17, line 26 skipping to change at page 17, line 42
to non-selective mode and flood-list #1 is used. to non-selective mode and flood-list #1 is used.
- If the destination IP matches its AR-IP and the source IP does - If the destination IP matches its AR-IP and the source IP does
not match any IP of its Selective AR-LEAF-set, the AR-REPLICATOR not match any IP of its Selective AR-LEAF-set, the AR-REPLICATOR
will forward the BM packet to flood-list #2 but skipping the AR- will forward the BM packet to flood-list #2 but skipping the AR-
REPLICATOR-set. REPLICATOR-set.
- If the destination IP matches its IR-IP, the AR-REPLICATOR will - If the destination IP matches its IR-IP, the AR-REPLICATOR will
use flood-list #1 but MUST skip all the overlay tunnels from the use flood-list #1 but MUST skip all the overlay tunnels from the
flooding list, i.e. it will only replicate to local ACs. This is flooding list, i.e. it will only replicate to local ACs. This is
the regular-IR behavior described in [EVPN]. the regular-IR behavior described in [RFC7432].
In any case, non-BM overlay tunnels are excluded from flood-lists and In any case, non-BM overlay tunnels are excluded from flood-lists
also source squelching is always done in order to ensure the traffic and, also, source squelching is always done in order to ensure the
is not sent back to the originating source. If the overlay traffic is not sent back to the originating source. If the
encapsulation is MPLS and the EVI label is not the bottom of the encapsulation is MPLSoGRE (or MPLSoUDP) and the EVI label is not the
stack, the AR-REPLICATOR MUST copy the rest of the labels when bottom of the stack, the AR-REPLICATOR MUST copy the rest of the
forwarding them to the egress overlay tunnels. labels when forwarding them to the egress overlay tunnels.
5.3.2. Selective AR-LEAF BM forwarding 5.3.2. Selective AR-LEAF BM forwarding
The Selective AR-LEAF nodes will build two flood-lists: The Selective AR-LEAF nodes will build two flood-lists:
1) Flood-list #1 - composed of ACs and the overlay tunnel to the 1) Flood-list #1 - composed of ACs and the overlay tunnel to the
selected AR-REPLICATOR (using the AR-IP as the tunnel selected AR-REPLICATOR (using the AR-IP as the tunnel
destination IP). destination IP).
2) Flood-list #2 - composed of ACs and overlay tunnels to the 2) Flood-list #2 - composed of ACs and overlay tunnels to the
remote IR-IP Addresses. remote IR-IP Addresses.
When an AR-LEAF receives a BM packet on an AC, it will check if there When an AR-LEAF receives a BM packet on an AC, it will check if there
skipping to change at page 18, line 5 skipping to change at page 18, line 19
2) Flood-list #2 - composed of ACs and overlay tunnels to the 2) Flood-list #2 - composed of ACs and overlay tunnels to the
remote IR-IP Addresses. remote IR-IP Addresses.
When an AR-LEAF receives a BM packet on an AC, it will check if there When an AR-LEAF receives a BM packet on an AC, it will check if there
is any selected AR-REPLICATOR. If there is, flood-list #1 will be is any selected AR-REPLICATOR. If there is, flood-list #1 will be
used. Otherwise, flood-list #2 will. used. Otherwise, flood-list #2 will.
When an AR-LEAF receives a BM packet on an overlay tunnel, will When an AR-LEAF receives a BM packet on an overlay tunnel, will
forward the BM packet to its local ACs and never to an overlay forward the BM packet to its local ACs and never to an overlay
tunnel. This is the regular IR behavior described in [EVPN]. tunnel. This is the regular IR behavior described in [RFC7432].
6. Pruned-Flood-Lists (PFL) 6. Pruned-Flood-Lists (PFL)
In addition to AR, the second optimization supported by this solution In addition to AR, the second optimization supported by this solution
is the ability for the all the EVI nodes to signal Pruned-Flood-Lists is the ability for the all the EVI nodes to signal Pruned-Flood-Lists
(PFL). As described in section 3, an EVPN node can signal a given (PFL). As described in section 3, an EVPN node can signal a given
value for the BM and U PFL flags in the IR Inclusive Multicast value for the BM and U PFL flags in the IR Inclusive Multicast
Routes, where: Routes, where:
+ BM= Broadcast and Multicast (BM) flag. BM=1 means "prune-me" from + BM= Broadcast and Multicast (BM) flag. BM=1 means "prune-me" from
skipping to change at page 18, line 42 skipping to change at page 19, line 9
In order to illustrate the use of the solution described in this In order to illustrate the use of the solution described in this
document, we will assume that EVI-1 in figure 1 is optimized-IR document, we will assume that EVI-1 in figure 1 is optimized-IR
enabled and: enabled and:
o PE1 and PE2 are administratively configured as AR-REPLICATORs, due o PE1 and PE2 are administratively configured as AR-REPLICATORs, due
to their high-performance replication capabilities. PE1 and PE2 to their high-performance replication capabilities. PE1 and PE2
will send a Replicator-AR route with BM/U flags = 00. will send a Replicator-AR route with BM/U flags = 00.
o NVE1 and NVE3 are administratively configured as AR-LEAF nodes, due o NVE1 and NVE3 are administratively configured as AR-LEAF nodes, due
to their low-performance software-based replication capabilities. to their low-performance software-based replication capabilities.
They will advertise a Leaf-AR route. Assuming both NVEs advertise They will advertise a Regular-IR route with type AR-LEAF. Assuming
all the attached VMs in EVPN as soon as they come up and don't have both NVEs advertise all the attached VMs in EVPN as soon as they
any VMs interested in multicast applications, they will be come up and don't have any VMs interested in multicast
configured to signal BM/U flags = 11 for EVI-1. applications, they will be configured to signal BM/U flags = 11 for
EVI-1.
o NVE2 is optimized-IR unaware; therefore it takes on the RNVE role o NVE2 is optimized-IR unaware; therefore it takes on the RNVE role
in EVI-1. in EVI-1.
Based on the above assumptions the following forwarding behavior will Based on the above assumptions the following forwarding behavior will
take place: take place:
(1) Any BM packets sent from VM11 will be sent to VM12 and PE1. PE1 (1) Any BM packets sent from VM11 will be sent to VM12 and PE1. PE1
will forward further the BM packets to TS1, WAN link, PE2 and will forward further the BM packets to TS1, WAN link, PE2 and
NVE2, but not to NVE3. PE2 and NVE2 will replicate the BM packets NVE2, but not to NVE3. PE2 and NVE2 will replicate the BM packets
skipping to change at page 19, line 30 skipping to change at page 19, line 45
unknown traffic cannot be at NVE1. unknown traffic cannot be at NVE1.
(4) Any Unknown unicast packet sent from TS1 will be forwarded by PE1 (4) Any Unknown unicast packet sent from TS1 will be forwarded by PE1
to the WAN link, PE2 and NVE2 but not to NVE1 and NVE3, since the to the WAN link, PE2 and NVE2 but not to NVE1 and NVE3, since the
target of the unknown traffic cannot be at those NVEs. target of the unknown traffic cannot be at those NVEs.
7. AR Procedures for single-IP AR-REPLICATORS 7. AR Procedures for single-IP AR-REPLICATORS
The procedures explained in sections 4 (Non-selective AR) and 5 The procedures explained in sections 4 (Non-selective AR) and 5
(Selective AR) assume that the AR-REPLICATOR can use two local (Selective AR) assume that the AR-REPLICATOR can use two local
routable IP addresses to terminate and initiate NVO tunnels, i.e. IR- routable IP addresses to terminate and originate NVO tunnels, i.e.
IP and AR-IP addresses. This is usually the case for PE-based AR- IR-IP and AR-IP addresses. This is usually the case for PE-based AR-
REPLICATOR nodes. REPLICATOR nodes.
In some cases, the AR-REPLICATOR node does not support more than one In some cases, the AR-REPLICATOR node does not support more than one
IP address to terminate and initiate NVO tunnels, i.e. the IR-IP and IP address to terminate and originate NVO tunnels, i.e. the IR-IP and
AR-IP are the same IP addresses. This may be the case in some AR-IP are the same IP addresses. This may be the case in some
software-based or low-end AR-REPLICATOR nodes. If this is the case, software-based or low-end AR-REPLICATOR nodes. If this is the case,
the procedures in sections 4 and 5 must be modified in the following the procedures in sections 4 and 5 must be modified in the following
way: way:
o The Replicator-AR routes generated by the AR-REPLICATOR use an AR- o The Replicator-AR routes generated by the AR-REPLICATOR use an AR-
IP that will match its IR-IP. In order to differentiate the data IP that will match its IR-IP. In order to differentiate the data
plane packets that need to use IR from the packets that must use AR plane packets that need to use IR from the packets that must use AR
forwarding mode, the Replicator-AR route must advertise a different forwarding mode, the Replicator-AR route must advertise a different
VNI/VSID than the one used by the Regular-IR route. For instance, VNI/VSID than the one used by the Regular-IR route. For instance,
skipping to change at page 20, line 14 skipping to change at page 20, line 29
to the tunnel IP DA lookup described in sections 4 and 5. Note to the tunnel IP DA lookup described in sections 4 and 5. Note
that, when replicating to remote AR-REPLICATOR nodes, the use of that, when replicating to remote AR-REPLICATOR nodes, the use of
the IR-VNI or AR-VNI advertised by the egress node will determine the IR-VNI or AR-VNI advertised by the egress node will determine
the IR or AR forwarding mode at the subsequent AR-REPLICATOR. the IR or AR forwarding mode at the subsequent AR-REPLICATOR.
The rest of the procedures will follow what is described in sections The rest of the procedures will follow what is described in sections
4 and 5. 4 and 5.
8. AR Procedures and EVPN Multi-homing Split-Horizon 8. AR Procedures and EVPN Multi-homing Split-Horizon
When EVPN is used for MPLS over GRE, all the multi-homing procedures
are compatible with sections 4 and 5 of this document.
If VXLAN or NVGRE are used, and if the Split-horizon is based on the If VXLAN or NVGRE are used, and if the Split-horizon is based on the
tunnel IP SA and "Local-Bias" as described in [EVPN-OVERLAY], the tunnel IP SA and "Local-Bias" as described in [EVPN-OVERLAY], the
Split-horizon check will not work if there is an Ethernet-Segment Split-horizon check will not work if there is an Ethernet-Segment
shared between two AR-LEAF nodes, and the AR-REPLICATOR changes the shared between two AR-LEAF nodes, and the AR-REPLICATOR changes the
tunnel IP SA of the packets with its own AR-IP. tunnel IP SA of the packets with its own AR-IP.
In order to be compatible with the IP SA split-horizon check, the AR- In order to be compatible with the IP SA split-horizon check, the AR-
REPLICATOR MAY keep the original received tunnel IP SA when REPLICATOR MAY keep the original received tunnel IP SA when
replicating packets to a remote AR-LEAF or AR-REPLICATOR. This will replicating packets to a remote AR-LEAF or AR-REPLICATOR. This will
allow DF (Designated Forwarder) AR-LEAF nodes to apply Split-horizon allow DF (Designated Forwarder) AR-LEAF nodes to apply Split-horizon
check procedures for BM packets, before sending them to the local check procedures for BM packets, before sending them to the local
Ethernet-Segment. Ethernet-Segment.
When EVPN is used for MPLS over GRE (or UDP), the ESI-label based
split-horizon procedure as in [RFC7432] will not work for multi-homed
Ethernet-Segments defined on AR-LEAF nodes. "Local-Bias" is
recommended in this case, as in the case of VXLAN or NVGRE explained
above. The "Local-Bias" and tunnel IP SA preservation mechanisms
provide the required split-horizon behavior in non-selective or
selective AR.
Note that if the AR-REPLICATOR implementation keeps the received Note that if the AR-REPLICATOR implementation keeps the received
tunnel IP SA, the use of uRPF in the IP fabric based on the tunnel IP tunnel IP SA, the use of uRPF in the IP fabric based on the tunnel IP
SA MUST be disabled. SA MUST be disabled.
9. Out-of-band distribution of Broadcast/Multicast traffic 9. Out-of-band distribution of Broadcast/Multicast traffic
The use of out-of-band mechanisms to distribute BM traffic between The use of out-of-band mechanisms to distribute BM traffic between
AR-REPLICATORS MAY be used. Details will be provided in future AR-REPLICATORS MAY be used.
versions of this document.
10. Benefits of the optimized-IR solution 10. Benefits of the optimized-IR solution
A solution for the optimization of Ingress Replication in EVPN is A solution for the optimization of Ingress Replication in EVPN is
described in this document (optimized-IR). The solution brings the described in this document (optimized-IR). The solution brings the
following benefits: following benefits:
o Optimizes the multicast forwarding in low-performance NVEs, by o Optimizes the multicast forwarding in low-performance NVEs, by
relaying the replication to high-performance NVEs (AR-REPLICATORs) relaying the replication to high-performance NVEs (AR-REPLICATORs)
and while preserving the packet ordering for unicast applications. and while preserving the packet ordering for unicast applications.
skipping to change at page 21, line 31 skipping to change at page 22, line 4
In this document, these words will appear with that interpretation In this document, these words will appear with that interpretation
only when in ALL CAPS. Lower case uses of these words are not to be only when in ALL CAPS. Lower case uses of these words are not to be
interpreted as carrying RFC-2119 significance. interpreted as carrying RFC-2119 significance.
In this document, the characters ">>" preceding an indented line(s) In this document, the characters ">>" preceding an indented line(s)
indicates a compliance requirement statement using the key words indicates a compliance requirement statement using the key words
listed above. This convention aids reviewers in quickly identifying listed above. This convention aids reviewers in quickly identifying
or finding the explicit compliance requirements of this RFC. or finding the explicit compliance requirements of this RFC.
12. Security Considerations 12. Security Considerations
This section will be added in future versions. This section will be added in future versions.
13. IANA Considerations 13. IANA Considerations
A new Tunnel-Type (AR) must be requested and allocated by IANA for IANA has allocated the following Border Gateway Protocol (BGP)
the PTA (PMSI Tunnel Attribute) used in this document. Parameters:
In addition to the new Tunnel-Type, this document requests the 1) Allocation in the P-Multicast Service Interface Tunnel (PMSI
allocation of the PTA flags as in section 3. A registry is created as Tunnel) Tunnel Types registry:
per [PTA-FLAGS].
Value Meaning Reference
0x0A Assisted-Replication Tunnel [This document]
2) Allocations in the P-Multicast Service Interface (PMSI) Tunnel
Attribute Flags registry:
Value Name Reference
3-4 Assisted-Replication Type (T) [This document]
5 Broadcast and Multicast (BM) [This document]
6 Unknown (U) [This document]
14. Terminology 14. Terminology
Regular-IR: Refers to Regular Ingress Replication, where the source Regular-IR: Refers to Regular Ingress Replication, where the source
NVE/PE sends a copy to each remote NVE/PE part of the EVI. NVE/PE sends a copy to each remote NVE/PE part of the EVI.
AR-IP: IP address owned by the AR-REPLICATOR and used to AR-IP: IP address owned by the AR-REPLICATOR and used to
differentiate the ingress traffic that must follow the AR differentiate the ingress traffic that must follow the AR
procedures. procedures.
IR-IP: IP address used for Ingress Replication as in [EVPN]. IR-IP: IP address used for Ingress Replication as in [RFC7432].
AR-VNI: VNI advertised by the AR-REPLICATOR along with the AR-VNI: VNI advertised by the AR-REPLICATOR along with the
Replicator-AR route. It is used to identify the ingress Replicator-AR route. It is used to identify the ingress
packets that must follow AR procedures ONLY in the Single-IP packets that must follow AR procedures ONLY in the Single-IP
AR-REPLICATOR case. AR-REPLICATOR case.
IR-VNI: VNI advertised along with the RT-3 for IR. IR-VNI: VNI advertised along with the RT-3 for IR.
AR forwarding mode: for an AR-LEF, it means sending an AC BM packet AR forwarding mode: for an AR-LEAF, it means sending an AC BM packet
to a single AR-REPLICATOR with tunnel destination IP AR-IP. to a single AR-REPLICATOR with tunnel destination IP AR-IP.
For an AR-REPLICATOR, it means sending a BM packet to a For an AR-REPLICATOR, it means sending a BM packet to a
selective number or all the overlay tunnels when the packet selective number or all the overlay tunnels when the packet
was previously received from an overlay tunnel. was previously received from an overlay tunnel.
IR forwarding mode: it refers to the Ingress Replication behavior IR forwarding mode: it refers to the Ingress Replication behavior
explained in [EVPN]. It means sending an AC BM packet copy to explained in [RFC7432]. It means sending an AC BM packet copy
each remote PE/NVE in the EVI and sending an overlay BM packet to each remote PE/NVE in the EVI and sending an overlay BM
only to the ACs and not other overlay tunnels. packet only to the ACs and not other overlay tunnels.
PTA: PMSI Tunnel Attribute PTA: PMSI Tunnel Attribute
RT-3: EVPN Route Type 3, Inclusive Multicast Ethernet Tag route RT-3: EVPN Route Type 3, Inclusive Multicast Ethernet Tag route
RT-11: EVPN Route Type 11, Leaf Auto-Discovery (AD) route
15. References 15. References
15.1 Normative References 15.1 Normative References
[RFC6514]Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514]Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", Encodings and Procedures for Multicast in MPLS/BGP IP VPNs",
RFC 6514, DOI 10.17487/RFC6514, February 2012, <http://www.rfc- RFC 6514, DOI 10.17487/RFC6514, February 2012, <http://www.rfc-
editor.org/info/rfc6514>. editor.org/info/rfc6514>.
[RFC7432]Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432]Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet
VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc- VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc-
editor.org/info/rfc7432>. editor.org/info/rfc7432>.
[RFC7902]Rosen, E. and Morin, T., "Registry and Extensions for P-
Multicast Service Interface Tunnel Attribute Flags", June 2016,
<http://www.rfc-editor.org/info/rfc7902>.
[EVPN-BUM] Zhang et al., "Updates on EVPN BUM Procedures", draft-
ietf-bess-evpn-bum-procedure-updates-01.txt, work in progress,
December 2016.
15.2 Informative References 15.2 Informative References
[EVPN-OVERLAY] Sajassi-Drake et al., "A Network Virtualization [EVPN-OVERLAY] Sajassi-Drake et al., "A Network Virtualization
Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-02.txt, Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07.txt,
work in progress, October 2015 work in progress, December 2016.
[PTA-FLAGS] Rosen, E., "IANA Registry for P-Multicast Service
Interface Tunnel Attribute Flags", draft-ietf-bess-pta-flags-01.txt,
work in progress, August 2015
16. Acknowledgments 16. Acknowledgments
The authors would like to thank Neil Hart, David Motz, Kiran Nagaraj, The authors would like to thank Neil Hart, David Motz, Kiran Nagaraj,
Dai Truong, Thomas Morin and Jeffrey Zhang for their valuable Dai Truong, Thomas Morin, Jeffrey Zhang and Shankar Murthy for their
feedback and contributions. valuable feedback and contributions.
17. Authors' Addresses 17. 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
Senthil Sathappan Senthil Sathappan
Nokia Nokia
Email: senthil.sathappan@nokia.com Email: senthil.sathappan@nokia.com
 End of changes. 71 change blocks. 
148 lines changed or deleted 190 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/