Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 3768

Obsoleted by:

RFC 9568

Author:

S. Nadas, Ed.

Stream:

IETF

Source:

vrrp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

This memo defines the Virtual Router Redundancy Protocol (VRRP) forIPv4 and IPv6. It is version three (3) of the protocol, and it isbased on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in"Virtual Router Redundancy Protocol for IPv6". VRRP specifies an electionprotocol that dynamically assigns responsibility for a virtual router to oneof the VRRP routers on a LAN. The VRRP router controlling the IPv4 or IPv6address(es) associated with a virtual router is called the Master, and itforwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routersare configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routersinfer the address family of the virtual addresses being carried based on thetransport protocol. Within a VRRP router, the virtual routers in each of theIPv4 and IPv6 address families are a domain unto themselves and do notoverlap. The election process provides dynamic failover in the forwardingresponsibility should the Master become unavailable. For IPv4, theadvantage gained from using VRRP is a higher-availability defaultpath without requiring configuration of dynamic routing or routerdiscovery protocols on every end-host. For IPv6, the advantagegained from using VRRP for IPv6 is a quicker switchover to Backuprouters than can be obtained with standard IPv6 Neighbor Discoverymechanisms. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.