DHCPv6 Relay Agents and NEMO
draft-dupont-mext-dhcrelay-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Francis Dupont , Wassim Haddad | ||
| Last updated | 2008-02-18 | ||
| 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
The IPv6 network mobility (NEMO) configuration relies on a prefix delegation service to fulfill its task. Such service has already been described in two different proposals, one is based on DHCPv6 and the other extends NEMO signaling. However, both failed to gather consensus. This memo describes how DHCPv6 Relay Agents can be used in order to provide the missing flexibility and pave the way for a solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)