draft-ietf-bess-evpn-vpws-11.txt   draft-ietf-bess-evpn-vpws-12.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: September 13, 2017 March 12, 2017 Expires: October 16, 2017 April 14, 2017
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-11.txt draft-ietf-bess-evpn-vpws-12.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 traditional way of Pseudowire (PW) signaling, and provides
fast protection convergence upon node or link failure. fast protection convergence upon node or link failure.
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, and this VNI may have VXLAN Network Identifier (VNI) for VXLAN encap as per [RFC7348], and
a global scope or local scope per PE and may also be equal to the this VNI will have a local scope per PE and may also be equal to the
VPWS service instance identifier set in the Ethernet A-D route. VPWS service instance identifier set in the Ethernet A-D route. When
using VXLAN encap, the BGP Encapsulation extended community is
included in the Ethernet A-D route as described in [ietf-evpn-
overlay].
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 7, line 22 skipping to change at page 7, line 24
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 defines a new extended community [RFC4360], to be included This document defines a new extended community [RFC4360], to be
with per-EVI Ethernet A-D routes. This attribute is mandatory if included with per-EVI Ethernet A-D routes. This attribute is
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) |
+------------------------------------+ +------------------------------------+
| Reserved (2 octets) | | Reserved (2 octets) |
+------------------------------------+ +------------------------------------+
skipping to change at page 13, line 9 skipping to change at page 13, line 9
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 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008, IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC7348] Mahalingam, M., et al, "VXLAN: A Framework for Overlaying
Virtualized Layer 2 Networks over Layer 3 Networks", RFC 7348, August
2014
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://www.mef.net/Assets/Technical_Specifications/PDF/MEF_6.1.pdf https://www.mef.net/Assets/Technical_Specifications/PDF/MEF_6.1.pdf
[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>.
 End of changes. 5 change blocks. 
8 lines changed or deleted 15 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/