Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6
RFC 5798, “Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6”, is a Proposed Standard document published in March 2010 by S. Nadas. It obsoletes RFC 3768. It has been obsoleted by RFC 9568 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It is version three (3) of the protocol, and it is based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in "Virtual Router Redundancy Protocol for IPv6". 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 Master, and it forwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routers are configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the address family of the virtual addresses being carried based on the transport protocol. Within a VRRP router, the virtual routers in each of the IPv4 and IPv6 address families are a domain unto themselves and do not overlap. The election process provides dynamic failover in the forwarding responsibility should the Master 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. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5798 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5797 FTP Command and Extension Registry
- RFC 5796 Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode Link-Local Messages
- RFC 5795 The RObust Header Compression Framework
- RFC 5801 Using Generic Security Service Application Program Interface Mechanisms in Simple Authentication and Security Layer : The GS2 Mechanism Family
- RFC 5794 A Description of the ARIA Encryption Algorithm
- RFC 5802 Salted Challenge Response Authentication Mechanism SASL and GSS-API Mechanisms
- RFC 5793 PB-TNC: A Posture Broker Protocol Compatible with Trusted Network Connect
- RFC 5803 Lightweight Directory Access Protocol Schema for Storing Salted Challenge Response Authentication Mechanism Secrets