FMIPv6 with LinkID
draft-subba-mipshop-fmip-linkid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Subba Reddy | ||
| Last updated | 2006-03-01 | ||
| 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
FMIPv6 aims to achieve seamless handoff but needs (AP-ID, AR-Info) in PARs to function and can't work if PAR doesn't have an entry for the next AP. In this draft, we present a scheme to dynamically build (AP-ID, AR-Info) tuple in PAR and make FMIPv6 perform even when PAR doesn't have a suitable (AP-ID, AR-Info) tuple by putting LinkID prefix in L2 beacon.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)