draft-ietf-l2vpn-evpn-05.txt   draft-ietf-l2vpn-evpn-06.txt 
Network Working Group A. Sajassi Network Working Group A. Sajassi, Ed.
INTERNET-DRAFT Cisco INTERNET-DRAFT Cisco
Category: Standards Track Category: Standards Track
R. Aggarwal R. Aggarwal
N. Bitar Arktan J. Drake Arktan
Verizon
W. Henderickx
J. Drake Alcatel-Lucent
Juniper Networks Juniper Networks
N. Bitar
W. Henderickx Verizon
Alcatel-Lucent
Aldrin Isaac Aldrin Isaac
Bloomberg Bloomberg
J. Uttaro J. Uttaro
AT&T AT&T
Expires: August 12, 2014 February 12, 2014 Expires: September 12, 2014 March 12, 2014
BGP MPLS Based Ethernet VPN BGP MPLS Based Ethernet VPN
draft-ietf-l2vpn-evpn-05 draft-ietf-l2vpn-evpn-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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 other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 3, line 9 skipping to change at page 3, line 9
8.2.1.1. Ethernet A-D Route Targets . . . . . . . . . . . . 18 8.2.1.1. Ethernet A-D Route Targets . . . . . . . . . . . . 18
8.3 Split Horizon . . . . . . . . . . . . . . . . . . . . . . . 19 8.3 Split Horizon . . . . . . . . . . . . . . . . . . . . . . . 19
8.3.1 ESI Label Assignment . . . . . . . . . . . . . . . . . . 19 8.3.1 ESI Label Assignment . . . . . . . . . . . . . . . . . . 19
8.3.1.1 Ingress Replication . . . . . . . . . . . . . . . . 19 8.3.1.1 Ingress Replication . . . . . . . . . . . . . . . . 19
8.3.1.2. P2MP MPLS LSPs . . . . . . . . . . . . . . . . . . 20 8.3.1.2. P2MP MPLS LSPs . . . . . . . . . . . . . . . . . . 20
8.4 Aliasing and Backup-Path . . . . . . . . . . . . . . . . . . 21 8.4 Aliasing and Backup-Path . . . . . . . . . . . . . . . . . . 21
8.4.1 Constructing the Ethernet A-D per EVPN Instance (EVI) 8.4.1 Constructing the Ethernet A-D per EVPN Instance (EVI)
Route . . . . . . . . . . . . . . . . . . . . . . . . . 22 Route . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4.1.1 Ethernet A-D Route Targets . . . . . . . . . . . . . 23 8.4.1.1 Ethernet A-D Route Targets . . . . . . . . . . . . . 23
8.5 Designated Forwarder Election . . . . . . . . . . . . . . . 23 8.5 Designated Forwarder Election . . . . . . . . . . . . . . . 24
8.6. Interoperability with Single-homing PEs . . . . . . . . . . 25 8.6. Interoperability with Single-homing PEs . . . . . . . . . . 26
9. Determining Reachability to Unicast MAC Addresses . . . . . . . 26 9. Determining Reachability to Unicast MAC Addresses . . . . . . . 26
9.1. Local Learning . . . . . . . . . . . . . . . . . . . . . . 26 9.1. Local Learning . . . . . . . . . . . . . . . . . . . . . . 27
9.2. Remote learning . . . . . . . . . . . . . . . . . . . . . . 27 9.2. Remote learning . . . . . . . . . . . . . . . . . . . . . . 27
9.2.1. Constructing the BGP EVPN MAC/IP Address 9.2.1. Constructing the BGP EVPN MAC/IP Address
Advertisement . . . . . . . . . . . . . . . . . . . . . 27 Advertisement . . . . . . . . . . . . . . . . . . . . . 27
9.2.2 Route Resolution . . . . . . . . . . . . . . . . . . . . 29 9.2.2 Route Resolution . . . . . . . . . . . . . . . . . . . . 29
10. ARP and ND . . . . . . . . . . . . . . . . . . . . . . . . . . 30 10. ARP and ND . . . . . . . . . . . . . . . . . . . . . . . . . . 30
10.1 Default Gateway . . . . . . . . . . . . . . . . . . . . . . 30 10.1 Default Gateway . . . . . . . . . . . . . . . . . . . . . . 31
11. Handling of Multi-Destination Traffic . . . . . . . . . . . . 32 11. Handling of Multi-Destination Traffic . . . . . . . . . . . . 32
11.1. Construction of the Inclusive Multicast Ethernet Tag 11.1. Construction of the Inclusive Multicast Ethernet Tag
Route . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Route . . . . . . . . . . . . . . . . . . . . . . . . . . 32
11.2. P-Tunnel Identification . . . . . . . . . . . . . . . . . 32 11.2. P-Tunnel Identification . . . . . . . . . . . . . . . . . 33
12. Processing of Unknown Unicast Packets . . . . . . . . . . . . 33 12. Processing of Unknown Unicast Packets . . . . . . . . . . . . 34
12.1. Ingress Replication . . . . . . . . . . . . . . . . . . . 34 12.1. Ingress Replication . . . . . . . . . . . . . . . . . . . 34
12.2. P2MP MPLS LSPs . . . . . . . . . . . . . . . . . . . . . . 34 12.2. P2MP MPLS LSPs . . . . . . . . . . . . . . . . . . . . . . 35
13. Forwarding Unicast Packets . . . . . . . . . . . . . . . . . . 35 13. Forwarding Unicast Packets . . . . . . . . . . . . . . . . . . 35
13.1. Forwarding packets received from a CE . . . . . . . . . . 35 13.1. Forwarding packets received from a CE . . . . . . . . . . 35
13.2. Forwarding packets received from a remote PE . . . . . . . 36 13.2. Forwarding packets received from a remote PE . . . . . . . 36
13.2.1. Unknown Unicast Forwarding . . . . . . . . . . . . . . 36 13.2.1. Unknown Unicast Forwarding . . . . . . . . . . . . . . 36
13.2.2. Known Unicast Forwarding . . . . . . . . . . . . . . . 36 13.2.2. Known Unicast Forwarding . . . . . . . . . . . . . . . 37
14. Load Balancing of Unicast Frames . . . . . . . . . . . . . . . 37 14. Load Balancing of Unicast Frames . . . . . . . . . . . . . . . 37
14.1. Load balancing of traffic from an PE to remote CEs . . . . 37 14.1. Load balancing of traffic from an PE to remote CEs . . . . 37
14.1.1 Single-Active Redundancy Mode . . . . . . . . . . . . . 37 14.1.1 Single-Active Redundancy Mode . . . . . . . . . . . . . 37
14.1.2 All-Active Redundancy Mode . . . . . . . . . . . . . . 38 14.1.2 All-Active Redundancy Mode . . . . . . . . . . . . . . 38
14.2. Load balancing of traffic between an PE and a local CE . . 39 14.2. Load balancing of traffic between an PE and a local CE . . 40
14.2.1. Data plane learning . . . . . . . . . . . . . . . . . 40 14.2.1. Data plane learning . . . . . . . . . . . . . . . . . 40
14.2.2. Control plane learning . . . . . . . . . . . . . . . . 40 14.2.2. Control plane learning . . . . . . . . . . . . . . . . 40
15. MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . . 40 15. MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . . 40
15.1. MAC Duplication Issue . . . . . . . . . . . . . . . . . . 42 15.1. MAC Duplication Issue . . . . . . . . . . . . . . . . . . 42
15.2. Sticky MAC addresses . . . . . . . . . . . . . . . . . . . 42 15.2. Sticky MAC addresses . . . . . . . . . . . . . . . . . . . 43
16. Multicast & Broadcast . . . . . . . . . . . . . . . . . . . . 42 16. Multicast & Broadcast . . . . . . . . . . . . . . . . . . . . 43
16.1. Ingress Replication . . . . . . . . . . . . . . . . . . . 43 16.1. Ingress Replication . . . . . . . . . . . . . . . . . . . 43
16.2. P2MP LSPs . . . . . . . . . . . . . . . . . . . . . . . . 43 16.2. P2MP LSPs . . . . . . . . . . . . . . . . . . . . . . . . 43
16.2.1. Inclusive Trees . . . . . . . . . . . . . . . . . . . 43 16.2.1. Inclusive Trees . . . . . . . . . . . . . . . . . . . 43
17. Convergence . . . . . . . . . . . . . . . . . . . . . . . . . 44 17. Convergence . . . . . . . . . . . . . . . . . . . . . . . . . 44
17.1. Transit Link and Node Failures between PEs . . . . . . . . 44 17.1. Transit Link and Node Failures between PEs . . . . . . . . 44
17.2. PE Failures . . . . . . . . . . . . . . . . . . . . . . . 44 17.2. PE Failures . . . . . . . . . . . . . . . . . . . . . . . 44
17.3. PE to CE Network Failures . . . . . . . . . . . . . . . . 44 17.3. PE to CE Network Failures . . . . . . . . . . . . . . . . 44
18. Frame Ordering . . . . . . . . . . . . . . . . . . . . . . . . 45 18. Frame Ordering . . . . . . . . . . . . . . . . . . . . . . . . 45
19. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45 19. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 46
20. Security Considerations . . . . . . . . . . . . . . . . . . . 46 20. Security Considerations . . . . . . . . . . . . . . . . . . . 46
21. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 47 21. Co-authors . . . . . . . . . . . . . . . . . . . . . . . . . . 47
22. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 22. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
23. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47 23. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
23.1 Normative References . . . . . . . . . . . . . . . . . . . 48 23.1 Normative References . . . . . . . . . . . . . . . . . . . 48
23.2 Informative References . . . . . . . . . . . . . . . . . . 48 23.2 Informative References . . . . . . . . . . . . . . . . . . 48
24. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 48 24. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 49
1. Specification of requirements 1. Specification of requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Terminology 2. Terminology
Bridge Domain: Bridge Domain:
skipping to change at page 10, line 31 skipping to change at page 10, line 31
responsible for performing VLAN ID translation to/from locally responsible for performing VLAN ID translation to/from locally
attached CE devices. attached CE devices.
If a VLAN is represented by a single VID across all PE devices If a VLAN is represented by a single VID across all PE devices
participating in that VLAN for that EVPN instance, then there is no participating in that VLAN for that EVPN instance, then there is no
need for VID translation at the PEs. Furthermore, some deployment need for VID translation at the PEs. Furthermore, some deployment
scenarios guarantee uniqueness of VIDs across all EVPN instances; scenarios guarantee uniqueness of VIDs across all EVPN instances;
all points of attachment for a given EVPN instance use the same VID all points of attachment for a given EVPN instance use the same VID
and no other EVPN instances use that VID. This allows the RT(s) for and no other EVPN instances use that VID. This allows the RT(s) for
each EVPN instance to be derived automatically from the corresponding each EVPN instance to be derived automatically from the corresponding
VID, as described in section 9.4.1.1.1 "Auto-Derivation from the VID, as described in section 8.4.1.1.1 "Auto-Derivation from the
Ethernet Tag ID". Ethernet Tag ID".
The following subsections discuss the relationship between broadcast The following subsections discuss the relationship between broadcast
domains (e.g., VLANs), Ethernet Tags (e.g., VIDs), and MAC-VRFs as domains (e.g., VLANs), Ethernet Tags (e.g., VIDs), and MAC-VRFs as
well as the setting of the Ethernet Tag Identifier, in the various well as the setting of the Ethernet Tag Identifier, in the various
EVPN BGP routes (defined in section 8), for the different types of EVPN BGP routes (defined in section 8), for the different types of
service interfaces described in [EVPN-REQ]. service interfaces described in [EVPN-REQ].
The following Ethernet Tag value is reserved: The following Ethernet Tag value is reserved:
skipping to change at page 11, line 31 skipping to change at page 11, line 31
translation is allowed for this service interface type. The MPLS translation is allowed for this service interface type. The MPLS
encapsulated frames MUST remain tagged with the originating VID. Tag encapsulated frames MUST remain tagged with the originating VID. Tag
translation is NOT permitted. The Ethernet Tag Identifier in all EVPN translation is NOT permitted. The Ethernet Tag Identifier in all EVPN
routes MUST be set to 0. routes MUST be set to 0.
6.2.1 Port Based Service Interface 6.2.1 Port Based Service Interface
This service interface is a special case of the VLAN Bundle service This service interface is a special case of the VLAN Bundle service
interface, where all of the VLANs on the port are part of the same interface, where all of the VLANs on the port are part of the same
service and map to the same bundle. The procedures are identical to service and map to the same bundle. The procedures are identical to
those described in section 7.2. those described in section 6.2.
6.3 VLAN Aware Bundle Service Interface 6.3 VLAN Aware Bundle Service Interface
With this service interface, an EVPN instance consists of several With this service interface, an EVPN instance consists of several
broadcast domains (e.g., several VLANs) with each VLAN having its own broadcast domains (e.g., several VLANs) with each VLAN having its own
bridge domain - e.g., multiple bridge domains (one per VLAN) is bridge domain - e.g., multiple bridge domains (one per VLAN) is
maintained by a single MAC-VRF corresponding to the EVPN instance. In maintained by a single MAC-VRF corresponding to the EVPN instance. In
the case where a single VLAN is represented by different VIDs on the case where a single VLAN is represented by different VIDs on
different CEs and thus tag (VID) translation is required, a different CEs and thus tag (VID) translation is required, a
normalized Ethernet Tag (VID) MUST be carried in the MPLS normalized Ethernet Tag (VID) MUST be carried in the MPLS
skipping to change at page 12, line 6 skipping to change at page 12, line 6
both the imposition as well as the disposition PEs (translating to both the imposition as well as the disposition PEs (translating to
normalized tag on imposition PE and translating to local tag on normalized tag on imposition PE and translating to local tag on
disposition PE). The Ethernet Tag Identifier in all EVPN routes MUST disposition PE). The Ethernet Tag Identifier in all EVPN routes MUST
be set to the normalized Ethernet Tag assigned by the EVPN provider. be set to the normalized Ethernet Tag assigned by the EVPN provider.
6.3.1 Port Based VLAN Aware Service Interface 6.3.1 Port Based VLAN Aware Service Interface
This service interface is a special case of the VLAN Aware Bundle This service interface is a special case of the VLAN Aware Bundle
service interface, where all of the VLANs on the port are part of the service interface, where all of the VLANs on the port are part of the
same service and map to the same bundle. The procedures are identical same service and map to the same bundle. The procedures are identical
to those described in section 7.3. to those described in section 6.3.
7. BGP EVPN NLRI 7. BGP EVPN NLRI
This document defines a new BGP NLRI, called the EVPN NLRI. This document defines a new BGP NLRI, called the EVPN NLRI.
Following is the format of the EVPN NLRI: Following is the format of the EVPN NLRI:
+-----------------------------------+ +-----------------------------------+
| Route Type (1 octet) | | Route Type (1 octet) |
+-----------------------------------+ +-----------------------------------+
skipping to change at page 13, line 21 skipping to change at page 13, line 21
| Ethernet Tag ID (4 octets) | | Ethernet Tag ID (4 octets) |
+---------------------------------------+ +---------------------------------------+
| MPLS Label (3 octets) | | MPLS Label (3 octets) |
+---------------------------------------+ +---------------------------------------+
For the purpose of BGP route key processing, only the Ethernet For the purpose of BGP route key processing, only the Ethernet
Segment ID and the Ethernet Tag ID are considered to be part of the Segment ID and the Ethernet Tag ID are considered to be part of the
prefix in the NLRI. The MPLS Label field is to be treated as a prefix in the NLRI. The MPLS Label field is to be treated as a
route attribute as opposed to being part of the route. route attribute as opposed to being part of the route.
For procedures and usage of this route please see section 9.2 "Fast For procedures and usage of this route please see section 8.2 "Fast
Convergence" and section 9.4 "Aliasing". Convergence" and section 8.4 "Aliasing".
7.2. MAC/IP Advertisement Route 7.2. MAC/IP Advertisement Route
A MAC advertisement route type specific EVPN NLRI consists of the A MAC advertisement route type specific EVPN NLRI consists of the
following: following:
+---------------------------------------+ +---------------------------------------+
| RD (8 octets) | | RD (8 octets) |
+---------------------------------------+ +---------------------------------------+
|Ethernet Segment Identifier (10 octets)| |Ethernet Segment Identifier (10 octets)|
skipping to change at page 14, line 8 skipping to change at page 14, line 8
+---------------------------------------+ +---------------------------------------+
| MPLS Label2 (0 or 3 octets) | | MPLS Label2 (0 or 3 octets) |
+---------------------------------------+ +---------------------------------------+
For the purpose of BGP route key processing, only the Ethernet Tag For the purpose of BGP route key processing, only the Ethernet Tag
ID, MAC Address Length, MAC Address, IP Address Length, and IP ID, MAC Address Length, MAC Address, IP Address Length, and IP
Address Address fields are considered to be part of the prefix in the Address Address fields are considered to be part of the prefix in the
NLRI. The Ethernet Segment Identifier and MPLS Label fields are to be NLRI. The Ethernet Segment Identifier and MPLS Label fields are to be
treated as route attributes as opposed to being part of the "route". treated as route attributes as opposed to being part of the "route".
For procedures and usage of this route please see section 10 For procedures and usage of this route please see section 9
"Determining Reachability to Unicast MAC Addresses" and section 15 "Determining Reachability to Unicast MAC Addresses" and section 14
"Load Balancing of Unicast Packets". "Load Balancing of Unicast Packets".
7.3. Inclusive Multicast Ethernet Tag Route 7.3. Inclusive Multicast Ethernet Tag Route
An Inclusive Multicast Ethernet Tag route type specific EVPN NLRI An Inclusive Multicast Ethernet Tag route type specific EVPN NLRI
consists of the following: consists of the following:
+---------------------------------------+ +---------------------------------------+
| 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) |
+---------------------------------------+ +---------------------------------------+
For procedures and usage of this route please see section 12 For procedures and usage of this route please see section 11
"Handling of Multi-Destination Traffic", section 13 "Processing of "Handling of Multi-Destination Traffic", section 13 "Processing of
Unknown Unicast Traffic" and section 17 "Multicast". Unknown Unicast Traffic" and section 16 "Multicast".
7.4 Ethernet Segment Route 7.4 Ethernet Segment Route
The Ethernet Segment Route is encoded in the EVPN NLRI using the The Ethernet Segment Route is encoded in the EVPN NLRI using the
Route Type value of 4. The Route Type Specific field of the NLRI is Route Type value of 4. The Route Type Specific field of the NLRI is
formatted as follows: formatted as follows:
+---------------------------------------+ +---------------------------------------+
| RD (8 octets) | | RD (8 octets) |
+---------------------------------------+ +---------------------------------------+
|Ethernet Segment Identifier (10 octets)| |Ethernet Segment Identifier (10 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) |
+---------------------------------------+ +---------------------------------------+
For procedures and usage of this route please see section 9.5 For procedures and usage of this route please see section 8.5
"Designated Forwarder Election". The IP address length is in bits. "Designated Forwarder Election". The IP address length is in bits.
7.5 ESI Label Extended Community 7.5 ESI Label Extended Community
This extended community is a new transitive extended community with This extended community is a new transitive extended community with
the Type field is 0x06, and the Sub-Type of 0x01. It may be the Type field is 0x06, and the Sub-Type of 0x01. It may be
advertised along with Ethernet Auto-Discovery routes and it enables advertised along with Ethernet Auto-Discovery routes and it enables
split-horizon procedures for multi-homed sites as described in split-horizon procedures for multi-homed sites as described in
section 9.3 "Split Horizon". section 8.3 "Split Horizon".
Each ESI Label Extended Community is encoded as a 8-octet value as Each ESI Label Extended Community is encoded as a 8-octet value as
follows: follows:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=0x06 | Sub-Type=0x01 | Flags (One Octet) |Reserved=0 | | Type=0x06 | Sub-Type=0x01 | Flags (One Octet) |Reserved=0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved = 0| ESI Label | | Reserved = 0| ESI Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 11 skipping to change at page 16, line 11
This document expands the definition of the Route Target extended This document expands the definition of the Route Target extended
community to allow the value of high order octet (Type field) to be community to allow the value of high order octet (Type field) to be
0x06 (in addition to the values specified in rfc4360). The value of 0x06 (in addition to the values specified in rfc4360). The value of
low order octet (Sub-Type field) of 0x02 indicates that this extended low order octet (Sub-Type field) of 0x02 indicates that this extended
community is of type "Route Target". The new value for Type field of community is of type "Route Target". The new value for Type field of
0x06 indicates that the structure of this RT is a six bytes value 0x06 indicates that the structure of this RT is a six bytes value
(e.g., a MAC address). A BGP speaker that implements RT-Constrain (e.g., a MAC address). A BGP speaker that implements RT-Constrain
(RFC4684) MUST apply the RT-Constrain procedures to the ES-import RT (RFC4684) MUST apply the RT-Constrain procedures to the ES-import RT
as-well. as-well.
For procedures and usage of this attribute, please see section 9.1 For procedures and usage of this attribute, please see section 8.1
"Redundancy Group Discovery". "MH Ethernet Segment Auto Discovery".
7.7 MAC Mobility Extended Community 7.7 MAC Mobility Extended Community
This extended community is a new transitive extended community with This extended community is a new transitive extended community with
the Type field of 0x06 and the Sub-Type of 0x00. It may be advertised the Type field of 0x06 and the Sub-Type of 0x00. It may be advertised
along with MAC Advertisement routes. The procedures for using this along with MAC Advertisement routes. The procedures for using this
Extended Community are described in section 16 "MAC Mobility". Extended Community are described in section 16 "MAC Mobility".
The MAC Mobility Extended Community is encoded as a 8-octet value as The MAC Mobility Extended Community is encoded as a 8-octet value as
follows: follows:
skipping to change at page 17, line 18 skipping to change at page 17, line 18
each other with minimal to no configuration through the exchange of each other with minimal to no configuration through the exchange of
the Ethernet Segment route. the Ethernet Segment route.
8.1.1 Constructing the Ethernet Segment Route 8.1.1 Constructing the Ethernet Segment Route
The Route-Distinguisher (RD) MUST be a Type 1 RD [RFC4364]. The value The Route-Distinguisher (RD) MUST be a Type 1 RD [RFC4364]. The value
field comprises an IP address of the MES (typically, the loopback field comprises an IP address of the MES (typically, the loopback
address) followed by 0's. address) followed by 0's.
The Ethernet Segment Identifier MUST be set to the ten octet ESI The Ethernet Segment Identifier MUST be set to the ten octet ESI
identifier described in section 6. identifier described in section 5.
The BGP advertisement that advertises the Ethernet Segment route MUST The BGP advertisement that advertises the Ethernet Segment route MUST
also carry an ES-Import extended community attribute, as defined in also carry an ES-Import route target, as defined in section 7.6.
section 8.6.
The Ethernet Segment Route filtering MUST be done such that the The Ethernet Segment Route filtering MUST be done such that the
Ethernet Segment Route is imported only by the PEs that are multi- Ethernet Segment Route is imported only by the PEs that are multi-
homed to the same Ethernet Segment. To that end, each PE that is homed to the same Ethernet Segment. To that end, each PE that is
connected to a particular Ethernet segment constructs an import connected to a particular Ethernet segment constructs an import
filtering rule to import a route that carries the ES-Import extended filtering rule to import a route that carries the ES-Import extended
community, constructed from the ESI. community, constructed from the ESI.
8.2 Fast Convergence 8.2 Fast Convergence
skipping to change at page 17, line 45 skipping to change at page 17, line 44
mechanism, the network convergence time is a function of the number mechanism, the network convergence time is a function of the number
of MAC Advertisement routes that must be withdrawn by the PE of MAC Advertisement routes that must be withdrawn by the PE
encountering a failure. For highly scaled environments, this scheme encountering a failure. For highly scaled environments, this scheme
yields slow convergence. yields slow convergence.
To alleviate this, EVPN defines a mechanism to efficiently and To alleviate this, EVPN defines a mechanism to efficiently and
quickly signal, to remote PE nodes, the need to update their quickly signal, to remote PE nodes, the need to update their
forwarding tables upon the occurrence of a failure in connectivity to forwarding tables upon the occurrence of a failure in connectivity to
an Ethernet segment. This is done by having each PE advertise a set an Ethernet segment. This is done by having each PE advertise a set
of Ethernet A-D per Ethernet segment (per ES) routes for each locally of Ethernet A-D per Ethernet segment (per ES) routes for each locally
attached Ethernet segment (refer to section 9.2.1 below for details attached Ethernet segment (refer to section 8.2.1 below for details
on how this route is constructed). Upon a failure in connectivity to on how this route is constructed). Upon a failure in connectivity to
the attached segment, the PE withdraws the corresponding Ethernet A-D the attached segment, the PE withdraws the corresponding Ethernet A-D
route. This triggers all PEs that receive the withdrawal to update route. This triggers all PEs that receive the withdrawal to update
their next-hop adjacencies for all MAC addresses associated with the their next-hop adjacencies for all MAC addresses associated with the
Ethernet segment in question. If no other PE had advertised an Ethernet segment in question. If no other PE had advertised an
Ethernet A-D route for the same segment, then the PE that received Ethernet A-D route for the same segment, then the PE that received
the withdrawal simply invalidates the MAC entries for that segment. the withdrawal simply invalidates the MAC entries for that segment.
Otherwise, the PE updates the next-hop adjacencies to point to the Otherwise, the PE updates the next-hop adjacencies to point to the
backup PE(s). backup PE(s).
8.2.1 Constructing the Ethernet A-D per Ethernet Segment (ES) Route 8.2.1 Constructing the Ethernet A-D per Ethernet Segment (ES) Route
This section describes the procedures used to construct the Ethernet This section describes the procedures used to construct the Ethernet
A-D per ES route, which is used for fast convergence (as discussed A-D per ES route, which is used for fast convergence (as discussed
above) and for advertising the ESI label used for split-horizon above) and for advertising the ESI label used for split-horizon
filtering (as discussed in section 9.3). Support of this route is filtering (as discussed in section 8.3). Support of this route is
MANDATORY. MANDATORY.
The Route-Distinguisher (RD) MUST be a Type 1 RD [RFC4364]. The value The Route-Distinguisher (RD) MUST be a Type 1 RD [RFC4364]. The value
field comprises an IP address of the PE (typically, the loopback field comprises an IP address of the PE (typically, the loopback
address) followed by a number unique to the PE. address) followed by a number unique to the PE.
The Ethernet Segment Identifier MUST be a ten octet entity as The Ethernet Segment Identifier MUST be a ten octet entity as
described in section "Ethernet Segment". This document does not described in section "Ethernet Segment". This document does not
specify the use of the Ethernet A-D route when the Segment Identifier specify the use of the Ethernet A-D route when the Segment Identifier
is set to 0. is set to 0.
skipping to change at page 18, line 41 skipping to change at page 18, line 39
in the flags of the ESI Label Extended Community MUST be set to 0 and in the flags of the ESI Label Extended Community MUST be set to 0 and
the MPLS label in that extended community MUST be set to a valid MPLS the MPLS label in that extended community MUST be set to a valid MPLS
label value. The MPLS label in this Extended Community is referred to label value. The MPLS label in this Extended Community is referred to
as the ESI label and MUST have the same value in each Ethernet A-D as the ESI label and MUST have the same value in each Ethernet A-D
per ES route advertised for the ES. This label MUST be a downstream per ES route advertised for the ES. This label MUST be a downstream
assigned MPLS label if the advertising PE is using ingress assigned MPLS label if the advertising PE is using ingress
replication for receiving multicast, broadcast or unknown unicast replication for receiving multicast, broadcast or unknown unicast
traffic from other PEs. If the advertising PE is using P2MP MPLS LSPs traffic from other PEs. If the advertising PE is using P2MP MPLS LSPs
for sending multicast, broadcast or unknown unicast traffic, then for sending multicast, broadcast or unknown unicast traffic, then
this label MUST be an upstream assigned MPLS label. The usage of this this label MUST be an upstream assigned MPLS label. The usage of this
label is described in section 9.3. label is described in section 8.3.
If Single-Active redundancy mode is desired, then the "Single-Active" If Single-Active redundancy mode is desired, then the "Single-Active"
bit in the flags of the ESI Label Extended Community MUST be set to 1 bit in the flags of the ESI Label Extended Community MUST be set to 1
and the ESI label MUST be set to zero. and the ESI label MUST be set to zero.
8.2.1.1. Ethernet A-D Route Targets 8.2.1.1. Ethernet A-D Route Targets
Each Ethernet A-D per ES route MUST carry one or more Route Target Each Ethernet A-D per ES route MUST carry one or more Route Target
(RT) attributes. The set of Ethernet A-D routes per ES MUST carry the (RT) attributes. The set of Ethernet A-D routes per ES MUST carry the
entire set of RTs for all the EVPN instances to which the Ethernet entire set of RTs for all the EVPN instances to which the Ethernet
skipping to change at page 19, line 17 skipping to change at page 19, line 17
Consider a CE that is multi-homed to two or more PEs on an Ethernet Consider a CE that is multi-homed to two or more PEs on an Ethernet
segment ES1 operating in All-Active redundancy mode. If the CE sends segment ES1 operating in All-Active redundancy mode. If the CE sends
a broadcast, unknown unicast, or multicast (BUM) packet to one of the a broadcast, unknown unicast, or multicast (BUM) packet to one of the
non-DF (Designated Forwarder) PEs, say PE1, then PE1 will forward non-DF (Designated Forwarder) PEs, say PE1, then PE1 will forward
that packet to all or subset of the other PEs in that EVPN instance that packet to all or subset of the other PEs in that EVPN instance
including the DF PE for that Ethernet segment. In this case the DF PE including the DF PE for that Ethernet segment. In this case the DF PE
that the CE is multi-homed to MUST drop the packet and not forward that the CE is multi-homed to MUST drop the packet and not forward
back to the CE. This filtering is referred to as "split horizon" back to the CE. This filtering is referred to as "split horizon"
filtering in this document. filtering in this document.
When a set of PEs operating in Single-Active redundancy mode, the use
of this split-horizon filtering mechanism is highly recommended
because it prevents transient loop at the time of failure or recovery
impacting the Ethernet Segment - e.g., when two PEs thinks that both
are DFs for that segment before DF election procedure settles down.
In order to achieve this split horizon function, every BUM packet In order to achieve this split horizon function, every BUM packet
originating from a non-DF PE is encapsulated with an MPLS label that originating from a non-DF PE is encapsulated with an MPLS label that
identifies the Ethernet segment of origin (i.e. the segment from identifies the Ethernet segment of origin (i.e. the segment from
which the frame entered the EVPN network). This label is referred to which the frame entered the EVPN network). This label is referred to
as the ESI label, and MUST be distributed by all PEs when operating as the ESI label, and MUST be distributed by all PEs when operating
in All-Active redundancy mode using a set of Ethernet A-D per ES in All-Active redundancy mode using a set of Ethernet A-D per ES
routes per section 9.2.1 above. This route is imported by the PEs routes per section 8.2.1 above. The ESI label SHOULD be distributed
by all PEs when operating in Single-Active redundancy mode using a
set of Ethernet A-D per ES route. This route is imported by the PEs
connected to the Ethernet Segment and also by the PEs that have at connected to the Ethernet Segment and also by the PEs that have at
least one EVPN instance in common with the Ethernet Segment in the least one EVPN instance in common with the Ethernet Segment in the
route. As described in section 9.1.1, the route MUST carry an ESI route. As described in section 8.1.1, the route MUST carry an ESI
Label Extended Community with a valid ESI label. The disposition DF Label Extended Community with a valid ESI label. The disposition PE
PE rely on the value of the ESI label to determine whether or not a rely on the value of the ESI label to determine whether or not a BUM
BUM frame is allowed to egress a specific Ethernet segment. It should frame is allowed to egress a specific Ethernet segment.
be noted that if the BUM frame is originated from the DF PE operating
in All-Active multi-homing mode, then the DF PE MAY not encapsulate
the frame with the ESI label. Furthermore, if the multi-homed PEs
operate in Single-Active redundancy mode, then the packet MUST NOT be
encapsulated with the ESI label and the label value MUST be set to
zero in ESI Label Extended Community per section 9.2.1 above.
8.3.1 ESI Label Assignment 8.3.1 ESI Label Assignment
The following subsections describe the assignment procedures for the The following subsections describe the assignment procedures for the
ESI label, which differ depending on the type of tunnels being used ESI label, which differ depending on the type of tunnels being used
to deliver multi-destination packets in the EVPN network. to deliver multi-destination packets in the EVPN network.
8.3.1.1 Ingress Replication 8.3.1.1 Ingress Replication
The non-DF PEs attached to a given ES that is operating in All-Active Each PE attached to a given ES that is operating in All-Active or
redundancy mode and that use ingress replication to receive BUM Single-Active redundancy mode and that uses ingress replication to
traffic advertise a downstream assigned ESI label in the set of receive BUM traffic advertises a downstream assigned ESI label in the
Ethernet A-D per ES routes for that ES. This label MUST be programmed set of Ethernet A-D per ES routes for that ES. This label MUST be
in the platform label space by the advertising PE. Further the programmed in the platform label space by the advertising PE and the
forwarding entry for this label must result in NOT forwarding packets forwarding entry for this label must result in NOT forwarding packets
received with this label onto the Ethernet segment that the label was received with this label onto the Ethernet segment for which the
distributed for. label was distributed.
Consider PE1 and PE2 that are multi-homed to CE1 on ES1 and operating The rules for the inclusion of the ESI label in a BUM packet by the
in All-Active multi-homing mode. Further consider that PE1 is using ingress PE operating in All-Active redundancy mode are as follows:
P2P or MP2P LSPs to send packets to PE2. Consider that PE1 is the
non-DF for VLAN1 and PE2 is the DF for VLAN1, and PE1 receives a BUM
packet from CE1 on VLAN1 on ES1. In this scenario, PE2 distributes an
Inclusive Multicast Ethernet Tag route for VLAN1 corresponding to an
EVPN instance. So, when PE1 sends a BUM packet, that it receives from
CE1, it MUST first push onto the MPLS label stack the ESI label that
PE2 has distributed for ES1. It MUST then push on the MPLS label
distributed by PE2 in the Inclusive Multicast Ethernet Tag route for
VLAN1. The resulting packet is further encapsulated in the P2P or
MP2P LSP label stack required to transmit the packet to PE2. When
PE2 receives this packet, it determines the set of ESIs to replicate
the packet to from the top MPLS label, after any P2P or MP2P LSP
labels have been removed. If the next label is the ESI label assigned
by PE2 for ES1, then PE2 MUST NOT forward the packet onto ES1. If the
next label is an ESI label which has not been assigned by PE2, then
PE2 MUST drop the packet. It should be noted that in this scenario,
if PE2 receives a BUM traffic for VLAN1 from CE1, then it doesn't
need to encapsulate the packet with an ESI label when sending it to
the PE1 since PE1 can use its DF logic to filter the BUM packets and
thus doesn't need to use split-horizon filtering for ES1.
8.3.1.2. P2MP MPLS LSPs A non-DF ingress PE MUST include the ESI label distributed by the DF
egress PE in the copy of a BUM packet sent to it.
An ingress PE (DF or non-DF) SHOULD include the ESI label distributed
by each non-DF egress PE in the copy of a BUM packet sent to it.
The rules for the inclusion of the ESI label in a BUM packet by the
ingress PE operating in Single-Active redundancy mode are as follows:
An ingress DF PE SHOULD include the ESI label distributed by the
egress PE in the copy of a BUM packet sent to it.
In both All-Active and Single-Active redundancy mode, an ingress PE
MUST NOT include an ESI label in the copy of a BUM packet sent to an
egress PE that is not attached to the ES through which the BUM packet
entered the EVI.
As an example, consider PE1 and PE2 that are multi-homed to CE1 on
ES1 and operating in All-Active multi-homing mode. Further consider
that PE1 is using P2P or MP2P LSPs to send packets to PE2. Consider
that PE1 is the non-DF for VLAN1 and PE2 is the DF for VLAN1, and PE1
receives a BUM packet from CE1 on VLAN1 on ES1. In this scenario, PE2
distributes an Inclusive Multicast Ethernet Tag route for VLAN1
corresponding to an EVPN instance. So, when PE1 sends a BUM packet,
that it receives from CE1, it MUST first push onto the MPLS label
stack the ESI label that PE2 has distributed for ES1. It MUST then
push on the MPLS label distributed by PE2 in the Inclusive Multicast
Ethernet Tag route for VLAN1. The resulting packet is further
encapsulated in the P2P or MP2P LSP label stack required to transmit
the packet to PE2. When PE2 receives this packet, it determines the
set of ESIs to replicate the packet to from the top MPLS label, after
any P2P or MP2P LSP labels have been removed. If the next label is
the ESI label assigned by PE2 for ES1, then PE2 MUST NOT forward the
packet onto ES1. If the next label is an ESI label which has not been
assigned by PE2, then PE2 MUST drop the packet. It should be noted
that in this scenario, if PE2 receives a BUM traffic for VLAN1 from
CE1, then it should encapsulate the packet with an ESI label received
from PE1 when sending it to the PE1 in order to avoid any transient
loop during a failure scenario impacting ES1 (e.g., port or link
failure).
8.3.1.2. P2MP MPLS LSPs
The non-DF PEs attached to a given ES that is operating in All-Active The non-DF PEs attached to a given ES that is operating in All-Active
redundancy mode and that use P2MP LSPs to send BUM traffic advertise redundancy mode and that use P2MP LSPs to send BUM traffic advertise
an upstream assigned ESI label in the set of Ethernet A-D per ES an upstream assigned ESI label in the set of Ethernet A-D per ES
routes for that ES. This label is upstream assigned by the PE that routes for that ES. This label is upstream assigned by the PE that
advertises the route. This label MUST be programmed by the other PEs, advertises the route. This label MUST be programmed by the other PEs,
that are connected to the ESI advertised in the route, in the context that are connected to the ESI advertised in the route, in the context
label space for the advertising PE. Further the forwarding entry for label space for the advertising PE. Further the forwarding entry for
this label must result in NOT forwarding packets received with this this label must result in NOT forwarding packets received with this
label onto the Ethernet segment that the label was distributed for. label onto the Ethernet segment that the label was distributed for.
This label MUST also be programmed by the other PEs, that import the This label MUST also be programmed by the other PEs, that import the
route but are not connected to the ESI advertised in the route, in route but are not connected to the ESI advertised in the route, in
the context label space for the advertising PE. Further the the context label space for the advertising PE. Further the
forwarding entry for this label must be a POP with no other forwarding entry for this label must be a POP with no other
associated action. associated action.
Consider PE1 and PE2 that are multi-homed to CE1 on ES1 and operating The DF PE attached to a given ES that is operating in Single-Active
in All-Active multi-homing mode. Also consider PE3 belongs to one of redundancy mode and that use P2MP LSPs to send BUM traffic should
the EVPN instances of ES1. Further, assume that PE1 which is the advertise an upstream assigned ESI label in the set of Ethernet A-D
non-DF, using P2MP MPLS LSPs to send BUM packets. When PE1 sends a per ES routes for that ES just as above paragraph.
BUM packet, that it receives from CE1, it MUST first push onto the
MPLS label stack the ESI label that it has assigned for the ESI that
the packet was received on. The resulting packet is further
encapsulated in the P2MP MPLS label stack necessary to transmit the
packet to the other PEs. Penultimate hop popping MUST be disabled on
the P2MP LSPs used in the MPLS transport infrastructure for EVPN.
When PE2 receives this packet, it de-capsulates the top MPLS label
and forwards the packet using the context label space determined by
the top label. If the next label is the ESI label assigned by PE1 to
ES1, then PE2 MUST NOT forward the packet onto ES1. When PE3 receives
this packet, it de-capsulates the top MPLS label and forwards the
packet using the context label space determined by the top label. If
the next label is the ESI label assigned by PE1 to ES1 and PE3 is not
connected to ES1, then PE3 MUST pop the label and flood the packet
over all local ESIs in that EVPN instance. It should be noted that
when PE2 sends a BUM frame over a P2MP LSP, it does not need to
encapsulate the frame with an ESI label because it is the DF for that
VLAN.
8.4 Aliasing and Backup-Path As an example, consider PE1 and PE2 that are multi-homed to CE1 on
ES1 and operating in All-Active multi-homing mode. Also consider PE3
belongs to one of the EVPN instances of ES1. Further, assume that
PE1 which is the non-DF, using P2MP MPLS LSPs to send BUM packets.
When PE1 sends a BUM packet, that it receives from CE1, it MUST first
push onto the MPLS label stack the ESI label that it has assigned for
the ESI that the packet was received on. The resulting packet is
further encapsulated in the P2MP MPLS label stack necessary to
transmit the packet to the other PEs. Penultimate hop popping MUST be
disabled on the P2MP LSPs used in the MPLS transport infrastructure
for EVPN. When PE2 receives this packet, it de-capsulates the top
MPLS label and forwards the packet using the context label space
determined by the top label. If the next label is the ESI label
assigned by PE1 to ES1, then PE2 MUST NOT forward the packet onto
ES1. When PE3 receives this packet, it de-capsulates the top MPLS
label and forwards the packet using the context label space
determined by the top label. If the next label is the ESI label
assigned by PE1 to ES1 and PE3 is not connected to ES1, then PE3 MUST
pop the label and flood the packet over all local ESIs in that EVPN
instance. It should be noted that when PE2 sends a BUM frame over a
P2MP LSP, it should encapsulate the frame with an ESI label even
though it is the DF for that VLAN in order to avoid any transient
loop during a failure scenario impacting ES1 (e.g., port or link
failure).
8.4 Aliasing and Backup-Path
In the case where a CE is multi-homed to multiple PE nodes, using a In the case where a CE is multi-homed to multiple PE nodes, using a
LAG with All-Active redundancy, it is possible that only a single PE LAG with All-Active redundancy, it is possible that only a single PE
learns a set of the MAC addresses associated with traffic transmitted learns a set of the MAC addresses associated with traffic transmitted
by the CE. This leads to a situation where remote PE nodes receive by the CE. This leads to a situation where remote PE nodes receive
MAC advertisement routes, for these addresses, from a single PE even MAC advertisement routes, for these addresses, from a single PE even
though multiple PEs are connected to the multi-homed segment. As a though multiple PEs are connected to the multi-homed segment. As a
result, the remote PEs are not able to effectively load-balance result, the remote PEs are not able to effectively load-balance
traffic among the PE nodes connected to the multi-homed Ethernet traffic among the PE nodes connected to the multi-homed Ethernet
segment. This could be the case, for e.g. when the PEs perform data- segment. This could be the case, for e.g. when the PEs perform data-
path learning on the access, and the load-balancing function on the path learning on the access, and the load-balancing function on the
skipping to change at page 23, line 30 skipping to change at page 24, line 13
automatically. automatically.
If an PE uses Route Target Constrain [RT-CONSTRAIN], the PE SHOULD If an PE uses Route Target Constrain [RT-CONSTRAIN], the PE SHOULD
advertise all such RTs using Route Target Constrains. The use of RT advertise all such RTs using Route Target Constrains. The use of RT
Constrains allows each Ethernet A-D route to reach only those PEs Constrains allows each Ethernet A-D route to reach only those PEs
that are configured to import at least one RT from the set of RTs that are configured to import at least one RT from the set of RTs
carried in the Ethernet A-D route. carried in the Ethernet A-D route.
8.4.1.1.1 Auto-Derivation from the Ethernet Tag ID 8.4.1.1.1 Auto-Derivation from the Ethernet Tag ID
The following is the procedure for deriving the RT attribute For the "Unique VLAN EVPN" scenario, it is highly desirable to auto-
automatically from the Ethernet Tag ID associated with the derive the RT from the Ethernet Tag ID (VLAN ID) for that EVPN
advertisement: instance. The following is the procedure for performing such auto-
derivation.
+ The Global Administrator field of the RT MUST
be set to the Autonomous System (AS) number that the PE
belongs to.
+ The Local Administrator field of the RT contains a 4 + The Global Administrator field of the RT MUST be set to
octets long number that encodes the Ethernet Tag-ID. If the the Autonomous System (AS) number that the PE associated
Ethernet Tag-ID is a two octet VLAN ID then it MUST be with.
encoded in the lower two octets of the Local Administrator
field and the higher two octets MUST be set to zero.
For the "Unique VLAN EVPN" this results in auto-deriving the RT from + The two octet VLAN ID MUST be encoded in the lower two
the Ethernet Tag, e.g., VLAN ID for that EVPN. octets of the Local Administrator field.
8.5 Designated Forwarder Election 8.5 Designated Forwarder Election
Consider a CE that is a host or a router that is multi-homed directly Consider a CE that is a host or a router that is multi-homed directly
to more than one PE in an EVPN instance on a given Ethernet segment. to more than one PE in an EVPN instance on a given Ethernet segment.
One or more Ethernet Tags may be configured on the Ethernet segment. One or more Ethernet Tags may be configured on the Ethernet segment.
In this scenario only one of the PEs, referred to as the Designated In this scenario only one of the PEs, referred to as the Designated
Forwarder (DF), is responsible for certain actions: Forwarder (DF), is responsible for certain actions:
- Sending multicast and broadcast traffic, on a given Ethernet - Sending multicast and broadcast traffic, on a given Ethernet
skipping to change at page 27, line 29 skipping to change at page 28, line 7
plane, to all the other PEs in that EVPN instance, using MP-BGP and plane, to all the other PEs in that EVPN instance, using MP-BGP and
specifically the MAC Advertisement route. specifically the MAC Advertisement route.
9.2.1. Constructing the BGP EVPN MAC/IP Address Advertisement 9.2.1. Constructing the BGP EVPN MAC/IP Address Advertisement
BGP is extended to advertise these MAC addresses using the MAC/IP BGP is extended to advertise these MAC addresses using the MAC/IP
Advertisement route type in the EVPN NLRI. Advertisement route type in the EVPN NLRI.
The RD MUST be the RD of the EVI that is advertising the NLRI. The The RD MUST be the RD of the EVI that is advertising the NLRI. The
procedures for setting the RD for a given EVI are described in procedures for setting the RD for a given EVI are described in
section 9.4.1. section 8.4.1.
The Ethernet Segment Identifier is set to the ten octet ESI described The Ethernet Segment Identifier is set to the ten octet ESI described
in section "Ethernet Segment". in section "Ethernet Segment".
The Ethernet Tag ID may be zero or may represent a valid Ethernet Tag The Ethernet Tag ID may be zero or may represent a valid Ethernet Tag
ID. This field may be non-zero when there are multiple bridge ID. This field may be non-zero when there are multiple bridge
domains in the MAC-VRF (e.g., the PE needs to perform qualified domains in the MAC-VRF (e.g., the PE needs to perform qualified
learning for the VLANs in that MAC-VRF). learning for the VLANs in that MAC-VRF).
When the the Ethernet Tag ID in the NLRI is set to a non-zero value, When the the Ethernet Tag ID in the NLRI is set to a non-zero value,
for a particular bridge domain, then this Ethernet Tag may either be for a particular bridge domain, then this Ethernet Tag may either be
the Ethernet tag value associated with the CE, e.g., VLAN ID, or it the Ethernet tag value associated with the CE, e.g., VLAN ID, or it
may be the Ethernet Tag Identifier, e.g., VLAN ID assigned by the may be the Ethernet Tag Identifier, e.g., VLAN ID assigned by the
EVPN provider and mapped to the CE's Ethernet tag. The latter would EVPN provider and mapped to the CE's Ethernet tag. The latter would
be the case if the CE Ethernet tags, e.g., VLAN ID, for a particular be the case if the CE Ethernet tags, e.g., VLAN ID, for a particular
bridge domain are different on different CEs. bridge domain are different on different CEs.
The MAC address length field is in bits and it is typically set to The MAC address length field is in bits and it is set to 48. The
48. However this specification enables specifying the MAC address as encoding of a MAC address MUST be the 6-octet MAC address specified
a prefix; in which case, the MAC address length field is set to the by [802.1D-ORIG] [802.1D-REV].
length of the prefix. This provides the ability to aggregate MAC
addresses if the deployment environment supports that. The encoding
of a MAC address MUST be the 6-octet MAC address specified by
[802.1D-ORIG] [802.1D-REV]. If the MAC address is advertised as a
prefix then the trailing bits of the prefix MUST be set to 0 to
ensure that the entire prefix is encoded as 6 octets.
The IP Address field is optional. By default, the IP Address Length The IP Address Field is optional. By default, the IP Address Length
field is set to 0 and the IP address field is omitted from the route. field is set to 0 and the IP address field is omitted from the route.
When a valid IP address or address prefix needs to be advertised When a valid IP address needs to be advertised, it is then encoded in
(e.g., for ARP suppression purposes or for inter-subnet switching), this route. When an IP address is present, the IP Address Length
it is then encoded in this route. field is in bits and it is set to 32 or 128 bits. Other IP Address
Length values are outside the scope of this document. The encoding of
The IP Address Length field is in bits and it is the length of the IP an IP address MUST be either 4 octets for IPv4 or 16 octets for IPv6.
prefix. This provides the ability to advertise IP address prefixes The length field of EVPN NLRI (which is in octets and is described in
when the deployment environment supports that. The encoding of an IP section 7) is sufficient to determine whether an IP address is
address MUST be either 4 octets for IPv4 or 16 octets for IPv6. When encoded in this route and if so, whether the encoded IP address is
the IP address is advertised as a prefix, then the trailing bits of IPV4 or IPv6.
the prefix MUST be set to 0 to ensure that the entire prefix is
encoded as either 4 or 16 octets. The length field of EVPN NLRI
(which is in octets and is described in section 8) is sufficient to
determine whether an IP address/prefix is encoded in this route and
if so, whether the encoded IP address/prefix is IPV4 or IPv6.
The MPLS label1 field is encoded as 3 octets, where the high-order 20 The MPLS label1 field is encoded as 3 octets, where the high-order 20
bits contain the label value. The MPLS label1 MUST be downstream bits contain the label value. The MPLS label1 MUST be downstream
assigned and it is associated with the MAC address being advertised assigned and it is associated with the MAC address being advertised
by the advertising PE. The advertising PE uses this label when it by the advertising PE. The advertising PE uses this label when it
receives an MPLS-encapsulated packet to perform forwarding based on receives an MPLS-encapsulated packet to perform forwarding based on
the destination MAC address. The forwarding procedures are specified the destination MAC address. The forwarding procedures are specified
in section "Forwarding Unicast Packets" and "Load Balancing of in section "Forwarding Unicast Packets" and "Load Balancing of
Unicast Packets". Unicast Packets".
skipping to change at page 31, line 12 skipping to change at page 31, line 27
the inter-subnet forwarding is performed at layer 3 and the PE that the inter-subnet forwarding is performed at layer 3 and the PE that
performs such function is called the default gateway. In this case performs such function is called the default gateway. In this case
when the PE receives an ARP Request for the IP address of the default when the PE receives an ARP Request for the IP address of the default
gateway, the PE originates an ARP Reply. gateway, the PE originates an ARP Reply.
Each PE that acts as a default gateway for a given EVPN instance MAY Each PE that acts as a default gateway for a given EVPN instance MAY
advertise in the EVPN control plane its default gateway MAC address advertise in the EVPN control plane its default gateway MAC address
using the MAC advertisement route, and indicates that such route is using the MAC advertisement route, and indicates that such route is
associated with the default gateway. This is accomplished by associated with the default gateway. This is accomplished by
requiring the route to carry the Default Gateway extended community requiring the route to carry the Default Gateway extended community
defined in [Section 8.8 Default Gateway Extended Community]. The ESI defined in [Section 7.8 Default Gateway Extended Community]. The ESI
field is set to zero when advertising the MAC route with the Default field is set to zero when advertising the MAC route with the Default
Gateway extended community. Gateway extended community.
Unless it is known a priori (by means outside of this document) that Unless it is known a priori (by means outside of this document) that
all PEs of a given EVPN instance act as a default gateway for that all PEs of a given EVPN instance act as a default gateway for that
EVPN instance, the MPLS label MUST be set to a valid downstream EVPN instance, the MPLS label MUST be set to a valid downstream
assigned label. assigned label.
Furthermore, even if all PEs of a given EVPN instance do act as a Furthermore, even if all PEs of a given EVPN instance do act as a
default gateway for that EVPN instance, but only some, but not all, default gateway for that EVPN instance, but only some, but not all,
skipping to change at page 32, line 27 skipping to change at page 32, line 39
Each PE MUST advertise an "Inclusive Multicast Ethernet Tag Route" to Each PE MUST advertise an "Inclusive Multicast Ethernet Tag Route" to
enable the above. The following subsection provides the procedures to enable the above. The following subsection provides the procedures to
construct the Inclusive Multicast Ethernet Tag route. Subsequent construct the Inclusive Multicast Ethernet Tag route. Subsequent
subsections describe in further detail its usage. subsections describe in further detail its usage.
11.1. Construction of the Inclusive Multicast Ethernet Tag Route 11.1. Construction of the Inclusive Multicast Ethernet Tag Route
The RD MUST be the RD of the EVI that is advertising the NLRI. The The RD MUST be the RD of the EVI that is advertising the NLRI. The
procedures for setting the RD for a given EVPN instance on a PE are procedures for setting the RD for a given EVPN instance on a PE are
described in section 9.4.1. described in section 8.4.1.
The Ethernet Tag ID is the identifier of the Ethernet Tag. It MAY be The Ethernet Tag ID is the identifier of the Ethernet Tag. It MAY be
set to 0 or to a valid Ethernet Tag value. set to 0 or to a valid Ethernet Tag value.
The Originating Router's IP address MUST be set to an IP address of The Originating Router's IP address MUST be set to an IP address of
the PE. This address SHOULD be common for all the EVIs on the PE the PE. This address SHOULD be common for all the EVIs on the PE
(e.,g., this address may be PE's loopback address). The IP Address (e.,g., this address may be PE's loopback address). The IP Address
Length field is in bits. Length field is in bits.
The Next Hop field of the MP_REACH_NLRI attribute of the route MUST The Next Hop field of the MP_REACH_NLRI attribute of the route MUST
skipping to change at page 33, line 16 skipping to change at page 33, line 29
instance on the PE, the PMSI Tunnel attribute of the Inclusive instance on the PE, the PMSI Tunnel attribute of the Inclusive
Multicast Ethernet Tag route is constructed as follows. Multicast Ethernet Tag route is constructed as follows.
+ If the PE that originates the advertisement uses a + If the PE that originates the advertisement uses a
P-Multicast tree for the P-tunnel for EVPN, the PMSI P-Multicast tree for the P-tunnel for EVPN, the PMSI
Tunnel attribute MUST contain the identity of the tree Tunnel attribute MUST contain the identity of the tree
(note that the PE could create the identity of the (note that the PE could create the identity of the
tree prior to the actual instantiation of the tree). tree prior to the actual instantiation of the tree).
+ An PE that uses a P-Multicast tree for the P-tunnel MAY + An PE that uses a P-Multicast tree for the P-tunnel MAY
aggregate two or more Ethernet Tags in the same or different aggregate two or more EVPN instances (EVIs) present
EVIs present on the PE onto the same tree. In this case, in on the PE onto the same tree. In this case, in addition
addition to carrying the identity of the tree, the PMSI Tunnel to carrying the identity of the tree, the PMSI Tunnel
attribute MUST carry an MPLS upstream assigned label which attribute MUST carry an MPLS upstream assigned label which
the PE has bound uniquely to the Ethernet Tag for the EVI the PE has bound uniquely to the EVI associated with this
associated with this update (as determined by its RTs). update (as determined by its RTs).
If the PE has already advertised Inclusive Multicast If the PE has already advertised Inclusive Multicast
Ethernet Tag routes for two or more Ethernet Tags that it Ethernet Tag routes for two or more EVIs that it now
now desires to aggregate, then the PE MUST re-advertise desires to aggregate, then the PE MUST re-advertise
those routes. The re-advertised routes MUST be the same those routes. The re-advertised routes MUST be the same
as the original ones, except for the PMSI Tunnel attribute as the original ones, except for the PMSI Tunnel attribute
and the label carried in that attribute. and the label carried in that attribute.
+ If the PE that originates the advertisement uses ingress + If the PE that originates the advertisement uses ingress
replication for the P-tunnel for EVPN, the route MUST replication for the P-tunnel for EVPN, the route MUST
include the PMSI Tunnel attribute with the Tunnel Type set to include the PMSI Tunnel attribute with the Tunnel Type set to
Ingress Replication and Tunnel Identifier set to a routable Ingress Replication and Tunnel Identifier set to a routable
address of the PE. The PMSI Tunnel attribute MUST carry a address of the PE. The PMSI Tunnel attribute MUST carry a
downstream assigned MPLS label. This label is used to downstream assigned MPLS label. This label is used to
skipping to change at page 35, line 48 skipping to change at page 36, line 14
remote PEs or to a locally attached CE. When forwarding to a remote remote PEs or to a locally attached CE. When forwarding to a remote
PE, the packet is encapsulated in the EVPN MPLS label advertised by PE, the packet is encapsulated in the EVPN MPLS label advertised by
the remote PE, for that MAC address, and in the MPLS LSP label stack the remote PE, for that MAC address, and in the MPLS LSP label stack
to reach the remote PE. to reach the remote PE.
If the MAC address is unknown and if the administrative policy on the If the MAC address is unknown and if the administrative policy on the
PE requires flooding of unknown unicast traffic then: PE requires flooding of unknown unicast traffic then:
- The PE MUST flood the packet to other PEs. The PE MUST first - The PE MUST flood the packet to other PEs. The PE MUST first
encapsulate the packet in the ESI MPLS label as described in section encapsulate the packet in the ESI MPLS label as described in section
9.3. If ingress replication is used, the packet MUST be replicated 8.3. If ingress replication is used, the packet MUST be replicated
one or more times to each remote PE with the outermost label being an one or more times to each remote PE with the outermost label being an
MPLS label determined as follows: This is the MPLS label advertised MPLS label determined as follows: This is the MPLS label advertised
by the remote PE in a PMSI Tunnel Attribute in the Inclusive by the remote PE in a PMSI Tunnel Attribute in the Inclusive
Multicast Ethernet Tag route for an <EVPN instance, Ethernet Tag> Multicast Ethernet Tag route for an <EVPN instance, Ethernet Tag>
combination. The Ethernet Tag in the route must be the same as the combination. The Ethernet Tag in the route must be the same as the
Ethernet Tag associated with the interface on which the ingress PE Ethernet Tag associated with the interface on which the ingress PE
receives the packet. If P2MP LSPs are being used the packet MUST be receives the packet. If P2MP LSPs are being used the packet MUST be
sent on the P2MP LSP that the PE is the root of for the Ethernet Tag sent on the P2MP LSP that the PE is the root of for the Ethernet Tag
in the EVPN instance. If the same P2MP LSP is used for all Ethernet in the EVPN instance. If the same P2MP LSP is used for all Ethernet
Tags, then all the PEs in the EVPN instance MUST be the leaves of the Tags, then all the PEs in the EVPN instance MUST be the leaves of the
skipping to change at page 42, line 13 skipping to change at page 42, line 25
need for ESI comparison. The reason ESI comparison is done for multi- need for ESI comparison. The reason ESI comparison is done for multi-
homing, is to prevent false detection of MAC move among the PEs homing, is to prevent false detection of MAC move among the PEs
attached to the same multi-homed site. attached to the same multi-homed site.
A PE receiving a MAC Advertisement route for a MAC address with a A PE receiving a MAC Advertisement route for a MAC address with a
different Ethernet segment identifier and a higher sequence number different Ethernet segment identifier and a higher sequence number
than that which it had previously advertised, withdraws its MAC than that which it had previously advertised, withdraws its MAC
Advertisement route. If two (or more) PEs advertise the same MAC Advertisement route. If two (or more) PEs advertise the same MAC
address with same sequence number but different Ethernet segment address with same sequence number but different Ethernet segment
identifiers, a PE that receives these routes selects the route identifiers, a PE that receives these routes selects the route
advertised by the PE with lowest IP address as the best route. advertised by the PE with lowest IP address as the best route. If the
PE is the originator of the MAC route and it receives the same MAC
address with the same sequence number that it generated, it will
compare its own IP address with the IP address of the remote PE and
will select the lowest IP. If its own route is not the best one, it
will withdraw the route.
15.1. MAC Duplication Issue 15.1. MAC Duplication Issue
A situation may arise where the same MAC address is learned by A situation may arise where the same MAC address is learned by
different PEs in the same VLAN because of two (or more hosts) being different PEs in the same VLAN because of two (or more hosts) being
mis-configured with the same (duplicate) MAC address. In such mis-configured with the same (duplicate) MAC address. In such
situation, the traffic originating from these hosts would trigger situation, the traffic originating from these hosts would trigger
continuous MAC moves among the PEs attached to these hosts. It is continuous MAC moves among the PEs attached to these hosts. It is
important to recognize such situation and avoid incrementing the important to recognize such situation and avoid incrementing the
sequence number (in the MAC Mobility attribute) to infinity. In order sequence number (in the MAC Mobility attribute) to infinity. In order
to remedy such situation, a PE that detects a MAC mobility event by to remedy such situation, a PE that detects a MAC mobility event by
way of local learning starts an M-second timer (default value of M = way of local learning starts an M-second timer (default value of M =
5) and if it detects N MAC moves before the timer expires (default 180) and if it detects N MAC moves before the timer expires (default
value for N = 3), it concludes that a duplicate MAC situation has value for N = 5), it concludes that a duplicate MAC situation has
occurred. The PE MUST alert the operator and stop sending and occurred. The PE MUST alert the operator and stop sending and
processing any BGP MAC Advertisement routes for that MAC address till processing any BGP MAC Advertisement routes for that MAC address till
a corrective action is taken by the operator. The values of M and N a corrective action is taken by the operator. The values of M and N
MUST be configurable to allow for flexibility in operator control. MUST be configurable to allow for flexibility in operator control.
Note that the other PEs in the E-VPN instance will forward the Note that the other PEs in the E-VPN instance will forward the
traffic for the duplicate MAC address to one of the PEs advertising traffic for the duplicate MAC address to one of the PEs advertising
the duplicate MAC address. the duplicate MAC address.
15.2. Sticky MAC addresses 15.2. Sticky MAC addresses
skipping to change at page 43, line 34 skipping to change at page 43, line 48
point-to-multipoint LSPs created by RSVP-TE or mLDP. point-to-multipoint LSPs created by RSVP-TE or mLDP.
16.2.1. Inclusive Trees 16.2.1. Inclusive Trees
An Inclusive Tree allows the use of a single multicast distribution An Inclusive Tree allows the use of a single multicast distribution
tree, referred to as an Inclusive P-Multicast tree, in the SP network tree, referred to as an Inclusive P-Multicast tree, in the SP network
to carry all the multicast traffic from a specified set of EVPN to carry all the multicast traffic from a specified set of EVPN
instances on a given PE. A particular P-Multicast tree can be set up instances on a given PE. A particular P-Multicast tree can be set up
to carry the traffic originated by sites belonging to a single EVPN to carry the traffic originated by sites belonging to a single EVPN
instance, or to carry the traffic originated by sites belonging to instance, or to carry the traffic originated by sites belonging to
different EVPN instances. The ability to carry the traffic of more several EVPN instances. The ability to carry the traffic of more than
than one EVPN instance on the same tree is termed 'Aggregation'. The one EVPN instance on the same tree is termed 'Aggregation' and the
tree needs to include every PE that is a member of any of the EVPN tree is called an Aggregate Inclusive P-Multicast tree or Aggregate
instances that are using the tree. This implies that an PE may Inclusive tree for short. The Aggregate Inclusive tree needs to
receive multicast traffic for a multicast stream even if it doesn't include every PE that is a member of any of the EVPN instances that
have any receivers that are interested in receiving traffic for that are using the tree. This implies that an PE may receive multicast
stream. traffic for a multicast stream even if it doesn't have any receivers
that are interested in receiving traffic for that stream.
An Inclusive P-Multicast tree as defined in this document is a P2MP An Inclusive or Aggregate Inclusive tree as defined in this document
tree. A P2MP tree is used to carry traffic only for EVPN CEs that is a P2MP tree. A P2MP tree is used to carry traffic only for EVPN
are connected to the PE that is the root of the tree. CEs that are connected to the PE that is the root of the tree.
The procedures for signaling an Inclusive Tree are the same as those The procedures for signaling an Inclusive tree are the same as those
in [VPLS-MCAST] with the VPLS-AD route replaced with the Inclusive in [VPLS-MCAST] with the VPLS-AD route replaced with the Inclusive
Multicast Ethernet Tag route. The P-Tunnel attribute [VPLS-MCAST] for Multicast Ethernet Tag route. The P-Tunnel attribute [VPLS-MCAST] for
an Inclusive tree is advertised in the Inclusive Multicast route as an Inclusive tree is advertised with the Inclusive Multicast Ethernet
described in section "Handling of Multi-Destination Traffic". Note Tag route as described in section "Handling of Multi-Destination
that an PE can "aggregate" multiple inclusive trees for different Traffic". Note that for an Aggregate Inclusive tree, an PE can
EVPN instances on the same P2MP LSP using upstream labels. The "aggregate" multiple EVPN instances on the same P2MP LSP using
procedures for aggregation are the same as those described in [VPLS- upstream labels. The procedures for aggregation are the same as those
MCAST], with VPLS A-D routes replaced by EVPN Inclusive Multicast described in [VPLS-MCAST], with VPLS A-D routes replaced by EVPN
routes. Inclusive Multicast ET routes.
17. Convergence 17. Convergence
This section describes failure recovery from different types of This section describes failure recovery from different types of
network failures. network failures.
17.1. Transit Link and Node Failures between PEs 17.1. Transit Link and Node Failures between PEs
The use of existing MPLS Fast-Reroute mechanisms can provide failure The use of existing MPLS Fast-Reroute mechanisms can provide failure
recovery in the order of 50ms, in the event of transit link and node recovery in the order of 50ms, in the event of transit link and node
skipping to change at page 46, line 4 skipping to change at page 46, line 17
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0| Reserved | Sequence Number | |0 0 0 0| Reserved | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In the above diagram the first 4 bits MUST be set to 0. The rest of In the above diagram the first 4 bits MUST be set to 0. The rest of
the first 16 bits are reserved for future use. They MUST be set to 0 the first 16 bits are reserved for future use. They MUST be set to 0
when transmitting, and MUST be ignored upon receipt. The next 16 bits when transmitting, and MUST be ignored upon receipt. The next 16 bits
provide a sequence number that MUST also be set to zero by default. provide a sequence number that MUST also be set to zero by default.
19. Acknowledgements 19. Acknowledgements
Special thanks to Yakov Rekhter for reviewing this draft several Special thanks to Yakov Rekhter for reviewing this draft several
times and providing valuable comments and for his very engaging times and providing valuable comments and for his very engaging
discussions on several topics of this draft that helped shape this discussions on several topics of this draft that helped shape this
document. We would also like to thank Pedro Marques, Kaushik Ghosh, document. We would also like to thank Pedro Marques, Kaushik Ghosh,
Nischal Sheth, Robert Raszuk, Amit Shukla and Nadeem Mohammed for Nischal Sheth, Robert Raszuk, Amit Shukla, and Nadeem Mohammed for
discussions that helped shape this document. We would also like to discussions that helped shape this document. We would also like to
thank Han Nguyen for his comments and support of this work. We would thank Han Nguyen for his comments and support of this work. We would
also like to thank Steve Kensil and Reshad Rahman for their reviews. also like to thank Steve Kensil and Reshad Rahman for their reviews.
We would like to thank Jorge Rabadan for his contribution to section We would like to thank Jorge Rabadan for his contribution to section
5 of this draft. We like to thank Thomas Morin for his review of this 5 of this draft. We like to thank Thomas Morin for his review of this
draft and his contribution of section 8.6. Last but not least, many draft and his contribution of section 8.6. Last but not least, many
thanks to Jakob Heitz for his help to improve several sections of thanks to Jakob Heitz for his help to improve several sections of
this draft. this draft.
20. Security Considerations We would also like to thank Clarence Filsfils, Dennis Cai, Quaizar
Vohra, Kireeti Kompella, Apurva Mehta for their contributions to this
document.
20. Security Considerations
Security considerations discussed in [RFC4761] and [RFC4762] apply to Security considerations discussed in [RFC4761] and [RFC4762] apply to
this document for MAC learning in data-plane over an Attachment this document for MAC learning in data-plane over an Attachment
Circuit (AC) and for flooding of unknown unicast and ARP messages Circuit (AC) and for flooding of unknown unicast and ARP messages
over the MPLS/IP core. Security considerations discussed in [RFC4364] over the MPLS/IP core. Security considerations discussed in [RFC4364]
apply to this document for MAC learning in control-plane over the apply to this document for MAC learning in control-plane over the
MPLS/IP core. This section describes additional considerations. MPLS/IP core. This section describes additional considerations.
As mentioned in [RFC4761], there are two aspects to achieving data As mentioned in [RFC4761], there are two aspects to achieving data
privacy and protecting against denial-of-service attacks in a VPN: privacy and protecting against denial-of-service attacks in a VPN:
skipping to change at page 47, line 15 skipping to change at page 47, line 35
One of the requirements for protecting the data plane is that the One of the requirements for protecting the data plane is that the
MPLS labels be accepted only from valid interfaces. For a PE, valid MPLS labels be accepted only from valid interfaces. For a PE, valid
interfaces comprise links from other routers in the PE's own AS. For interfaces comprise links from other routers in the PE's own AS. For
an ASBR, valid interfaces comprise links from other routers in the an ASBR, valid interfaces comprise links from other routers in the
ASBR's own AS, and links from other ASBRs in ASes that have instances ASBR's own AS, and links from other ASBRs in ASes that have instances
of a given EVPN. It is especially important in the case of multi-AS of a given EVPN. It is especially important in the case of multi-AS
EVPN instances that one accept EVPN packets only from valid EVPN instances that one accept EVPN packets only from valid
interfaces. interfaces.
It is also important to help limit malicious traffic into a network It is also important to help limit malicious traffic into a network
for an imposter MAC address. The mechanism described in section 16.1, for an imposter MAC address. The mechanism described in section 15.1,
shows how duplicate MAC addresses can be detected and continous false shows how duplicate MAC addresses can be detected and continous false
MAC mobility can be prevented. The mechanism described in section MAC mobility can be prevented. The mechanism described in section
16.2, shows how MAC addresses can be pinned to a given Ethernet 15.2, shows how MAC addresses can be pinned to a given Ethernet
Segment, such that if they appear behind any other Ethernet Segments, Segment, such that if they appear behind any other Ethernet Segments,
the traffic for those MAC addresses be prevented from entering the the traffic for those MAC addresses be prevented from entering the
EVPN network from the other Ethernet Segments. EVPN network from the other Ethernet Segments.
21. Contributors 21. Co-authors
In addition to the authors listed above, the following individuals In addition to the authors listed on the front page, the following
also contributed to this document: individuals have also helped to shape this document:
Keyur Patel
Samer Salam Samer Salam
Sami Boutros Sami Boutros
Keyur Patel
Clarence Filsfils
Dennis Cai
Cisco Cisco
Yakov Rekhter
Ravi Shekhar Ravi Shekhar
Quaizar Vohra
Kireeti Kompella
Apurva Mehta
Nadeem Mohammad
Juniper Networks Juniper Networks
Florin Balus Florin Balus
Nuage Networks Nuage Networks
22. IANA Considerations 22. IANA Considerations
This document defines a new NLRI, called "EVPN", to be carried in BGP This document defines a new NLRI, called "EVPN", to be carried in BGP
using multiprotocol extensions. This NLRI uses the existing AFI of using multiprotocol extensions. This NLRI uses the existing AFI of
25 (L2VPN). IANA has assigned it a SAFI value of 70. 25 (L2VPN). IANA has assigned it a SAFI value of 70.
skipping to change at page 49, line 4 skipping to change at page 49, line 18
Forwarding", RFC 6790, November 2012. Forwarding", RFC 6790, November 2012.
24. Author's Address 24. Author's Address
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
Rahul Aggarwal Rahul Aggarwal
Email: raggarwa_1@yahoo.com Email: raggarwa_1@yahoo.com
Wim Henderickx
Alcatel-Lucent Nabil Bitar
e-mail: wim.henderickx@alcatel-lucent.com Verizon Communications
Email : nabil.n.bitar@verizon.com
Aldrin Isaac Aldrin Isaac
Bloomberg Bloomberg
Email: aisaac71@bloomberg.net Email: aisaac71@bloomberg.net
James Uttaro James Uttaro
AT&T AT&T
200 S. Laurel Avenue
Middletown, NJ 07748
USA
Email: uttaro@att.com Email: uttaro@att.com
Nabil Bitar
Verizon Communications
Email : nabil.n.bitar@verizon.com
John Drake John Drake
Juniper Networks Juniper Networks
Email: jdrake@juniper.net Email: jdrake@juniper.net
Wim Henderickx
Alcatel-Lucent
e-mail: wim.henderickx@alcatel-lucent.com
 End of changes. 76 change blocks. 
203 lines changed or deleted 212 lines changed or added

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