Bi-directional Tunneling for Mobile IP
draft-montenegro-tunneling-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gabriel Montenegro | ||
| Last updated | 1996-09-09 (Latest revision 1996-01-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 Mobile IP specification uses tunneling from the home agent to the mobile node, but rarely in the reverse direction. Usually, a mobile node sends its packets through a router in the foreign net, and assumes that routing is independent of source address. When this assumption is not true, it is convenient to establish topologically correct bi-directional tunnels between the home agent and the mobile node's care-of address. This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct bi-directional tunnels. This document does not attempt to solve the problems posed by firewalls located between the home agent and the mobile node's care-of address.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)