The Extended Remote Boot Option for DHCPv4
draft-ietf-dhc-opt-extrboot-00
Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
---|---|---|---|
Author | a Vijayabhaskar | ||
Last updated | 2004-02-09 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)