Applicability of Bidirectional Forwarding Detection (BFD) for Multi-point Networks in Virtual Router Redundancy Protocol (VRRP)

Introduction The is the current specification of the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6 networks. VRRPv3 allows for a faster switchover to a Backup router. Using such capability with the software-based implementation of VRRP may prove challenging. But it still may be possible to deploy VRRP and provide sub-second detection of Active router failure by Backup routers. Bidirectional Forwarding Detection (BFD) had been originally defined to detect failure of point-to-point (p2p) paths: single-hop , multihop . Single-hop BFD may be used to enable Backup routers to detect a failure of the Active router within 100 msec or faster. extends for multipoint and multicast networks, which matches the deployment scenarios for VRRP over the LAN segment. This document demonstrates how point-to-multipoint (p2mp) BFD can enable faster detection of the Active router failure and thus minimize service disruption in a VRRP domain. The document also defines the extension to VRRP to bootstrap a VRRP Backup router to join in a p2mp BFD session.

Conventions used in this document

Terminology BFD: Bidirectional Forwarding Detection p2mp: Pont-to-Multipoint VRRP: Virtual Router Redundancy Protocol

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Problem Statement A router may be part of several Virtual Router Redundancy groups, as Active in some and as Backup in others. Supporting sub-second mode for VRRPv3 for all these roles without specialized support in the data plane may prove challenging because of the increased load on the control plane. BFD already has many implementations based on HW that are capable of supporting multiple sub-second sessions concurrently.

Applicability of p2mp BFD may provide an efficient and scalable solution for fast-converging environment that uses the default route rather than dynamic routing. Each redundancy group presents itself as a p2mp BFD session, with its Active router being the root and Backup routers being the tails of the p2mp BFD session. displays the extension of VRRP to bootstrap a tail of the p2mp BFD session.

B(FD) - a one-bit flag that indicates that the Active Router Discriminator field is appended to VRRP packet defined in ;
Active Router Discriminator - the four-octet field. The value MUST NOT be zero, and it equals the My Discriminator value allocated by the root of the p2mp BFD session.

The Active router, configured to use p2mp BFD to support faster convergence of VRRP, starts transmitting BFD control packets with IPvX address associated with the Virtual Router as a source IP address and the locally allocated value as the value of the My Discriminator field (). The same non-zero value of My Discriminator MUST be set as the value of the Active Router Discriminator field. The BFD flag MUST be set in the VRRP packet. A Backup router demultiplexes p2mp BFD test sessions based on IPvX address associated with the Virtual Router that it has been configured with and the non-zero My Discriminator value it learns from the received VRRP packet. When a Backup router detects the failure of the Active router, according to the Section 5.11 , it re-evaluates its role in the Virtual Router. As a result, the Backup router may become the Active router of the given Virtual Router or continue as a Backup router. If the former is the case, then the new Active router MUST select its new My Discriminator value, include that value in the VRRP packet to bootstrap a new p2mp BFD session, and start transmitting p2mp BFD control packets using the Active router IP address as the source IP address for p2mp BFD control packets and its new My Discriminator value. If the latter is the case, the Backup router MUST wait for the VRRP packet from the new VRRP Active router that will bootstrap the new p2mp BFD session.

Multipoint BFD Encapsulation The MultipointHead of p2mp BFD session when transmitting BFD control packet:

MUST set TTL or Hop Limit value to 255 (Section 5 ). Similarly, all received BFD Control packets that are demultiplexed to the session MUST be discarded if the received TTL or Hop Limit is not equal to 255;
SHOULD use group address VRRP ('224.0.0.18' for IPv4 and 'FF02:0:0:0:0:0:0:12' for IPv6) as destination IP address
MAY use network broadcast address for IPv4 or link-local all nodes multicast group for IPv6 as destination IP address;
MUST set destination UDP port value to 3784 when transmitting BFD control packets, as defined in ;
MUST use the Active router IP address as the source IP address.

IANA Considerations This document makes no requests for IANA allocations. This section may be deleted by RFC Editor.

Security Considerations This document defines an alternative way, to the one defined in , to accelerate detecting a failure that affects VRRP functionality using p2mp BFD. The operation of either protocol is not changed. Security considerations discussed in , , , and , apply to this document.

Acknowledgements