Transition from RFC2131-style to RFC3315-style Client Identifiers for DHCPv4
draft-lemon-dhcpv4-to-v6-id-trans-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ted Lemon | ||
| Last updated | 2004-01-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
This document explores ways for a node that is configured using DHCP and that has in the past been configured using one of the client identification schemes described in RFC2131 and RFC2132 to make the transition to using the identification scheme described in RFC3315 and in draft-ietf-dhc-3315-id-for-v4.txt.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)