Internet Group Management Protocol version 3 (IGMPv3) supports multicast source filtering. Multicast source filtering allows a host to specify the source addresses from which it will receive multicast traffic; it also allows a host to specify the source addresses from which it will not receive multicast traffic. IGMP version 1 (IGMPv1) and IGMPv2 do not provide support for multicast source filtering.

Although IGMPv3 supports querier elections, this feature was introduced in IGMPv2. The router with the lowest IP address on the subnet is elected as the querier.
The querier is responsible for periodically sending out membership query messages to determine whether any hosts want to receive multicast packets for the multicast group. If at least one host responds with a membership report message, the querier will continue to send those multicast packets on that network segment. By default, membership query messages are sent every 60 seconds.
Although IGMPv3 supports leave group messages, this feature was introduced in IGMPv2.
In IGMPv1, a host leaves a multicast group silently. In IGMPv2, a host sends an IGMP leave message when it wants to leave a multicast group. IGMP routers maintain the IP address of the last reporter, which is the last host that sent a membership report message for that multicast group. If the last reporter sends a leave message, the IGMP router will wait an amount of time configured in the last member query response interval before sending a response and deleting the group. By default, the last member query response interval is one second.
Although IGMPv3 supports groupspecific queries, this feature was introduced in IGMPv2.
IGMPv1 queries are general queries sent to the 224.0.0.1 all hosts multicast address.
IGMPv2 queries are either general queries, which are sent to 224.0.0.1, or groupspecific queries, which are sent only to members of a particular multicast group.
When IGMPv2 is used, the Max Response Time field in membership query messages contains a nonzero value. In IGMPv1 messages, the field is set to a value of 0, which is interpreted to mean 100 deciseconds, or 10 seconds. The IGMPv2 membership query message is the only message that contains a nonzero value in the Max Response Time field; all other message types set the field to a value of 0. IGMPv3 membership query messages, on the other hand, use a Max Resp Code field from which the Max Response Time value is derived.
IGMPv3 does not support host membership report suppression; in fact, IGMPv3 removed support for host membership report suppression. This feature, which is supported in IGMPv1 and IGMPv2, prevents the sending of a membership report if a similar report is detected from another host on the network. IGMPv3 removes this restriction.