| draft-ietf-vrrp-spec-v2-05.txt | draft-ietf-vrrp-spec-v2-06.txt | |||
|---|---|---|---|---|
| INTERNET-DRAFT S. Knight | ||||
| January 5, 2000 D. Weaver | INTERNET-DRAFT R. Hinden | |||
| Ascend Communications, Inc. | February 28, 2002 D. Mitzel | |||
| D. Whipple | ||||
| Microsoft, Inc. | ||||
| R. Hinden | ||||
| D. Mitzel | ||||
| P. Hunt | P. Hunt | |||
| Nokia | Nokia | |||
| P. Higginson | P. Higginson | |||
| M. Shand | M. Shand | |||
| Digital Equipment Corp. | Digital Equipment Corp. | |||
| A. Lindem | A. Lindem | |||
| IBM Corporation | IBM Corporation | |||
| S. Knight | ||||
| D. Weaver | ||||
| Ascend Communications, Inc. | ||||
| D. Whipple | ||||
| Microsoft, Inc. | ||||
| Virtual Router Redundancy Protocol | Virtual Router Redundancy Protocol | |||
| <draft-ietf-vrrp-spec-v2-05.txt> | <draft-ietf-vrrp-spec-v2-06.txt> | |||
| Status of this Memo | Status of this Memo | |||
| This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
| all provisions of Section 10 of [RFC2026]. | all provisions of Section 10 of [RFC2026]. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | To view the list Internet-Draft Shadow Directories, see | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | ||||
| The list of Internet-Draft Shadow Directories can be accessed at | ||||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This internet draft expires on July 5, 2000. | This internet draft expires on August 28, 2002. | |||
| Abstract | Abstract | |||
| This memo defines the Virtual Router Redundancy Protocol (VRRP). | This memo defines the Virtual Router Redundancy Protocol (VRRP). | |||
| VRRP specifies an election protocol that dynamically assigns | VRRP specifies an election protocol that dynamically assigns | |||
| responsibility for a virtual router to one of the VRRP routers on a | responsibility for a virtual router to one of the VRRP routers on a | |||
| LAN. The VRRP router controlling the IP address(es) associated with | LAN. The VRRP router controlling the IP address(es) associated with | |||
| a virtual router is called the Master, and forwards packets sent to | a virtual router is called the Master, and forwards packets sent to | |||
| these IP addresses. The election process provides dynamic fail over | these IP addresses. The election process provides dynamic fail over | |||
| in the forwarding responsibility should the Master become | in the forwarding responsibility should the Master become | |||
| skipping to change at page 29, line 43 | skipping to change at page 29, line 43 | |||
| 3", RFC2026, BCP00009, October 1996. | 3", RFC2026, BCP00009, October 1996. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", RFC2119, BCP0014, March 1997. | Requirement Levels", RFC2119, BCP0014, March 1997. | |||
| [TKARCH] IBM Token-Ring Network, Architecture Reference, Publication | [TKARCH] IBM Token-Ring Network, Architecture Reference, Publication | |||
| SC30-3374-02, Third Edition, (September, 1989). | SC30-3374-02, Third Edition, (September, 1989). | |||
| 14. Author's Addresses | 14. Author's Addresses | |||
| P. Higginson Phone: +44 118 920 6293 | ||||
| Digital Equipment Corp. EMail: higginson@mail.dec.com | ||||
| Digital Park | ||||
| Imperial Way | ||||
| Reading | ||||
| Berkshire | ||||
| RG2 0TE | ||||
| UK | ||||
| Robert Hinden Phone: +1 650 625-2004 | ||||
| Nokia EMail: hinden@iprg.nokia.com | ||||
| 313 Fairchild Drive | ||||
| Mountain View, CA 94043 | ||||
| USA | ||||
| Peter Hunt Phone: +1 650 625-2093 | ||||
| Nokia EMail: hunt@iprg.nokia.com | ||||
| 313 Fairchild Drive | ||||
| Mountain View, CA 94043 | ||||
| USA | ||||
| Steven Knight Phone: +1 612 943-8990 | Steven Knight Phone: +1 612 943-8990 | |||
| Ascend Communications EMail: Steven.Knight@ascend.com | Ascend Communications EMail: Steven.Knight@ascend.com | |||
| High Performance Network Division | High Performance Network Division | |||
| 10250 Valley View Road, Suite 113 | 10250 Valley View Road, Suite 113 | |||
| Eden Prairie, MN USA 55344 | Eden Prairie, MN USA 55344 | |||
| USA | USA | |||
| Douglas Weaver Phone: +1 612 943-8990 | ||||
| Ascend Communications EMail: Doug.Weaver@ascend.com | ||||
| High Performance Network Division | ||||
| 10250 Valley View Road, Suite 113 | ||||
| Eden Prairie, MN USA 55344 | ||||
| USA | ||||
| David Whipple Phone: +1 206 703-3876 | ||||
| Microsoft Corporation EMail: dwhipple@microsoft.com | ||||
| One Microsoft Way | ||||
| Redmond, WA 98052-6399 | ||||
| USA | ||||
| Robert Hinden Phone: +1 650 625-2004 | Acee Lindem Phone: 1-919-254-1805 | |||
| Nokia EMail: hinden@iprg.nokia.com | IBM Corporation E-Mail: acee@raleigh.ibm.com | |||
| 313 Fairchild Drive | P.O. Box 12195 | |||
| Mountain View, CA 94043 | Research Triangle Park, NC 27709 | |||
| USA | USA | |||
| Danny Mitzel Phone: +1 650 625-2037 | Danny Mitzel Phone: +1 650 625-2037 | |||
| Nokia EMail: mitzel@iprg.nokia.com | Nokia EMail: mitzel@iprg.nokia.com | |||
| 313 Fairchild Drive | 313 Fairchild Drive | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| USA | USA | |||
| Peter Hunt Phone: +1 650 625-2093 | ||||
| Nokia EMail: hunt@iprg.nokia.com | ||||
| 313 Fairchild Drive | ||||
| Mountain View, CA 94043 | ||||
| USA | ||||
| P. Higginson Phone: +44 118 920 6293 | ||||
| Digital Equipment Corp. EMail: higginson@mail.dec.com | ||||
| Digital Park | ||||
| Imperial Way | ||||
| Reading | ||||
| Berkshire | ||||
| RG2 0TE | ||||
| UK | ||||
| M. Shand Phone: +44 118 920 4424 | M. Shand Phone: +44 118 920 4424 | |||
| Digital Equipment Corp. EMail: shand@mail.dec.com | Digital Equipment Corp. EMail: shand@mail.dec.com | |||
| Digital Park | Digital Park | |||
| Imperial Way | Imperial Way | |||
| Reading | Reading | |||
| Berkshire | Berkshire | |||
| RG2 0TE | RG2 0TE | |||
| UK | UK | |||
| Acee Lindem Phone: 1-919-254-1805 | ||||
| IBM Corporation E-Mail: acee@raleigh.ibm.com | Douglas Weaver Phone: +1 612 943-8990 | |||
| P.O. Box 12195 | Ascend Communications EMail: Doug.Weaver@ascend.com | |||
| Research Triangle Park, NC 27709 | High Performance Network Division | |||
| 10250 Valley View Road, Suite 113 | ||||
| Eden Prairie, MN USA 55344 | ||||
| USA | ||||
| David Whipple Phone: +1 206 703-3876 | ||||
| Microsoft Corporation EMail: dwhipple@microsoft.com | ||||
| One Microsoft Way | ||||
| Redmond, WA 98052-6399 | ||||
| USA | USA | |||
| 14. Changes from RFC2338 | 14. Changes from RFC2338 | |||
| - Revised the section 4 examples text with a clearer description of | - Revised the section 4 examples text with a clearer description of | |||
| mapping of IP address owner, priorities, etc. | mapping of IP address owner, priorities, etc. | |||
| - Clarify the section 7.1 text describing address list validation. | - Clarify the section 7.1 text describing address list validation. | |||
| - Corrected text in Preempt_Mode definition. | - Corrected text in Preempt_Mode definition. | |||
| - Changed authentication to be per Virtual Router instead of per | - Changed authentication to be per Virtual Router instead of per | |||
| Interface. | Interface. | |||
| - Added new subsection (9.3) stating that VRRP over ATM LANE is | - Added new subsection (9.3) stating that VRRP over ATM LANE is | |||
| beyond the scope of this document. | beyond the scope of this document. | |||
| - Clarified text describing received packet length check. | - Clarified text describing received packet length check. | |||
| - Clarified text describing received authentication check. | - Clarified text describing received authentication check. | |||
| - Clarified text describing VRID verification check. | - Clarified text describing VRID verification check. | |||
| - Added new subsection (8.4) describing need to not forward packets | - Added new subsection (8.4) describing need to not forward packets | |||
| for adopted IP addresses. | for adopted IP addresses. | |||
| - Added clarification to the security considerations section. | - Added clarification to the security considerations section. | |||
| - Added reference for computing the internet checksum. | - Added reference for computing the internet checksum. | |||
| - Updated references and author information. | - Updated references and author information. | |||
| - Changed order of author list based on contribution level. | ||||
| End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ | ||||