RFC 9568: Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6
In plain English — editorial summary, not part of the RFC
This document defines version 3 of the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, which previously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768, which specified VRRP (version 2) for IPv4. VRRP specifies an election protocol that dynamically assigns responsibility for a Virtual Router to one of the VRRP Routers on a LAN. The VRRP Router controlling the IPv4 or IPv6 address(es) associated with a Virtual Router is called the Active Router, and it forwards packets routed to these IPv4 or IPv6 addresses. Active Routers are configured with virtual IPv4 or IPv6 addresses, and Backup Routers infer the address family of the virtual addresses being advertised based on the IP protocol version. Within a VRRP Router, the Virtual Routers in each of the IPv4 and IPv6 address families are independent of one another and always treated as separate Virtual Router instances. The election process provides dynamic failover in the forwarding responsibility should the Active Router become unavailable. For IPv4, the advantage gained from using VRRP is a higher-availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup Routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms.
Document record
- Document ID
- RFC9568
- Published
- April 2024
- Authors
- A. Lindem; A. Dogra
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
- Obsoletes:
- RFC 5798
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2338 (1998)
- RFC 3768 (2004)
- RFC 5798 (2010)
- RFC 9568 (2024)
Read the full history of Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9570Deprecating the Use of Router Alert in LSP PingCurrent
May 2024
- RFC 9566Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IPCurrent
April 2024
- RFC 9571Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow LabelsCurrent
May 2024
- RFC 9572Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) ProceduresCurrent
May 2024
- RFC 9573MVPN/EVPN Tunnel Aggregation with Common LabelsCurrent
May 2024
- RFC 9574Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)Current
May 2024
- RFC 9552Distribution of Link-State and Traffic Engineering Information Using BGPCurrent
December 2023
- RFC 9551Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)Current
March 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?