| BESS WorkGroup | A. Sajassi |
| Internet-Draft | S. Thoria |
| Intended status: Standards Track | Cisco Systems |
| Expires: October 30, 2020 | K. Patel |
| Arrcus | |
| J. Drake | |
| W. Lin | |
| Juniper Networks | |
| April 28, 2020 |
IGMP and MLD Proxy for EVPN
draft-ietf-bess-evpn-igmp-mld-proxy-05
Ethernet Virtual Private Network (EVPN) solution is becoming pervasive in data center (DC) applications for Network Virtualization Overlay (NVO) and DC interconnect (DCI) services, and in service provider (SP) applications for next generation virtual private LAN services.
This draft describes how to support efficiently endpoints running IGMP for the above services over an EVPN network by incorporating IGMP proxy procedures on EVPN PEs.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 30, 2020.
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Ethernet Virtual Private Network (EVPN) solution [RFC7432] is becoming pervasive in data center (DC) applications for Network Virtualization Overlay (NVO) and DC interconnect (DCI) services, and in service provider (SP) applications for next generation virtual private LAN services.
In DC applications, a point of delivery (POD) can consist of a collection of servers supported by several top of rack (TOR) and Spine switches. This collection of servers and switches are self contained and may have their own control protocol for intra-POD communication and orchestration. However, EVPN is used as standard way of inter-POD communication for both intra-DC and inter-DC. A subnet can span across multiple PODs and DCs. EVPN provides robust multi-tenant solution with extensive multi-homing capabilities to stretch a subnet (VLAN) across multiple PODs and DCs. There can be many hosts/VMs ( several hundreds) attached to a subnet that is stretched across several PODs and DCs.
These hosts/VMs express their interests in multicast groups on a given subnet/VLAN by sending IGMP membership reports (Joins) for their interested multicast group(s). Furthermore, an IGMP router periodically sends membership queries to find out if there are hosts on that subnet that are still interested in receiving multicast traffic for that group. The IGMP/MLD Proxy solution described in this draft accomplishes has three objectives:
The first two objectives are achieved by using IGMP/MLD proxy on the PE and the third objective is achieved by setting up a multicast tunnel (e.g., ingress replication) only among the PEs that have interest in that multicast group(s) based on the trigger from IGMP/MLD proxy processes. The proposed solutions for each of these objectives are discussed in the following sections.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
This document also assumes familiarity with the terminology of [RFC7432]. Though most of the place this document uses term IGMP membership request (Joins), the text applies equally for MLD membership request too. Similarly, text for IGMPv2 applies to MLDv1 and text for IGMPv3 applies to MLDv2. IGMP / MLD version encoding in BGP update is stated in Section 9
The IGMP Proxy mechanism is used to reduce the flooding of IGMP messages over an EVPN network similar to ARP proxy used in reducing the flooding of ARP messages over EVPN. It also provides a triggering mechanism for the PEs to setup their underlay multicast tunnels. The IGMP Proxy mechanism consists of two components:
When IGMP protocol is used between hosts/VMs and their first hop EVPN router (EVPN PE), Proxy-reporting is used by the EVPN PE to summarize (when possible) reports received from downstream hosts and propagate them in BGP to other PEs that are interested in the information. This is done by terminating the IGMP Reports in the first hop PE, and translating and exchanging the relevant information among EVPN BGP speakers. The information is again translated back to IGMP message at the recipient EVPN speaker. Thus it helps create an IGMP overlay subnet using BGP. In order to facilitate such an overlay, this document also defines a new EVPN route type NLRI, the EVPN Selective Multicast Ethernet Tag route, along with its procedures to help exchange and register IGMP multicast groups Section 9.
When a PE wants to advertise an IGMP membership report (Join) using the BGP EVPN route, it follows the following rules (BGP encoding stated in Section 9):
When a PE wants to withdraw an EVPN SMET route corresponding to an IGMPv2 Leave Group (Leave) or IGMPv3 "Leave" equivalent message, it follows the following rules:
As mentioned in the previous sections, each PE MUST have proxy querier functionality for the following reasons:
Consider the EVPN network of Figure-1, where there is an EVPN instance configured across the PEs shown in this figure (namely PE1, PE2, and PE3). Let's consider that this EVPN instance consists of a single bridge domain (single subnet) with all the hosts, sources, and the multicast router connected to this subnet. PE1 only has hosts connected to it. PE2 has a mix of hosts and a multicast source. PE3 has a mix of hosts, a multicast source, and a multicast router. Furthermore, let's consider that for (S1,G1), R1 is used as the multicast router. The following subsections describe the IGMP proxy operation in different PEs with regard to whether the locally attached devices for that subnet are:
+--------------+
| |
| |
+----+ | | +----+
H1:(*,G1)v2 ---| | | | | |---- H6(*,G1)v2
H2:(*,G1)v2 ---| PE1| | IP/MPLS | | PE2|---- H7(S2,G2)v3
H3:(*,G1)v3 ---| | | Network | | |---- S2
H4:(S2,G2)v3 --| | | | | |
+----+ | | +----+
| |
+----+ | |
H5:(S1,G1)v3 --| | | |
S1 ---| PE3| | |
R1 ---| | | |
+----+ | |
| |
+--------------+
Figure 1: EVPN network
When PE1 receives an IGMPv2 Join Report from H1, it does not forward this join to any of its other ports (for this subnet) because all these local ports are associated with the hosts/VMs. PE1 sends an EVPN Multicast Group route corresponding to this join for (*,G1) and setting v2 flag. This EVPN route is received by PE2 and PE3 that are the members of the same BD (i.e., same EVI in case of VLAN-based service or EVI,VLAN in case of VLAN-aware bundle service). PE3 reconstructs the IGMPv2 Join Report from this EVPN BGP route and only sends it to the port(s) with multicast routers attached to it (for that subnet). In this example, PE3 sends the reconstructed IGMPv2 Join Report for (*,G1) only to R1. Furthermore, even though PE2 receives the EVPN BGP route, it does not send it to any of its ports for that subnet; viz, ports associated with H6 and H7.
When PE1 receives the second IGMPv2 Join from H2 for the same multicast group (*,G1), it only adds that port to its OIF list but it doesn't send any EVPN BGP route because there is no change in information. However, when it receives the IGMPv3 Join from H3 for the same (*,G1). Besides adding the corresponding port to its OIF list, it re-advertises the previously sent EVPN SMET route with the v3 and exclude flag set.
Finally when PE1 receives the IMGMPv3 Join from H4 for (S2,G2), it advertises a new EVPN SMET route corresponding to it.
The main difference in this case is that when PE2 receives the IGMPv3 Join from H7 for (S2,G2), it does advertise it in BGP to support source move even though PE2 knows that S2 is attached to its local AC. PE2 adds the port associated with H7 to its OIF list for (S2,G2). The processing for IGMPv2 received from H6 is the same as the IGMPv2 Join described in previous section.
The main difference in this case relative to the previous two sections is that IGMP v2/v3 Join messages received locally needs to be sent to the port associated with router R1. Furthermore, the Joins received via BGP (SMET) need to be passed to the R1 port but filtered for all other ports.
Because the LAG flow hashing algorithm used by the CE is unknown at the PE, in an All-Active redundancy mode it must be assumed that the CE can send a given IGMP message to any one of the multi-homed PEs, either DF or non-DF; i.e., different IGMP Join messages can arrive at different PEs in the redundancy group and furthermore their corresponding Leave messages can arrive at PEs that are different from the ones that received the Join messages. Therefore, all PEs attached to a given ES must coordinate IGMP Join and Leave Group (x,G) state, where x may be either '*' or a particular source S, for each BD on that ES. This allows the DF for that [ES,BD] to correctly advertise or withdraw a Selective Multicast Ethernet Tag (SMET) route for that (x,G) group in that BD when needed. All-Active multihoming PEs for a given ES MUST support IGMP synchronization procedures described in this section if they need to perform IGMP proxy for hosts connected to that ES.
When a PE, either DF or non-DF, receives on a given multihomed ES operating in All-Active redundancy mode, an IGMP Membership Report for (x,G), it determines the BD to which the IGMP Membership Report belongs. If the PE doesn't already have local IGMP Join (x,G) state for that BD on that ES, it MUST instantiate local IGMP Join (x,G) state and MUST advertise a BGP IGMP Join Synch route for that [ES,BD]. Local IGMP Join (x, G) state refers to IGMP Join (x,G) state that is created as a result of processing an IGMP Membership Report for (x,G).
The IGMP Join Synch route MUST carry the ES-Import RT for the ES on which the IGMP Membership Report was received. Thus it MUST only be sent to the PEs attached to that ES and not any other PEs.
When a PE, either DF or non-DF, receives an IGMP Join Synch route it installs that route and if it doesn't already have IGMP Join (x,G) state for that [ES,BD], it MUST instantiate that IGMP Join (x,G) state - i.e., IGMP Join (x,G) state is the union of the local IGMP Join (x,G) state and the installed IGMP Join Synch route. If the DF did not already advertise (originate) a SMET route for that (x,G) group in that BD, it MUST do so now.
When a PE, either DF or non-DF, deletes its local IGMP Join (x, G) state for that [ES,BD], it MUST withdraw its BGP IGMP Join Synch route for that [ES,BD].
When a PE, either DF or non-DF, receives the withdrawal of an IGMP Join Synch route from another PE it MUST remove that route. When a PE has no local IGMP Join (x,G) state and it has no installed IGMP Join Synch routes, it MUST remove IGMP Join (x,G) state for that [ES,BD]. If the DF no longer has IGMP Join (x,G) state for that BD on any ES for which it is DF, it MUST withdraw its SMET route for that (x,G) group in that BD.
In other words, a PE advertises an SMET route for that (x,G) group in that BD when it has IGMP Join (x,G) state in that BD on at least one ES for which it is DF and it withdraws that SMET route when it does not have IGMP Join (x,G) state in that BD on any ES for which it is DF.
When a PE, either DF or non-DF, receives, on a given multihomed ES operating in All-Active redundancy mode, an IGMP Leave Group message for (x,G) from the attached CE, it determines the BD to which the IGMPv2 Leave Group belongs. Regardless of whether it has IGMP Join (x,G) state for that [ES,BD], it initiates the (x,G) leave group synchronization procedure, which consists of the following steps:
When a PE, either DF or non-DF, receives an IGMP Leave Synch route it installs that route and it starts a timer for (x,G) on the specified [ES,BD] whose value is set to the Maximum Response Time in the received IGMP Leave Synch route. Note that the receipt of subsequent IGMPv2 Leave Group messages or BGP Leave Synch routes for (x,G) do not change the value of a currently running Maximum Response Time timer and are ignored by the PE.
If a PE attached to the multihomed ES receives an IGMP Membership Report for (x,G) before the Maximum Response Time timer expires, it advertises a BGP IGMP Join Synch route for that [ES,BD]. If it doesn't already have local IGMP Join (x, G) state for that [ES, BD], it instantiates local IGMP Join (x,G) state. If the DF is not currently advertising (originating) a SMET route for that (x,G) group in that BD, it does so now.
If a PE attached to the multihomed ES receives an IGMP Join Synch route for (x,G) before the Maximum Response Time timer expires, it installs that route and if it doesn't already have IGMP Join (x,G) state for that BD on that ES, it instantiates that IGMP Join (x,G) state. If the DF has not already advertised (originated) a SMET route for that (x,G) group in that BD, it does so now.
When the Maximum Response Timer expires a PE that has advertised an IGMP Leave Synch route, withdraws it. Any PE attached to the multihomed ES, that started the Maximum Response Time and has no local IGMP Join (x,G) state and no installed IGMP Join Synch routes, it removes IGMP Join (x,G) state for that [ES,BD]. If the DF no longer has IGMP Join (x,G) state for that BD on any ES for which it is DF, it withdraws its SMET route for that (x,G) group in that BD.
A PE which has received an IGMP Join, would have synced the IGMP Join by the procedure defined in section 6.1. If a PE with local join state goes down or the PE to CE link goes down, it would lead to a mass withdraw of multicast routes. Remote PEs (PEs where these routes were remote IGMP Joins) SHOULD not remove the state immediately; instead General Query SHOULD be generated to refresh the states. There are several ways to Some of the way to detect failure at a peer, e.g. using IGP next hop tracking or ES route withdraw.
Note that to facilitate state synchronization after failover, the PEs attached to a mutihomed ES operating in Single-Active redundancy mode SHOULD also coordinate IGMP Join (x,G) state. In this case all IGMP Join messages are received by the DF and distributed to the non-DF PEs using the procedures described above.
If an ingress PE uses ingress replication, then for a given (x,G) group in a given 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).
This document defines three new BGP EVPN routes to carry IGMP membership reports. The route type is known as:
+ 6 - Selective Multicast Ethernet Tag Route
+ 7 - Multicast Join Synch Route
+ 8 - Multicast Leave Synch Route
The detailed encoding and procedures for this route type are described in subsequent sections.
A Selective Multicast Ethernet Tag route type specific EVPN NLRI consists of the following:
+---------------------------------------+
| RD (8 octets) |
+---------------------------------------+
| Ethernet Tag ID (4 octets) |
+---------------------------------------+
| Multicast Source Length (1 octet) |
+---------------------------------------+
| Multicast Source Address (variable) |
+---------------------------------------+
| Multicast Group Length (1 octet) |
+---------------------------------------+
| Multicast Group Address (Variable) |
+---------------------------------------+
| Originator Router Length (1 octet) |
+---------------------------------------+
| Originator Router Address (variable) |
+---------------------------------------+
| Flags (1 octet) |
+---------------------------------------+
For the purpose of BGP route key processing, all the fields are considered to be part of the prefix in the NLRI except for the one- octet flag field. The Flags fields are defined as follows:
0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+
| reserved |IE|v3|v2|v1|
+--+--+--+--+--+--+--+--+
This section describes the procedures used to construct the Selective Multicast Ethernet Tag (SMET) route.
The Route Distinguisher (RD) SHOULD be a Type 1 RD [RFC4364] . The value field comprises an IP address of the PE (typically, the loopback address) followed by a number unique to the PE.
The Ethernet Tag ID MUST be set as follows:
The Multicast Source Length MUST be set to length of the multicast Source address in bits. If the Multicast Source Address field contains an IPv4 address, then the value of the Multicast Source Length field is 32. If the Multicast Source Address field contains an IPv6 address, then the value of the Multicast Source Length field is 128. In case of a (*, G) Join, the Multicast Source Length is set to 0.
The Multicast Source Address is the source IP address from the IGMP membership report. In case of a (*, G), this field is not used.
The Multicast Group Length MUST be set to length of multicast group address in bits. If the Multicast Group Address field contains an IPv4 address, then the value of the Multicast Group Length field is 32. If the Multicast Group Address field contains an IPv6 address, then the value of the Multicast Group Length field is 128.
The Multicast Group Address is the Group address from the IGMP or MLD membership report.
The Originator Router Length is the length of the Originator Router Address in bits.
The Originator Router Address is the IP address of router originating this route. The SMET Originator Router IP address MUST match that of the IMET (or SPMSI AD) route originated for the same EVI by the same downstream PE.
The Flags field indicates the version of IGMP protocol from which the membership report was received. It also indicates whether the multicast group had the INCLUDE or EXCLUDE bit set.
Reserve bit MUST be set to 0. They can be defined in future by other document.
IGMP is used to receive group membership information from hosts/VMs by TORs. Upon receiving the hosts/VMs expression of interest of a particular group membership, this information is then forwarded using SMET route. The NLRI also keeps track of receiver's IGMP protocol version and any source filtering for a given group membership. All EVPN SMET routes are announced with per- EVI Route Target extended communities.
When a router that receives a BGP Update that contains the Selective Multicast Route flag with its Partial bit set (Not following this specification) determines that the route is malformed, the router SHOULD treat this Update as malformed . Error MUST be considered as BGP error and SHOULD be discarded as per [RFC7606]. An implementation SHOULD provide debugging facilities to permit issues caused by a malformed join sync route to be diagnosed. At a minimum, such facilities MUST include logging an error when such an route is detected.
If there is multicast router connected behind the EVPN domain, the PE MAY originate a default SMET (*,*) to get all multicast traffic in domain.
+--------------+
| |
| |
| | +----+
| | | |---- H1(*,G1)v2
| IP/MPLS | | PE1|---- H2(S2,G2)v3
| Network | | |---- S2
| | | |
| | +----+
| |
+----+ | |
+----+ | | | |
| | S1 ---| PE2| | |
|PIM |----R1 ---| | | |
|ASM | +----+ | |
| | | |
+----+ +--------------+
Figure 2: Multicast Router behind EVPN domain
Consider the EVPN network of Figure-2, where there is an EVPN instance configured across the PEs. Lets consider PE2 is connected to multicast router R1 and there is a network running PIM ASM behind R1. If there are receivers behind the PIM ASM network, the PIM Join would be forwarded to the PIM RP (Rendezvous Point). If receivers behind PIM ASM network are interested in a multicast flow originated by multicast source S2 (behind PE1), it is necessary for PE2 to receive multicast traffic. In this case PE2 MUST originate a (*,*) SMET route to receive all of the multicast traffic in the EVPN domain.
This EVPN route type is used to coordinate IGMP Join (x,G) state for a given BD between the PEs attached to a given ES operating in All- Active (or Single-Active) redundancy mode and it consists of following:
+--------------------------------------------------+
| RD (8 octets) |
+--------------------------------------------------+
| Ethernet Segment Identifier (10 octets) |
+--------------------------------------------------+
| Ethernet Tag ID (4 octets) |
+--------------------------------------------------+
| Multicast Source Length (1 octet) |
+--------------------------------------------------+
| Multicast Source Address (variable) |
+--------------------------------------------------+
| Multicast Group Length (1 octet) |
+--------------------------------------------------+
| Multicast Group Address (Variable) |
+--------------------------------------------------+
| Originator Router Length (1 octet) |
+--------------------------------------------------+
| Originator Router Address (variable) |
+--------------------------------------------------+
| Flags (1 octet) |
+--------------------------------------------------+
For the purpose of BGP route key processing, all the fields are considered to be part of the prefix in the NLRI except for the one- octet Flags field, whose fields are defined as follows:
0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+
| reserved |IE|v3|v2|v1|
+--+--+--+--+--+--+--+--+
The Flags field assists in distributing IGMP membership interest of a given host/VM for a given multicast route. The version bits help associate IGMP version of receivers participating within the EVPN domain. The include/exclude bit helps in creating filters for a given multicast route.
If route is being prepared for IPv6 (MLD) then bit 7 indicates support for MLD version 1. The second least significant bit, bit 6 indicates support for MLD version 2. Since there is no MLD version 3, in case of IPv6 route third least significant bit MUST be 0. In case of IPv6 route, the fourth least significant bit MUST be ignored if bit 6 is not set.
This section describes the procedures used to construct the IGMP Join Synch route. Support for this route type is optional. If a PE does not support this route, then it MUST NOT indicate that it supports 'IGMP proxy' in the Multicast Flag extended community for the EVIs corresponding to its multi-homed Ethernet Segments (ESs).
An IGMP Join Synch route MUST carry exactly one ES-Import Route Target extended community, the one that corresponds to the ES on which the IGMP Join was received. It MUST also carry exactly one EVI-RT EC, the one that corresponds to the EVI on which the IGMP Join was received. See Section 9.5 for details on how to encode and construct the EVI-RT EC.
The Route Distinguisher (RD) SHOULD be a Type 1 RD [RFC4364] . The value field comprises an IP address of the PE (typically, the loopback address) followed by a number unique to the PE.
The Ethernet Segment Identifier (ESI) MUST be set to the 10-octet value defined for the ES.
The Ethernet Tag ID MUST be set as follows:
The Multicast Source length MUST be set to length of Multicast Source address in bits. If the Multicast Source field contains an IPv4 address, then the value of the Multicast Source Length field is 32. If the Multicast Source field contains an IPv6 address, then the value of the Multicast Source Length field is 128. In case of a (*,G) Join, the Multicast Source Length is set to 0.
The Multicast Source is the Source IP address of the IGMP membership report. In case of a (*, G) Join, this field does not exist.
The Multicast Group length MUST be set to length of multicast group address in bits. If the Multicast Group field contains an IPv4 address, then the value of the Multicast Group Length field is 32. If the Multicast Group field contains an IPv6 address, then the value of the Multicast Group Length field is 128.
The Multicast Group is the Group address of the IGMP membership report.
The Originator Router Length is the length of the Originator Router address in bits.
The Originator Router Address is the IP address of Router Originating the prefix.
The Flags field indicates the version of IGMP protocol from which the membership report was received. It also indicates whether the multicast group had INCLUDE or EXCLUDE bit set.
Reserve bit MUST be set to 0. They can be defined in future by other document.
When a multihomed router that receives a BGP Update that contains the Multicast Join Sync Route flag with its Partial bit set (Not following this specification) determines that the route is malformed, the router SHOULD treat this Update as malformed . Error MUST be considered as BGP error and SHOULD be discarded as per [RFC7606]. An implementation SHOULD provide debugging facilities to permit issues caused by a malformed join sync route to be diagnosed. At a minimum, such facilities MUST include logging an error when such an route is detected.
This EVPN route type is used to coordinate IGMP Leave Group (x,G) state for a given BD between the PEs attached to a given ES operating in All-Active (or Single-Active) redundancy mode and it consists of following:
+--------------------------------------------------+
| RD (8 octets) |
+--------------------------------------------------+
| Ethernet Segment Identifier (10 octets) |
+--------------------------------------------------+
| Ethernet Tag ID (4 octets) |
+--------------------------------------------------+
| Multicast Source Length (1 octet) |
+--------------------------------------------------+
| Multicast Source Address (variable) |
+--------------------------------------------------+
| Multicast Group Length (1 octet) |
+--------------------------------------------------+
| Multicast Group Address (Variable) |
+--------------------------------------------------+
| Originator Router Length (1 octet) |
+--------------------------------------------------+
| Originator Router Address (variable) |
+--------------------------------------------------+
| Reserved (4 octet) |
+--------------------------------------------------+
| Maximum Response Time (1 octet) |
+--------------------------------------------------+
| Flags (1 octet) |
+--------------------------------------------------+
For the purpose of BGP route key processing, all the fields are considered to be part of the prefix in the NLRI except for the Reserved, Maximum Response Time and the one-octet Flags field, whose fields are defined as follows:
0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+
| reserved |IE|v3|v2|v1|
+--+--+--+--+--+--+--+--+
The Flags field assists in distributing IGMP membership interest of a given host/VM for a given multicast route. The version bits help associate IGMP version of receivers participating within the EVPN domain. The include/exclude bit helps in creating filters for a given multicast route.
If route is being prepared for IPv6 (MLD) then bit 7 indicates support for MLD version 1. The second least significant bit, bit 6 indicates support for MLD version 2. Since there is no MLD version 3, in case of IPv6 route third least significant bit MUST be 0. In case of IPv6 route, the fourth least significant bit MUST be ignored if bit 6 is not set.
Reserve bit in flag MUST be set to 0. They can be defined in future by other document.
This section describes the procedures used to construct the IGMP Leave Synch route. Support for this route type is optional. If a PE does not support this route, then it MUST not indicate that it supports 'IGMP proxy' in Multicast Flag extended community for the EVIs corresponding to its multi-homed Ethernet Segments.
An IGMP Leave Synch route MUST carry exactly one ES-Import Route Target extended community, the one that corresponds to the ES on which the IGMP Leave was received. It MUST also carry exactly one EVI-RT EC, the one that corresponds to the EVI on which the IGMP Leave was received. See Section 9.5 for details on how to form the EVI-RT EC.
The Route Distinguisher (RD) SHOULD be a Type 1 RD [RFC4364]. The value field comprises an IP address of the PE (typically, the loopback address) followed by a number unique to the PE.
The Ethernet Segment Identifier (ESI) MUST be set to the 10-octet value defined for the ES.
The Ethernet Tag ID MUST be set as follows:
The Multicast Source length MUST be set to length of multicast source address in bits. If the Multicast Source field contains an IPv4 address, then the value of the Multicast Source Length field is 32. If the Multicast Source field contains an IPv6 address, then the value of the Multicast Source Length field is 128. In case of a (*, G) Join, the Multicast Source Length is set to 0.
The Multicast Source is the Source IP address of the IGMP membership report. In case of a (*, G) Join, this field does not exist.
The Multicast Group length MUST be set to length of multicast group address in bits. If the Multicast Group field contains an IPv4 address, then the value of the Multicast Group Length field is 32. If the Multicast Group field contains an IPv6 address, then the value of the Multicast Group Length field is 128.
The Multicast Group is the Group address of the IGMP membership report.
The Originator Router Length is the length of the Originator Router address in bits.
The Originator Router Address is the IP address of Router Originating the prefix.
Reserved field is not part of the route key. The originator MUST set the reserved field to Zero , the receiver SHOULD ignore it and if it needs to be propagated, it MUST propagate it unchanged
Maximum Response Time is value to be used while sending query as defined in [RFC2236]
The Flags field indicates the version of IGMP protocol from which the membership report was received. It also indicates whether the multicast group had INCLUDE or EXCLUDE bit set.
When a multihomed router that receives a BGP Update that contains the Multicast Leave Sync Route flag with its Partial bit set (Not following this specification) determines that the route is malformed, the router SHOULD treat this Update as malformed . Error MUST be considered as BGP error and SHOULD be discarded as per [RFC7606]. An implementation SHOULD provide debugging facilities to permit issues caused by a malformed join sync route to be diagnosed. At a minimum, such facilities MUST include logging an error when such an route is detected.
The 'Multicast Flags' extended community is a new EVPN extended community. EVPN extended communities are transitive extended communities with a Type field value of 6. IANA will assign a Sub-Type from the 'EVPN Extended Community Sub-Types' registry.
A PE that supports IGMP proxy on a given BD MUST attach this extended community to the Inclusive Multicast Ethernet Tag (IMET) route it advertises for that BD and it MUST set the IGMP Proxy Support flag to 1. Note that an [RFC7432] compliant PE will not advertise this extended community so its absence indicates that the advertising PE does not support IGMP Proxy.
The advertisement of this extended community enables more efficient multicast tunnel setup from the source PE specially for ingress replication - i.e., if an egress PE supports IGMP proxy but doesn't have any interest in a given (x,G), it advertises its IGMP proxy capability using this extended community but it does not advertise any SMET route for that (x,G). When the source PE (ingress PE) receives such advertisements from the egress PE, it does not replicate the multicast traffic to that egress PE; however, it does replicate the multicast traffic to the egress PEs that don't advertise such capability even if they don't have any interests in that (x,G).
A Multicast Flags extended community is encoded as an 8-octet value, as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=0x06 | Sub-Type=0x09| Flags (2 Octets) |M|I|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved=0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The low-order (lease significant) two bits are defined as the "IGMP Proxy Support and MLD Proxy Support" bit. The absence of this extended community also means that the PE does not support IGMP proxy. where:
If a router does not support this specification, it MUST not add Multicast Flags Extended Community in BGP route. A router receiving BGP update , if M and I both flag are zero (0), the router MUST treat this Update as malformed . Receiver of such update MUST ignore the extended community.
In EVPN, every EVI is associated with one or more Route Targets (RTs). These Route Targets serve two functions:
An IGMP Join Synch or IGMP Leave Synch route is associated with a particular combination of ES and EVI. These routes need to be distributed only to PEs that are attached to the associated ES. Therefore these routes carry the ES-Import RT for that ES.
Since an IGMP Join Synch or IGMP Leave Synch route does not need to be distributed to all the PEs on which the associated EVI exists, these routes cannot carry the RT associated with that EVI. Therefore, when such a route arrives at a particular PE, the route's RTs cannot be used to identify the EVI to which the route applies. Some other means of associating the route with an EVI must be used.
This document specifies four new Extended Communities (EC) that can be used to identify the EVI with which a route is associated, but which do not have any effect on the distribution of the route. These new ECs are known as the "Type 0 EVI-RT EC", the "Type 1 EVI-RT EC", the "Type 2 EVI-RT EC", and the "Type 3 EVI-RT EC".
Each IGMP Join Synch or IGMP Leave Synch route MUST carry exactly one EVI-RT EC. The EVI-RT EC carried by a particular route is constructed as follows. Each such route is the result of having received an IGMP Join or an IGMP Leave message from a particular BD. The route is said to be associated associated with that BD. For each BD, there is a corresponding RT that is used to ensure that routes "about" that BD are distributed to all PEs attached to that BD. So suppose a given IGMP Join Synch or Leave Synch route is associated with a given BD, say BD1, and suppose that the corresponding RT for BD1 is RT1. Then:
An IGMP Join Synch or Leave Synch route MUST carry exactly one EVI-RT EC.
Suppose a PE receives a particular IGMP Join Synch or IGMP Leave Synch route, say R1, and suppose that R1 carries an ES-Import RT that is one of the PE's Import RTs. If R1 has no EVI-RT EC, or has more than one EVI-RT EC, the PE MUST apply the "treat-as-withdraw" procedure of [RFC7606].
Note that an EVI-RT EC is not a Route Target Extended Community, is not visible to the RT Constrain mechanism [RFC4684] , and is not intended to influence the propagation of routes by BGP.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=0x06 | Sub-Type=n | RT associated with EVI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RT associated with the EVI (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the value of 'n' is 0x0A, 0x0B, 0x0C, or 0x0D corresponding to EVI-RT type 0, 1, 2, or 3 respectively.
There are certain situations in which an ES is attached to a set of PEs that are not all in the same AS, or not all operated by the same provider. In some such situations, the RT that corresponds to a particular EVI may be different in each AS. If a route is propagated from AS1 to AS2, an ASBR at the AS1/AS2 border may be provisioned with a policy that removes the RTs that are meaningful in AS1 and replaces them with the corresponding (i.e., RTs corresponding to the same EVIs) RTs that are meaningful in AS2. This is known as RT-rewriting.
Note that if a given route's RTs are rewritten, and the route carries an EVI-RT EC, the EVI-RT EC needs to be rewritten as well.
IGMP MAY be configured with immediate leave option. This allows the device to remove the group entry from the multicast routing table immediately upon receiving a IGMP leave message for (x,G). In case of all active multi-homing while synchronizing the IGMP Leave state to redundancy peers, Maximum Response Time MAY be filled in as Zero. Implementations SHOULD have identical configuration across multi-homed peers. In case IGMP Leave Synch route is received with Maximum Response Time Zero, irrespective of local IGMP configuration it MAY be processed as an immediate leave.
This document does not provide any detail about IGMPv1 processing. Multicast working group are in process of deprecating uses of IGMPv1. Implementations MUST only use IGMPv2 and above for IPv4 and MLDv1 and above for IPv6. IGMP V1 routes MUST be considered as invalid and handled as per [RFC7606]
Same security considerations as [RFC7432] ,[RFC2236] ,[RFC3376] , [RFC2710], [RFC3810].
IANA has allocated the following codepoints from the EVPN Extended Community sub-types registry.
0x09 Multicast Flags Extended Community [this document]
0x0A EVI-RT Type 0 [this document]
0x0B EVI-RT Type 1 [this document]
0x0C EVI-RT Type 2 [this document]
IANA is requested to allocate a new codepoint from the EVPN Extended Community sub-types registry for the following.
0x0D EVI-RT Type 3 [this document]
IANA has allocated the following EVPN route types from the EVPN Route Type registry.
6 - Selective Multicast Ethernet Tag Route
7 - Multicast Join Synch Route
8 - Multicast Leave Synch Route
The Multicast Flags Extended Community contains a 16-bit Flags field. The bits are numbered 0-15, from high-order to low-order.
The registry should be initialized as follows:
Bit Name Reference
---- -------------- -------------
0 - 13 Unassigned
14 MLD Proxy Support This document
15 IGMP Proxy Support This document
The registration policy should be "First Come First Served".
The authors would like to thank Stephane Litkowski, Jorge Rabadan, Anoop Ghanwani, Jeffrey Haas, Krishna Muddenahally Ananthamurthy for reviewing and providing valuable comment.
Mankamana Mishra
Cisco systems
Email: mankamis@cisco.com
Derek Yeung
Arrcus
Email: derek@arrcus.com
| [RFC4541] | Christensen, M., Kimball, K. and F. Solensky, "Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006. |