There are three types of networks: publisher, consumer, and transport. Many publisher networks can originate content and many
consumer networks can be interested in the content. The transport network, owned and operated by a service provider, connects
the publisher and the consumer networks.
The consumer and the transport networks are connected as follows:
For a specific group range, or all-groups range (similar to a default route), the service provider defines a particular rendezvous
point (RP), such as RP-A. Reverse path forwarding of RP-A from a consumer device will cause a (*,G) Join to be sent towards
the transport network.
For the same group, the service provider may define a different RP, such as RP-B, that is used to build the shared tree within
the transport network for G. RP-A and RP-B are typically different RPs and each RP is defined for different group ranges.
RFC 4601 dictates that if a device receives a (*, G) Join and the RP that is specified in the (*, G) Join is different than
what the receiving device expects (unknown RPs), the incoming (*, G) Join must be ignored. The PIM Allow RP feature enables
the receiving device to use its own RP to create state and build shared trees when an incoming (*, G) Join is processed and
a different RP is identified. This allows the receiving device to accept the (*, G) Join from the different RP.
PIM Allow RP is only applicable for downstream traffic, for building the shared tree. It does not work with Auto-RP or BSR.
Only static configuration is supported. However, PIM Allow RP does compensate for the embedded RP in the consumer network
to be different than the one configured statically in the transport network.