BUB: Binding Update Backhauling
draft-haddad-mipv6-bub-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wassim Haddad | ||
| Last updated | 2004-02-14 (Latest revision 2004-02-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
Mobile IPv6 [1] defines two different modes to handle the mobility problem (i.e., mobile node moving accross different networks and changing its IP address). The two modes had been mainly designed for scenarios involving one mobile node and one static node (correspondent node). This document answers issues related to scenarios involving two mobile nodes (i.e., the correspodent node is also a mobile node). The document addresses also the double jumping problem where two mobile nodes move at the same time (i.e., switch to new subnets). The document proposes a new mode called 'BUB' (Binding Update Backhauling) allowing a more secure, reliable and optimized exchange of Binding Updates (BUs) between two mobile endpoints.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)