I was wondering if instead use multicast boundary feature i can filter the advertising of multicast traffic for 239.0.0.0/8 groups on SW2 by the use of ip pim accept rp 150.1.5.5 command and automatically ignoring the 239.0.0.0 range advertised from R3.
I know that ip multicast boundary is more precise as you can implement it on the interface itself but since SW2 is on the edge of the multicast domain and it's not on the path of other pim neighbors hence it can't affect others multicast paths i suppose it is possible resolve also with ip pim accept rp in this case; anybody agree with me?