NOTE: This charter is a snapshot of the 44th IETF Meeting in Minneapolis, Minnesota. It may now be out-of-date. Last Modified: 11-Jan-99
Chair(s):
Bob Hinden <hinden@iprg.nokia.com>
Routing Area Director(s):
Rob Coltun <rcoltun@lightera.com>
Routing Area Advisor:
Rob Coltun <rcoltun@lightera.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. |
Internet-Drafts:
Request For Comments:
RFC |
Status |
Title |
RFC2338 |
PS |
Virtual Router Redundancy Protocol |
VRRP Minutes - 44th IETF, Minneapolis, MN, 3/16/99
Bob Hinden - Chair
Minutes taken by Barbara Denny (3COM)
Agenda:
- Review Agenda
- Interoperabilty Test Report
- VRRP Protocol Review <draft-ietf-vrrp-spec-v2-01.txt>
- VRRP MIB Review <draft-ietf-vrrp-mib-05.txt>
Review Agenda
No modifications were made to the Agenda.
Interoperability Testing
Presented by Ray LaRoca, UNH
Held February 23, 24, and 25th at UNH's IOL
Participants: 3Com, Cabletron, Fore, IBM, Nokia, Xedia
The following tests were conducted:
1) Conformance testing Basic VRRP functionality (UNH test software)
2) Pairwise vendor testing
3) All vendor test
Testing was successful. Misconfiguration problems resulted in text clarifications to the current draft.
VRRP Protocol Review
The changes made to the VRRP protocol in the current draft are:
· Authentication to be per virtual router instead of per interface
· New Subsection 9.4 declaring VRRP over ATM Lane is out of scope (There have been a couple volunteers to write this up but no progress has been made.)
· Clarified received packet length check
· Clarified received authentication check
· Clarified VRID verification check
· New section 8.4 describing not to forward packets for adopted IP addresses
· Added reference for computing internet checksum
· Updated references
Working group chair plans to issue last call for draft standard in next couple weeks.
There was a question regarding if there was anything to report regarding patent claims. Nothing new is known.
VRRP MIB Review
Presented by Brian Jewell, 3Com.
The current version of the MIB is 5. This did not make the IETF cutoff but a draft was available via anonymous ftp. The working group chair plans to issue last call for proposed standard when new draft is out as an ID.
The changes made to this version are
· Objects under "vrrpRouterStatsEntry" were renumbered. OID's became out-of-sequence due to changes made in the last revision (04).
· Format of section numbers was changed ('.' added) to be consistent with other RFC's.
· Changed the type of "vrrpNodeVersion" from INTEGER to Integer32. Also made DEFVAL (for this object) a decimal number.
· A few spelling and typographical corrections were made.
· Revisions were made to the format of some of the references to make then more concise and consistent.
· Reworded the Overview section to attempt to make the description of VRRP more in-line with the VRRP RFC.
Meeting Adjourned