< draft-yu-bess-evpn-mass-withdraw-01.txt   draft-yu-bess-evpn-mass-withdraw-02.txt >
BESS Workgroup T. Yu BESS Workgroup T. Yu
Internet-Draft April 24, 2019 Internet-Draft June 20, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: October 26, 2019 Expires: December 22, 2019
EVPN Enhanced Mass Withdraw EVPN Enhanced Mass Withdraw
draft-yu-bess-evpn-mass-withdraw-01 draft-yu-bess-evpn-mass-withdraw-02
Abstract Abstract
This document aims to define an enhanced mass withdraw process in This document aims to define an enhanced mass withdraw process in
case of failure of multiple ESs or vESs. This document also improves case of failure of multiple ESs or vESs. This document also improves
the withdraw efficiency of failure of single-homed ES or vES. the withdraw efficiency of failure of single-homed ES or vES.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 26, 2019. This Internet-Draft will expire on December 22, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
1. Introduction 1. Introduction
EVPN [RFC7432] defines a mass withdraw mechanism to efficiently and EVPN [RFC7432] defines a mass withdraw mechanism to efficiently and
quickly signal to remote PE nodes in case of a connection to ES quickly signal to remote PE nodes in case of a connection to ES
fails. But there are particular scenarios that cannot be covered by fails. But there are particular scenarios that cannot be covered by
[RFC7432]: [RFC7432]:
Multi-homed scenario: Multi-homed scenario:
o Failure of a line-card leads to failure of multiple ESs/vESs.
o EVC scenario (described in section 1.1 of o EVC scenario (described in section 1.1 of
[I-D.ietf-bess-evpn-virtual-eth-segment]): [I-D.ietf-bess-evpn-virtual-eth-segment]):
* Failure of physical port leads to failure of multiple multi- * Failure of physical port leads to failure of multiple multi-
homed vESs aggregating EVC. homed vESs aggregating EVC.
* Failure of LAG leads to failure of multiple multi-homed vESs * Failure of LAG leads to failure of multiple multi-homed vESs
aggregating EVC. aggregating EVC.
o PW scenario (described in section 1.2 of o PW scenario (described in section 1.2 of
skipping to change at page 3, line 5 skipping to change at page 3, line 5
4.4.1 of [RFC4448]), with multiple VLAN services inside, and 4.4.1 of [RFC4448]), with multiple VLAN services inside, and
EVPN is using vlan-based interface and the services. This EVPN is using vlan-based interface and the services. This
scenario is called "PW 1:N" in the following context of this scenario is called "PW 1:N" in the following context of this
document. document.
* Failure of PW leads to failure of particular VLAN(s) in EVPN. * Failure of PW leads to failure of particular VLAN(s) in EVPN.
One of the example is: a couple of PWs terminated by a EVPN One of the example is: a couple of PWs terminated by a EVPN
using vlan-aware-bundle interface. This scenario is called "PW using vlan-aware-bundle interface. This scenario is called "PW
N:1" in the following context of this document. N:1" in the following context of this document.
o A single point of failure leads to failure of multiple ESs/vESs
(e.g. failure of a line-card).
The mass withdraw mechanism MUST handle both single-active and The mass withdraw mechanism MUST handle both single-active and
active-active multi-homed vES in scenarios described above. active-active multi-homed vES in scenarios described above.
Single-homed scenario: Single-homed scenario:
o A failure of single-homed ES or vES interface requires a per-MAC o A failure of single-homed ES or vES interface requires a per-MAC
based flush, which brings burden to the control plane. based flush, which brings burden to the control plane.
o A failure of line-card leads to failure of multiple single-homed
ESs/vESs.
o EVC scenario: o EVC scenario:
* Failure of physical port leads to failure of multiple single- * Failure of physical port leads to failure of multiple single-
homed vESs aggregating EVC. homed vESs aggregating EVC.
* Failure of LAG leads to failure of multiple single-homed vESs * Failure of LAG leads to failure of multiple single-homed vESs
aggregating EVC. aggregating EVC.
o PW scenario: o PW scenario:
* Failure of PW leads to failure of multiple single-homed vESs in * Failure of PW leads to failure of multiple single-homed vESs in
EVPN. EVPN.
* Failure of PW leads to failure of particular VLAN(s) in EVPN. * Failure of PW leads to failure of particular VLAN(s) in EVPN.
The mass withdraw mechanism SHOULD handle a huge number of vES. o A single point of failure leads to failure of multiple single-
homed ESs/vESs (e.g. failure of a line-card).
The mass withdraw mechanism SHOULD handle a huge number of ES/vES.
Convergence mechanism independent of number of (v)ES and MAC/IP Convergence mechanism independent of number of (v)ES and MAC/IP
routes is preferred when possible. routes is preferred when possible.
2. Specification of Requirements 2. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
3. Terminology 3. Terminology
skipping to change at page 3, line 48 skipping to change at page 4, line 4
NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
3. Terminology 3. Terminology
EVPN: BGP MPLS-Based Ethernet VPN defined in [RFC7432] EVPN: BGP MPLS-Based Ethernet VPN defined in [RFC7432]
EVI: EVPN Instance EVI: EVPN Instance
EVPN VPWS: Refers to [RFC8214] EVPN VPWS: Refers to [RFC8214]
vES: Virtual Ethernet Segment vES: Virtual Ethernet Segment
[I-D.ietf-bess-evpn-virtual-eth-segment] [I-D.ietf-bess-evpn-virtual-eth-segment]
EVC: Ethernet Virtual Circuit EVC: Ethernet Virtual Circuit
PW: Pseudowire PW: Pseudowire
4. Solution Description 4. Solution Description
To achieve a fast convergence time in case of multiple vES fails, a To achieve a fast convergence time in case of multiple (v)ES fails, a
concept of Administrative Group (AG) is introduced into EVPN. (v)ESs concept of Administrative Group (AG) is introduced into EVPN. (v)ESs
belonging to the same failure domain will be set with the same belonging to the same failure domain will be set with the same
Administrative Group. A (v)ES MAY have more than one Administrative Administrative Group. A (v)ES MAY have more than one Administrative
Groups. Groups.
A new EVPN BGP Extended Community called EVPN Administrative Group A new EVPN BGP Extended Community called EVPN Administrative Group
Community is defined as below. This new extended community is a Community is defined as below. This new extended community is a
transitive extended community with the Type field of 0x06 (EVPN) and transitive extended community with the Type field of 0x06 (EVPN) and
the Sub-Type of TBD. the Sub-Type of TBD.
skipping to change at page 5, line 28 skipping to change at page 5, line 34
o Type 2 (0x02): The Administrative Group is retrieved via ID of the o Type 2 (0x02): The Administrative Group is retrieved via ID of the
PW the EVPN is terminating. PW the EVPN is terminating.
o Type 3 (0x03): The Administrative Group is retrieved via service o Type 3 (0x03): The Administrative Group is retrieved via service
instance identifier of EVPN VPWS the EVPN is terminating. There instance identifier of EVPN VPWS the EVPN is terminating. There
is also a scenario that EVPN ELAN is terminating EVPN VPWS instead is also a scenario that EVPN ELAN is terminating EVPN VPWS instead
of FEC128-based [RFC4762] or FEC129-based [RFC6074] PW, in such of FEC128-based [RFC4762] or FEC129-based [RFC6074] PW, in such
case the Administrative Group is retrieved via service instance case the Administrative Group is retrieved via service instance
identifier which is defined in [RFC8214]. identifier which is defined in [RFC8214].
o Type 4 (0x04): The Administrative Group is retrieved via Ethernet
Tag ID of the EVPN is terminating. One example of using this is
failure or disabling of particular VLAN in a vlan-aware-bundle
interface.
o Self-defined (0xF0~0xFF): These values are used for proprietary o Self-defined (0xF0~0xFF): These values are used for proprietary
implementations to retrieve system parameters to generate self- implementations to retrieve system parameters to generate self-
defined value of the Administrative Group. An example is to use a defined value of the Administrative Group. An example is to use a
type in this range to color the MAC address with ID of the line- type in this range to color the MAC address with ID of the line-
card, which is a single-point-of-failure of a series of (v)ESs. card, which is a single-point-of-failure of a series of (v)ESs.
In case of failure of the line-card, a withdraw message with the In case of failure of the line-card, a withdraw message with the
self-defined type plus ID of the line-card can be sent to remote self-defined type plus ID of the line-card can be sent to remote
PE to withdraw all impacted (v)ESs. The remote PE is not required PE to withdraw all impacted (v)ESs. The remote PE is not required
to understand the meaning of self-defined type. There is no to understand the meaning of self-defined type. There is no
difference on the coloring and flushing procedure when using self- difference on the coloring and flushing procedure when using self-
skipping to change at page 7, line 40 skipping to change at page 7, line 50
This document creates registry below. This document creates registry below.
Administrative Group Type: Administrative Group Type:
Value Meaning Reference Value Meaning Reference
--------------------------------------------------------------------- ---------------------------------------------------------------------
0x00 Manually managed Administrative Group This document 0x00 Manually managed Administrative Group This document
0x01 AG is retrieved via ifindex This document 0x01 AG is retrieved via ifindex This document
0x02 AG is retrieved via ID of PW This document 0x02 AG is retrieved via ID of PW This document
0x03 AG is retrieved via EVPN service instance id This document 0x03 AG is retrieved via EVPN service instance id This document
0x04 AG is retrieved via Ethernet Tag ID of EVPN This document
0xF0~0xFF Reserved for proprietary implementation This document 0xF0~0xFF Reserved for proprietary implementation This document
Administrative Group Flags: Administrative Group Flags:
Value Meaning Reference Value Meaning Reference
--------------------------------------------------------------------- ---------------------------------------------------------------------
0x01 Flush-all-from-me This document 0x01 Flush-all-from-me This document
0x02 FRR-all-from-me This document 0x02 FRR-all-from-me This document
8. References 8. References
8.1. Normative References 8.1. Normative References
skipping to change at page 8, line 13 skipping to change at page 8, line 19
0x02 FRR-all-from-me This document 0x02 FRR-all-from-me This document
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-bess-evpn-proxy-arp-nd] [I-D.ietf-bess-evpn-proxy-arp-nd]
Rabadan, J., Sathappan, S., Nagaraj, K., Henderickx, W., Rabadan, J., Sathappan, S., Nagaraj, K., Henderickx, W.,
Hankins, G., King, T., Melzer, D., and E. Nordmark, Hankins, G., King, T., Melzer, D., and E. Nordmark,
"Operational Aspects of Proxy-ARP/ND in EVPN Networks", "Operational Aspects of Proxy-ARP/ND in EVPN Networks",
draft-ietf-bess-evpn-proxy-arp-nd-05 (work in progress), draft-ietf-bess-evpn-proxy-arp-nd-06 (work in progress),
November 2018. April 2019.
[I-D.ietf-bess-evpn-virtual-eth-segment] [I-D.ietf-bess-evpn-virtual-eth-segment]
Sajassi, A., Brissette, P., Schell, R., Drake, J., and J. Sajassi, A., Brissette, P., Schell, R., Drake, J., and J.
Rabadan, "EVPN Virtual Ethernet Segment", draft-ietf-bess- Rabadan, "EVPN Virtual Ethernet Segment", draft-ietf-bess-
evpn-virtual-eth-segment-04 (work in progress), January evpn-virtual-eth-segment-04 (work in progress), January
2019. 2019.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
 End of changes. 15 change blocks. 
15 lines changed or deleted 21 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/