draft-ietf-bess-evpn-vpls-seamless-integ-04.txt   draft-ietf-bess-evpn-vpls-seamless-integ-05.txt 
BESS Workgroup A. Sajassi (Editor) BESS Workgroup A. Sajassi (Editor)
INTERNET-DRAFT S. Salam INTERNET-DRAFT S. Salam
Intended Status: Standard Track Cisco Intended Status: Standard Track Cisco
N. Del Regno N. Del Regno
Verizon Verizon
J. Rabadan J. Rabadan
Nokia Nokia
Expires: October 25, 2018 April 25, 2018 Expires: May 27, 2019 November 27, 2018
(PBB-)EVPN Seamless Integration with (PBB-)VPLS (PBB-)EVPN Seamless Integration with (PBB-)VPLS
draft-ietf-bess-evpn-vpls-seamless-integ-04 draft-ietf-bess-evpn-vpls-seamless-integ-05
Abstract Abstract
This draft specifies procedures for backward compatibility of the This draft specifies procedures for backward compatibility of
(PBB-)EVPN solution with (PBB-)VPLS and provides mechanisms for Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN (PBB-
seamless integration of the two technologies in the same MPLS/IP EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider
network on a per-VPN-instance basis. Implementation of this draft Backbone Bridge VPLS (PBB-VPLS) solutions (PBB-)VPLS. It also
enables service providers to introduce (PBB-)EVPN PEs in their brown- provides mechanisms for seamless integration of these two
field deployments of (PBB-)VPLS networks. technologies in the same MPLS/IP network on a per-VPN-instance basis.
Implementation of this draft enables service providers to introduce
(PBB-)EVPN PEs in their brown-field deployments of (PBB-)VPLS
networks.
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 2, line 29 skipping to change at page 2, line 32
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Specification of Requirements . . . . . . . . . . . . . . 4 1.1. Specification of Requirements . . . . . . . . . . . . . . 4
1.2. Terms and Abbreviations . . . . . . . . . . . . . . . . . 4 1.2. Terms and Abbreviations . . . . . . . . . . . . . . . . . 4
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 VPLS Integration with EVPN . . . . . . . . . . . . . . . . . . . 6 3 VPLS Integration with EVPN . . . . . . . . . . . . . . . . . . . 6
3.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 7 3.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 7
3.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 7 3.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 7
3.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 9 3.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 9
3.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 9 3.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 9
3.4.2 P2MP Tunnel . . . . . . . . . . . . . . . . . . . . . . 10 3.4.2 P2MP Tunnel . . . . . . . . . . . . . . . . . . . . . . 9
4 PBB-VPLS Integration with PBB-EVPN . . . . . . . . . . . . . . . 10 4 PBB-VPLS Integration with PBB-EVPN . . . . . . . . . . . . . . . 10
4.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 10 4.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 10
4.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 10 4.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 10
4.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 11 4.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 11 4.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 11
4.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 11 4.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 11
4.4.2 P2MP Tunnel - Inclusive Tree . . . . . . . . . . . . . . 12 4.4.2 P2MP Tunnel - Inclusive Tree . . . . . . . . . . . . . . 12
5 Security Considerations . . . . . . . . . . . . . . . . . . . . 12 5 Security Considerations . . . . . . . . . . . . . . . . . . . . 12
6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12 6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12
7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1 Normative References . . . . . . . . . . . . . . . . . . . 12 7.1 Normative References . . . . . . . . . . . . . . . . . . . 12
7.2 Informative References . . . . . . . . . . . . . . . . . . 13 7.2 Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1 Introduction 1 Introduction
Virtual Private LAN Service (VPLS) and Provider Backbone Bridging Virtual Private LAN Service (VPLS) and Provider Backbone Bridging
VPLS (PBB-VPLS) are widely-deployed Layer-2 VPN (L2VPN) technologies. VPLS (PBB-VPLS) are widely-deployed Layer-2 VPN (L2VPN) technologies.
Many Service Providers (SPs) who are looking at adopting Ethernet VPN Many Service Providers (SPs) who are looking at adopting Ethernet VPN
(EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) want to (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) want to
preserve their investment in the VPLS and PBB-VPLS networks. Hence, preserve their investment in the VPLS and PBB-VPLS networks. Hence,
they require procedures by which EVPN and PBB-EVPN technology can be they require procedures by which EVPN and PBB-EVPN technology can be
introduced into their brown-field VPLS and PBB-VPLS networks without introduced into their brown-field VPLS and PBB-VPLS networks without
skipping to change at page 3, line 38 skipping to change at page 3, line 38
|PE4|----| MPLS/IP |---|PE5| |PE4|----| MPLS/IP |---|PE5|
+---+ | Core | +---+ +---+ | Core | +---+
| | | |
+---------------+ +---------------+
/ \ / \
+---+ +---+ +---+ +---+
|PE2| |PE3| |PE2| |PE3|
+---+ +---+ +---+ +---+
VPLS PE VPLS PE VPLS PE VPLS PE
Figure 1: Seamless Integration of (PBB-)EVPN PEs & (PBB-)VPLS Figure 1: Seamless Integration of (PBB-)EVPN & (PBB-)VPLS
Section 2 provides the details of the requirements. Section 3 Section 2 provides the details of the requirements. Section 3
specifies procedures for the seamless integration of VPLS and EVPN specifies procedures for the seamless integration of VPLS and EVPN
networks. And section 4 specifies procedures for the seamless networks. And section 4 specifies procedures for the seamless
integration of PBB-VPLS and PBB-EVPN networks. integration of PBB-VPLS and PBB-EVPN networks.
It should be noted that the scenarios for PBB-VPLS integration with It should be noted that the scenarios for PBB-VPLS integration with
EVPN and VPLS integration with PBB-EVPN are not covered in this EVPN and VPLS integration with PBB-EVPN are not covered in this
document because there haven't been any requirements from service document because there haven't been any requirements from service
providers for these scenarios. The reason for that is that providers for these scenarios. The reason for that is that
skipping to change at page 4, line 20 skipping to change at page 4, line 20
delivery, the solution reduces the scope of [MMRP] (which is a soft- delivery, the solution reduces the scope of [MMRP] (which is a soft-
state protocol) to only that of existing VPLS PEs, and uses the more state protocol) to only that of existing VPLS PEs, and uses the more
robust BGP-based mechanism for multicast pruning among new EVPN PEs. robust BGP-based mechanism for multicast pruning among new EVPN PEs.
- It is completely backward compatible. - It is completely backward compatible.
- New PEs can leverage the extensive multi-homing mechanisms and - New PEs can leverage the extensive multi-homing mechanisms and
provisioning simplifications of (PBB-)EVPN: provisioning simplifications of (PBB-)EVPN:
a. Auto-sensing of MHN / MHD a. Auto-sensing of MHN / MHD
b. Auto-discovery of redundancy group b. Auto-discovery of redundancy group
c. Auto-provisioning in DF election and VLAN carving c. Auto-provisioning of Designated Forwarder election and
VLAN carving
1.1. Specification of Requirements 1.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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.2. Terms and Abbreviations 1.2. Terms and Abbreviations
B-MAC: Backbone MAC
B-VID: Backbone VLAN ID
Broadcast Domain: In a bridged network, the broadcast domain Broadcast Domain: In a bridged network, the broadcast domain
corresponds to a Virtual LAN (VLAN), where a VLAN is typically corresponds to a Virtual LAN (VLAN), where a VLAN is typically
represented by a single VLAN ID (VID) but can be represented by represented by a single VLAN ID (VID) but can be represented by
several VIDs where Shared VLAN Learning (SVL) is used per several VIDs where Shared VLAN Learning (SVL) is used per
[IEEE.802.1ah]. [IEEE.802.1ah].
Bridge Table: An instantiation of a broadcast domain on a MAC-VRF Bridge Table: An instantiation of a broadcast domain on a MAC-VRF
RIB: Routing Information Base - An instantiation of a routing table RIB: Routing Information Base - An instantiation of a routing table
on a MAC-VRF on a MAC-VRF
FIB: Forwarding Information Base - An instantiation of a forwarding FIB: Forwarding Information Base - An instantiation of a forwarding
table on a MAC-VRF table on a MAC-VRF
CE: A Customer Edge device, e.g., a host, router, or switch. CE: A Customer Edge device, e.g., a host, router, or switch.
EVI: An EVPN Instance spanning the Provider Edge (PE) devices
participating in that EVPN.
MAC-VRF: A Virtual Routing and Forwarding table for Media Access MAC-VRF: A Virtual Routing and Forwarding table for Media Access
Control (MAC) addresses on an EVPN PE. Control (MAC) addresses on an EVPN PE.
MAC address: Media Access Control address MAC address: Media Access Control address
ES: When a customer site (device or network) is connected to one or C-MAC address: Customer MAC address - e.g., host or CE's MAC address
more PEs via a set of Ethernet links, then that set of links is
referred to as an "Ethernet Segment".
ESI: An Ethernet Segment Identifier is a unique non-zero identifier B-MAC address: Backbone MAC address - e.g., PE's MAC address
that identifies an ES
Ethernet segment (ES): Refers to the set of Ethernet links that
connects a customer site (device or network) to one or more PEs.
Ethernet Tag: An Ethernet Tag identifies a particular broadcast Ethernet Tag: An Ethernet Tag identifies a particular broadcast
domain, e.g., a VLAN. An EVPN instance consists of one or more domain, e.g., a VLAN. An EVPN instance consists of one or more
broadcast domains broadcast domains
MHD: Multi-Homed Device MHD: Multi-Homed Device
MHN: Multi-Homed Network MHN: Multi-Homed Network
P2MP: Point-to-Multipoint P2MP: Point-to-Multipoint
skipping to change at page 6, line 9 skipping to change at page 5, line 52
(PBB-)EVPN: refers to both, PBB-EVPN and EVPN. This document uses (PBB-)EVPN: refers to both, PBB-EVPN and EVPN. This document uses
this abbreviation when a given description applies to both this abbreviation when a given description applies to both
technologies. technologies.
(PBB-)VPLS: refers to both, PBB-VPLS and VPLS. As for EVPN, this (PBB-)VPLS: refers to both, PBB-VPLS and VPLS. As for EVPN, this
abbreviation is used when the text applies to both technologies. abbreviation is used when the text applies to both technologies.
VPLS A-D: refers to Virtual Private LAN Services with BGP-based Auto VPLS A-D: refers to Virtual Private LAN Services with BGP-based Auto
Discovery as in [RFC6074]. Discovery as in [RFC6074].
PW: Pseudowire. PW: Pseudowire
I-SID: Ethernet Services Instance Identifier
2. Requirements 2. Requirements
Following are the key requirements for backward compatibility between Following are the key requirements for backward compatibility between
(PBB-)EVPN and (PBB-)VPLS: (PBB-)EVPN and (PBB-)VPLS:
1. The solution MUST allow for staged migration towards (PBB-)EVPN on 1. The solution MUST allow for staged migration towards (PBB-)EVPN on
a site-by-site basis per VPN instance - e.g., new EVPN sites to be a site-by-site basis per VPN instance - e.g., new EVPN sites to be
provisioned on (PBB-)EVPN Provider Edge devices (PEs). provisioned on (PBB-)EVPN Provider Edge devices (PEs).
skipping to change at page 7, line 4 skipping to change at page 6, line 44
PEs and (PBB-)VPLS PEs is outside the scope of this document. PEs and (PBB-)VPLS PEs is outside the scope of this document.
These requirements collectively allow for the seamless insertion of These requirements collectively allow for the seamless insertion of
the (PBB-)EVPN technology into brown-field (PBB-)VPLS deployments. the (PBB-)EVPN technology into brown-field (PBB-)VPLS deployments.
3 VPLS Integration with EVPN 3 VPLS Integration with EVPN
In order to support seamless integration with VPLS PEs, this document In order to support seamless integration with VPLS PEs, this document
requires that VPLS PEs support VPLS A-D per [RFC6074] and EVPN PEs requires that VPLS PEs support VPLS A-D per [RFC6074] and EVPN PEs
support both BGP EVPN routes per [RFC7432] and VPLS A-D per support both BGP EVPN routes per [RFC7432] and VPLS A-D per
[RFC6074]. All the logic for seamless integration shall reside on the
[RFC6074]. All the logic for seamless integration SHALL reside on the
EVPN PEs. If a VPLS instance is setup without the use of VPLS A-D, it EVPN PEs. If a VPLS instance is setup without the use of VPLS A-D, it
is still possible (but cumbersome) for EVPN PEs to integrate into is still possible (but cumbersome) for EVPN PEs to integrate into
that VPLS instance by manually configuring Pseudowires (PWs) to all that VPLS instance by manually configuring Pseudowires (PWs) to all
the VPLS PEs in that instance (i.e., the integration is no longer the VPLS PEs in that instance (i.e., the integration is no longer
seamless). seamless).
3.1 Capability Discovery 3.1 Capability Discovery
The EVPN PEs MUST advertise both the BGP VPLS Auto-Discovery (A-D) The EVPN PEs MUST advertise both the BGP VPLS Auto-Discovery (A-D)
route as well as the BGP EVPN Inclusive Multicast Ethernet Tag (IMET) route as well as the BGP EVPN Inclusive Multicast Ethernet Tag (IMET)
skipping to change at page 7, line 47 skipping to change at page 7, line 40
only PEs. only PEs.
3.2 Forwarding Setup and Unicast Operation 3.2 Forwarding Setup and Unicast Operation
The procedures for forwarding state setup and unicast operation on The procedures for forwarding state setup and unicast operation on
the VPLS PE are per [RFC8077], [RFC4761], [RFC4762]. the VPLS PE are per [RFC8077], [RFC4761], [RFC4762].
The procedures for forwarding state setup and unicast operation on The procedures for forwarding state setup and unicast operation on
the EVPN PE are as follows: the EVPN PE are as follows:
- The EVPN PE MUST establish a PW to a remote PE from which it has - The EVPN PE MUST establish a PW to each remote PE from which it has
received only a VPLS A-D route for the corresponding VPN instance, received only a VPLS A-D route for the corresponding VPN instance,
and MUST set up the label stack corresponding to the PW FEC. For and MUST set up the label stack corresponding to the PW FEC. For
seamless integration between EVPN and VPLS PEs, the PW that is setup seamless integration between EVPN and VPLS PEs, the PW that is setup
between a pair of VPLS and EVPN PEs is between the VSI of the VPLS PE between a pair of VPLS and EVPN PEs is between the VSI of the VPLS PE
and the MAC-VRF of the EVPN PE. and the MAC-VRF of the EVPN PE.
- The EVPN PE must set up the label stack corresponding to the MP2P - The EVPN PE must set up the label stack corresponding to the MP2P
VPN unicast FEC to any remote PE that has advertised EVPN IMET route. VPN unicast FEC to any remote PE that has advertised EVPN IMET route.
- If an EVPN PE receives a VPLS A-D route followed by an EVPN IMET - If an EVPN PE receives a VPLS A-D route from a given PE, it sets up
route from the same PE and a PW is already setup to that PE, then the a PW to that PE. If it then receives an EVPN IMET route from the same
EVPN MUST bring that PW operationally down. PE, then the EVPN PE MUST bring that PW operationally down.
- If an EVPN PE receives an EVPN IMET route followed by a VPLS A-D - If an EVPN PE receives an EVPN IMET route followed by a VPLS A-D
route from the same PE, then the EVPN PE will setup the PW but MUST route from the same PE, then the EVPN PE will setup the PW but MUST
keep it operationally down. keep it operationally down.
- In case VPLS AD is not used in some VPLS PEs, the EVPN PEs need to - In case VPLS AD is not used in some VPLS PEs, the EVPN PEs need to
be provisioned manually with PWs to those remote VPLS PEs for each be provisioned manually with PWs to those remote VPLS PEs for each
VPN instance. In that case, if an EVPN PE receives an EVPN IMET route VPN instance. In that case, if an EVPN PE receives an EVPN IMET route
from a PE to which a PW exists, the PW will be brought operationally from a PE to which a PW exists, the EVPN PE MUST bring the PW
down. operationally down.
When the EVPN PE receives traffic over the VPLS PWs, it learns the When the EVPN PE receives traffic over the VPLS PWs, it learns the
associated C-MAC addresses in the data-plane. The C-MAC addresses associated C-MAC addresses in the data-plane. The C-MAC addresses
learned over these PWs MUST be injected into the bridge table of the learned over these PWs MUST be injected into the bridge table of the
associated MAC-VRF on that EVPN PE. The learned C-MAC addresses MAY associated MAC-VRF on that EVPN PE. The learned C-MAC addresses MAY
also be injected into the RIB/FIB tables of the associated MAC-VRF on also be injected into the RIB/FIB tables of the associated MAC-VRF on
that EVPN PE. For seamless integration between EVPN and VPLS PEs, that EVPN PE. For seamless integration between EVPN and VPLS PEs,
since these PWs belong to the same split-horizon group as the MP2P since these PWs belong to the same split-horizon group as the MP2P
EVPN service tunnels, then the C-MAC addresses learned and associated EVPN service tunnels, then the C-MAC addresses learned and associated
to the PWs will NOT be advertised in the control plane to any remote to the PWs MUST NOT be advertised in the control plane to any remote
EVPN PEs. This is because every EVPN PE can send and receive traffic EVPN PEs. This is because every EVPN PE can send and receive traffic
directly to/from every VPLS PE belonging to the same VPN instance. directly to/from every VPLS PE belonging to the same VPN instance.
The C-MAC addresses learned over local Attachment Circuits (ACs) by The C-MAC addresses learned over local Attachment Circuits (ACs) by
an EVPN PE are learned in data-plane. For EVPN PEs, these C-MAC an EVPN PE are learned in data-plane. For EVPN PEs, these C-MAC
addresses MUST be injected into the corresponding MAC-VRF and addresses MUST be injected into the corresponding MAC-VRF and
advertised in the control-plane using BGP EVPN routes. Furthermore, advertised in the control-plane using BGP EVPN routes. Furthermore,
the C-MAC addresses learned in the control plane via the BGP EVPN the C-MAC addresses learned in the control plane via the BGP EVPN
routes sent by remote EVPN PEs, are injected into the corresponding routes sent by remote EVPN PEs, are injected into the corresponding
MAC-VRF table. MAC-VRF table.
skipping to change at page 10, line 16 skipping to change at page 10, line 11
The procedures for multicast operation on the EVPN PEs using P2MP The procedures for multicast operation on the EVPN PEs using P2MP
tunnels are outside of the scope of this document. tunnels are outside of the scope of this document.
4 PBB-VPLS Integration with PBB-EVPN 4 PBB-VPLS Integration with PBB-EVPN
In order to support seamless integration between PBB-VPLS and PBB- In order to support seamless integration between PBB-VPLS and PBB-
EVPN PEs, this document requires that PBB-VPLS PEs support VPLS A-D EVPN PEs, this document requires that PBB-VPLS PEs support VPLS A-D
per [RFC6074] and PBB-EVPN PEs support both BGP EVPN routes per per [RFC6074] and PBB-EVPN PEs support both BGP EVPN routes per
[RFC7432] and VPLS A-D per [RFC6074]. All the logic for this seamless [RFC7432] and VPLS A-D per [RFC6074]. All the logic for this seamless
integration SHALL reside on the PBB-EVPN PEs. integration shall reside on the PBB-EVPN PEs.
4.1 Capability Discovery 4.1 Capability Discovery
The procedures for capability discovery are per Section 3.1 above. The procedures for capability discovery are per Section 3.1 above.
4.2 Forwarding Setup and Unicast Operation 4.2 Forwarding Setup and Unicast Operation
The procedures for forwarding state setup and unicast operation on The procedures for forwarding state setup and unicast operation on
the PBB-VPLS PE are per [RFC8077] and [RFC7080]. the PBB-VPLS PE are per [RFC8077] and [RFC7080].
The procedures for forwarding state setup and unicast operation on The procedures for forwarding state setup and unicast operation on
the PBB-EVPN PE are similar to that of section 3.2 except for the the PBB-EVPN PE are as follows:
following:
- For seamless integration between EVPN and VPLS PEs, the PW that is - The PBB-EVPN PE MUST establish a PW to each remote PBB-VPLS PE from
setup between a pair of PBB-VPLS and PBB-EVPN PEs, is between B- which it has received only a VPLS A-D route for the corresponding VPN
components of PBB-EVPN PE and PBB-VPLS PE per section 4 of instance, and MUST set up the label stack corresponding to the PW
FEC. For seamless integration between PBB-EVPN and PBB-VPLS PEs, the
PW that is setup between a pair of PBB-VPLS and PBB-EVPN PEs, is
between B-components of PBB-EVPN PE and PBB-VPLS PE per section 4 of
[RFC7041]. [RFC7041].
- The PBB-EVPN PE must set up the label stack corresponding to the
MP2P VPN unicast FEC to any remote PBB-EVPN PE that has advertised
EVPN IMET route.
- If a PBB-EVPN PE receives a VPLS A-D route from a given PE, it sets
up a PW to that PE. If it then receives an EVPN IMET route from the
same PE, then the PBB-EVPN PE MUST bring that PW operationally down.
- If a PBB-EVPN PE receives an EVPN IMET route followed by a VPLS A-D
route from the same PE, then the PBB-EVPN PE will setup the PW but
MUST keep it operationally down.
- In case VPLS AD is not used in some PBB-VPLS PEs, the PBB-EVPN PEs
need to be provisioned manually with PWs to those remote PBB-VPLS PEs
for each VPN instance. In that case, if a PBB-EVPN PE receives an
EVPN IMET route from a PE to which a PW exists, the PBB-EVPN PE MUST
bring the PW operationally down.
- When the PBB-EVPN PE receives traffic over the PBB-VPLS PWs, it - When the PBB-EVPN PE receives traffic over the PBB-VPLS PWs, it
learns the associated B-MAC addresses in the data-plane. The B-MAC learns the associated B-MAC addresses in the data-plane. The B-MAC
addresses learned over these PWs MUST be injected into the bridge addresses learned over these PWs MUST be injected into the bridge
table of the associated MAC-VRF on that PBB-EVPN PE. The learned B- table of the associated MAC-VRF on that PBB-EVPN PE. The learned B-
MAC addresses MAY also be injected into the RIB/FIB tables of the MAC addresses MAY also be injected into the RIB/FIB tables of the
associated the MAC-VRF on that BPP-EVPN PE. For seamless integration associated the MAC-VRF on that BPP-EVPN PE. For seamless integration
between PBB-EVPN and PBB-VPLS PEs, since these PWs belongs to the between PBB-EVPN and PBB-VPLS PEs, since these PWs belongs to the
same split-horizon group as the MP2P EVPN service tunnels, then the same split-horizon group as the MP2P EVPN service tunnels, then the
B-MAC addresses learned and associated to the PWs will NOT be B-MAC addresses learned and associated to the PWs MUST NOT be
advertised in the control plane to any remote PBB-EVPN PEs. This is advertised in the control plane to any remote PBB-EVPN PEs. This is
because every PBB-EVPN PE can send and receive traffic directly because every PBB-EVPN PE can send and receive traffic directly
to/from every PBB-VPLS PE belonging to the same VPN instance. to/from every PBB-VPLS PE belonging to the same VPN instance.
- The C-MAC addresses learned over local Attachment Circuits (ACs) by - The C-MAC addresses learned over local Attachment Circuits (ACs) by
an PBB-EVPN PE are learned in data-plane. For PBB-EVPN PEs, these C- an PBB-EVPN PE are learned in data-plane. For PBB-EVPN PEs, these C-
MAC addresses are learned in I-component of PBB-EVPN PEs and they are MAC addresses are learned in I-component of PBB-EVPN PEs and they are
not advertised in the control-plane per [RFC7623]. not advertised in the control-plane per [RFC7623].
- The B-MAC addresses learned in the control plane via the BGP EVPN - The B-MAC addresses learned in the control plane via the BGP EVPN
routes sent by remote PBB-EVPN PEs, are injected into the routes sent by remote PBB-EVPN PEs, are injected into the
corresponding MAC-VRF table. corresponding MAC-VRF table.
4.3 MAC Mobility 4.3 MAC Mobility
In PBB-EVPN, a given B-MAC address can be learnt either over the BGP In PBB-EVPN, a given B-MAC address can be learnt either over the BGP
control-plane from a remote PBB-EVPN PE, or in the data-plane over a control-plane from a remote PBB-EVPN PE, or in the data-plane over a
PW from a remote PBB-VPLS PE. There is no mobility associated with B- PW from a remote PBB-VPLS PE. There is no mobility associated with B-
MAC addresses in this context. Hence, when the same B-MAC address MAC addresses in this context. Hence, when the same B-MAC address
shows up behind both a remote PBB-VPLS PE as well as a PBB-EVPN PE, shows up behind both a remote PBB-VPLS PE as well as a PBB-EVPN PE,
the local PE can deduce that it is an anomaly and notify the the local PE can deduce that it is an anomaly and SHOULD notify the
operator. operator.
4.4 Multicast Operation 4.4 Multicast Operation
4.4.1 Ingress Replication 4.4.1 Ingress Replication
The procedures for multicast operation on the PBB-VPLS PE, using The procedures for multicast operation on the PBB-VPLS PE, using
ingress replication, are per [RFC7041] and [RFC7080]. ingress replication, are per [RFC7041] and [RFC7080].
The procedures for multicast operation on the PBB-EVPN PE, for The procedures for multicast operation on the PBB-EVPN PE, for
skipping to change at page 11, line 43 skipping to change at page 12, line 9
exchange of the EVPN IMET routes, as described in [RFC7623]. This exchange of the EVPN IMET routes, as described in [RFC7623]. This
will be referred to as sub-list A. It comprises MP2P service tunnels will be referred to as sub-list A. It comprises MP2P service tunnels
used for delivering PBB-EVPN BUM traffic. used for delivering PBB-EVPN BUM traffic.
- The PBB-EVPN PE builds a replication sub-list per VPN instance to - The PBB-EVPN PE builds a replication sub-list per VPN instance to
all the remote PBB-VPLS PEs. This will be referred to as sub-list B. all the remote PBB-VPLS PEs. This will be referred to as sub-list B.
It comprises PWs from the PBB-EVPN PE in question to all the remote It comprises PWs from the PBB-EVPN PE in question to all the remote
PBB-VPLS PEs in the same VPN instance. PBB-VPLS PEs in the same VPN instance.
- The PBB-EVPN PE may further prune sub-list B, on a per I-SID basis, - The PBB-EVPN PE may further prune sub-list B, on a per I-SID basis,
if [MMRP] is run over the PBB-VPLS network. This will be referred to by running [MMRP] over the PBB-VPLS network. This will be referred to
as sub-list C. This list comprises a pruned set of the PWs in the as sub-list C. This list comprises a pruned set of the PWs in the
sub-list B. sub-list B.
The replication list maintained per I-SID on a given PBB-EVPN PE will The replication list maintained per I-SID on a given PBB-EVPN PE will
be the union of sub-list A and sub-list B if [MMRP] is NOT used, and be the union of sub-list A and sub-list B if [MMRP] is not used, and
the union of sub-list A and sub-list C if [MMRP] is used. Note that the union of sub-list A and sub-list C if [MMRP] is used. Note that
the PE must enable split-horizon over all the entries in the the PE must enable split-horizon over all the entries in the
replication list, across both pseudowires and MP2P service tunnels. replication list, across both pseudowires and MP2P service tunnels.
4.4.2 P2MP Tunnel - Inclusive Tree 4.4.2 P2MP Tunnel - Inclusive Tree
The procedures for multicast operation on the PBB-EVPN PEs using P2MP The procedures for multicast operation on the PBB-EVPN PEs using P2MP
tunnels are outside of the scope of this document. tunnels are outside of the scope of this document.
5 Security Considerations 5 Security Considerations
 End of changes. 25 change blocks. 
44 lines changed or deleted 61 lines changed or added

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