draft-ietf-bess-evpn-vpws-08.txt   draft-ietf-bess-evpn-vpws-09.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 11, 2017 February 7, 2017 Expires: August 25, 2017 February 21, 2017
VPWS support in EVPN VPWS support in EVPN
draft-ietf-bess-evpn-vpws-08.txt draft-ietf-bess-evpn-vpws-09.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 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
1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . 7 2.2.1 Port-Based Service Interface . . . . . . . . . . . . . . 6
2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 7 2.3 VLAN-Aware Bundle Service Interface . . . . . . . . . . . . 6
3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 7 3. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 8 3.1 EVPN Layer 2 attributes extended community . . . . . . . . . 7
4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5 EVPN Comparison to PW Signaling . . . . . . . . . . . . . . . . 11 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 . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 12 10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1 Normative References . . . . . . . . . . . . . . . . . . . 12 10.1 Normative References . . . . . . . . . . . . . . . . . . . 12
10.2 Informative References . . . . . . . . . . . . . . . . . . 13 10.2 Informative References . . . . . . . . . . . . . . . . . . 12
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
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 (EVPN-VPWS) brings the benefits of EVPN to p2p mechanisms for VPWS (EVPN-VPWS) brings the benefits of EVPN to p2p
services. These benefits include single-active redundancy as well as services. These benefits include single-active redundancy as well as
all-active redundancy with flow-based load-balancing. Furthermore, all-active redundancy with flow-based load-balancing. Furthermore,
skipping to change at page 3, line 34 skipping to change at page 3, line 34
forwarding capability of EVPN based on the exchange of a pair of forwarding capability of EVPN based on the exchange of a pair of
Ethernet Auto-discovery (A-D) routes is used; whereas, for more Ethernet Auto-discovery (A-D) routes is used; whereas, for more
general VPWS as per [RFC4664], traffic forwarding capability of EVPN general VPWS as per [RFC4664], traffic forwarding capability of EVPN
based on the exchange of a group of Ethernet AD routes (one Ethernet based on the exchange of a group of Ethernet AD routes (one Ethernet
AD route per AC/ES) is used. In a VPWS service, the traffic from an AD route per AC/ES) is used. In a VPWS service, the traffic from an
originating Ethernet Segment can be forwarded only to a single originating Ethernet Segment can be forwarded only to a single
destination Ethernet Segment; hence, no MAC lookup is needed and the destination Ethernet Segment; hence, no MAC lookup is needed and the
MPLS label associated with the per EVPN instance (EVI) Ethernet A-D MPLS label associated with the per EVPN instance (EVI) Ethernet A-D
route can be used in forwarding user traffic to the destination AC. route can be used in forwarding user traffic to the destination AC.
Both services are supported by using the per EVI Ethernet A-D route For both EPL and EVPL services, a specific VPWS service instance is
which contains an Ethernet Segment Identifier, in which the customer identified by a pair of per EVI Ethernet A-D routes which together
ES is encoded, and an Ethernet Tag, in which the VPWS service identify the VPWS service instance endpoints and the VPWS service
instance identifier is encoded. I.e., for both EPL and EVPL instance. In the control plane the VPWS service instance is
services, a specific VPWS service instance is identified by a pair of identified using the VPWS service instance identifiers advertised by
per EVI Ethernet A-D routes which together identify the VPWS service each PE and in the data plane the value of the MPLS label advertised
instance endpoints and the VPWS service instance. In the control by one PE is used by the other PE to send traffic for that VPWS
plane the VPWS service instance is identified using the VPWS service service instance. As with the Ethernet Tag in standard EVPN, the VPWS
instance identifiers advertised by each PE and in the data plane the service instance identifier has uniqueness within an EVPN instance.
value of the MPLS label advertised by one PE is used by the other PE
to send traffic for that VPWS service instance. As with the Ethernet
Tag in standard EVPN, the VPWS service instance identifier has
uniqueness within an EVPN instance.
Unlike EVPN where Ethernet Tag ID in EVPN routes are set to zero for Unlike EVPN where Ethernet Tag ID in EVPN routes are set to zero for
Port-based, vlan-based, and vlan-bundle interface mode and it is set Port-based, vlan-based, and vlan-bundle interface mode and it is set
to non-zero Ethernet tag ID for vlan-aware bundle mode, in EVPN-VPWS, to non-zero Ethernet tag ID for vlan-aware bundle mode, in EVPN-VPWS,
for all the four interface modes, Ethernet tag ID in the Ethernet A-D for all the four interface modes, Ethernet tag ID in the Ethernet A-D
route MUST be set to a non-zero value in all the service interface route MUST be set to a non-zero value in all the service interface
types. types.
In terms of route advertisement and MPLS label lookup behavior, EVPN- In terms of route advertisement and MPLS label lookup behavior, EVPN-
VPWS resembles the vlan-aware bundle mode of [RFC7432] such that when VPWS resembles the vlan-aware bundle mode of [RFC7432] such that when
a PE advertises per EVI Ethernet A-D route, the VPWS service instance a PE advertises per EVI Ethernet A-D route, the VPWS service instance
serves as a 24-bit normalized Ethernet tag ID. The value of the MPLS serves as a 32-bit normalized Ethernet tag ID. The value of the MPLS
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 lookup of the MPLS disposition PE can identify the egress AC from the lookup of the MPLS
label alone and perform any required tag translation. For EVPL label alone and perform any required tag translation. For EVPL
service, the Ethernet frames transported over an MPLS/IP network service, the Ethernet frames transported over an MPLS/IP network
SHOULD remain tagged with the originating Vlan-ID (VID) and any VID SHOULD remain tagged with the originating Vlan-ID (VID) and any VID
translation MUST be performed at the disposition PE. For EPL service, translation MUST be performed at the disposition PE. For EPL service,
the Ethernet frames are transported as is and the tags are not the Ethernet frames are transported as is and the tags are not
altered. altered.
skipping to change at page 5, line 45 skipping to change at page 5, line 41
multi-homed device for a given VLAN, then such multi-homing or multi-homed device for a given VLAN, then such multi-homing or
redundancy is referred to as "All-Active". redundancy is referred to as "All-Active".
VPWS Service Instance: It is represented by a pair of EVPN service VPWS Service Instance: It is represented by a pair of EVPN service
labels associated with a pair of endpoints. Each label is downstream labels associated with a pair of endpoints. Each label is downstream
assigned and advertised by the disposition PE through an Ethernet A-D assigned and advertised by the disposition PE through an Ethernet A-D
per-EVI route. The downstream label identifies the endpoint on the per-EVI route. The downstream label identifies the endpoint on the
disposition PE. A VPWS service instance can be associated with only disposition PE. A VPWS service instance can be associated with only
one VPWS service identifier. one VPWS service identifier.
1.2 Requirements
1. EPL service access circuit MUST map to the whole Ethernet port.
2. EVPL service access circuit MUST map to an individual VLAN or
double tagged <S-VLAN,C-VLAN> combination on a given trunk port,
without any direct dependency on any other VLANs on the same trunk.
Other VLANs on the same trunk MAY also be used for EVPL services, but
MAY also be associated with other services.
3. If multiple VLANs on the same trunk are associated with EVPL
services, the respective remote endpoints of these EVPLs MAY be
dispersed across any number of PEs, i.e. different VLANs MAY lead to
different destinations.
4. The VLAN tag on the access trunk MUST only have PE-local
significance. The VLAN tag on the remote end could be different, and
could also be double tagged when the other side is single tagged.
5. Also, multiple EVPL service VLANs on the same trunk MAY belong to
the same EVPN instance (EVI), or they MAY belong to different EVIs.
This should be purely an administrative choice of the network
operator.
6. A given PE MAY have thousands of EVPLs configured. It MUST be
possible to configure multiple EVPL services within the same EVI.
7. Local access circuits configured to belong to a given EVPN
instance MAY also belong to different physical access trunks.
8. EP-LAN and EVP-LAN MAY be possible on the same system and also
ESIs can be shared between EVPL and EVP-LANs.
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
skipping to change at page 7, line 34 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 24-bit VPWS service instance identifier value. For both EPL and the VPWS service instance identifier value. For both EPL and EVPL
EVPL services, for a given VPWS service instance the pair of PEs services, for a given VPWS service instance the pair of PEs
instantiating that VPWS service instance will each advertise a per instantiating that VPWS service instance will each advertise a per
EVI Ethernet A-D route with its VPWS service instance identifier and EVI Ethernet A-D route with its VPWS service instance identifier and
will each be configured with the other PE's VPWS service instance will each be configured with the other PE's VPWS service instance
identifier. When each PE has received the other PE's per EVI Ethernet identifier. When each PE has received the other PE's per EVI Ethernet
A-D route the VPWS service instance is instantiated. It should be A-D route the VPWS service instance is instantiated. It should be
noted that the same VPWS service instance identifier may be noted that the same VPWS service instance identifier may be
configured on both PEs. 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, to be This draft proposes a new extended community, defined below as per
[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) |
+------------------------------------+ +------------------------------------+
| Reserved (2 octets) | | Reserved (2 octets) |
+------------------------------------+ +------------------------------------+
Figure 1: EVPN Layer 2 attributes extended community
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ |C|P|B| (MBZ = MUST Be Zero) | MBZ |C|P|B| (MBZ = MUST Be Zero)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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.
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 octets. MTU in bytes.
A received L2 MTU=0 means no MTU checking against local MTU is A received L2 MTU=0 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, both B and P flags MUST NOT be both set. A
PE that receives an update with both B and P flags set MUST treat the PE 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
unset, it MUST NOT forward any traffic to the sender PE. unset, it MUST discard the received route 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 bit to 1. A remote PE will do per-flow to/from the CE will set the P Flag to 1. A remote PE will do per-flow
load balancing to the PEs that send P=1 for the same Ethernet Tag and load balancing to the PEs that send P=1 for the same Ethernet Tag and
ESI. B bit in control flags SHOULD not be set in the multihoming all- ESI. B Flag in control flags SHOULD NOT be set in the multihoming
active scenario and MUST be ignored by receiving PE(s) if set. all-active scenario and MUST be ignored by receiving PE(s) if set.
In multihoming single-active scenario, the DF election will determine
who the primary and the backup PEs are, and only those PEs will set
the P bit and B bit respectively. A remote PE will forward the
traffic to the primary PE and switch over to the backup PE as soon as
it receives an Ethernet A-D route withdrawal from the primary PE in
the Ethernet Segment.
In multihoming single-active scenario, during transient situations, a In multihoming single-active scenario, for a given VPWS service
remote PE receiving P=1 from more than one PE will select the last instance, in steady state, as result of DF election, the Primary
advertising PE as the primary PE when forwarding traffic. A remote PE elected PE for the VPWS service instance should signal P=1,B=0, the
receiving B=1 from more than one PE will select only one backup PE. A Backup elected PE should signal P=0,B=1, and the rest of the PEs in
remote PE MUST receive P=1 from at least one PE before forwarding the same ES should signal P=0,B=0. When the primary PE/ES fails, the
traffic. primary PE will withdraw the associated Ethernet A-D routes for the
VPWS service instance from the remote PE, the remote PEs should then
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
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
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
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
will select only one backup PE. A remote PE MUST receive P=1 from at
least one PE before forwarding traffic.
If a network uses entropy labels per [RFC6790] then the C Bit 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.
4 Operation 4 Operation
The following figure shows an example of a P2P service deployed with The following figure shows an example of a P2P service deployed with
EVPN. EVPN.
Ethernet Ethernet Ethernet Ethernet
Native |<--------- EVPN Instance ----------->| Native Native |<--------- EVPN Instance ----------->| Native
Service | | Service Service | | Service
(AC) | |<-PSN1->| |<-PSN2->| | (AC) (AC) | |<-PSN1->| |<-PSN2->| | (AC)
skipping to change at page 10, line 15 skipping to change at page 9, line 35
| |-------+-----+ +-----+ +-----+ +-----+-------| | | |-------+-----+ +-----+ +-----+ +-----+-------| |
+----+ | | PE2 |======|ASBR3|==|ASBR4|===| PE4 | | +----+ +----+ | | PE2 |======|ASBR3|==|ASBR4|===| PE4 | | +----+
^ +-----+ +-----+ +-----+ +-----+ ^ ^ +-----+ +-----+ +-----+ +-----+ ^
| Provider Edge 1 ^ Provider Edge 2 | | Provider Edge 1 ^ Provider Edge 2 |
| | | | | |
| | | | | |
| EVPN Inter-provider point | | EVPN Inter-provider point |
| | | |
|<---------------- Emulated Service -------------------->| |<---------------- Emulated Service -------------------->|
Figure 1: EVPN-VPWS Deployement Model Figure 3: EVPN-VPWS Deployment Model
iBGP sessions are established between PE1, PE2, ASBR1 and ASBR3, iBGP sessions are established between PE1, PE2, ASBR1 and ASBR3,
possibly via a BGP route-reflector. Similarly, iBGP sessions are possibly via a BGP route-reflector. Similarly, iBGP sessions are
established between PE3, PE4, ASBR2 and ASBR4. eBGP sessions are established between PE3, PE4, ASBR2 and ASBR4. eBGP sessions are
established among ASBR1, ASBR2, ASBR3, and ASBR4. established among ASBR1, ASBR2, ASBR3, and ASBR4.
All PEs and ASBRs are enabled for the EVPN SAFI and exchange per EVI All PEs and ASBRs are enabled for the EVPN SAFI and exchange per EVI
Ethernet A-D routes, one route per VPWS service instance. For inter- Ethernet A-D routes, one route per VPWS service instance. For inter-
AS option B, the ASBRs re-advertise these routes with NEXT_HOP AS option B, the ASBRs re-advertise these routes with NEXT_HOP
attribute set to their IP addresses as per [RFC4271]. The link attribute set to their IP addresses as per [RFC4271]. The link
between the CE and the PE is either a C-tagged or S-tagged interface, between the CE and the PE is either a C-tagged or S-tagged interface,
skipping to change at page 12, line 31 skipping to change at page 12, line 4
The mechanisms in this document use EVPN control plane as defined in The mechanisms in this document use EVPN control plane as defined in
[RFC7432]. Security considerations described in [RFC7432] are equally [RFC7432]. Security considerations described in [RFC7432] are equally
applicable. applicable.
This document uses MPLS and IP-based tunnel technologies to support This document uses MPLS and IP-based tunnel technologies to support
data plane transport. Security considerations described in [RFC7432] data plane transport. Security considerations described in [RFC7432]
and in [ietf-evpn-overlay] are equally applicable. and in [ietf-evpn-overlay] are equally applicable.
9 IANA Considerations 9 IANA Considerations
IANA has allocated the following EVPN Extended Community sub-type: IANA has allocated the following EVPN Extended Community sub-type:
SUB-TYPE VALUE NAME Reference SUB-TYPE VALUE NAME Reference
0x04 EVPN Layer 2 attributes [RFCXXXX] 0x04 EVPN Layer 2 attributes [RFCXXXX]
This document creates a registry called "EVPN Layer 2 attributes
Control Flags". New registrations will be made through the "RFC
Required" procedure defined in [RFC5226].
Initial registrations are as follows:
P Advertising PE is the Primary PE.
B Advertising PE is the Backup PE.
C Control word [RFC4448] MUST be present
10 References 10 References
10.1 Normative References 10.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March
1997, <http://www.rfc-editor.org/info/rfc2119>. 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet
skipping to change at page 13, line 4 skipping to change at page 12, line 36
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet
VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc- VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc-
editor.org/info/rfc7432>. editor.org/info/rfc7432>.
[RFC4448] Martini, L., Rosen, E., El-Aawar, N., and G. Heron, [RFC4448] Martini, L., Rosen, E., El-Aawar, N., and G. Heron,
"Encapsulation Methods for Transport of Ethernet over MPLS Networks", "Encapsulation Methods for Transport of Ethernet over MPLS Networks",
RFC 4448, April 2006. RFC 4448, April 2006.
[RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and L. [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and L.
Yong, "The Use of Entropy Labels in MPLS Forwarding", November 2012. Yong, "The Use of Entropy Labels in MPLS Forwarding", November 2012.
[RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP Extended
Communities", RFC 7153, March 2014, <http://www.rfc-
editor.org/info/rfc7153>.
[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>.
[RFC4664] Andersson, L., Ed., and E. Rosen, Ed., "Framework for [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006, Communities Attribute", RFC 4360, February 2006, <http://www.rfc-
<http://www.rfc-editor.org/info/rfc4664>. editor.org/info/rfc4360>.
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,
<http://metroethernetforum.org/Assets/Technical_Specifications/PDF/ https://urldefense.proofpoint.com/v2/url?u=https-
MEF6-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
Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006,
<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
In addition to the authors listed on the front page, the following In addition to the authors listed on the front page, the following
co-authors have also contributed to this document: co-authors have also contributed to this document:
 End of changes. 27 change blocks. 
97 lines changed or deleted 80 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/