Redundant TCP
draft-kilsdonk-redundant-tcp-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Daniel D. Kilsdonk | ||
Last updated | 2005-06-13 | ||
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
This memo documents a process which can be used to avoid network outages during the upgrading of a router's software. In this way, disruptions to the network community are avoided. The upgrade process definition comprises requirements for inserting a replacement router or upgrading the software in a working router within an operational network. To do this, it maximizes the use of accepted internet standards with minimal alteration.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)