An IPv6 multicast group is an arbitrary group of receivers that want to receive a particular data stream. This group has no physical or geographical boundaries--receivers can be located anywhere on the Internet or in any private network. Receivers that are interested in receiving data flowing to a particular group must join the group by signaling their local device. This signaling is achieved with the MLD protocol.

Devices use the MLD protocol to learn whether members of a group are present on their directly attached subnets. Hosts join multicast groups by sending MLD report messages. The network then delivers data to a potentially unlimited number of receivers, using only one copy of the multicast data on each subnet. IPv6 hosts that wish to receive the traffic are known as group members.

Packets delivered to group members are identified by a single multicast group address. Multicast packets are delivered to a group using best-effort reliability, just like IPv6 unicast packets.

The multicast environment consists of senders and receivers. Any host, regardless of whether it is a member of a group, can send to a group. However, only the members of a group receive the message.

A multicast address is chosen for the receivers in a multicast group. Senders use that address as the destination address of a datagram to reach all members of the group.

Membership in a multicast group is dynamic; hosts can join and leave at any time. There is no restriction on the location or number of members in a multicast group. A host can be a member of more than one multicast group at a time.

How active a multicast group is, its duration, and its membership can vary from group to group and from time to time. A group that has members may have no activity.

Cisco software supports the following protocols to implement IPv6 multicast routing:

• MLD is used by IPv6 devices to discover multicast listeners (nodes that want to receive multicast packets destined for specific multicast addresses) on directly attached links. There are two versions of MLD:

  • MLD version 1 is based on version 2 of the Internet Group Management Protocol (IGMP) for IPv4.
  • MLD version 2 is based on version 3 of the IGMP for IPv4.
• IPv6 multicast for Cisco software uses both MLD version 2 and MLD version 1. MLD version 2 is fully backward-compatible with MLD version 1 (described in RFC 2710). Hosts that support only MLD version 1 will interoperate with a device running MLD version 2. Mixed LANs with both MLD version 1 and MLD version 2 hosts are likewise supported.
• PIM-SM is used between devices so that they can track which multicast packets to forward to each other and to their directly connected LANs.
• PIM in Source Specific Multicast (PIM-SSM) is similar to PIM-SM with the additional ability to report interest in receiving packets from specific source addresses (or from all but the specific source addresses) to an IP multicast address.

The figure below shows where MLD and PIM-SM operate within the IPv6 multicast environment.

Figure 1. IPv6 Multicast Routing Protocols Supported for IPv6

To start implementing multicasting in the campus network, users must first define who receives the multicast. The MLD protocol is used by IPv6 devices to discover the presence of multicast listeners (for example, nodes that want to receive multicast packets) on their directly attached links, and to discover specifically which multicast addresses are of interest to those neighboring nodes. It is used for discovering local group and source-specific group membership. The MLD protocol provides a means to automatically control and limit the flow of multicast traffic throughout your network with the use of special multicast queriers and hosts.

The difference between multicast queriers and hosts is as follows:

• A querier is a network device, such as a device, that sends query messages to discover which network devices are members of a given multicast group.
• A host is a receiver, including devices, that send report messages to inform the querier of a host membership.

A set of queriers and hosts that receive multicast data streams from the same source is called a multicast group. Queriers and hosts use MLD reports to join and leave multicast groups and to begin receiving group traffic.

MLD uses the Internet Control Message Protocol (ICMP) to carry its messages. All MLD messages are link-local with a hop limit of 1, and they all have the alert option set. The alert option implies an implementation of the hop-by-hop option header.

MLD has three types of messages:

• Query--General, group-specific, and multicast-address-specific. In a query message, the multicast address field is set to 0 when MLD sends a general query. The general query learns which multicast addresses have listeners on an attached link.

Group-specific and multicast-address-specific queries are the same. A group address is a multicast address.

• Report--In a report message, the multicast address field is that of the specific IPv6 multicast address to which the sender is listening.
• Done--In a done message, the multicast address field is that of the specific IPv6 multicast address to which the source of the MLD message is no longer listening.

An MLD report must be sent with a valid IPv6 link-local source address, or the unspecified address (::), if the sending interface has not yet acquired a valid link-local address. Sending reports with the unspecified address is allowed to support the use of IPv6 multicast in the Neighbor Discovery Protocol.

For stateless autoconfiguration, a node is required to join several IPv6 multicast groups in order to perform duplicate address detection (DAD). Prior to DAD, the only address the reporting node has for the sending interface is a tentative one, which cannot be used for communication. Therefore, the unspecified address must be used.

MLD states that result from MLD version 2 or MLD version 1 membership reports can be limited globally or by interface. The MLD group limits feature provides protection against denial of service (DoS) attacks caused by MLD packets. Membership reports in excess of the configured limits will not be entered in the MLD cache, and traffic for those excess membership reports will not be forwarded.

MLD provides support for source filtering. Source filtering allows a node to report interest in listening to packets only from specific source addresses (as required to support SSM), or from all addresses except specific source addresses sent to a particular multicast address.

When a host using MLD version 1 sends a leave message, the device needs to send query messages to reconfirm that this host was the last MLD version 1 host joined to the group before it can stop forwarding traffic. This function takes about 2 seconds. This "leave latency" is also present in IGMP version 2 for IPv4 multicast.

MLD access groups provide receiver access control in Cisco IPv6 multicast devices. This feature limits the list of groups a receiver can join, and it allows or denies sources used to join SSM channels.

1.    enable


2.    configure terminal


3.    ipv6 multicast-routing [vrf vrf-name]

Device> enable

Device# configure terminal

Device(config)# ipv6 multicast-routing

1.    enable


2.    configure terminal


3.    interface type number


4.    ipv6 mld join-group [group-address] [[include | exclude] {source-address | source-list [acl]}


5.    ipv6 mld access-group access-list-name


6.    ipv6 mld static-group [group-address] [[include| exclude] {source-address | source-list [acl]}


7.    ipv6 mld query-max-response-time seconds


8.    ipv6 mld query-timeout seconds


9.    ipv6 mld query-interval seconds


10.    end


11.    show ipv6 mld groups [link-local] [group-name | group-address] [interface-type interface-number] [detail | explicit


12.    show ipv6 mfib summary


13.    show ipv6 mld interface [type number

Device> enable

Device# configure terminal

Device(config)# interface GigabitEthernet 1/0/0

Device(config-if)# ipv6 mld join-group FF04::12 exclude 2001:DB8::10::11

Device(config-if)# ipv6 access-list acc-grp-1

Device(config-if)# ipv6 mld static-group ff04::10 include 100::1

Device(config-if)# ipv6 mld query-max-response-time 20

Device(config-if)# ipv6 mld query-timeout 130

Device(config-if)# ipv6 mld query-interval 60

Device(config-if)# end

Device# show ipv6 mld groups GigabitEthernet 2/1/0

Device# show ipv6 mfib summary

Device# show ipv6 mld interface GigabitEthernet 2/1/0

1.    enable


2.    configure terminal


3.    interface type number


4.    no ipv6 mld router

Device> enable

Device# configure terminal

Device(config)# interface GigabitEthernet 1/0/0

Device(config-if)# no ipv6 mld router

1.    enable


2.    clear ipv6 mld [vrf vrf-name] traffic


3.    show ipv6 mld [vrf vrf-name] traffic

Device> enable

Device# clear ipv6 mld traffic

Device# show ipv6 mld traffic

1.    enable


2.    clear ipv6 mld [vrf vrf-name] counters interface-type

Device> enable

Device# clear ipv6 mld counters GigabitEthernet1/0/0