draft-ietf-bess-evpn-virtual-eth-segment-01.txt   draft-ietf-bess-evpn-virtual-eth-segment-02.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Internet Working Group A. Sajassi Internet Working Group A. Sajassi
Internet Draft P. Brissette Internet Draft P. Brissette
Category: Standards Track Cisco Category: Standards Track Cisco
R. Schell R. Schell
Verizon Verizon
J. Drake J. Drake
Juniper Juniper
J. Rabadan J. Rabadan
Nokia Nokia
Expires: July 06, 2019 January 06, 2019 Expires: July 08, 2019 January 08, 2019
EVPN Virtual Ethernet Segment EVPN Virtual Ethernet Segment
draft-ietf-bess-evpn-virtual-eth-segment-01 draft-ietf-bess-evpn-virtual-eth-segment-02
Abstract Abstract
EVPN and PBB-EVPN introduce a family of solutions for multipoint EVPN and PBB-EVPN introduce a family of solutions for multipoint
Ethernet services over MPLS/IP network with many advanced Ethernet services over MPLS/IP network with many advanced
capabilities among which their multi-homing capabilities. These capabilities among which their multi-homing capabilities. These
solutions define two types of multi-homing for an Ethernet Segment solutions define two types of multi-homing for an Ethernet Segment
(ES): 1) Single-Active and 2) All-Active, where an Ethernet Segment (ES): 1) Single-Active and 2) All-Active, where an Ethernet Segment
is defined as a set of links between the multi-homed device/network is defined as a set of links between the multi-homed device/network
and the set of PE devices that they are connected to. and the set of PE devices that they are connected to.
skipping to change at page 3, line 14 skipping to change at page 3, line 14
5.1. Failure Handling for Single-Active vES in EVPN . . . . . . 15 5.1. Failure Handling for Single-Active vES in EVPN . . . . . . 15
5.2. EVC Failure Handling for Single-Active vES in PBB-EVPN . . 16 5.2. EVC Failure Handling for Single-Active vES in PBB-EVPN . . 16
5.3. Port Failure Handling for Single-Active vES's in EVPN . . . 17 5.3. Port Failure Handling for Single-Active vES's in EVPN . . . 17
5.4. Port Failure Handling for Single-Active vES's in PBB-EVPN . 17 5.4. Port Failure Handling for Single-Active vES's in PBB-EVPN . 17
5.5. Fast Convergence in PBB-EVPN . . . . . . . . . . . . . . . 18 5.5. Fast Convergence in PBB-EVPN . . . . . . . . . . . . . . . 18
6. BGP Encoding . . . . . . . . . . . . . . . . . . . . . . . . . 20 6. BGP Encoding . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. I-SID Extended Community . . . . . . . . . . . . . . . . . 21 6.1. I-SID Extended Community . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 21 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 21 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 21
10. Intellectual Property Considerations . . . . . . . . . . . . . 21 10. Intellectual Property Considerations . . . . . . . . . . . . . 22
11. Normative References . . . . . . . . . . . . . . . . . . . . . 21 11. Normative References . . . . . . . . . . . . . . . . . . . . . 22
12. Informative References . . . . . . . . . . . . . . . . . . . . 22 12. Informative References . . . . . . . . . . . . . . . . . . . . 22
13. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 13. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
[RFC7432] and [RFC7623] introduce a family of solutions for [RFC7432] and [RFC7623] introduce a family of solutions for
multipoint Ethernet services over MPLS/IP network with many advanced multipoint Ethernet services over MPLS/IP network with many advanced
capabilities among which their multi-homing capabilities. These capabilities among which their multi-homing capabilities. These
solutions define two types of multi-homing for an Ethernet Segment solutions define two types of multi-homing for an Ethernet Segment
(ES): 1) Single-Active and 2) All-Active, where an Ethernet Segment (ES): 1) Single-Active and 2) All-Active, where an Ethernet Segment
skipping to change at page 5, line 8 skipping to change at page 5, line 8
many of such EVCs (e.g., VLANs) can be aggregated on a single many of such EVCs (e.g., VLANs) can be aggregated on a single
physical External Network-to-Network Interface (ENNI). An ES that physical External Network-to-Network Interface (ENNI). An ES that
consists of a set of EVCs instead of physical links is referred to as consists of a set of EVCs instead of physical links is referred to as
a virtual ES (vES). Figure below depicts two PE devices (PE1 and PE2) a virtual ES (vES). Figure below depicts two PE devices (PE1 and PE2)
each with an ENNI where a number of vES's are aggregated on - each of each with an ENNI where a number of vES's are aggregated on - each of
which through its associated EVC. which through its associated EVC.
Carrier Carrier
Ethernet Ethernet
+-----+ Network +-----+ Network
| CE11|EVC1 +---------+ | CE11|EVC1 +---------+ <---- EVPN Network ----->
+-----+ \ | | +---+ +-----+ \ | | +---+
Cust. A \-0=========0--ENNI1| | Cust. A \-0=========0--ENNI1| |
+-----+ | | ENNI1| | +-------+ +---+ +-----+ | | ENNI1| | +-------+ +---+
| CE12|EVC2--0=========0--ENNI1|PE1|---| | | | | CE12|EVC2--0=========0--ENNI1|PE1|---| | | |
+-----+ | | ENNI1| | | |---|PE3|- +-----+ | | ENNI1| | | |---|PE3|-
| ==0--ENNI1| | |IP/MPLS| | | \ +---+ | ==0--ENNI1| | |IP/MPLS| | | \ +---+
+-----+ | / | +---+ |Network| +---+ \-| | +-----+ | / | +---+ |Network| +---+ \-| |
| CE22|EVC3--0==== / | | | |CE4| | CE22|EVC3--0==== / | | | |CE4|
+-----+ | X | | | +---+ | | +-----+ | X | | | +---+ | |
| / \ | +---+ | | | | /-| | | / \ | +---+ | | | | /-| |
skipping to change at page 6, line 11 skipping to change at page 6, line 11
may also be associated with tens or hundreds of All-Active vES's. may also be associated with tens or hundreds of All-Active vES's.
1.2 Virtual Ethernet Segments in Access MPLS Networks 1.2 Virtual Ethernet Segments in Access MPLS Networks
Other Service Providers (SPs) want to extend the concept of the Other Service Providers (SPs) want to extend the concept of the
physical links in an ES to individual Pseudowires (PWs) or to MPLS physical links in an ES to individual Pseudowires (PWs) or to MPLS
Label Switched Paths (LSPs) per [EVPN-VPWS] in Access MPLS networks. Label Switched Paths (LSPs) per [EVPN-VPWS] in Access MPLS networks.
Figure 2 illustrates this concept. Figure 2 illustrates this concept.
MPLS Aggregation MPLS Aggregation
Network Network
+-----+ +----------------+ <----EVPN Network-----> +-----+ +----------------+ <---- EVPN Network ----->
| CE11|EVC1 | | | CE11|EVC1 | |
+-----+ \+AG1--+ PW1 +-----+ +-----+ \+AG1--+ PW1 +-----+
Cust. A -0----|===========| | Cust. A -0----|===========| |
+-----+ | ---+===========| | +-------+ +---+ +-----+ | ---+===========| | +-------+ +---+
| CE12|EVC2-0/ | PW2 /\ | PE1 +---+ | | | | CE12|EVC2-0/ | PW2 /\ | PE1 +---+ | | |
+-----+ ++---+ ==||=| | | +---+PE3+- +-----+ ++---+ ==||=| | | +---+PE3+-
| //=||=| | |IP/MPLS| | | \ +---+ | //=||=| | |IP/MPLS| | | \ +---+
| // \/ ++----+ |Network| +---+ \-+ | | // \/ ++----+ |Network| +---+ \-+ |
+-----+EVC3 | PW3// LSP1 | | | |CE4| +-----+EVC3 | PW3// LSP1 | | | |CE4|
| CE13| +AG2--+===/PW4 | | | +---+ | | | CE13| +AG2--+===/PW4 | | | +---+ | |
skipping to change at page 9, line 29 skipping to change at page 9, line 29
3.3. Local Switching 3.3. Local Switching
Many vES's of different types can be aggregated on a single physical Many vES's of different types can be aggregated on a single physical
port on a PE device and some of these vES can belong to the same port on a PE device and some of these vES can belong to the same
service instance (or customer). This translates into the need for service instance (or customer). This translates into the need for
supporting local switching among the vES's of the same service supporting local switching among the vES's of the same service
instance on the same physical port (e.g., ENNI) of the PE. instance on the same physical port (e.g., ENNI) of the PE.
(R3a) A PE MUST support local switching among different vES's (R3a) A PE MUST support local switching among different vES's
belonging to the same service instance (or customer) on a single belonging to the same service instance (or customer) on a single
physical port. For example, in the above figure (1), PE1 MUST physical port. For example, in the above Figure 1, PE1 MUST support
support local switching between CE11 and CE12 (both belonging to local switching between CE11 and CE12 (both belonging to customer A)
customer A) that are mapped to two Single-homed vES's on ENNI1. that are mapped to two Single-homed vES's on ENNI1.
In case of Single-Active vES's, the local switching is performed In case of Single-Active vES's, the local switching is performed
among active EVCs belonging to the same service instance on the same among active EVCs belonging to the same service instance on the same
ENNI. ENNI.
3.4. EVC Service Types 3.4. EVC Service Types
A physical port (e.g., ENNI) of a PE can aggregate many EVCs each of A physical port (e.g., ENNI) of a PE can aggregate many EVCs each of
which is associated with a vES. Furthermore, an EVC may carry one or which is associated with a vES. Furthermore, an EVC may carry one or
more VLANs. Typically, an EVC carries a single VLAN and thus it is more VLANs. Typically, an EVC carries a single VLAN and thus it is
skipping to change at page 13, line 20 skipping to change at page 13, line 20
+----+\ | PE1| | IP/MPLS | | PE3| +----+ +----+\ | PE1| | IP/MPLS | | PE3| +----+
\ +----+ | Network | +----+ \ +----+ | Network | +----+
\ | | \ | |
EVC2\ +----+ | | EVC2\ +----+ | |
\ | | | | \ | | | |
\| PE2| | | \| PE2| | |
+----+ | | +----+ | |
/\ +--------------+ /\ +--------------+
|| ||
BEB BEB
<--802.1Q---> <---PBB over MPLS---> <--802.1Q-> <--802.1Q--><---------- PBB-EVPN --------><--802.1Q->
Figure 2: PBB-EVPN Network Figure 3: PBB-EVPN Network
4.1. EVPN DF Election for vES 4.1. EVPN DF Election for vES
The procedure for service carving for virtual Ethernet Segments is The procedure for service carving for virtual Ethernet Segments is
the same as the one outlined in section 8.5 of [RFC7432] except for the same as the one outlined in section 8.5 of [RFC7432] except for
the fact that ES is replaced with vES. For the sake of clarity and the fact that ES is replaced with vES. For the sake of clarity and
completeness, this procedure is repeated below: completeness, this procedure is repeated below:
1. When a PE discovers the vESI or is configured with the vESI 1. When a PE discovers the vESI or is configured with the vESI
associated with its attached vES, it advertises an Ethernet Segment associated with its attached vES, it advertises an Ethernet Segment
skipping to change at page 15, line 32 skipping to change at page 15, line 32
+-----+ | / | +---+ |Network| | | +---+ +-----+ | / | +---+ |Network| | | +---+
| |EVC2--0== | | | +---+ | |EVC2--0== | | | +---+
| CE2 | | | +---+ | | | CE2 | | | +---+ | |
| |EVC3--0=====0--ENNI2|PE2|---| | | |EVC3--0=====0--ENNI2|PE2|---| |
+-----+ | | | | +-------+ +-----+ | | | | +-------+
+-----+ +---+ +-----+ +---+
/\ /\ /\ /\ /\ /\
|| || || || || ||
A C E A C E
Figure 3: Failure Scenarios A,B,C,D and E Figure 4: Failure Scenarios A,B,C,D and E
5.1. Failure Handling for Single-Active vES in EVPN 5.1. Failure Handling for Single-Active vES in EVPN
When a PE connected to a Single-Active multi-homed Ethernet Segment When a PE connected to a Single-Active multi-homed Ethernet Segment
loses connectivity to the segment, due to link or port failure, it loses connectivity to the segment, due to link or port failure, it
signals the remote PE to flush all CMAC addresses associated with signals the remote PE to flush all CMAC addresses associated with
that Ethernet Segment. This is done by advertising a mass-withdraw that Ethernet Segment. This is done by advertising a mass-withdraw
message using Ethernet A-D per-ES route. To be precise, there is no message using Ethernet A-D per-ES route. To be precise, there is no
MAC flush per-se if there is only one backup PE for a given ES - MAC flush per-se if there is only one backup PE for a given ES -
i.e., only an update of the forwarding entries per backup-path i.e., only an update of the forwarding entries per backup-path
skipping to change at page 20, line 24 skipping to change at page 20, line 24
| |AC4--0=====0--ENNI3|PE2|--| | +---+ +---+ | |AC4--0=====0--ENNI3|PE2|--| | +---+ +---+
+----+ | ====0--ENNI3| | | | +----+ | ====0--ENNI3| | | |
|/ | +---+ | | |/ | +---+ | |
0 | | | 0 | | |
+----+ /| | +---+ | | +----+ /| | +---+ | |
| CE3|AC5- | | |PE3|--| | | CE3|AC5- | | |PE3|--| |
| |AC6--0=====0--ENNI4| | +-------+ | |AC6--0=====0--ENNI4| | +-------+
+----+ | | +---+ +----+ | | +---+
+-----+ +-----+
Figure 4: Fast Convergence Upon ENNI Failure Figure 5: Fast Convergence Upon ENNI Failure
The following describes the procedure for coloring vES's and fast The following describes the procedure for coloring vES's and fast
convergence using this color in more details: convergence using this color in more details:
1- When a vES is configured, the PE colors the vES with the MAC 1- When a vES is configured, the PE colors the vES with the MAC
address of the corresponding physical port and advertises the address of the corresponding physical port and advertises the
Ethernet Segment route for this vES with this color. Ethernet Segment route for this vES with this color.
2- All other PEs (in the redundancy group) take note of this color 2- All other PEs (in the redundancy group) take note of this color
and add the vES to the list for this color. and add the vES to the list for this color.
skipping to change at page 21, line 10 skipping to change at page 21, line 10
noted the ES route withdrawal messages are not used for executing DF noted the ES route withdrawal messages are not used for executing DF
election procedures by the receiving PEs. election procedures by the receiving PEs.
6. BGP Encoding 6. BGP Encoding
This document defines one new BGP Extended Community for EVPN. This document defines one new BGP Extended Community for EVPN.
6.1. I-SID Extended Community 6.1. I-SID Extended Community
A new EVPN BGP Extended Community called I-SID is introduced. This A new EVPN BGP Extended Community called I-SID is introduced. This
new extended community is a transitive extended community with the new extended community is a transitive extended community with the
Type field of 0x06 (EVPN) and the Sub-Type of 0x04. Type field of 0x06 (EVPN) and the Sub-Type of 0x07.
The I-SID Extended Community is encoded as an 8-octet value as The I-SID Extended Community is encoded as an 8-octet value as
follows: follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=0x06 | Sub-Type=0x03 | Base I-SID | | Type=0x06 | Sub-Type=0x03 | Base I-SID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cont. | Bit Map (24 bits) | | Cont. | Bit Map (24 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: I-SID Extended Community
This extended community is used to indicate the list of I-SIDs This extended community is used to indicate the list of I-SIDs
associated with a given Ethernet Segment. associated with a given Ethernet Segment.
24-bit map represents the next 24 I-SID after the base I-SID. For 24-bit map represents the next 24 I-SID after the base I-SID. For
example based I-SID of 10025 with 24-bit map of zero means, only a example based I-SID of 10025 with 24-bit map of zero means, only a
single I-SID of 10025. I-SID of 10025 with bit map of 0x000001 means single I-SID of 10025. I-SID of 10025 with bit map of 0x000001 means
there are two I-SIDs, 10025 and 10026. there are two I-SIDs, 10025 and 10026.
7. Acknowledgements 7. Acknowledgements
The authors would like to thanks Mei Zhang and Jose Liste for their The authors would like to thanks Mei Zhang and Jose Liste for their
reviews and feedbacks of this document. reviews and feedbacks of this document.
8. Security Considerations This document does not introduce any 8. Security Considerations
additional security constraints.
All the security considerations in [RFC7432] and [RFC7623] apply
directly to this document because this document leverages the control
and data plane procedures described in those documents.
This document does not introduce any new security considerations
beyond that of [RFC7432] and [RFC7623] because advertisements and
processing of Ethernet Segment route for vES in this document follows
that of physical ES in those RFCs.
9. IANA Considerations 9. IANA Considerations
IANA has allocated sub-type value 7 in the "EVPN Extended Community
Sub-Types" registry defined in "https://www.iana.org/assignments/bgp-
extended-communities/bgp-extended-communities.xhtml#evpn" as follows:
TBD. SUB-TYPE NAME Reference
---- -------------- -------------
0x07 I-SID Ext Comm [draft-sajassi-bess-evpn-virtual-eth-segment]
It is requested from IANA to update the reference to this document.
10. Intellectual Property Considerations 10. Intellectual Property Considerations
This document is being submitted for use in IETF standards This document is being submitted for use in IETF standards
discussions. discussions.
11. Normative References 11. Normative References
[PBB] Clauses 25 and 26 of "IEEE Standard for Local and metropolitan [PBB] Clauses 25 and 26 of "IEEE Standard for Local and metropolitan
area networks - Media Access Control (MAC) Bridges and area networks - Media Access Control (MAC) Bridges and
 End of changes. 15 change blocks. 
17 lines changed or deleted 34 lines changed or added

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