draft-ietf-bess-evpn-igmp-mld-proxy-11.txt   draft-ietf-bess-evpn-igmp-mld-proxy-12.txt 
BESS WorkGroup A. Sajassi BESS WorkGroup A. Sajassi
Internet-Draft S. Thoria Internet-Draft S. Thoria
Intended status: Standards Track M. Mishra Intended status: Standards Track M. Mishra
Expires: January 6, 2022 Cisco Systems Expires: February 24, 2022 Cisco Systems
K. Patel K. Patel
Arrcus Arrcus
J. Drake J. Drake
W. Lin W. Lin
Juniper Networks Juniper Networks
July 5, 2021 August 23, 2021
IGMP and MLD Proxy for EVPN IGMP and MLD Proxy for EVPN
draft-ietf-bess-evpn-igmp-mld-proxy-11 draft-ietf-bess-evpn-igmp-mld-proxy-12
Abstract Abstract
Ethernet Virtual Private Network (EVPN) solution is becoming Ethernet Virtual Private Network (EVPN) solution is becoming
pervasive in data center (DC) applications for Network Virtualization pervasive in data center (DC) applications for Network Virtualization
Overlay (NVO) and DC interconnect (DCI) services, and in service Overlay (NVO) and DC interconnect (DCI) services, and in service
provider (SP) applications for next generation virtual private LAN provider (SP) applications for next generation virtual private LAN
services. services.
This draft describes how to support efficiently endpoints running This draft describes how to support efficiently endpoints running
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 January 6, 2022. This Internet-Draft will expire on February 24, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 47 skipping to change at page 2, line 47
6.2. Local IGMP/MLD Leave Group Synchronization . . . . . . . 12 6.2. Local IGMP/MLD Leave Group Synchronization . . . . . . . 12
6.2.1. Remote Leave Group Synchronization . . . . . . . . . 13 6.2.1. Remote Leave Group Synchronization . . . . . . . . . 13
6.2.2. Common Leave Group Synchronization . . . . . . . . . 13 6.2.2. Common Leave Group Synchronization . . . . . . . . . 13
6.3. Mass Withdraw of Multicast join Sync route in case of 6.3. Mass Withdraw of Multicast join Sync route in case of
failure . . . . . . . . . . . . . . . . . . . . . . . . . 14 failure . . . . . . . . . . . . . . . . . . . . . . . . . 14
7. Single-Active Multi-Homing . . . . . . . . . . . . . . . . . 14 7. Single-Active Multi-Homing . . . . . . . . . . . . . . . . . 14
8. Selective Multicast Procedures for IR tunnels . . . . . . . . 14 8. Selective Multicast Procedures for IR tunnels . . . . . . . . 14
9. BGP Encoding . . . . . . . . . . . . . . . . . . . . . . . . 15 9. BGP Encoding . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Selective Multicast Ethernet Tag Route . . . . . . . . . 15 9.1. Selective Multicast Ethernet Tag Route . . . . . . . . . 15
9.1.1. Constructing the Selective Multicast Ethernet Tag 9.1.1. Constructing the Selective Multicast Ethernet Tag
route . . . . . . . . . . . . . . . . . . . . . . . . 17 route . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1.2. Default Selective Multicast Route . . . . . . . . . . 18 9.1.2. Default Selective Multicast Route . . . . . . . . . . 18
9.2. Multicast Join Synch Route . . . . . . . . . . . . . . . 19 9.2. Multicast Join Synch Route . . . . . . . . . . . . . . . 18
9.2.1. Constructing the Multicast Join Synch Route . . . . . 21 9.2.1. Constructing the Multicast Join Synch Route . . . . . 20
9.3. Multicast Leave Synch Route . . . . . . . . . . . . . . . 22 9.3. Multicast Leave Synch Route . . . . . . . . . . . . . . . 21
9.3.1. Constructing the Multicast Leave Synch Route . . . . 24 9.3.1. Constructing the Multicast Leave Synch Route . . . . 23
9.4. Multicast Flags Extended Community . . . . . . . . . . . 25 9.4. Multicast Flags Extended Community . . . . . . . . . . . 24
9.5. EVI-RT Extended Community . . . . . . . . . . . . . . . . 27 9.5. EVI-RT Extended Community . . . . . . . . . . . . . . . . 26
9.6. Rewriting of RT ECs and EVI-RT ECs by ASBRs . . . . . . . 29 9.6. Rewriting of RT ECs and EVI-RT ECs by ASBRs . . . . . . . 28
9.7. BGP Error Handling . . . . . . . . . . . . . . . . . . . 29 9.7. BGP Error Handling . . . . . . . . . . . . . . . . . . . 28
10. IGMP/MLD Immediate Leave . . . . . . . . . . . . . . . . . . 29 10. IGMP/MLD Immediate Leave . . . . . . . . . . . . . . . . . . 28
11. IGMP Version 1 Membership Report . . . . . . . . . . . . . . 30 11. IGMP Version 1 Membership Report . . . . . . . . . . . . . . 29
12. Security Considerations . . . . . . . . . . . . . . . . . . . 30 12. Security Considerations . . . . . . . . . . . . . . . . . . . 29
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
14. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 31 14. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 30
15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
16.1. Normative References . . . . . . . . . . . . . . . . . . 31 16.1. Normative References . . . . . . . . . . . . . . . . . . 30
16.2. Informative References . . . . . . . . . . . . . . . . . 33 16.2. Informative References . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
Ethernet Virtual Private Network (EVPN) solution [RFC7432] is Ethernet Virtual Private Network (EVPN) solution [RFC7432] is
becoming pervasive in data center (DC) applications for Network becoming pervasive in data center (DC) applications for Network
Virtualization Overlay (NVO) and DC interconnect (DCI) services, and Virtualization Overlay (NVO) and DC interconnect (DCI) services, and
in service provider (SP) applications for next generation virtual in service provider (SP) applications for next generation virtual
private LAN services. private LAN services.
In DC applications, a point of delivery (POD) can consist of a In DC applications, a point of delivery (POD) can consist of a
skipping to change at page 5, line 48 skipping to change at page 5, line 48
defined to be operating in All-Active redundancy mode. defined to be operating in All-Active redundancy mode.
o PMSI: P-Multicast Service Interface - a conceptual interface for a o PMSI: P-Multicast Service Interface - a conceptual interface for a
PE to send customer multicast traffic to all or some PEs in the PE to send customer multicast traffic to all or some PEs in the
same VPN. same VPN.
o S-PMSI: Selective PMSI - to some of the PEs in the same VPN. o S-PMSI: Selective PMSI - to some of the PEs in the same VPN.
o AC: Attachment Circuit. o AC: Attachment Circuit.
o OIF: Outgoing Interface o OIF: Outgoing Interface for multicast. It can be physical
interface, virtual interface or tunnel.
This document also assumes familiarity with the terminology of This document also assumes familiarity with the terminology of
[RFC7432]. Though most of the place this document uses term IGMP [RFC7432]. Though most of the place this document uses term IGMP
Membership Report (Joins), the text applies equally for MLD Membership Report (Joins), the text applies equally for MLD
Membership Report too. Similarly, text for IGMPv2 applies to MLDv1 Membership Report too. Similarly, text for IGMPv2 applies to MLDv1
and text for IGMPv3 applies to MLDv2. IGMP / MLD version encoding in and text for IGMPv3 applies to MLDv2. IGMP / MLD version encoding in
BGP update is stated in Section 9 BGP update is stated in Section 9
4. IGMP/MLD Proxy 4. IGMP/MLD Proxy
skipping to change at page 7, line 30 skipping to change at page 7, line 31
version flag(s). In other words, the first hop PE MUST NOT version flag(s). In other words, the first hop PE MUST NOT
withdraw the EVPN route before sending the new route because the withdraw the EVPN route before sending the new route because the
flag field is not part of BGP route key processing. flag field is not part of BGP route key processing.
4. When the first hop PE receives an IGMP version-X Join first for 4. When the first hop PE receives an IGMP version-X Join first for
(*,G) and then later it receives an IGMPv3 Join for the same (*,G) and then later it receives an IGMPv3 Join for the same
multicast group address but for a specific source address S, then multicast group address but for a specific source address S, then
the PE MUST advertise a new EVPN SMET route with v3 flag set (and the PE MUST advertise a new EVPN SMET route with v3 flag set (and
v2 reset). The IE flag also need to be set accordingly. Since v2 reset). The IE flag also need to be set accordingly. Since
source IP address is used as part of BGP route key processing it source IP address is used as part of BGP route key processing it
is considered as a new BGP route advertisement. is considered as a new BGP route advertisement. When different
version of IGMP join are received, final state MUST be as per
section 5.1 of [RFC3376]. At the end of route processing local
and remote group record state MUST be as per section 5.1 of
[RFC3376].
5. When a PE receives an EVPN SMET route with more than one version 5. When a PE receives an EVPN SMET route with more than one version
flag set, it will generate the corresponding IGMP report for flag set, it will generate the corresponding IGMP report for
(*,G) for each version specified in the flags field. With (*,G) for each version specified in the flags field. With
multiple version flags set, there must not be source IP address multiple version flags set, there must not be source IP address
in the received EVPN route. If there is, then an error SHOULD be in the received EVPN route. If there is, then an error SHOULD be
logged. If the v3 flag is set (in addition to v2), then the IE logged. If the v3 flag is set (in addition to v2), then the IE
flag MUST indicate "exclude". If not, then an error SHOULD be flag MUST indicate "exclude". If not, then an error SHOULD be
logged. The PE MUST generate an IGMP Membership Report (Join) logged. The PE MUST generate an IGMP Membership Report (Join)
for that (*,G) and each IGMP version in the version flag. for that (*,G) and each IGMP version in the version flag.
skipping to change at page 15, line 5 skipping to change at page 15, line 5
Inclusive Multicast Tag route for the BD without the "IGMP Proxy Inclusive Multicast Tag route for the BD without the "IGMP Proxy
Support" flag. Support" flag.
2. It sends (x,G) traffic to the set of PEs supporting IGMP Proxy 2. It sends (x,G) traffic to the set of PEs supporting IGMP Proxy
and having listeners for that (x,G) group in that BD. This set and having listeners for that (x,G) group in that BD. This set
consists of any PE that has advertised an Inclusive Multicast consists of any PE that has advertised an Inclusive Multicast
Ethernet Tag route for the BD with the "IGMP Proxy Support" flag Ethernet Tag route for the BD with the "IGMP Proxy Support" flag
and that has advertised a SMET route for that (x,G) group in that and that has advertised a SMET route for that (x,G) group in that
BD. BD.
If an ingress PE's Selective P-Tunnel for a given BD uses P2MP and
all of the PEs in the BD support that tunnel type and IGMP proxy,
then for a given (x,G) group in a given BD it sends (x,G) traffic
using the Selective P-Tunnel for that (x,G) group in that BD. This
tunnel includes those PEs that have advertised a SMET route for that
(x,G) group on that BD (for Selective P-tunnel) but it may include
other PEs as well (for Aggregate Selective P-tunnel).
9. BGP Encoding 9. BGP Encoding
This document defines three new BGP EVPN routes to carry IGMP This document defines three new BGP EVPN routes to carry IGMP
Membership Reports. The route types are known as: Membership Reports. The route types are known as:
+ 6 - Selective Multicast Ethernet Tag Route + 6 - Selective Multicast Ethernet Tag Route
+ 7 - Multicast Join Synch Route + 7 - Multicast Join Synch Route
+ 8 - Multicast Leave Synch Route + 8 - Multicast Leave Synch Route
skipping to change at page 30, line 21 skipping to change at page 29, line 21
Implementations MUST only use IGMPv2 and above for IPv4 and MLDv1 and Implementations MUST only use IGMPv2 and above for IPv4 and MLDv1 and
above for IPv6. IGMP V1 routes MUST be considered as invalid and the above for IPv6. IGMP V1 routes MUST be considered as invalid and the
PE MUST apply the "treat-as-withdraw" procedure as per [RFC7606]. PE MUST apply the "treat-as-withdraw" procedure as per [RFC7606].
Initial version of draft did mention use of IGMPv1 and flag had Initial version of draft did mention use of IGMPv1 and flag had
provision to support IGMPv1. There may be an implemention which is provision to support IGMPv1. There may be an implemention which is
deployed as initial version of draft, to interop flag has not been deployed as initial version of draft, to interop flag has not been
changed. changed.
12. Security Considerations 12. Security Considerations
Same security considerations as [RFC7432], [RFC2236], [RFC3376], TThis document does not add any new security considirattions, Same
[RFC2710], [RFC3810]. security considerations as [RFC7432], [RFC2236], [RFC3376],
[RFC2710], [RFC3810], [RFC6513], [RFC6514] are applicable.
13. IANA Considerations 13. IANA Considerations
IANA has allocated the following codepoints from the EVPN Extended IANA has allocated the following codepoints from the EVPN Extended
Community sub-types registry. Community sub-types registry.
0x09 Multicast Flags Extended Community [this document] 0x09 Multicast Flags Extended Community [this document]
0x0A EVI-RT Type 0 [this document] 0x0A EVI-RT Type 0 [this document]
0x0B EVI-RT Type 1 [this document] 0x0B EVI-RT Type 1 [this document]
0x0C EVI-RT Type 2 [this document] 0x0C EVI-RT Type 2 [this document]
skipping to change at page 31, line 32 skipping to change at page 30, line 35
Derek Yeung Derek Yeung
Arrcus Arrcus
Email: derek@arrcus.com Email: derek@arrcus.com
16. References 16. References
16.1. Normative References 16.1. Normative References
[I-D.ietf-bess-evpn-bum-procedure-updates]
Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A.
Sajassi, "Updates on EVPN BUM Procedures", draft-ietf-
bess-evpn-bum-procedure-updates-08 (work in progress),
November 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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, DOI 10.17487/RFC2236, November 1997, 2", RFC 2236, DOI 10.17487/RFC2236, November 1997,
<https://www.rfc-editor.org/info/rfc2236>. <https://www.rfc-editor.org/info/rfc2236>.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
skipping to change at page 32, line 31 skipping to change at page 31, line 26
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, [RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
R., Patel, K., and J. Guichard, "Constrained Route R., Patel, K., and J. Guichard, "Constrained Route
Distribution for Border Gateway Protocol/MultiProtocol Distribution for Border Gateway Protocol/MultiProtocol
Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684, Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
November 2006, <https://www.rfc-editor.org/info/rfc4684>. November 2006, <https://www.rfc-editor.org/info/rfc4684>.
[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <https://www.rfc-editor.org/info/rfc6513>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<https://www.rfc-editor.org/info/rfc6514>.
[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
RFC 6625, DOI 10.17487/RFC6625, May 2012, RFC 6625, DOI 10.17487/RFC6625, May 2012,
<https://www.rfc-editor.org/info/rfc6625>. <https://www.rfc-editor.org/info/rfc6625>.
[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 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
2015, <https://www.rfc-editor.org/info/rfc7432>. 2015, <https://www.rfc-editor.org/info/rfc7432>.
skipping to change at page 33, line 7 skipping to change at page 32, line 7
Patel, "Revised Error Handling for BGP UPDATE Messages", Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015, RFC 7606, DOI 10.17487/RFC7606, August 2015,
<https://www.rfc-editor.org/info/rfc7606>. <https://www.rfc-editor.org/info/rfc7606>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
16.2. Informative References 16.2. Informative References
[I-D.ietf-bess-evpn-bum-procedure-updates]
Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A.
Sajassi, "Updates on EVPN BUM Procedures", draft-ietf-
bess-evpn-bum-procedure-updates-08 (work in progress),
November 2019.
[RFC4541] Christensen, M., Kimball, K., and F. Solensky, [RFC4541] Christensen, M., Kimball, K., and F. Solensky,
"Considerations for Internet Group Management Protocol "Considerations for Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) Snooping (IGMP) and Multicast Listener Discovery (MLD) Snooping
Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006, Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006,
<https://www.rfc-editor.org/info/rfc4541>. <https://www.rfc-editor.org/info/rfc4541>.
Authors' Addresses Authors' Addresses
Ali Sajassi Ali Sajassi
Cisco Systems Cisco Systems
 End of changes. 14 change blocks. 
41 lines changed or deleted 48 lines changed or added

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