draft-ietf-bess-evpn-vpws-02.txt   draft-ietf-bess-evpn-vpws-03.txt 
INTERNET-DRAFT Sami Boutros INTERNET-DRAFT Sami Boutros
Intended Status: Standard Track Ali Sajassi Intended Status: Standard Track VMware
Ali Sajassi
Samer Salam Samer Salam
Cisco Systems Cisco Systems
John Drake John Drake
Juniper Networks Juniper Networks
Jeff Tantsura Jeff Tantsura
Ericsson Ericsson
Dirk Steinberg Dirk Steinberg
Steinberg Consulting Steinberg Consulting
Thomas Beckhaus Thomas Beckhaus
Deutsche Telecom Deutsche Telecom
J. Rabadan J. Rabadan
Alcatel-Lucent Alcatel-Lucent
Expires: April 17, 2016 October 15, 2015 Expires: September 17, 2016 March 16, 2016
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-02.txt draft-ietf-bess-evpn-vpws-03.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 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 18 skipping to change at page 2, line 19
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright and License Notice Copyright and License Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(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
skipping to change at page 2, line 45 skipping to change at page 2, line 46
1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 6 2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 6 2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 6
2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 7 2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 7
2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 7 2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 7
2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 7 2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 7
2.4 Flexible CrossConnect Service . . . . . . . . . . . . . . . 7 2.4 Flexible CrossConnect Service . . . . . . . . . . . . . . . 7
3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 8 3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 9 3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 9
4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 11 5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 12
6 ESI Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 12 6 ESI Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 12
7 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 12 7 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 12
7.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 13 7.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 13
7.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 13 7.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 13
8 VPWS with multiple sites . . . . . . . . . . . . . . . . . . . . 13 8 VPWS with multiple sites . . . . . . . . . . . . . . . . . . . . 13
9 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13 9 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
10 Security Considerations . . . . . . . . . . . . . . . . . . . . 13 10 Security Considerations . . . . . . . . . . . . . . . . . . . . 13
11 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 13 11 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 13
12 References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 12 References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
12.1 Normative References . . . . . . . . . . . . . . . . . . . 13 12.1 Normative References . . . . . . . . . . . . . . . . . . . 13
12.2 Informative References . . . . . . . . . . . . . . . . . . 13 12.2 Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
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
skipping to change at page 7, line 38 skipping to change at page 7, line 38
group of VLANs on a specific port to the MPLS LSP. The MPLS- group of VLANs on a specific port to the MPLS LSP. The MPLS-
encapsulated frames MUST remain tagged with the originating VID. encapsulated frames MUST remain tagged with the originating VID.
2.2.1 Port-Based Service Interface 2.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 mapped to the same interface, where all of the VLANs on the port are mapped to the same
VPWS service instance identifier. The procedures are identical to VPWS service instance identifier. The procedures are identical to
those described in Section 6.2. those described in Section 6.2.
2.3 VLAN-Aware Bundle Service Interface Contrary to EVPN, in EVPN-VPWS 2.3 VLAN-Aware Bundle Service Interface
this service interface maps to VLAN-based service interface (defined
in section 6.1) and thus this service interface is not used in EVPN-
VPWS. In other words, if one tries to define data-plane and control
plane behavior for this service interface, he would realize that it
is the same as that of VLAN-based service.
2.4 Flexible CrossConnect Service This service provides the ultimate Contrary to EVPN, in EVPN-VPWS this service interface maps to VLAN-
flexibility at the expense of additional lookup. With this EVPN-VPWS based service interface (defined in section 6.1) and thus this
service a large number of attachments circuits (ACs), each of which service interface is not used in EVPN-VPWS. In other words, if one
represented by either single VLAN tag or double VLAN tags (QinQ) tries to define data-plane and control plane behavior for this
across multiple endpoints, are multiplexed in a single EVPN-VPWS service interface, he would realize that it is the same as that of
service instance. An endpoint can be a physical interface, VSI, an VLAN-based service.
IP-VRF, a MAC-VRF, or any other endpoint where cross-connection of
the associated AC is desired. Because in this service mode, 2.4 Flexible CrossConnect Service
aggregation is performed across multiple endpoints, besides MPLS
label, an additional VLAN ID lookup (either single tag or double tag) This service provides the ultimate flexibility at the expense of
needs to be performed at the disposition PE in order to identify the additional lookup. With this EVPN-VPWS service a large number of
destination endpoint. One can think of this as, the EVPN label attachments circuits (ACs), each of which represented by either
identifies a cross-connect table and then a single tag (or double single VLAN tag or double VLAN tags (QinQ) across multiple endpoints,
tag) lookup is performed to identify the endpoint. Each cross-connect are multiplexed in a single EVPN-VPWS service instance. An endpoint
table has its own unique VLAN space which mean it can have upto 4K can be a physical interface, VSI, an IP-VRF, a MAC-VRF, or any other
single-tag VLAN (or upto 16M double-tag VLANs). VLAN IDs can be endpoint where cross-connection of the associated AC is desired.
overlap across different cross-connect tables but MUST be unique Because in this service mode, aggregation is performed across
within a table. multiple endpoints, besides MPLS label, an additional VLAN ID lookup
(either single tag or double tag) needs to be performed at the
disposition PE in order to identify the destination endpoint. One can
think of this as, the EVPN label identifies a cross-connect table and
then a single tag (or double tag) lookup is performed to identify the
endpoint. Each cross-connect table has its own unique VLAN space
which mean it can have upto 4K single-tag VLAN (or upto 16M double-
tag VLANs). VLAN IDs can be overlap across different cross-connect
tables but MUST be unique within a table.
The EVPN label besides identifying the cross-connect table, also The EVPN label besides identifying the cross-connect table, also
identifies the following types of VID look-ups: Single VID lookup: identifies the following types of VID look-ups: Single VID lookup:
The disposition PE MUST support single VID lookup where upon outer- The disposition PE MUST support single VID lookup where upon outer-
VID lookup, the destination end-point is identified. Double VID VID lookup, the destination end-point is identified. Double VID
lookup: The disposition PE MUST support double VID lookup where upon lookup: The disposition PE MUST support double VID lookup where upon
outer most two VIDs lookup, the destination end-point is identified. outer most two VIDs lookup, the destination end-point is identified.
Wildcard VID Lookup: The disposition PE MAY support special double Wildcard VID Lookup: The disposition PE MAY support special double
VID lookup where the first VID is outer most VID and the 2nd VID is VID lookup where the first VID is outer most VID and the 2nd VID is
skipping to change at page 14, line 24 skipping to change at page 14, line 26
[RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service [RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service
(VPLS) Using BGP for Auto-Discovery and Signaling", RFC4761, January (VPLS) Using BGP for Auto-Discovery and Signaling", RFC4761, January
2007. 2007.
[draft-ietf-idr-link-bandwidth] P. Mohapatra, R. Fernando, "BGP Link [draft-ietf-idr-link-bandwidth] P. Mohapatra, R. Fernando, "BGP Link
Bandwidth Extended Community", draft-ietf-idr-link-bandwidth-06.txt Bandwidth Extended Community", draft-ietf-idr-link-bandwidth-06.txt
Authors' Addresses Authors' Addresses
Sami Boutros Sami Boutros
Cisco VMware, Inc.
Email: sboutros@cisco.com Email: sboutros@vmware.com
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
Samer Salam Samer Salam
Cisco Cisco
Email: ssalam@cisco.com Email: ssalam@cisco.com
John Drake John Drake
 End of changes. 10 change blocks. 
33 lines changed or deleted 37 lines changed or added

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