A new Request for Comments is now available in online RFC libraries.


	RFC 2338:

        Title:      Virtual Router Redundancy Protocol
	Author(s):  S. Knight, D. Weaver, D. Whipple, R. Hinden,
		    D. Mitzel, P. Hunt,  P. Higginson, M. Shand,
		    A. Lindem
	Status:     Proposed Standard
	Date:       April 1998
        Mailbox:    Steven.Knight@ascend.com, Doug.Weaver@ascend.com,
		    dwhipple@microsoft.com, hinden@iprg.nokia.com,
		    mitzel@iprg.nokia.com, hunt@iprg.nokia.com, 
		    higginson@mail.dec.com, shand@mail.dec.com,
		    acee@raleigh.ibm.com
	Pages:      27
        Characters: 59871
        Updates/Obsoletes: None

        URL:        ftp://ftp.isi.edu/in-notes/rfc2338.txt


This memo defines the Virtual Router Redundancy Protocol (VRRP).  VRRP
specifies an election protocol that dynamically assigns responsibility
for a virtual router to one of the VRRP routers on a LAN.  The VRRP
router controlling the IP address(es) associated with a virtual router
is called the Master, and forwards packets sent to these IP addresses.
The election process provides dynamic fail over in the forwarding
responsibility should the Master become unavailable.  This allows any
of the virtual router IP addresses on the LAN to be used as the
default first hop router by end-hosts.  The advantage gained from
using VRRP is a higher availability default path without requiring
configuration of dynamic routing or router discovery protocols on
every end-host.

This document is a product of the Virtual Router Redundancy Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.
 
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@ISI.EDU.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute