A new Request for Comments is now available in online RFC libraries.
RFC 9568
Title: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6
Author: A. Lindem,
A. Dogra
Status: Standards Track
Stream: IETF
Date: April 2024
Mailbox: acee.i...@gmail.com,
addo...@cisco.com
Pages: 35
Obsoletes: RFC 5798
I-D Tag: draft-ietf-rtgwg-vrrp-rfc5798bis-18.txt
URL: https://www.rfc-editor.org/info/rfc9568
DOI: 10.17487/RFC9568
This document defines version 3 of the Virtual Router Redundancy
Protocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, which
previously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768,
which specified VRRP (version 2) for IPv4. 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 Active Router, and it forwards packets routed to these IPv4 or
IPv6 addresses. Active Routers are configured with virtual IPv4 or
IPv6 addresses, and Backup Routers infer the address family of the
virtual addresses being advertised based on the IP protocol version.
Within a VRRP Router, the Virtual Routers in each of the IPv4 and
IPv6 address families are independent of one another and always
treated as separate Virtual Router instances. The election process
provides dynamic failover in the forwarding responsibility should the
Active Router 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.
This document is a product of the Routing Area Working Group Working Group of
the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
