TCP Multi-Home Options
draft-arifumi-tcp-mh-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Arifumi Matsumoto | ||
Last updated | 2003-10-08 | ||
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
In the existing TCP, only one local and one remote address is used through a TCP session, even when a client or a server is located under multi-homed site and has multiple IP addresses. When a network outage occurs and the access-line associated with the local and remote addresses is down, the TCP session itself gets lost even if another access-line is alive. TCP MH option makes it possible to handle multiple local and remote address pairs in one TCP session and to survive network outages by finding out an alternative network path. Our path transition mechanism is simple, fast, lightweight and as secure as existing TCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)