Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Obsoletes:

RFC 5798

Authors:

A. Lindem
A. Dogra

Stream:

IETF

Source:

rtgwg (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9568

Discuss this RFC: Send questions or comments to the mailing listrtgwg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9568

Abstract

This document defines version 3 of the Virtual Router RedundancyProtocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, whichpreviously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768,which specified VRRP (version 2) for IPv4. VRRP specifies an electionprotocol that dynamically assigns responsibility for a Virtual Routerto one of the VRRP Routers on a LAN. The VRRP Router controlling theIPv4 or IPv6 address(es) associated with a Virtual Router is calledthe Active Router, and it forwards packets routed to these IPv4 orIPv6 addresses. Active Routers are configured with virtual IPv4 orIPv6 addresses, and Backup Routers infer the address family of thevirtual addresses being advertised based on the IP protocol version. Within a VRRP Router, the Virtual Routers in each of the IPv4 andIPv6 address families are independent of one another and alwaystreated as separate Virtual Router instances. The election processprovides dynamic failover in the forwarding responsibility should theActive Router become unavailable. For IPv4, the advantage gainedfrom using VRRP is a higher-availability default path withoutrequiring configuration of dynamic routing or router discoveryprotocols on every end-host. For IPv6, the advantage gained fromusing VRRP for IPv6 is a quicker switchover to Backup Routers thancan be obtained with standard IPv6 Neighbor Discovery mechanisms.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.