< draft-boutros-l2vpn-evpn-vpws-04.txt   draft-boutros-l2vpn-evpn-vpws-05.txt >
skipping to change at page 1, line 20 skipping to change at page 1, line 20
Jeff Tantsura Jeff Tantsura
Ericsson Ericsson
Dirk Steinberg Dirk Steinberg
Steinberg Consulting Steinberg Consulting
Thomas Beckhaus Thomas Beckhaus
Deutsche Telecom Deutsche Telecom
Expires: January 3, 2015 July 2, 2014 Expires: April 24, 2015 October 21, 2014
VPWS support in E-VPN VPWS support in E-VPN
draft-boutros-l2vpn-evpn-vpws-04.txt draft-boutros-l2vpn-evpn-vpws-05.txt
Abstract Abstract
This document describes how E-VPN can be used to support virtual This document describes how E-VPN can be used to support virtual
private wire service (VPWS) in MPLS/IP networks. E-VPN enables the private wire service (VPWS) in MPLS/IP networks. E-VPN enables the
following characteristics for VPWS: single-active as well as all- following characteristics for VPWS: single-active as well as all-
active multi-homing with flow-based load-balancing, eliminates the active multi-homing with flow-based load-balancing, eliminates the
need for single-segment and multi-segment PW signaling, and provides need for single-segment and multi-segment PW signaling, and provides
fast protection using data-plane prefix independent convergence upon fast protection using data-plane prefix independent convergence upon
node or link failure. node or link failure.
skipping to change at page 2, line 36 skipping to change at page 2, line 36
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
2. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 5 2. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 7 4 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 7
5 ESI Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 7 5 ESI Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 7
6 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 8
6.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 8
6.1 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 8
7 VPWS with multiple sites . . . . . . . . . . . . . . . . . . . . 8 7 VPWS with multiple sites . . . . . . . . . . . . . . . . . . . . 8
8 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8 8 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
9 Security Considerations . . . . . . . . . . . . . . . . . . . . 8 9 Security Considerations . . . . . . . . . . . . . . . . . . . . 8
10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11 References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11 References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1 Normative References . . . . . . . . . . . . . . . . . . . 8 11.1 Normative References . . . . . . . . . . . . . . . . . . . 9
11.2 Informative References . . . . . . . . . . . . . . . . . . 8 11.2 Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Introduction 1 Introduction
This document describes how EVPN can be used to support virtual This document describes how EVPN can be used to support virtual
private wire service (VPWS) in MPLS/IP networks. The use of EVPN private wire service (VPWS) in MPLS/IP networks. The use of EVPN
mechanisms for VPWS brings the benefits of EVPN to p2p services. mechanisms for VPWS brings the benefits of EVPN to p2p services.
These benefits include single-active redundancy as well as all-active These benefits include single-active redundancy as well as all-active
redundancy with flow-based load-balancing. Furthermore, the use of redundancy with flow-based load-balancing. Furthermore, the use of
EVPN for VPWS eliminates the need for signaling single-segment and EVPN for VPWS eliminates the need for signaling single-segment and
multi-segment PWs for p2p Ethernet services. multi-segment PWs for p2p Ethernet services.
skipping to change at page 8, line 9 skipping to change at page 8, line 9
for the Bandwidth requested by this EVPL service. for the Bandwidth requested by this EVPL service.
In the case where PSN resources are not available, the PE receiving In the case where PSN resources are not available, the PE receiving
this attribute MUST re-send its local Ethernet AD routes for this this attribute MUST re-send its local Ethernet AD routes for this
EVPL service with the ESI Bandwidth = All FFs to declare that the EVPL service with the ESI Bandwidth = All FFs to declare that the
"PSN Resources Unavailable". "PSN Resources Unavailable".
The scope of the ESI Bandwidth is limited to only one Autonomous The scope of the ESI Bandwidth is limited to only one Autonomous
System. System.
6 Failure Scenarios
On a link or port failure between the CE and the PE for both single
and multi-homed CEs, the PE must withdraw all the associated Ethernet
AD routes for the VPWS service instances on the failed port or link.
6.1 Single-Homed CEs
Unlike [EVPN], EVPN-VPWS uses Ethernet AD route advertisements for
single-homed Ethernet Segments. Therefore, upon a link/port failure
of this single-homed Ethernet Segment, the PE MUST withdraw the
associated Ethernet A-D routes.
6.1 Multi-Homed CEs
For a faster convergence in multi-homed scenarios with either Single-
Active Redundancy or All-active redundancy, mass withdraw technique
as per [EVPN] baseline is used. A PE previously advertising an
Ethernet A-D per ES route, can withdraw this route signaling to the
remote PEs to switch all the VPWS service instances associated with
this multi-homed ES to the backup PE
7 VPWS with multiple sites 7 VPWS with multiple sites
The VPWS among multiple sites (full mesh of P2P connections - one per The VPWS among multiple sites (full mesh of P2P connections - one per
pair of sites) that can be setup automatically without any explicit pair of sites) that can be setup automatically without any explicit
provisioning of P2P connections among the sites is outside the scope provisioning of P2P connections among the sites is outside the scope
of this document. of this document.
8 Acknowledgements 8 Acknowledgements
The authors would like to acknowledge Wen Lin contributions to this The authors would like to acknowledge Wen Lin contributions to this
 End of changes. 5 change blocks. 
5 lines changed or deleted 30 lines changed or added

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