[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

From: C. M. Heard
Subject: RE: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150
Date: Wed, 28 Sep 2005 11:02:37 -0700 (PDT)

>>>>> On Saturday, March 12, 2005 8:25 AM Yoshinori K. Okuji wrote:
Okuji> I would like to notify that GNU GRUB uses the DHCP option
Okuji> 150, according to
Okuji> RFC 3942.
Okuji> GNU GRUB Configuration Path
Okuji> This specifies the path-name that contains a configuration
Okuji> for GNU GRUB.
Okuji> The code for this option is 150.  Its minimum length is 1.
Okuji>     Code   Len    Configuration Pathname
Okuji>    +-----+-----+-----+-----+-----+-----+--
Okuji>    | 150 |  n  |  n1 |  n2 |  n3 |  n4 |  ...
Okuji>    +-----+-----+-----+-----+-----+-----+--

>>>>> On Sat, 12 Mar 2005 13:07:35 -0500 Bernie Volz replied:
Bernie> Looks like we now have 3 "users" of Option 150:
Bernie> 1. GNU GRUB
Bernie> 3. Etherboot

In http://www.iana.org/assignments/bootp-dhcp-parameters, however,
I see the following:

   150     TFTP server address (Tentatively Assigned - 23 Jun 2005)
   150     Etherboot    
   150     GRUB configuration path name

This seems to contradict RFC 3942, which says that if multiple vendors
come forward none will be assigned the option:

      NOTE: If multiple vendors of an option number come forward and can
      demonstrate that their usage is in reasonably wide use, none of
      the vendors will be allowed to keep the current option number, and
      they MUST go through the normal process of getting a publicly
      assigned option [RFC2939].                                     

What gives?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]