draft-ietf-bess-evpn-vpws-09.txt   draft-ietf-bess-evpn-vpws-10.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: August 25, 2017 February 21, 2017 Expires: September 1, 2017 February 28, 2017
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-09.txt draft-ietf-bess-evpn-vpws-10.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 5, line 51 skipping to change at page 5, line 51
2 Service interface 2 Service interface
2.1 VLAN-Based Service Interface 2.1 VLAN-Based Service Interface
With this service interface, a VPWS instance identifier corresponds With this service interface, a VPWS instance identifier corresponds
to only a single VLAN on a specific interface. Therefore, there is a to only a single VLAN on a specific interface. Therefore, there is a
one-to-one mapping between a VID on this interface and the VPWS one-to-one mapping between a VID on this interface and the VPWS
service instance identifier. The PE provides the cross-connect service instance identifier. The PE provides the cross-connect
functionality between MPLS LSP identified by the VPWS service functionality between MPLS LSP identified by the VPWS service
instance identifier and a specific <port,VLAN>. If the VLAN is instance identifier and a specific <port,VLAN>. If the VLAN is
represented by different VIDs on different PEs. (e.g., a different represented by different VIDs on different PEs and different ES(es)
VID per Ethernet segment per PE), then each PE needs to perform VID (e.g., a different VID per Ethernet segment per PE), then each PE
translation for frames destined to its Ethernet segment. In such needs to perform VID translation for frames destined to its Ethernet
scenarios, the Ethernet frames transported over an MPLS/IP network segment. In such scenarios, the Ethernet frames transported over an
SHOULD remain tagged with the originating VID, and a VID translation MPLS/IP network SHOULD remain tagged with the originating VID, and a
MUST be supported in the data path and MUST be performed on the VID translation MUST be supported in the data path and MUST be
disposition PE. performed on the disposition PE.
2.2 VLAN Bundle Service Interface 2.2 VLAN Bundle Service Interface
With this service interface, a VPWS service instance identifier With this service interface, a VPWS service instance identifier
corresponds to multiple VLANs on a specific interface. The PE corresponds to multiple VLANs on a specific interface. The PE
provides the cross-connect functionality between MPLS label provides the cross-connect functionality between MPLS label
identified by the VPWS service instance identifier and a group of identified by the VPWS service instance identifier and a group of
VLANs on a specific interface. For this service interface, each VLAN VLANs on a specific interface. For this service interface, each VLAN
is presented by a single VID which means no VLAN translation is is presented by a single VID which means no VLAN translation is
allowed. The receiving PE, can direct the traffic based on EVPN label allowed. The receiving PE, can direct the traffic based on EVPN label
skipping to change at page 6, line 46 skipping to change at page 6, line 46
service interface is not used in EVPN-VPWS. In other words, if one service interface is not used in EVPN-VPWS. In other words, if one
tries to define data-plane and control plane behavior for this tries to define data-plane and control plane behavior for this
service interface, he would realize that it is the same as that of service interface, he would realize that it is the same as that of
VLAN-based service. VLAN-based service.
3. BGP Extensions 3. BGP Extensions
This document specifies the use of the per EVI Ethernet A-D route to This document specifies the use of the per EVI Ethernet A-D route to
signal VPWS services. The Ethernet Segment Identifier field is set to signal VPWS services. The Ethernet Segment Identifier field is set to
the customer ES and the Ethernet Tag ID 32-bit field MUST be set to the customer ES and the Ethernet Tag ID 32-bit field MUST be set to
the VPWS service instance identifier value. For both EPL and EVPL the VPWS service instance identifier value, the VPWS service instance
services, for a given VPWS service instance the pair of PEs identifier value MAY be set to a 24-bit value, when 24-bit value is
instantiating that VPWS service instance will each advertise a per used, it MUST be right aligned. For both EPL and EVPL services, for a
EVI Ethernet A-D route with its VPWS service instance identifier and given VPWS service instance the pair of PEs instantiating that VPWS
will each be configured with the other PE's VPWS service instance service instance will each advertise a per EVI Ethernet A-D route
identifier. When each PE has received the other PE's per EVI Ethernet with its VPWS service instance identifier and will each be configured
A-D route the VPWS service instance is instantiated. It should be with the other PE's VPWS service instance identifier. When each PE
noted that the same VPWS service instance identifier may be has received the other PE's per EVI Ethernet A-D route the VPWS
configured on both PEs. service instance is instantiated. It should be noted that the same
VPWS service instance identifier may be configured on both PEs.
The Route-Target (RT) extended community with which the per EVI The Route-Target (RT) extended community with which the per EVI
Ethernet A-D route is tagged identifies the EVPN instance in which Ethernet A-D route is tagged identifies the EVPN instance in which
the VPWS service instance is configured. It is the operator's choice the VPWS service instance is configured. It is the operator's choice
as to how many and which VPWS service instances are configured in a as to how many and which VPWS service instances are configured in a
given EVPN instance. However, a given EVPN instance MUST NOT be given EVPN instance. However, a given EVPN instance MUST NOT be
configured with both VPWS service instances and standard EVPN multi- configured with both VPWS service instances and standard EVPN multi-
point services. point services.
3.1 EVPN Layer 2 attributes extended community 3.1 EVPN Layer 2 attributes extended community
This draft proposes a new extended community, defined below as per This draft proposes a new extended community [RFC4360], to be
[RFC7432] in addition to the values specified in [RFC4360], to be
included with the per EVI Ethernet A-D route. This attribute is included with the per EVI Ethernet A-D route. This attribute is
mandatory if multihoming is enabled. mandatory if multihoming is enabled.
+------------------------------------+ +------------------------------------+
| Type(0x06)/Sub-type(0x04)(2 octet)| | Type(0x06)/Sub-type(0x04)(2 octet)|
+------------------------------------+ +------------------------------------+
| Control Flags (2 octets) | | Control Flags (2 octets) |
+------------------------------------+ +------------------------------------+
| L2 MTU (2 octets) | | L2 MTU (2 octets) |
+------------------------------------+ +------------------------------------+
skipping to change at page 8, line 48 skipping to change at page 8, line 48
instance, in steady state, as result of DF election, the Primary instance, in steady state, as result of DF election, the Primary
elected PE for the VPWS service instance should signal P=1,B=0, the elected PE for the VPWS service instance should signal P=1,B=0, the
Backup elected PE should signal P=0,B=1, and the rest of the PEs in Backup elected PE should signal P=0,B=1, and the rest of the PEs in
the same ES should signal P=0,B=0. When the primary PE/ES fails, the the same ES should signal P=0,B=0. When the primary PE/ES fails, the
primary PE will withdraw the associated Ethernet A-D routes for the primary PE will withdraw the associated Ethernet A-D routes for the
VPWS service instance from the remote PE, the remote PEs should then VPWS service instance from the remote PE, the remote PEs should then
send traffic associated with the VPWS instance to the backup PE. DF send traffic associated with the VPWS instance to the backup PE. DF
re-election will happen between the PE(s) in the same ES, and there re-election will happen between the PE(s) in the same ES, and there
will be a new elected primary PE and new elected backup PE that will will be a new elected primary PE and new elected backup PE that will
signal the P and B Flags as described. A remote PE SHOULD receive P=1 signal the P and B Flags as described. A remote PE SHOULD receive P=1
from only one Primary PE and a B-1 from only one Backup PE. However from only one Primary PE and a B=1 from only one Backup PE. However
during transient situations, a remote PE receiving P=1 from more than during transient situations, a remote PE receiving P=1 from more than
one PE will select the last advertising PE as the primary PE when one PE will select the last advertising PE as the primary PE when
forwarding traffic. A remote PE receiving B=1 from more than one PE forwarding traffic. A remote PE receiving B=1 from more than one PE
will select only one backup PE. A remote PE MUST receive P=1 from at will select only one backup PE. A remote PE MUST receive P=1 from at
least one PE before forwarding traffic. least one PE before forwarding traffic.
If a network uses entropy labels per [RFC6790] then the C Flag MUST If a network uses entropy labels per [RFC6790] then the C Flag MUST
NOT be set to 1 and control word MUST NOT be used when sending EVPN- NOT be set to 1 and control word MUST NOT be used when sending EVPN-
encapsulated packets over a P2P LSP. encapsulated packets over a P2P LSP.
skipping to change at page 10, line 15 skipping to change at page 10, line 15
label will identify the VPWS service instance and if translation is label will identify the VPWS service instance and if translation is
needed, it should be done by the Ethernet interface for each service. needed, it should be done by the Ethernet interface for each service.
For single-homed CE, in an advertised per EVI Ethernet A-D route the For single-homed CE, in an advertised per EVI Ethernet A-D route the
ESI field is set to 0 and the Ethernet Tag ID is set to the VPWS ESI field is set to 0 and the Ethernet Tag ID is set to the VPWS
service instance identifier that identifies the EVPL or EPL service. service instance identifier that identifies the EVPL or EPL service.
For a multi-homed CE, in an advertised per EVI Ethernet A-D route the For a multi-homed CE, in an advertised per EVI Ethernet A-D route the
ESI field is set to the CE's ESI and the Ethernet Tag ID is set to ESI field is set to the CE's ESI and the Ethernet Tag ID is set to
the VPWS service instance identifier, which MUST have the same value the VPWS service instance identifier, which MUST have the same value
on all PEs attached to that ES. This allows an ingress PE to perform on all PEs attached to that ES. This allows an ingress PE in a
flow-based load-balancing of traffic flows to all of the PEs attached multihoming all-active scenario to perform flow-based load-balancing
to that ES. In all cases traffic follows the transport paths, which of traffic flows to all of the PEs attached to that ES. In all cases
may be asymmetric. traffic follows the transport paths, which may be asymmetric.
The VPWS service instance identifier encoded in the Ethernet Tag ID The VPWS service instance identifier encoded in the Ethernet Tag ID
in an advertised per EVI Ethernet A-D route MUST either be unique in an advertised per EVI Ethernet A-D route MUST either be unique
across all ASs, or an ASBR needs to perform a translation when the across all ASs, or an ASBR needs to perform a translation when the
per EVI Ethernet A-D route is re-advertised by the ASBR from one AS per EVI Ethernet A-D route is re-advertised by the ASBR from one AS
to the other AS. to the other AS.
Per ES Ethernet A-D route can be used for mass withdraw to withdraw Per ES Ethernet A-D route can be used for mass withdraw to withdraw
all per EVI Ethernet A-D routes associated with the multi-home site all per EVI Ethernet A-D routes associated with the multi-home site
on a given PE. on a given PE.
skipping to change at page 12, line 46 skipping to change at page 12, line 46
Yong, "The Use of Entropy Labels in MPLS Forwarding", November 2012. Yong, "The Use of Entropy Labels in MPLS Forwarding", November 2012.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border
Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006, <http://www.rfc- Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006, <http://www.rfc-
editor.org/info/rfc4271>. editor.org/info/rfc4271>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, February 2006, <http://www.rfc- Communities Attribute", RFC 4360, February 2006, <http://www.rfc-
editor.org/info/rfc4360>. editor.org/info/rfc4360>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
10.2 Informative References 10.2 Informative References
[MEF] Metro Ethernet Forum, "Ethernet Services Definitions - Phase [MEF] Metro Ethernet Forum, "Ethernet Services Definitions - Phase
2", Technical Specification MEF 6.1, April 2008, 2", Technical Specification MEF 6.1, April 2008,
https://urldefense.proofpoint.com/v2/url?u=https- https://www.mef.net/Assets/Technical_Specifications/PDF/MEF_6.1.pdf
3A__www.mef.net_Assets_Technical-5FSpecifications_PDF_MEF-
5F6.1.pdf&d=DwIGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-
2K-LV98&m=GH5FIfqtBUACPwx-LVV2v5zPrGcNzhCEjfj8-0-
R2OI&s=5b19ceQDqdsz0TepqsV7daJoYm9uDMyco7BZ4NeICWU&e=
[RFC4664] Andersson, L., Ed., and E. Rosen, Ed., "Framework for [RFC4664] Andersson, L., Ed., and E. Rosen, Ed., "Framework for
Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006, Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006,
<http://www.rfc-editor.org/info/rfc4664>. <http://www.rfc-editor.org/info/rfc4664>.
[ietf-evpn-overlay] Sajassi-Drake et al., "A Network Virtualization [ietf-evpn-overlay] Sajassi-Drake et al., "A Network Virtualization
Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07.txt, Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07.txt,
work in progress, December, 2016 work in progress, December, 2016
Contributors Contributors
 End of changes. 9 change blocks. 
30 lines changed or deleted 30 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/