idnits 2.17.1 draft-liu-bess-evpn-mcast-synch-enhance-01.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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 10, 2018) is 1963 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ES' is mentioned on line 142, but not defined == Missing Reference: 'BD' is mentioned on line 142, but not defined == Outdated reference: A later version (-21) exists of draft-ietf-bess-evpn-igmp-mld-proxy-02 -- No information found for draft-skr-evpn-bess-pim-proxy - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'EVPN-PIM-PROXY' Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 BESS Working Group Yisong Liu 2 Internet Draft Donald Eastlake 3 Intended status: Standards Track Huawei Technologies 4 Expires: June 10, 2019 December 10, 2018 6 EVPN Multicast Synchronization Enhancement 7 draft-liu-bess-evpn-mcast-synch-enhance-01 9 Status of this Memo 11 This Internet-Draft is submitted in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other documents 21 at any time. It is inappropriate to use Internet-Drafts as 22 reference material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 This Internet-Draft will expire on June 10, 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 (http://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 42 respect to this document. Code Components extracted from this 43 document must include Simplified BSD License text as described in 44 Section 4.e of the Trust Legal Provisions and are provided without 45 warranty as described in the Simplified BSD License. 47 Abstract 48 Ethernet Virtual Private Network (EVPN, RFC7432) solutions is becoming 49 prevalent in Data Centers, Data Center Interconnect (DCI) and Service 50 Provider VPN applications. In the scenario of multi-homing from a CE to 51 multiple PEs with links used in a single-active or all-active 52 redundancy mode, IGMP & MLD Join/Leave and PIM Join/RPT-Prune 53 synchronization procedures have been provided. This document specifies 54 an enhancement for IGMP/PIM signaling synchronization when using 55 different Ethernet tag encapsulation mode. 57 Table of Contents 59 1. Introduction ................................................ 2 60 1.1. Requirements Language .................................. 3 61 1.2. Terminology ............................................ 3 62 2. Enhancement of IGMP/PIM Synchronization ..................... 3 63 3. BGP Encoding Improvement .................................... 4 64 3.1. IGMP/PIM Join Synch Route .............................. 4 65 3.2. IGMP Leave Synch Route ................................. 5 66 3.3. PIM RPT-Prune Synch Route .............................. 7 67 4. Security Considerations ..................................... 8 68 5. IANA Considerations ......................................... 8 69 6. References .................................................. 8 70 6.1. Normative References ................................... 8 71 6.2. Informative References ................................. 8 72 7. Acknowledgments ............................................. 8 74 1. Introduction 76 Ethernet Virtual Private Network (EVPN [RFC7432]) solutions are 77 becoming prevalent in Data Centers, Data Center Interconnect (DCI) 78 and Service Provider VPN applications. In the scenario of multi- 79 homing from a CE to multiple PEs with links used in a single-active 80 or all-active redundancy mode, [EVPN-IGMP-MLD-PROXY] for IGMP&MLD 81 Join/Leave and [EVPN-PIM-PROXY] for PIM Join/RPT-Prune 82 synchronization procedures have been provided. 84 However, there may be multiple ways for a CE to connect to PE, 85 including Ethernet tag termination and Q-in-Q termination. When 86 IGMP/PIM synch routes are transmitted from one PE to another PE both 87 multi-homing to the same CE, the appropriate VLAN tags should be 88 included in the routes. This document specifies an improvement in 89 IGMP/PIM synchronization process. 91 1.1. Requirements Language 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in 96 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 97 capitals, as shown here. 99 1.2. Terminology 101 CE - Customer Edge equipment 103 EVPN: Ethernet Virtual Private Network 105 Ethernet Segment (ES): When a customer site (device or network) is 106 connected to one or more PEs via a set of Ethernet links, then that 107 set of links is referred to as an 'Ethernet segment'. 109 Ethernet Segment Identifier (ESI): A unique non-zero identifier that 110 identifies an Ethernet segment is called an 'Ethernet Segment 111 Identifier'. 113 IGMP: Internet Group Management Protocol 115 MLD: Multicast Listener Discovery 117 PE: Provider Edge device 119 PIM: Protocol Independent Multicast 121 2. Enhancement of IGMP/PIM Synchronization 123 Consider the situation where one CE is dual-homed to two PEs. If the 124 CE is connected through one VLAN and only one VLAN under the EVPN 125 instance at the PE, the IGMP/PIM synch message can be directly sent 126 from one PE to another PE with the ESI, which can represent the 127 appropriate interface and can be encapsulated with the appropriate 128 VLAN ID. 130 However, there may be Ethernet tag termination and Q-in-Q 131 termination on the PE interface connected to CE. When IGMP/PIM 132 synchronization procedures are implemented between the two dual- 133 homed PEs, the receiver PE cannot obtain the appropriate VLANs 134 because of the information lacking in the IGMP/PIM synch route 135 message. For example, PE1 and PE2 connect to the CE dual-homed for 136 the same ES, and VLAN tag 1 to 10 termination is configured on the 137 interface for CE connecting to PE1 and PE2. After receiving a 138 IGMP/PIM join with VLAN tag 2 from the interface, PE1 sends a 139 IGMP/PIM join synch route to PE2 with the ESI. But PE2 cannot get 140 the VLAN tag information from the route, so that PE doesn't create 141 the IGMP Join state accurately. It can only know the VLAN tag 1-10 142 termination on the corresponding interface according to the [ES,BD]. 143 Especially Q-in-Q termination is configured on the interface for CE 144 connecting to PE1 and PE2, outer and inner VLAN tag information will 145 be both needed when IGMP/PIM synch routes are advertised between the 146 dual-homed PE1 and PE2. 148 This document extends the IGMP/PIM synch routes to solve the problem 149 mentioned above. VLAN tag information from the original IGMP/PIM 150 message is added in the synch routes NLRI as a part of the route 151 key. 153 3. BGP Encoding Improvement 155 This document extends the following routes defined in [EVPN-IGMP- 156 MLD-PROXY] and [EVPN-PIM-PROXY] 158 + Type 6 - IGMP/PIM Join Synch Route 160 + Type 7 - IGMP Leave Synch Route 162 + Type TBD - PIM RPT-Prune Synch Route 164 3.1. IGMP/PIM Join Synch Route 166 This document extends the IGMP/PIM Join Synch Route defined in 167 [EVPN-PIM-PROXY] with new fields and Flags as shown in Figure 1. 169 +----------------------------------------------+ 170 | RD (8 octets) | 171 +----------------------------------------------+ 172 | Ethernet Segment Identifier (10 octets) | 173 +----------------------------------------------+ 174 | Ethernet Tag ID (4 octets) | 175 +----------------------------------------------+ 176 | Multicast Source Length (1 octet) | 177 +----------------------------------------------+ 178 | Multicast Source Address (variable) | 179 +----------------------------------------------+ 180 | Multicast Group Length (1 octet) | 181 +----------------------------------------------+ 182 | Multicast Group Address (Variable) | 183 +----------------------------------------------+ 184 | Originator Router Length (1 octet) | 185 +----------------------------------------------+ 186 | Originator Router Address (variable) | 187 +----------------------------------------------+ 188 | Flags (1 octet) | 189 +----------------------------------------------+ 190 | Upstream Router Length (1B)(optional) | 191 +----------------------------------------------+ 192 | Upstream Router Addr (variable)(opt) | 193 +----------------------------------------------+ 194 | Outer VLAN (2 octets) | 195 +----------------------------------------------+ 196 | Inner VLAN (2 octets) | 197 +----------------------------------------------+ 199 Flags: 201 0 1 2 3 4 5 6 7 202 +--+--+--+--+--+--+--+--+ 203 | | | V| P|IE|v3|v2|v1| 204 +--+--+--+--+--+--+--+--+ 206 Figure 1 IGMP/PIM Join Synch Route 208 This route will be added the following extra fields: 210 Outer VLAN Can be used for single layer VLAN tag and the outer layer 211 of double layer VLAN tags, and can be 0. When 0, it means there is 212 no VLAN tag information needed to be advertised. 214 Inner VLAN Can be used for the inner layer of double layer VLAN 215 tags, and can be 0. When 0, it means there is no inner VLAN. 217 Flags: This field encodes Flags that are already relevant to IGMP 218 and PIM. The following new Flag is defined: 220 - Flag V: Indicates the Join Synch route carries VLAN tag 221 information by the encapsulation of the received protocol packet. 222 When V=1, the Outer VLAN and Inner VLAN fields are present in the 223 route. Otherwise the two fields will not be present. 225 Compared to [EVPN-PIM-PROXY] there are two additional fields 226 considered part of the route key for BGP processing when Flag V is 227 set 1. 229 3.2. IGMP Leave Synch Route 231 This document extends the IGMP Leave Synch Route defined in [EVPN- 232 IGMP-MLD-PROXY] as shown in Figure 2 233 +--------------------------------------------------+ 234 | RD (8 octets) | 235 +--------------------------------------------------+ 236 | Ethernet Segment Identifier (10 octets) | 237 +--------------------------------------------------+ 238 | Ethernet Tag ID (4 octets) | 239 +--------------------------------------------------+ 240 | Multicast Source Length (1 octet) | 241 +--------------------------------------------------+ 242 | Multicast Source Address (variable) | 243 +--------------------------------------------------+ 244 | Multicast Group Length (1 octet) | 245 +--------------------------------------------------+ 246 | Multicast Group Address (Variable) | 247 +--------------------------------------------------+ 248 | Originator Router Length (1 octet) | 249 +--------------------------------------------------+ 250 | Originator Router Address (variable) | 251 +--------------------------------------------------+ 252 | Leave Group Synchronization # (4 octets) | 253 +--------------------------------------------------+ 254 | Maximum Response Time (1 octet) | 255 +--------------------------------------------------+ 256 | Flags (1 octet) | 257 +--------------------------------------------------+ 258 | Outer VLAN (2 octets) | 259 +--------------------------------------------------+ 260 | Inner VLAN (2 octets) | 261 +--------------------------------------------------+ 263 Flags: 265 0 1 2 3 4 5 6 7 266 +--+--+--+--+--+--+--+--+ 267 | | | | V|IE|v3|v2|v1| 268 +--+--+--+--+--+--+--+--+ 270 Figure 2 IGMP Leave Synch Route 272 This route will have the same extra fields as described in section 273 3.1 added. 275 Compared to [EVPN-IGMP-MLD-PROXY] there are two additional fields 276 considered part of the route key for BGP processing when Flag V is 277 set 1. 279 3.3. PIM RPT-Prune Synch Route 281 This document extends the PIM RPT-Prune Synch Route defined in 282 [EVPN-PIM-PROXY] as shown in Figure 3 284 +----------------------------------------------+ 285 | RD (8 octets) | 286 +----------------------------------------------+ 287 | Ethernet Segment Identifier (10 octets) | 288 +----------------------------------------------+ 289 | Ethernet Tag ID (4 octets) | 290 +----------------------------------------------+ 291 | Multicast Source Length (1 octet) | 292 +----------------------------------------------+ 293 | Multicast Source Address (variable) | 294 +----------------------------------------------+ 295 | Multicast Group Length (1 octet) | 296 +----------------------------------------------+ 297 | Multicast Group Address (Variable) | 298 +----------------------------------------------+ 299 | Originator Router Length (1 octet) | 300 +----------------------------------------------+ 301 | Originator Router Address (variable) | 302 +----------------------------------------------+ 303 | Upstream Router Length (1B)(optional) | 304 +----------------------------------------------+ 305 | Upstream Router Addr (variable)(opt) | 306 +----------------------------------------------+ 307 | Flags (1 octet) | 308 +----------------------------------------------+ 309 | Outer VLAN (2 octets) | 310 +----------------------------------------------+ 311 | Inner VLAN (2 octets) | 312 +----------------------------------------------+ 314 Flags: 316 0 1 2 3 4 5 6 7 317 +--+--+--+--+--+--+--+--+ 318 | | | | | | | | V| 319 +--+--+--+--+--+--+--+--+ 321 Figure 3 PIM RPT-Prune Synch Route 323 This route will have the same Outer VLAN and Inner VLAN fields as 324 described in section 3.1 added and an extra Flags field as IGMP/PIM 325 Join Synch Route and IGMP Leave Synch Route to indicate the existing 326 VLAN information. 328 Compared to [EVPN-PIM-PROXY] there are two additional fields 329 considered part of the route key for BGP processing when Flag V is 330 set 1. 332 4. Security Considerations 334 TBD 336 For general EVPN Security Considerations, see [RFC7432]. 338 5. IANA Considerations 340 TBD 342 6. References 344 6.1. Normative References 346 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 347 Requirement Levels", BCP 14, RFC 2119, March 1997. 349 [RFC7432] A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. 350 Uttaro, J. Drake, and W. Henderickx, "BGP MPLS-Based 351 Ethernet VPN", RFC 7432, February 2015 353 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 354 2119 Key Words", BCP 14, RFC 8174, May 2017 356 [EVPN-IGMP-MLD-PROXY] Ali Sajassi, Samir Thoria, Keyur Patel, Derek 357 Yeung, John Drake and Wen Lin, "IGMP and MLD Proxy for 358 EVPN", June 2018, work-in-progress, draft-ietf-bess-evpn- 359 igmp-mld-proxy-02. 361 [EVPN-PIM-PROXY] J. Rabadan, Ed., J. Kotalwar, S. Sathappan, Z. 362 Zhang and A. Sajassi, "PIM Proxy in EVPN Networks", 363 October 2017, expired, draft-skr-evpn-bess-pim-proxy-01. 365 6.2. Informative References 367 TBD 369 7. Acknowledgments 371 The authors would like to thank the following for their valuable 372 contributions of this document: 374 TBD 375 Authors' Addresses 377 Yisong Liu 378 Huawei Technologies 379 Huawei Bld., No.156 Beiqing Rd. 380 Beijing 100095 381 China 383 Email: liuyisong@huawei.com 385 Donald E. Eastlake, 3rd 386 Huawei Technologies 387 155 Beaver Street 388 Milford, MA 01757 USA 390 Phone: +1-508-333-2270 391 Email: d3e3e3@gmail.com