RFC 2338: Virtual Router Redundancy Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3768.
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2338
- Published
- April 1998
- Authors
- S. Knight; D. Weaver; D. Whipple; R. Hinden; D. Mitzel; P. Hunt; P. Higginson; M. Shand; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
- Obsoleted by:
- RFC 3768
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2338 (1998)
- RFC 3768 (2004)
- RFC 5798 (2010)
- 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.
- RFC 3069VLAN Aggregation for Efficient IP Address AllocationCurrent
February 2001
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 2201Core Based Trees (CBT) Multicast Routing ArchitectureCurrent
September 1997
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 2285Benchmarking Terminology for LAN Switching DevicesCurrent
February 1998
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?