Trace Control Support for Proxy Mobile IPv6
draft-wang-netext-trace-control-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yungui Wang , Qin Wu | ||
| Last updated | 2009-07-06 | ||
| 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
In some Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployments, a mobility session needs to be traced by the back-end network manager for network diagnosis, troubleshooting, new service testing, etc. This document defines a Trace Session option for PMIPv6 protocol to control and manage (activation and de-activation) a trace session associated with a mobility session of the mobile node. This option is sent by the mobile access gateway in Proxy Binding Update message to request the local mobile anchor to activate the trace session. When the local mobile anchor successfully processes the Proxy Binding Update, it then activates the trace session and starts to record/report the traced mobility session based on the corresponding trace parameters.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)