draft-ietf-bess-evpn-vpws-12.txt   draft-ietf-bess-evpn-vpws-13.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
INTERNET-DRAFT Sami Boutros INTERNET-DRAFT Sami Boutros
Intended Status: Standard Track VMware Intended Status: Standard Track VMware
Ali Sajassi Ali Sajassi
Samer Salam Samer Salam
Cisco Systems Cisco Systems
John Drake John Drake
Juniper Networks Juniper Networks
J. Rabadan J. Rabadan
Nokia Nokia
Expires: October 16, 2017 April 14, 2017 Expires: November 5, 2017 May 4, 2017
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-12.txt draft-ietf-bess-evpn-vpws-13.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 Pseudowire (PW) signaling, and provides need for Pseudowire (PW) signaling, and provides fast protection
fast protection convergence upon node or link failure. convergence upon node or link failure.
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 21 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 5 2 Service interface . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 5 2.1 VLAN-Based Service Interface . . . . . . . . . . . . . . . . 6
2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 6 2.2 VLAN Bundle Service Interface . . . . . . . . . . . . . . . 6
2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 6 2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 6
2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 6 2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 6
3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 6 3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 7 3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 7
4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 10 5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 10
6 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 11 6 Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11 6.1 Single-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11
6.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11 6.2 Multi-Homed CEs . . . . . . . . . . . . . . . . . . . . . . 11
7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11 7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12
8 Security Considerations . . . . . . . . . . . . . . . . . . . . 11 8 Security Considerations . . . . . . . . . . . . . . . . . . . . 12
9 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12 9 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12
10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1 Normative References . . . . . . . . . . . . . . . . . . . 12 10.1 Normative References . . . . . . . . . . . . . . . . . . . 12
10.2 Informative References . . . . . . . . . . . . . . . . . . 13 10.2 Informative References . . . . . . . . . . . . . . . . . . 13
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
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
skipping to change at page 4, line 15 skipping to change at page 4, line 15
label in this route represents both the EVI and the VPWS service label in this route represents both the EVI and the VPWS service
instance, so that upon receiving an MPLS encapsulated packet, the instance, so that upon receiving an MPLS encapsulated packet, the
disposition PE can identify the egress AC from the MPLS label and disposition PE can identify the egress AC from the MPLS label and
subsequently perform any required tag translation. For EVPL service, subsequently perform any required tag translation. For EVPL service,
the Ethernet frames transported over an MPLS/IP network SHOULD remain the Ethernet frames transported over an MPLS/IP network SHOULD remain
tagged with the originating VLAN-ID (VID) and any VID translation tagged with the originating VLAN-ID (VID) and any VID translation
MUST be performed at the disposition PE. For EPL service, the MUST be performed at the disposition PE. For EPL service, the
Ethernet frames are transported as is and the tags are not altered. Ethernet frames are transported as is and the tags are not altered.
The MPLS label value in the Ethernet A-D route can be set to the The MPLS label value in the Ethernet A-D route can be set to the
VXLAN Network Identifier (VNI) for VXLAN encap as per [RFC7348], and Virtual Extensible LAN (VXLAN) Network Identifier (VNI) for VXLAN
this VNI will have a local scope per PE and may also be equal to the encap as per [RFC7348], and this VNI will have a local scope per PE
VPWS service instance identifier set in the Ethernet A-D route. When and may also be equal to the VPWS service instance identifier set in
using VXLAN encap, the BGP Encapsulation extended community is the Ethernet A-D route. When using VXLAN encap, the BGP Encapsulation
included in the Ethernet A-D route as described in [ietf-evpn- extended community is included in the Ethernet A-D route as described
overlay]. in [ietf-evpn-overlay]. The VXLAN VNI like the MPLS label that will
be set in the tunnel header used to tunnel Ethernet packets from all
the service interface types defined in section 2. The EVPN-VPWS
techniques defined in this document has no dependency on the
tunneling technology.
The Ethernet Segment identifier encoded in the Ethernet A-D per-EVI The Ethernet Segment identifier encoded in the Ethernet A-D per-EVI
route is not used to identify the service. However it can be used for route is not used to identify the service. However it can be used for
flow-based load-balancing and mass withdraw functions as per the flow-based load-balancing and mass withdraw functions as per the
[RFC7432] baseline. [RFC7432] baseline.
As with standard EVPN, the Ethernet A-D per-ES route is used for fast As with standard EVPN, the Ethernet A-D per-ES route is used for fast
convergence upon link or node failure. The Ethernet Segment route is convergence upon link or node failure. The Ethernet Segment route is
used for auto-discovery of the PEs attached to a given multi-homed CE used for auto-discovery of the PEs attached to a given multi-homed CE
and to synchronize state between them. and to synchronize state between them.
skipping to change at page 5, line 21 skipping to change at page 5, line 27
S-VLAN: Service VLAN identifier. S-VLAN: Service VLAN identifier.
C-VLAN: Customer VLAN identifier. C-VLAN: Customer VLAN identifier.
VID: VLAN-ID. VID: VLAN-ID.
VPWS: Virtual Private Wire Service. VPWS: Virtual Private Wire Service.
EVI: EVPN Instance. EVI: EVPN Instance.
P2P: Point to Point.
VXLAN: Virtual Extensible LAN.
ES: Ethernet Segment on a PE refers to the link attached to it, this ES: Ethernet Segment on a PE refers to the link attached to it, this
link can be part of a set of links attached to different PEs in multi link can be part of a set of links attached to different PEs in multi
homed cases, or could be a single link in single homed cases. homed cases, or could be a single link in single homed cases.
ESI: Ethernet Segment Identifier. ESI: Ethernet Segment Identifier.
Single-Active Mode: When a device or a network is multi-homed to two Single-Active Mode: When a device or a network is multi-homed to two
or more PEs and when only a single PE in such redundancy group can or more PEs and when only a single PE in such redundancy group can
forward traffic to/from the multi-homed device or network for a given forward traffic to/from the multi-homed device or network for a given
VLAN, then such multi-homing or redundancy is referred to as "Single- VLAN, then such multi-homing or redundancy is referred to as "Single-
skipping to change at page 8, line 4 skipping to change at page 8, line 14
| MBZ |C|P|B| (MBZ = MUST Be Zero) | MBZ |C|P|B| (MBZ = MUST Be Zero)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: EVPN Layer 2 attributes Control Flags Figure 2: EVPN Layer 2 attributes Control Flags
The following bits in the Control Flags are defined; the remaining The following bits in the Control Flags are defined; the remaining
bits MUST be set to zero when sending and MUST be ignored when bits MUST be set to zero when sending and MUST be ignored when
receiving this community. receiving this community.
Name Meaning Name Meaning
P If set to 1 in multihoming single-active scenarios, it P If set to 1 in multihoming single-active scenarios, it
indicates that the advertising PE is the Primary PE. indicates that the advertising PE is the Primary PE.
MUST be set to 1 for multihoming all-active scenarios by MUST be set to 1 for multihoming all-active scenarios by
all active PE(s). all active PE(s).
B If set to 1 in multihoming single-active scenarios, it B If set to 1 in multihoming single-active scenarios, it
indicates that the advertising PE is the Backup PE. indicates that the advertising PE is the Backup PE.
C If set to 1, a Control word [RFC4448] MUST be present C If set to 1, a Control word [RFC4448] MUST be present
when sending EVPN packets to this PE. when sending EVPN packets to this PE. It is recommended to
include the control word in the absence of Entropy Label.
L2 MTU (Maximum Transmission Unit) is a 2-octet value indicating the L2 MTU (Maximum Transmission Unit) is a 2-octet value indicating the
MTU in bytes. MTU in bytes.
A received L2 MTU of zero means no MTU checking against local MTU is A received L2 MTU of zero means no MTU checking against local MTU is
needed. A received non-zero MTU MUST be checked against local MTU and needed. A received non-zero MTU MUST be checked against local MTU and
if there is a mismatch, the local PE MUST NOT add the remote PE as if there is a mismatch, the local PE MUST NOT add the remote PE as
the EVPN destination for the corresponding VPWS service instance. the EVPN destination for the corresponding VPWS service instance.
The usage of the Per ES Ethernet A-D route is unchanged from its The usage of the Per ES Ethernet A-D route is unchanged from its
usage in [RFC7432], i.e., the "Single-Active" bit in the flags of the usage in [RFC7432], i.e., the "Single-Active" bit in the flags of the
ESI Label extended community will indicate if single-active or all- ESI Label extended community will indicate if single-active or all-
active redundancy is used for this ES. active redundancy is used for this ES.
In multihoming scenarios, both B and P flags MUST NOT be both set. A In multihoming scenarios, the B and P flags MUST be cleared. A PE
PE that receives an update with both B and P flags set MUST treat the that receives an update with both B and P flags set MUST treat the
route as a withdrawal. If the PE receives a route with both B and P route as a withdrawal. If the PE receives a route with both B and P
clear, it MUST treat the route as a withdrawal from the sender PE. clear, it MUST treat the route as a withdrawal from the sender PE.
In a multihoming all-active scenario, there is no DF election, and In a multihoming all-active scenario, there is no DF election, and
all the PEs in the ES that are active and ready to forward traffic all the PEs in the ES that are active and ready to forward traffic
to/from the CE will set the P Flag. A remote PE will do per-flow to/from the CE will set the P Flag. A remote PE will do per-flow
load-balancing to the PEs that set the P Flag for the same Ethernet load-balancing to the PEs that set the P Flag for the same Ethernet
Tag and ESI. The B Flag in control flags SHOULD NOT be set in the Tag and ESI. The B Flag in control flags SHOULD NOT be set in the
multihoming all-active scenario and MUST be ignored by receiving multihoming all-active scenario and MUST be ignored by receiving
PE(s) if set. PE(s) if set.
 End of changes. 11 change blocks. 
18 lines changed or deleted 28 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/