Mobility Support For TCP
draft-eddy-tcp-mobility-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wesley Eddy | ||
| Last updated | 2004-04-09 | ||
| 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
Once a TCP connection is established, there are no mechanisms for dynamically rebinding the connection to new IP addresses or port numbers. During the lifetime of a TCP connection, a mobile host's transition between networks (and the corresponding change in its IP address) will break any established TCP connections. As a remedy, this document presents an extension of TCP with support for dynamic bindings of IP addresses and port numbers. Compatibility with existing TCP implementations is maintained, and reasonable steps are taken to prevent remote-redirction attacks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)