draft-ietf-bess-evpn-vpls-seamless-integ-06.txt   draft-ietf-bess-evpn-vpls-seamless-integ-07.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: July 21, 2019 January 21, 2019 Expires: July 31, 2019 January 31, 2019
(PBB-)EVPN Seamless Integration with (PBB-)VPLS (PBB-)EVPN Seamless Integration with (PBB-)VPLS
draft-ietf-bess-evpn-vpls-seamless-integ-06 draft-ietf-bess-evpn-vpls-seamless-integ-07
Abstract Abstract
This document specifies mechanisms for backward compatibility of This document specifies mechanisms for backward compatibility of
Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN (PBB- Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN (PBB-
EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider
Backbone Bridge VPLS (PBB-VPLS) solutions. It also provides Backbone Bridge VPLS (PBB-VPLS) solutions. It also provides
mechanisms for seamless integration of these two technologies in the mechanisms for seamless integration of these two technologies in the
same MPLS/IP network on a per-VPN-instance basis. Implementation of same MPLS/IP network on a per-VPN-instance basis. Implementation of
this document enables service providers to introduce EVPN/PBB-EVPN this document enables service providers to introduce EVPN/PBB-EVPN
skipping to change at page 2, line 30 skipping to change at page 2, line 30
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Specification of Requirements . . . . . . . . . . . . . . 5 1.1. Specification of Requirements . . . . . . . . . . . . . . 5
1.2. Terms and Abbreviations . . . . . . . . . . . . . . . . . 5 1.2. Terms and Abbreviations . . . . . . . . . . . . . . . . . 5
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 VPLS Integration with EVPN . . . . . . . . . . . . . . . . . . . 7 3 VPLS Integration with EVPN . . . . . . . . . . . . . . . . . . . 8
3.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 8 3.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 8
3.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 8 3.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 8
3.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 9 3.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 10 3.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 10
3.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 10 3.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 10
3.4.2 P2MP Tunnel . . . . . . . . . . . . . . . . . . . . . . 11 3.4.2 P2MP Tunnel . . . . . . . . . . . . . . . . . . . . . . 11
4 PBB-VPLS Integration with PBB-EVPN . . . . . . . . . . . . . . . 11 4 PBB-VPLS Integration with PBB-EVPN . . . . . . . . . . . . . . . 11
4.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 11 4.1 Capability Discovery . . . . . . . . . . . . . . . . . . . . 11
4.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 11 4.2 Forwarding Setup and Unicast Operation . . . . . . . . . . . 11
4.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 12 4.3 MAC Mobility . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 13 4.4 Multicast Operation . . . . . . . . . . . . . . . . . . . . 13
4.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 13 4.4.1 Ingress Replication . . . . . . . . . . . . . . . . . . 13
4.4.2 P2MP Tunnel - Inclusive Tree . . . . . . . . . . . . . . 13 4.4.2 P2MP Tunnel - Inclusive Tree . . . . . . . . . . . . . . 14
5 Security Considerations . . . . . . . . . . . . . . . . . . . . 13 5 Security Considerations . . . . . . . . . . . . . . . . . . . . 14
6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14 6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1 Normative References . . . . . . . . . . . . . . . . . . . 14 7.1 Normative References . . . . . . . . . . . . . . . . . . . 14
7.2 Informative References . . . . . . . . . . . . . . . . . . 15 7.2 Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Introduction 1 Introduction
Virtual Private LAN Service (VPLS) and Provider Backbone Bridging Virtual Private LAN Service (VPLS) and Provider Backbone Bridging
skipping to change at page 6, line 23 skipping to change at page 6, line 23
Ethernet segment (ES): Refers to the set of Ethernet links that Ethernet segment (ES): Refers to the set of Ethernet links that
connects a customer site (device or network) to one or more PEs. 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
FEC: Forwarding Equivalence Class FEC: Forwarding Equivalence Class
LSP: Label Switched Path
MHD: Multi-Homed Device MHD: Multi-Homed Device
MHN: Multi-Homed Network MHN: Multi-Homed Network
P2MP: Point-to-Multipoint P2MP: Point to Multipoint - a P2MP LSP typically refers to a LSP for
multicast traffic
MP2P: Multipoint to Point - a MP2P LSP typically refers to a LSP for
unicast traffic as the result of downstream-assigned label
PBB: Provider Backbone Bridge PBB: Provider Backbone Bridge
PE: Provider Edge device PE: Provider Edge device
VSI: Virtual Switch Instance VSI: Virtual Switch Instance
VPLS: Virtual Private LAN Service VPLS: Virtual Private LAN Service
Single-Active Redundancy Mode: When only a single PE, among all the Single-Active Redundancy Mode: When only a single PE, among all the
skipping to change at page 7, line 37 skipping to change at page 7, line 44
segments. segments.
4. The solution must support single-active redundancy of multi-homed 4. The solution must support single-active redundancy of multi-homed
networks and multi-homed devices for (PBB-)EVPN PEs. networks and multi-homed devices for (PBB-)EVPN PEs.
5. In case of single-active redundancy, the participant VPN instances 5. In case of single-active redundancy, the participant VPN instances
may span across both (PBB-)EVPN PEs and (PBB-)VPLS PEs as long as the may span across both (PBB-)EVPN PEs and (PBB-)VPLS PEs as long as the
MHD or MHN is connected to (PBB-)EVPN PEs. MHD or MHN is connected to (PBB-)EVPN PEs.
6. The support of All-Active redundancy mode across both (PBB-)EVPN 6. The support of All-Active redundancy mode across both (PBB-)EVPN
PEs and (PBB-)VPLS PEs is outside the scope of this document. PEs and (PBB-)VPLS PEs is outside the scope of this document. All-
Active redundancy is not applicable to VPLS and PBB-VPLS. Therefore,
when EVPN (or PBB-EVPN) PEs need to operate seamlessly with VPLS (or
PBB-VPLS) PEs, then they MUST use a redundancy mode that is
applicable to VPLS (or PBB-VPLS). This redundancy mode is Single-
Active.
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
 End of changes. 9 change blocks. 
9 lines changed or deleted 20 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/