DHCP option for MIP type Decision
draft-zhao-dhc-miptype-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yuankui Zhao | ||
| Last updated | 2007-03-02 | ||
| 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
Dynamic Host Configuration Protocol is used as the trigger of network to distinguish if a MS need the proxy mip capability.But a MS maybe has the MIP capability.We need a flag to know if a MS need or require Proxy MIP capability.This document explains we can define a flag in dhcp option to state that a MS wish or doesn't wish to have the Proxy MIP capability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)