Routing and Remote Access Service

Previous Topic Next Topic

IP Multicast Components and Processes

The IP multicast components of the Routing and Remote Access service are shown in Figure 2.3.

Figure 2.3    IP Multicast and the Routing and Remote Access Service
Enlarge figure

Figure 2.3 IP Multicast and the Routing and Remote Access Service

The following sections describe typical IP multicast forwarding processes in terms of the Routing and Remote Access service IP multicast components.

Incoming Multicast Packet (MFE Not Present)

An incoming IP multicast packet's source address and group address are compared to the MFEs to the IP multicast forwarding table. If an entry for the [source, group] is not found, an inactive MFE for the [source, group] is added to the multicast forwarding table and communicated to the Multicast Group Manager. The packet is placed in a buffer awaiting the change from an inactive MFE to an active MFE.

Incoming Multicast Packet (Active MFE Present)

An incoming IP multicast packet's source address and group address are compared to the MFEs in the IP multicast forwarding table. If an active entry for the [source, group] is found, the multicast traffic is forwarded out the appropriate interface(s).

Multicast Routing Protocol Network Communication

The IGMP v2 IP multicast routing protocol operates like any other Windows Sockets application sending and receiving IP packets.

Multicast Forwarding Table Updates

Based on the ongoing IGMP traffic on interfaces on which IGMP router mode is enabled, the IGMP v2 multicast routing protocol updates [source, group] entries in the Multicast Group Manager. The Multicast Group Manager then updates the IP multicast forwarding table.

© 1985-2000 Microsoft Corporation. All rights reserved.