Limitations exist in IP mobility support applications
draft-zhao-nemo-limitations-ps-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yuankui Zhao | ||
| Last updated | 2007-11-12 | ||
| 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
There already exist several mobility support solutions and each solution uses its own method to achieve specific goals.But different solutions may not work properly when they are combined in an integrated application environment because network entities have little information about each other.Specially when PMIP meet with the Nemo network environment something need to be considered more. This document describes several limitations on NEMO application and provides a possible solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)