metasystema.org
ObsoletedDRAFT STANDARDIETF stream

RFC 3768: Virtual Router Redundancy Protocol (VRRP)

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

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). 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 IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. 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. [STANDARDS-TRACK]

Document record

Document ID
RFC3768
Published
April 2004
Authors
R. Hinden
Status
DRAFT STANDARD
Stream
IETF
Area
rtg
Pages
27
Also known as
—
Obsoletes:
RFC 2338
Obsoleted by:
RFC 5798

Topics

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/3768-virtual-router-redundancy-protocol-vrrp