DHCPv4 Vendor-specific Message
draft-ietf-dhc-dhcpv4-vendor-message-01
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2009-08-04) | ||
| Replaces | draft-volz-dhc-dhcpv4-vendor-message | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead::AD Followup) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note | Ted Lemon (mellon@nominum.com) is the document shepherd. | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-dhc-dhcpv4-vendor-message-01.txt
https://www.ietf.org/archive/id/draft-ietf-dhc-dhcpv4-vendor-message-01.txt
Abstract
This document requests a vendor-specific DHCPv4 message assignment. This message can be used for vendor specific and experimental purposes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)