IETF Logo Mail Archive

Re: NT 3.51 dhcp client and server ip address

Ted Lemon <mellon@fugue.com> Tue, 03 December 1996 03:29 UTC

Received: from cnri by ietf.org id aa12459; 2 Dec 96 22:29 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa22783; 2 Dec 96 22:29 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA04103; Mon, 2 Dec 1996 22:19:34 -0500
Date: Mon, 2 Dec 1996 22:19:34 -0500
Message-Id: <199612030308.TAA04436@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: 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

> The server identifier is used by the client to identify the DHCP
> server which extended the lease - not the BOOTP relay agent, or any
> other intermediary.

This is correct, but doesn't answer the question.

A simple way to rephrase the question would be: should the client
unicast DHCPREQUEST packets to the IP address in the Server Identifier
option, or should it unicast these packets to the IP source address
from which the last DHCPACK came?

I think it would be worthwhile to clarify this in the protocol
specification.

			       _MelloN_

v2.8.7 | Report a Bug | By Email