draft-ietf-bess-evpn-vpws-05.txt   draft-ietf-bess-evpn-vpws-06.txt 
skipping to change at page 1, line 22 skipping to change at page 1, line 22
Dirk Steinberg Dirk Steinberg
Steinberg Consulting Steinberg Consulting
Thomas Beckhaus Thomas Beckhaus
Deutsche Telecom Deutsche Telecom
J. Rabadan J. Rabadan
Nokia Nokia
Expires: December 9, 2016 June 7, 2016 Expires: December 9, 2016 June 7, 2016
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-05.txt draft-ietf-bess-evpn-vpws-06.txt
Abstract Abstract
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. EVPN enables the Private Wire Service (VPWS) in MPLS/IP networks. EVPN 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 traditional way of PW signaling, and provides fast need for traditional way of PW signaling, and provides fast
protection convergence upon node or link failure. protection convergence upon node or link failure.
skipping to change at page 2, line 27 skipping to change at page 2, line 24
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 7 2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 7 2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 6
2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 7 2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 6
2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 7 2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 6
2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 8 2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 7
3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 8 3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 8 3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 7
4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 11 5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 10
6 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 12 6 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 12 6.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11
6.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 12 6.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11
7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12 7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11
8 Security Considerations . . . . . . . . . . . . . . . . . . . . 12 8 Security Considerations . . . . . . . . . . . . . . . . . . . . 11
9 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12 9 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1 Normative References . . . . . . . . . . . . . . . . . . . 13 10.1 Normative References . . . . . . . . . . . . . . . . . . . 12
10.2 Informative References . . . . . . . . . . . . . . . . . . 13 10.2 Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
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 traditional way of PW signaling EVPN for VPWS eliminates the need for traditional way of PW signaling
for p2p Ethernet services, as described in section 4. for p2p Ethernet services, as described in section 4.
 End of changes. 2 change blocks. 
23 lines changed or deleted 23 lines changed or added

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