Redundant Fault Tolerant Configurations
draft-pitta-redundant-fault-tol-conf-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Srinivas Pitta | ||
| Last updated | 2003-05-05 | ||
| 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
The ability of the system to deliver its normal service in the presence of any unexpected errors and able to recover from the errors and restore to normal operation is called a fault tolerant system. Such systems whose behavior is predictable in nearly every possible situation are often in redundant fault tolerant configurations. This document defines the various redundant fault tolerant configurations that make these systems dependable systems or high availability systems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)