RE: [dhcwg] IDs on remote boot support for DHCP

Vijay:

I don't understand the suboption (1) encoding for the multiple servers (ts
field) and the bootfiles (fn fields). Perhaps something happened with this
document or it is incomplete? Please look it over. Perhaps it is my problem,
but if it isn't clear, I'm sure others will have similar issues. Why don't
you just use two suboptions, one for the list of TFTP servers to use and
another for the bootfile names? Also, can the TFTP server names be IP
addresses? Perhaps you should consider using the DNS wire format instead of
ASCII?

I have a similar issue with the DHCPv6 draft. Seems to me if makes more
sense to have two options - one to list the TFTP servers and another to list
the bootfiles? (I guess there could be an argument made that different
bootfiles might be used with different servers???) It is also odd that you
would want to allow multiple TFTP server addresses in the DHCPv4 case, but
only allow one in the DHCPv6 case. Or have I missed something? One way
around this problem might be to allow multiple OPTION_REMOTE_BOOT and for
each of these, one can have a list of server (OPTION_REMOTE_BOOT_SERVERS)
and one or more boot files (OPTION_REMOTE_BOOT_FILES). For each instances of
the OPTION_REMOTE_BOOT, the servers would all use the same boot files.
However, if you want servers to use different boot files, you simply specify
multiple OPTION_REMOTE_BOOTs.

- Bernie

-----Original Message-----
From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of
Vijayabhaskar A K
Sent: Friday, October 31, 2003 10:16 AM
To: dhcwg@ietf.org
Subject: [dhcwg] IDs on remote boot support for DHCP

Hi All

I am attaching two new drafts dealing with remote boot support for DHCP.
I could not submit the draft to ID queue, as the deadline has crossed.
Please go through these drafts and let me know your comments. The
abstract of these drafts are given below

* The Extended Remote Boot Option for DHCPv4

Single TFTP 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 servers and
bootfiles.

* DHCPv6 Support for Remote Boot

This document provides new DHCPv6 (Dynamic Host Configuration
protocol version 6) options for clients, to obtain information about
TFTP servers and bootfiles needed for booting.

Vijay

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg