Reflector Extension for Route Optimization Agent
draft-cui-netext-route-optimization-agent-ext-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Xiangsong Cui | ||
| Last updated | 2009-12-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
Route Optimization is a very useful feature in Mobile IPv6. Mobile node can communicate with correspondent node without the involvement of the home agent in Route Optimization mode. But there are some limitations to this feature. One problem is that the mobile node and the correspondent node must be capable for Route Optimization. This document introduces a Route Optimization Agent function used for Route Optimization and this extension mechanism can enable Route Optimization mode to be used between mobile node and simple IP node. In the extension solution, the Route Optimization Agent function may be implemented in LMA or MAG and the Agent entity can reflect the RO-related signal messages and accomplish the Route Optimization procedure on behalf of the simple IP node. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)