Abstract
This specification allows Anycast-RP (Rendezvous Point) to be used inside a domain that runs Protocol Independent Multicast (PIM) only. Other multicast protocols, such as Multicast Source Discovery Protocol (MSDP), which has been used traditionally to solve this problem, are not required to support Anycast-RP. This memo extends the Register mechanism in PIM so Anycast-RP functionality can be retained without using MSDP.
Introduction
In Protocol Independent Multicast - Sparse Mode (PIM-SM), the Rendezvous Point (RP) is a critical infrastructure component acting as the focal point for sources and receivers. Sources register with the RP, and receivers join the RP-rooted shared tree to discover those sources. However, relying on a single RP creates a single point of failure and can lead to suboptimal routing if the RP is geographically distant from certain network segments.
To address these issues, network engineers deploy Anycast-RP. In this configuration, multiple routers share the same IP address (the Anycast address). Unicast routing naturally directs traffic to the topologically "closest" RP. The primary challenge of Anycast-RP is synchronization: if a source registers with one RP, all other RPs in the set must be informed so they can serve their local receivers.
The Anycast-RP Mechanism
RFC 4610 provides a "PIM-only" solution for Anycast-RP synchronization, eliminating the need for the Multicast Source Discovery Protocol (MSDP). The mechanism relies on extending the standard PIM Register process.
Operational Steps
- Configuration: A set of RPs (the Anycast-RP set) is configured. Each RP has a shared Anycast IP address on a loopback interface and a unique unicast IP address for peer-to-peer communication.
- Registration: When a source (e.g., S1 in the figure) starts transmitting, its Designated Router (DR) sends a PIM Register message to the Anycast-RP address. Unicast routing delivers this to the nearest RP (e.g., RP1).
- Copy and Forward: Upon receiving the Register message, RP1 performs its standard PIM duties. Additionally, it encapsulates the Register message and forwards a copy to the unique IP addresses of all other members in the Anycast-RP set (RP2 and RP3).
- Local Delivery: When RP2 receives the forwarded Register message from RP1, it decapsulates the data and forwards it to its local receivers (e.g., R2).
Key Insights and Design Principles
- Protocol Minimization: By leveraging the existing PIM Register message—which already contains the source, group, and initial data—the protocol avoids the overhead of maintaining MSDP peering sessions and Source-Active (SA) state.
- Loop Prevention: To prevent infinite loops, the protocol dictates that an RP only forwards Register messages that it receives directly from a DR. If a Register message arrives from a peer RP, it is processed locally but never re-forwarded.
- Convergence: Failover is handled by the underlying unicast routing protocol. If RP1 fails, the unicast routing table will update, and the DR will automatically begin sending Register messages to the next closest RP.
Results and Advantages
The adoption of RFC 4610 simplifies multicast deployments significantly:
- Reduced Complexity: Operators no longer need to configure and troubleshoot MSDP, which involves complex timers and filtering rules.
- Native Integration: The solution is a natural extension of PIM, making it easier for network equipment to support and for engineers to understand.
- Efficiency: It provides the benefits of Anycast (load balancing and redundancy) with minimal control plane overhead.
Limitations and Considerations
While powerful, the PIM-only Anycast-RP approach has specific constraints:
- Scaling: Because every Register message is copied to every other RP, the control plane load increases with the number of RPs ($N$). This mechanism is best suited for small-to-medium Anycast-RP sets.
- Intra-domain Scope: This protocol is designed for use within a single administrative domain. For inter-domain source discovery (connecting different organizations), MSDP remains the standard.
- Security: As with all PIM mechanisms, it is susceptible to DoS attacks via forged Register messages. Implementers should use PIM's built-in security features, such as IPsec or MD5 authentication for peer communication and rate-limiting for Register messages.
Summary updated