Ipv6 Administrative Scoping Overview - HP MSR2003 Configuration Manual

Figure 92 RPT building at the IPv6 multicast source side
As shown in
4. When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in
each subnet unconditionally forwards the packets to the RP.
5. The routers along the path from the source's directly connected router to the RP constitute an RPT
branch. Each router on this branch adds to its forwarding table a (*, G) entry, where the asterisk
(*) represents any IPv6 multicast source.
After a bidirectional RPT is built, the IPv6 multicast sources send multicast traffic to the RP along the
source-side RPT. The RP forwards the traffic to the receivers along the receiver-side RPT.
IMPORTANT:
If a receiver and a source are at the same side of the RP, the source-side RPT and the receiver-side RPT
might meet at a node before reaching the RP. In this case, the multicast packets from the IPv6 multicast
source to the receiver are directly forwarded by the node, instead of by the RP.

IPv6 administrative scoping overview

Typically, an IPv6 PIM-SM domain or an IPv6 BIDIR-PIM domain contains only one BSR, which is
responsible for advertising RP-set information within the entire domain. Information about all IPv6
multicast groups is forwarded within the network that the BSR administers. This is called the "IPv6
non-scoped BSR mechanism."
IPv6 administrative scoping mechanism
To implement refined management, you can divide an IPv6 PIM-SM domain or IPv6 BIDIR-PIM domain
into an IPv6 global-scoped zone and multiple IPv6 administratively-scoped zones (admin-scoped zones).
This is called the "IPv6 administrative scoping mechanism."
The administrative scoping mechanism effectively releases stress on the management in a single-BSR
domain and enables provision of zone-specific services through private group addresses.
Figure 92, the process for building a source-side RPT is relatively simple:
287