The Extended Remote Boot Option for DHCPv4
draft-ietf-dhc-opt-extrboot-00
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2004-02-09 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| 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-opt-extrboot-00.txt
https://www.ietf.org/archive/id/draft-ietf-dhc-opt-extrboot-00.txt
Abstract
Single TFTP [2] server for huge number of diskless clients is prone to single point of failure. So, Multiple TFTP servers are needed for high availability. Moreover, some of the clients need multiple bootfiles for boot up. This document provides a new DHCPv4 option for clients to obtain information about multiple TFTP [2] servers and bootfiles.
Authors
a Vijayabhaskar (vijayak@india.hp.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)