Hand-off Extensions for Reverse Tunneling
draft-oneill-mip-revtun-ho-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alan W. O'Neill | ||
| Last updated | 2002-02-27 | ||
| 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
Reverse tunneling in RFC3024 [RevTun] introduces new packet loss scenarios at the HA and also incurs similar packet routing issues as RFC3220 [MIPv4] between Foreign Agents, during a handoff. Whether a Co- located Care-of-Address or a Foreign Agent Care-of-Address is used during Mobile IP registration, any packets from the new Foreign that are received at the Home Agent before the visitor list has been updated will be dropped. In addition, any in-flight packets from the old Foreign agent will be dropped once the visitor list has been updated.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)