2.5.11 Virtual Router Redundancy Protocol (vrrp)

NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98


Bob Hinden <hinden@iprg.nokia.com>

Routing Area Director(s):

Rob Coltun <rcoltun@fore.com>

Routing Area Advisor:

Rob Coltun <rcoltun@fore.com>

Mailing Lists:

General Discussion:vrrp@drcoffsite.com
To Subscribe: listserv@drcoffsite.com w
In Body: subscribe vrrp <your_name>
Archive: ftp://ftp.ietf.org/ietf-mail-archive/vrrp/*

Description of Working Group:

The purpose of this working group is to define and develop a standard virtual router redundancy protocol for IPv4 and IPv6. A virtual router redundancy protocol is a protocol which allows several routers on a multiaccess link to utilize the same virtual IP address. One router will be elected as a master with the other routers acting as backups in case of the failure of the master router. The primary motivation to using a virtual router redundancy protocol is that host systems may be configured (manually or via DHCP) with a single default gateway, rather than running an active routing protocol. The protocol should also support the ability to load share traffic when both routers are up.

The goals of this working group are:

1. Define and develop a standard virtual router redundancy protocol for IPv4 and IPv6.

2. Develop VRRP MIB(s).

3. Separate specifications will be developed for IPv4 and IPv6.

4. Determine whether static (configuration based) load sharing is adequate or if some amount of dynamic load sharing is required.

5. Working group will examine security issues to determine what security threats it is appropriate for the VRRP protocol to handle and include the appropriate mechanisms in the VRRP protocol.

6. The internet draft "Virtual Router Redundancy Protocol" <draft-hinden-vrrp-00.txt will be use as the basis of virtual router redundancy protocol. The working group will also consider other internet drafts related to this topic allowing for issues regarding change control, security, running code, etc.

7. Intellectual property issues regarding the technology to develop a virtual router redundancy protocol will be identified and addressed.

Goals and Milestones:

Jun 97


Charter Working Group

Jul 97


Issue new Internet Drafts for IPv4 version of the protocol.

Aug 97


Issue Internet Draft for IPv6 version of VRRP.

Aug 97


Review and finalize IPv4 Internet Drafts.

Aug 97


Resolve any intellectual property issues regarding protocol.

Sep 97


Submit revised IPv4 Internet Drafts to IESG for proposed standard.

Oct 97


Issue VRRP MIB drafts.

Oct 97


Issue revised draft for IPv6 version of VRRP.

Dec 97


Review and finalize IPv6 Internet Drafts.

Dec 97


Finalize MIB draft and submit to IESG.

Jan 98


Submit revised IPv6 Internet Drafts to IESG for proposed standard.


Request For Comments:







Virtual Router Redundancy Protocol

Current Meeting Report

Virtual Router Redundancy Protocol Working Group
Orlando IETF
Dec. 1998

Bob Hinden / Nokia
W.G. Chair

Minutes taken by David Whipple <dwhipple@microsoft.com>

Chair introduced meeting and presented introduction slide and agenda:

- Working Group Chartered by IESG on 12Jun97
- Mailing List
- General Discussion:vrrp@drcoffsite.com
- To Subscribe send message to listserv@drcoffsite.com with subscribe vrrp <your_name> in the body of the message.

- Introduction
- Review Agenda
- Report on resolution of open issues w/ VRRP and LANE
- Interoperability Testing
- Finalize VRRP MIB

- Issue reported regarding running VRRP on ATM "LAN Emulation"
- Relates to LANE cache flushing mechanisms
- Requires "LE_NARP" function
- May not be included in all LANE implementations
- FORE and Nortel have VRRP LANE implementations
- Resolution:
- Add note to VRRP specification describing the issue
- Rob Montgomery and volunteer from FORE (with help from Rob Coltun) will write document on running VRRP over LANE.

- Implementation reports received from:
- Nortel Networks, IBM, Xedia, Nokia, 3COM, 3COM, Cabletron, FORE
- Reports available at ftp://playground.sun.com/pub/hinden/vrrp/vrrp-implementations.txt
- Interoperability Testing at UNH Feb 23-25, 1999 (Tuesday - Thursday)

Bill Lenharth <whl@unh.edu> from UNH described the role of UNH testing lab. There will be a fee to do this interop testing. Information on UNH testing will be sent to vrrp mailing list in early January.

- Name of Implementation: <product or module name>
- Platform: <platforms that implementation runs on>
- Organization: <group or company that developed code>
- Origin of Code: <developed from scratch, ported from, etc.>
- Information supplied by: <name and email of person filling in form>
- Tested Interoperability:
- <list of implementations tested against>
- <list of implementations tested against>
- <list of implementations tested against>

- Current Draft
- Title: Definitions of Managed Objects for the Virtual Router Redundancy Protocol using SNMPv2
- Author(s): B. Jewell, D. Chuang
- Filename: draft-ietf-vrrp-mib-03.txt
- Pages: 28
- Date: 11-Nov-98
- Comments?
No comments received.

Slide was shown that was to be presented at Routing area meeting later in the week:

- RFC2338 Virtual Router Redundancy Protocol
- Proposed Standard on 18 Mar 1998
- Provides for Router Redundancy on LAN for Hosts
- Uses Real IP Addresses and Virtual MAC
- ICMP Redirects supported
- Hosts switch to backup router transparently
- W. G. Status
- Finalizing VRRP MIB
- Collecting implementation information for Draft Std Nortel Networks, IBM, Xedia, Nokia, 3COM, 3COM, Cabletron, FORE, Xylan
- VRRP Interoperability testing at UNH Feb 23-25 '99


None received.