RFC 2338:Virtual Router Redundancy Protocol
RFC-Ref

RFC - 2338

Virtual Router Redundancy Protocol

Original: ftp://ftp.isi.edu/in-notes/rfc2338.txt
Authors: S. Knight [Ascend Communications, Inc.], D. Weaver [Ascend Communications, Inc.], D. Whipple [Microsoft, Inc.], R. Hinden [Nokia], D. Mitzel [Nokia], P. Hunt [Nokia], P. Higginson [Digital Equipment Corp.], M. Shand [Digital Equipment Corp.], A. Lindem [IBM Corporation]
Date: April 1998
Category: Informational
 
This specification has been !!! obsoleted !!!



Obsoleted by:
RFC-3768draft Virtual Router Redundancy Protocol (VRRP)

Referred by: 16 RFC
Refers to: 7 RFC

Status

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.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

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.


About Resource

Google
Web
RFC-Ref