Ipv6 Administrative Scoping Overview - HP A8800 Configuration Manual

Figure 110 RPT building at the multicast source side
Receiver
Source
Server A
As shown in
1. When an IPv6 multicast source sends IPv6 multicast packets to IPv6 multicast group G, the DF in
each network segment unconditionally forwards the packets to the RP.
2. The routers along the path from the source's directly connected router to the RP form an RPT branch.
Each router on this branch adds a (*, G) entry to its forwarding table. The * means any IPv6
multicast source.
After a bidirectional RPT is built, multicast traffic is forwarded along the source-side RPT and receiver-side
RPT from IPv6 multicast sources to receivers.
NOTE:
If a receiver and an IPv6 multicast source are at the same side of the RP, the source-side RPT and the
receiver-side RPT may meet at a node before reaching the RP. In this case, IPv6 multicast packets from the
IPv6 multicast source are directly forwarded by the node to the receiver, instead of by the RP.

IPv6 administrative scoping overview

Division of IPv6 PIM-SM domains
Typically, an IPv6 PIM-SM/IPv6 BIDIR-PIM domain contains only one BSR, which is responsible for
advertising RP-set information within the entire IPv6 PIM-SM/IPv6 BIDIR-PIM domain. The information for
all multicast groups is forwarded within the network scope administered by the BSR. We call this IPv6
non-scoped BSR mechanism.
To implement refined management, an IPv6 PIM-SM/IPv6 BIDIR-PIM domain can be divided into one
IPv6 global-scoped zone and multiple IPv6 administratively scoped zones (IPv6 admin-scoped zones).
We call this IPv6 administrative scoping mechanism.
The IPv6 administrative scoping mechanism effectively releases stress on the management in a
single-BSR domain and enables provision of zone-specific services using private group addresses.
Host A
Source-side RPT
IPv6 Multicast packets
Figure 1 10, the process of building a source-side RPT is relatively simple:
RP
385
Source
Server B
Receiver
Host B
Receiver
Host C