idnits 2.17.1 draft-yu-bess-evpn-mass-withdraw-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (January 15, 2019) is 1928 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-15) exists of draft-ietf-bess-evpn-virtual-eth-segment-03 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BESS Workgroup T. Yu 3 Internet-Draft January 15, 2019 4 Intended status: Experimental 5 Expires: July 19, 2019 7 EVPN Enhanced Mass Withdraw 8 draft-yu-bess-evpn-mass-withdraw-00 10 Abstract 12 This document aims to define a enhanced mass withdraw process in case 13 of multiple ES or vES fails. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on July 19, 2019. 32 Copyright Notice 34 Copyright (c) 2019 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Specification of Requirements . . . . . . . . . . . . . . . . 2 51 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Requriments . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5. Solution Description . . . . . . . . . . . . . . . . . . . . 3 54 6. EVPN Mass-Withdraw Community . . . . . . . . . . . . . . . . 4 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 56 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 9. Normative References . . . . . . . . . . . . . . . . . . . . 5 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 EVPN [RFC7432] defines a mass withdraw mechanism to efficiently and 63 quickly signal to remote PE nodes in case of a connection to ES 64 fails. But there are paticular scenarios that failure of multiple 65 ESs can happen listed but not limited below: 67 o ES scenario: Failue of a line-card leads to failure of multiple 68 ESs. 70 o vES scenario: Failure of physical port leads to failure of 71 multiple vESs aggregating EVC. 73 o vES scenario: Failure of LAG leads to failure of multiple vESs 74 aggregating EVC. 76 o vES scenario: Failure of multiple MPLS NNI ports leads to failure 77 of LSP and multiple vESs aggregating PWs. 79 o vES scenario: Failure of EVC leading to failure of multiple vESs. 81 o vES scenario: Failure of PW leading to failure of multiple vESs. 83 o vES scenario: Failure of line-card leads to failure of multiple 84 vESs. 86 This document aims to introduce a solution improving convegence 87 performance in case of failure on multiple ESs. 89 2. Specification of Requirements 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 92 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 93 this document are to be interpreted as described in [RFC2119]. 95 3. Terminology 97 EVPN: BGP MPLS-Based Ethernet VPN defined in [RFC7432] 99 EVI: EVPN Instance 101 EVPN VPWS: Refers to [RFC8214] 103 vES: Virtual Ethernet Segment 104 [I-D.ietf-bess-evpn-virtual-eth-segment] 106 EVC: Ethernet Virtual Circuit 108 PW: Pseudowire 110 4. Requriments 112 (R1a): The mass withdraw mechanism MUST handle both single-active and 113 active-active multi-homed ES. 115 (R1b): The mass withdraw mechanism MUST handle both single-active and 116 active-active multi-homed vES. 118 (R1c): The mass withdraw mechanism SHOULD handle a huge number of ES/ 119 vES. 121 (R1d): The mass withdraw mechanism SHOULD handle failure scenarios 122 mentioned in section 1. 124 (R1e): The mass withdraw mechanism SHOULD allowing aggregating 125 sequential ESI. 127 (R1f): A suppresion mechanism is requried in case flapping occours 128 leading to failure of large number of ES/vES 130 5. Solution Description 132 In order to reduce the number of ES/vES withdraw routes, the PE 133 SHOULD aggregate ESI if the impacted ESI are sequential and send 134 along with EVPN mass-withdraw community defined in section 6. If the 135 impacted ES/vES are nonsequential then multiple EVPN mass-withdraw 136 communities can be sent along the flush message. 138 To achieve a fast convergence time in case of multiple ES/vES fails, 139 a sequential ES/vES helps. This can be achieved via proper ES/vES 140 auto-generating algorithm or proper planning. An example is given 141 below: 143 Assume type 0 ESI is used. An ESI/vESI planning rule is: 145 3 octs are used to identify device id 147 4 octs are used to identify ifindex. Ifindex uniquelly idenfies 148 physical port, LAG or any logical ENNI port. 150 3 octs are used to identify service id under each interface, if 0 it 151 is used as ES, if not 0 it is used as vES. 153 In case of port LAG or PW failure, an EVPN mass-withdraw community 154 can be generated with all impacted vES with bit map. 156 The auto-generating algorithm and planning rule on ES/vES is out of 157 scope of current document. Example given above is only used to 158 explan the possibility of ESI aggregation. 160 A timer SHOULD be started each time for each flushing. Further 161 failure during the timer SHOULD be suppressed. A half-life based 162 damping mechanism MAY be implemented. 164 6. EVPN Mass-Withdraw Community 166 A new EVPN BGP Extended Community called EVPN Mass-Withdraw Community 167 is introduced. This new extended community is a transitive extended 168 community with the Type field of 0x06 (EVPN) and the Sub-Type of TBD. 170 +-------------------------------------------+ 171 | Type (0x06) / Sub-type (TBD) (2 octets) | 172 +-------------------------------------------+ 173 | ESI (10 octets) | 174 +-------------------------------------------+ 175 | Bitmap (10 octets) | 176 +-------------------------------------------+ 178 Figure 1: EVPN Mass-Withdraw Community 180 7. Security Considerations 182 TBD 184 8. IANA Considerations 186 Sub-type for EVPN Mass-Withdraw Community to be allocated. 188 9. Normative References 190 [I-D.ietf-bess-evpn-virtual-eth-segment] 191 Sajassi, A., Brissette, P., Schell, R., Drake, J., and J. 192 Rabadan, "EVPN Virtual Ethernet Segment", draft-ietf-bess- 193 evpn-virtual-eth-segment-03 (work in progress), January 194 2019. 196 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 197 Requirement Levels", BCP 14, RFC 2119, 198 DOI 10.17487/RFC2119, March 1997, 199 . 201 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 202 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 203 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 204 2015, . 206 [RFC8214] Boutros, S., Sajassi, A., Salam, S., Drake, J., and J. 207 Rabadan, "Virtual Private Wire Service Support in Ethernet 208 VPN", RFC 8214, DOI 10.17487/RFC8214, August 2017, 209 . 211 Author's Address 213 Tianpeng Yu 215 EMail: yutianpeng.ietf@gmail.com