Re: Best way to retrieve DHCP vendor specific options?

Ted Lemon <mellon@fugue.com> Thu, 19 December 1996 22:18 UTC

Received: from cnri by ietf.org id aa15713; 19 Dec 96 17:18 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa22622; 19 Dec 96 17:18 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA03752; Thu, 19 Dec 1996 17:16:18 -0500
Date: Thu, 19 Dec 1996 17:16:18 -0500
Message-Id: <199612192142.NAA14541@toccata.fugue.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ted Lemon <mellon@fugue.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Best way to retrieve DHCP vendor specific options?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

The only time that the client is in a position to choose a server
based on what it offers is when it is in the SELECTING state, after
having sent out a DHCPDISCOVER message.  After it's got an address,
it's stuck with what it got unless it gives up the address and goes
back to the INIT-REBOOT state.

If it is important that a DHCP client receive vendor-specific options,
then it must request them in the DHCPDISCOVER broadcast, wait around
for some reasonable period of time collecting DHCPOFFERs, and take the
offer that most closely matches what it's looking for.  If it doesn't
get a DHCPOFFER with the appropriate vendor tags, it has a choice of
either going back to INIT-REBOOT and trying again, or settling for
what it got.

			       _MelloN_