A Rendezvous Point (RP) is a router in a multicast network domain that acts as a shared root for a multicast shared tree. Any number of routers can be configured to work as RPs and they can be configured to cover different group ranges. For correct operation, every multicast router within a Protocol Independent Multicast (PIM) domain must be able to map a particular multicast group address to the same RP.
This document attempts to describe, compare and contrast the different methods for deploying RPs. For details on how to configure an RP using any of the methods discussed in this document please refer to the following White Paper:
Configuring a Rendezvous Point.
This document discusses the following mechanisms:
• Static RP
• Bootstrap Router (BSR)
• Phantom RP
• Embedded RP
It is possible to statically configure an RP for a multicast group range. The address of the RP must be configured on every router in the domain. Configuring static RPs is relatively easy and can be done with one or two lines of configuration on each router. If the network does not have many different RPs defined and/or they do not change very often, then this could be the simplest method to define RPs. This can also be an attractive option if the network is small.
However this can be a laborious task in a large and complex network. Every router must have the same RP address. This means changing the RP address requires reconfiguring every router. If several RPs are active for different groups, then information regarding which RP is handling which group must be known by all routers. To ensure this information is complete, several configuration commands may be required. If the manually configured RP fails, there is no failover procedure for another router to take over the function performed by the failed RP. This method does not provide any kind of load-balancing. Static RP can be combined with Anycast RP to provide RP load sharing and redundancy.
Static RP can co-exist with dynamic RP mechanisms (ie: Auto-RP). Dynamically learned RP takes precedence over manually configured RPs. If a router receives Auto-RP information for a multicast group that has manually configured RP information, then the Auto-RP information will be used.
The Bootstrap Router (BSR) is a mechanism for a router to learn RP information. It ensures that all routers in the PIM domain have the same RP cache as the BSR. It is possible to configure the BSR to help select an RP set from BSR candidate RPs. The function of the BSR is to broadcast the RP set to all routers in the domain.
Figure 1 shows the BSR mechanism, where the elected BSR sends BSR messages with RP set information out on all enabled interfaces, which are flooded hop-by-hop to all routers in the network. The candidate-RPs send their candidate-RP advertisements directly to the elected BSR.
Figure 1. BSR Mechanism
The elected BSR receives candidate-RP messages from all candidate-RPs in the domain. The bootstrap message sent by the BSR includes information about all the candidate-RPs. Each router uses a common algorithm to select the same RP address for a given multicast group.
For more information about bootstrap routers, see
The BSR mechanism is a nonproprietary method of defining RPs that can be used with third-party routers (which support the BSR mechanism). There is no configuration necessary on every router separately (except on candidate-BSRs and candidate-RPs). The mechanism is largely self-configuring making it easier to modify RP information. Information regarding several RPs for different groups is automatically communicated to all routers, reducing administrative overhead. The mechanism is robust to router failover and permits back-up RPs to be configured. In case of RP failure, the secondary RP for the group can take over as the RP for the group.
Auto-RP and BSR protocols must not be configured together in the same network.
Auto-RP is a mechanism to automate distribution of RP information in a multicast network. The Auto-RP mechanism operates using two basic components, the candidate RPs and the RP mapping agents.
• Candidate RPs advertize their willingness to be an RP via "RP-announcement" messages. These messages are periodically sent to a reserved well-known group 188.8.131.52 (CISCO-RP-ANNOUNCE).
• RP mapping agents join group 184.108.40.206 and map the RPs to the associated groups. The RP mapping agents advertise the authoritative RP-mappings to another well-known group address 220.127.116.11 (CISCO-RP-DISCOVERY). All PIM routers join 18.104.22.168 and store the RP-mappings in their private cache.
Figure 2 shows the Auto-RP mechanism where the RP mapping agent periodically multicasts the RP information that it receives to the Cisco-RP-Discovery group.
Figure 2. Auto-RP Mechanism
All routers automatically learn the RP information making it easier to administer and update RP information. There is no configuration needed on every router separately (except on candidate RPs and mapping agents). Auto-RP permits back-up RPs to be configured enabling an RP failover mechanism.
Auto-RP is not supported for IPv6 Multicast. Auto-RP is a Cisco proprietary mechanism.
BSR and Auto-RP protocols must not be configured together in the same network.
Anycast RP is used to define redundant and load-balanced RPs. Anycast-RP has two implementations:
• Using Multicast Source Discovery Protocol (MSDP) described in RFC3446.
• Using Protocol Independent Multicast (PIM) described in RFC4610.
Anycast-RP allows two or more RPs to share the load for source registration and to act as hot back-up routers for each other. Multicast Source Discovery Protocol (MSDP) is the protocol RPs to share information about active sources. With Anycast RP, the RPs are configured to establish MSDP peering sessions using a TCP connection. Group participants use the closest RP that is favored by the IP unicast route table.
Figure 3. Anycast-RP Mechanism
Figure 3 shows the Anycast-RP mechanism. Two or more RPs are configured with the same IP address on loopback interfaces. All the downstream routers are configured to "know" that the Anycast RP loopback address is the IP address of their RP. When an RP fails, IP routing converges and the other RP assumes the RP role. Further details on Anycast-RP can be found in the following White Paper:
Anycast RP Overview.
PIM Anycast-RP extends the Register mechanism in PIM so that Anycast-RP functionality can be retained without using MSDP. PIM register messages are sent to the closest RP and PIM join-prune, messages are sent in the direction of the closest RP as determined by the unicast routing protocols. If one of the RPs goes down, unicast routing ensures these messages will be sent in the direction of the next-closest RP.
Anycast-RP provides RP failover and redundancy. Anycast-RP can be used along with static RP or Auto-RP to provide RP redundancy.
In Bidirectional PIM (Bidir-PIM), the RP does not have an actual protocol function. The RP acts as a routing vector in which all the traffic converges. The RP can be configured as an address that is not assigned to any particular device called a Phantom RP. This means that the RP address does not need to reside on a physical router interface, but can just be an address in a subnet. The RP can also be a physical router, but it is not necessary.
Embedded RP defines an address allocation policy in which the address of the RP is encoded in an IPv6 multicast group address. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. IPv6 Multicast group addresses embedded with RP information start with ff
70::/12 where the flag value of
7 means embedded RP.
Figure 4. Multicast Address with Embedded RP
There is no need to pre-configure routers with the RP address information. Routers can automatically extract and use the RP information from the IPv6 multicast group address. This allows for a large number of RPs to be deployed anywhere in the Internet. Embedded RP requires no change in protocol operations. It can be considered an automatic replacement for static RP configuration.
The router can learn only one RP address for a multicast group using embedded RP. It cannot support RP redundancy. Proposals are being considered to introduce RP redundancy by mechanisms other than BSR for IPv6 multicast. Embedded RP does not support Bidirectional PIM. Embedded RP allows the application to dictate which router is the RP. There is the possibility that a low-end router could end up becoming the RP for hundreds of high data rate sources if the application defines an erroneous RP address (this can be prevented by disabling Embedded RP learning).