metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5798: Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9568.

Current document in this lineage: RFC 9568 — Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5798
Published
March 2010
Authors
S. Nadas
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
40
Also known as
—
Obsoletes:
RFC 3768
Obsoleted by:
RFC 9568

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 2338 (1998)
  2. RFC 3768 (2004)
  3. RFC 5798 (2010)
  4. RFC 9568 (2024) ✓

Read the full history of Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5798-virtual-router-redundancy-protocol-vrrp-version-3-for-ipv4-and-ipv6