Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 - how to proceed?

[Jarrod Johnson <jarrod.b.johnson+dhcwg at gmail.com>]

I know that gPXE and pxelinux also support distinct sets of extended
options (sometimes mixing and matching using a 'plain' option and
using an option encapsulating other options).  Even with that all in
place, they almost all additionally reference a configuration file
(which they usually do via excessive requests based on their identity,
though I usually drive a more specific behavior through a dhcp
option).  For second-stage loaders with rich scripting behaviors,
cramming that into a DHCP option would probably not be nice for many
administrators.

With all that said, it seems exceedingly common that at least two
things are commonly referenced in a potentially common way in a
typical netboot fashion:
-The second stage loader executable code
-Optionally, a configuration file or script for that second stage
loader, that typically points to other requisite files that vary from
OS to os (i.e. multiboot images, or a linux kernel/initrd, and various
things in a Windows BCD file, though the Windows search for BCD file
is less flexible today than I would like)

As a potential slight tangent, this discussion has been focused on
netboot scenarios focused on downloading an executable and running it,
but what about registering network based SAN strategies (i.e. iSCSI
per RFC 4173)?  One aspect I didn't like of that standard was to imply
it was used for configuring a boot volume only with the expectation
that it would be the boot device of that boot, as I have a scenario
where the two actions on the client network device are separate (i.e.
it will configure itself and connect to the iSCSI target, and
configure firmware tables, but then still allow me to boot via
'filename' so that the PXE booted OS would be aware of the iSCSI
target configuration).  I mention that in fear that it is suggested to
simply re-use boot-uri, which would preclude the potential of
DHCP-driven SAN configuration at the same time a netboot is desired.


On Sat, Oct 10, 2009 at 1:32 PM, Ted Lemon <Ted.Lemon at nominum.com> wrote:
> Wow, a lot to think about.   I guess we should have had this discussion a
> year ago - I'm sorry for not doing more to make it happen earlier.
>
> I like the idea of getting rid of the priority entirely, and that makes
> sense if the bootfiles are all the same.   And since there's no way to
> differentiate between them, it makes sense that they are the same.
> However, mentioning PXE and yaboot does point out a problem with this
> approach: it failed last time.   We wound up with yaboot options that were
> allocated without a draft or contact with the IANA, and PXE was a bit of a
> mess too.
>
> So let me ask you this: suppose we took out the priority option, and only
> allowed a single boot parameters option.   Would that draft be something
> that people here would actually use as it was?   Or would they find
> themselves adding extensions?
>
> _______________________________________________
> dhcwg mailing list
> dhcwg at ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>