When the multicast group manager is notified that receivers are leaving a group on an interface, the multicast group manager invokes the PMGM_PRUNE_ALERT_CALLBACK callback. This callback notifies the routing protocols that clients no longer belong to the specified group. Therefore, the routing protocols must stop requesting multicast data for the specified groups.
The multicast group manager has a predefined set of rules that are used to determine when this callback is invoked. These rules are based on both the type of prune request sent by the client and the order the prune requests were received in.
Wildcard Prune Requests
When a wildcard prune for a group (*, g) is received and the final interface is being removed for the second-to-last client (that is, when interfaces for only a single client remain), the multicast group manager invokes the PMGM_PRUNE_ALERT_CALLBACK callback to that remaining client. After the final interface is removed for the last client (that is, when no other interfaces remain), then this callback is invoked for all the other clients that are registered with the multicast group manager.
Source-Specific Prune Requests
When a source-specific prune for a group (s, g) is received, the multicast group manager invokes the PMGM_PRUNE_ALERT_CALLBACK callback only for the client that owns the incoming interface towards the source s.
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
