IETF Logo Mail Archive

Re: NT 3.51 dhcp client and server ip address

Matt Crawford <crawdad@fnal.gov> Tue, 03 December 1996 15:37 UTC

Received: from cnri by ietf.org id aa23428; 3 Dec 96 10:37 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa11940; 3 Dec 96 10:37 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA11902; Tue, 3 Dec 1996 10:26:31 -0500
Date: Tue, 3 Dec 1996 10:26:31 -0500
Message-Id: <199612031507.JAA24249@gungnir.fnal.gov>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Matt Crawford <crawdad@fnal.gov>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: NT 3.51 dhcp client and server ip address
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

Tim Rowe:
> I agree that the server identifier is used by the client to identify
> the DHCP server which extended the lease, but it shouldn't expect the
> identifier to have any other meaning.  'Fred' should be a valid server
> id as long as its unique among servers that may respond.

RFC1541. page 9:
            A DHCP server always returns its own address in the 'server
   identifier' option.

The siaddr field may not be the address of the DHCP server, so the
only certain places to get the server's IP address are in the IP
header and the server identifier.
_________________________________________________________
Matt Crawford          crawdad@fnal.gov          Fermilab
  PGP: D5 27 83 7A 25 25 7D FB  09 3C BA 33 71 C4 DA 6A

v2.8.7 | Report a Bug | By Email