Update to RFC2937: The Name Service Search Option for DHCP
draft-williams-rfc2937bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Aidan Williams , Erik Guttman | ||
| Last updated | 2001-09-14 | ||
| 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
Hosts may use the Dynamic Host Configuration Protocol (RFC2131) [DHCP] as a mechanism to retrieve configuration information. The Name Service Search Option for DHCP (RFC2937) [NSSO] allows the DHCP server to specify the order in which various kinds of name services RFC2937 uses a list of DHCP option code numbers to identify the specific name service type, in the order it is to be consulted. This specification extends RFC2937 to support name service types which currently have no DHCP option number -- either because they do not need additional configuration information, or because this configuration is not typically supplied via DHCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)