DHCPv6 Remote Boot Options
draft-zimmer-dhc-dhcpv6-remote-boot-options-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|---|---|---|
| Authors | Dave Thaler , Vincent Zimmer | |
| Last updated | 2008年11月03日 | |
| 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 describes a means by which to support network boot of a bare-metal platform utilizing a pre-boot execution environment, such as the Unified Extensible Firmware Interface [UEFI22]. The problem being addressed is that the PXE [PXE21] and UEFI Specifications [UEFI22] only describe how to ascertain boot configuration options using DHCPv4 [RFC2131], not for DHCPv6 [RFC3315]. Similarly, iSCSI boot [RFC4173] does not specify how to discover boot device information in an DHCPv6 environment. This document will describe how to ascertain this boot information in an IPv6 environment utilizing options in the DHCPv6 hand-off [RFC3315].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)