2.5.11 Virtual Router Redundancy Protocol (vrrp)

NOTE: This charter is a snapshot of the 45th IETF Meeting in Oslo, Norway. It may now be out-of-date. Last Modified: 06-Jul-99


Bob Hinden <hinden@iprg.nokia.com>

Routing Area Director(s):

David Oran <oran@cisco.com>
Rob Coltun <rcoltun@siara.com>

Routing Area Advisor:

Rob Coltun <rcoltun@siara.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

VRRP Minutes - 45th IETF, Oslo, 7/14/99
Bob Hinden - Chair

Minutes taken by Barbara Denny / 3COM


- Introduction
- Review Agenda
- Status of VRRP to Draft Standard
- Status of VRRP MIB to Proposed Standard
- Interoperability Testing
- Review of VRRP over LANE draft
- Q & A

Introduction & Review Agenda
- No modifications were made to the agenda.

Status of VRRP to Draft Standard
- Working Group last call was completed and the document has been submitted to the IESG. There are some IESG comments so there will be one more iteration on the specification.

Status of VRRP MIB to Proposed Standard
- Working Group last call was completed. An OID has been assigned for the MIB (68). There will be a new draft because the format of MIBs have changed. The Management Area Directorate has also made some IESG specific comments. The author is currently iterating on those comments. A new draft will be issued with last call.

Interoperability Testing
- There are no plans for another interoperability test.

VRRP Over LAN Emulation
Atul Bansal/Fore - Presenter
- Testing over VRRP over ATM LANE was done at the last interoperability test.
- The presenter reviewed ATM LANE address resolution and how VRRP would work with ATM LANE and Token Ring LANE. There are no new messages and the specification does not break "normal" protocol operation. The specification defines how to use existing messages.
- There were some comments on the current version of the document. The document needs to specify what is recommended (for example, timing values). The failure conditions should be noted. Regarding MPS, Multiprotocol Server, you need to make the description adequate or not have any. The security considerations section should be enhanced. Once a new draft is sent out, a working group last call will be made.

Q & A
- There was a question regarding VRRP over a distributed switching environment. The question will be submitted to the mailing list. The problem may be "out-of-scope" for the w.g.
- There was also a question regarding any news on patent claims. There is no news.


None received.