Question 120
At a multimedia training network running Junos multicast routers, a Junos specialist investigates this scenario: An enterprise deploys IPv6 group delivery but attempts to identify receivers with ordinary IPv6 unicast addresses. The corrected tree must respect source and group authorization. When would the described mechanism be appropriate?
Explanation
Correct Answer
For a multimedia training network running Junos multicast routers, this mechanism fits the requirement: Use scoped IPv6 multicast addresses for one-to-many IPv6 applications. The design is appropriate because: IPv6 multicast destinations begin in the FF00::/8 range and include scope information. In this scenario, the observed issue is: An enterprise deploys IPv6 group delivery but attempts to identify receivers with ordinary IPv6 unicast addresses. The corresponding implementation is: Select a suitable IPv6 multicast group and scope for the approved application.
Incorrect Answers
IPv4 multicast traffic uses group addresses from 224.0.0.0 through 239.255.255.255 rather than ordinary unicast host destinations. The appropriate correction for the reported case is: Select a suitable IPv6 multicast group and scope for the approved application.
PIM-SM shared-tree construction depends on consistent mappings of multicast groups to suitable RPs. Fixing that different mechanism would not address the current root cause: IPv6 multicast destinations begin in the FF00::/8 range and include scope information.
Shared-tree (*,G) state expresses interest in traffic to group G from potentially multiple sources. Its verification is distinct from the reported condition: An enterprise deploys IPv6 group delivery but attempts to identify receivers with ordinary IPv6 unicast addresses. The corrected tree must respect source and group authorization. When would the described mechanism be appropriate.