Virtual Router Redundancy Protocol (vrrp)
This Working Group Did Not Meet
NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 03-Feb-00
Chair(s):
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" 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. |
Internet-Drafts:
Request For Comments:
RFC |
Status |
Title |
RFC2787 |
PS |
Definitions of Managed Objects for the Virtual Router Redundancy Protocol using SNMPv2 |
RFC2338 |
PS |
Virtual Router Redundancy Protocol |