Slave Virtual Router Redundancy Protocol (SVRRP)
draft-zhang-vrrp-svrrp-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Huihong Building , Dacheng Zhang | ||
Last updated | 2009-10-19 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Zhang. Expires April 19, 2010 [page 1] Internet-Draft Management Virtual Router Redundancy Protocol October 2009 In this document, we propose a simplified VRRP protocol called the Slave Virtual Router Redundancy Protocol (SVRRP).The design objective of SVRRP is to specify an election protocol that dynamically assigns responsibility for a virtual router to one of the SVRRP routers on a LAN, which is exactly as same as that of VRRP. However, SVRRP executions do not exchange signaling packets and need the assistance of VRRP to perform their functionality appropriately. This approach can be used to improve the efficiency of VRRP routers in certain scenarios. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119].
Authors
Huihong Building
Dacheng Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)