IETF Logo Mail Archive

Re: NT 3.51 dhcp client and server ip address

David Lapp <lapp@waterloo.hp.com> Mon, 16 December 1996 16:31 UTC

Received: from cnri by ietf.org id aa06526; 16 Dec 96 11:31 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa14305; 16 Dec 96 11:31 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA28424; Mon, 16 Dec 1996 11:19:21 -0500
Date: Mon, 16 Dec 1996 11:19:21 -0500
Message-Id: <199612161534.AA088690492@hppadan.waterloo.hp.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: David Lapp <lapp@waterloo.hp.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
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL21]

Ralph wrote:
> 
> I suggest the following text as a new paragraph to follow the second
> paragraph in draft-ietf-dhc-dhcp-08.txt:
> 
> The 'server identifier' field is used both to identify a DHCP server in a
.. text deleted
> 'server identifier' option for any unicast requests to the DHCP server.
> 
Sounds good to me.

> If pressed, I would also consider adding the following sentence to the
> first paragraph of section 9.7 of draft-ietf-dhc-options-1533update-05.txt:
> 
> DHCP clients use the contents of the 'server identifier' field as the
> destination address for any DHCP messages unicast to the DHCP server.
> 
> Comments?
>
Since it reflects the actual use of the server identifier
I think that this line should be added.

Dave Lapp

v2.8.7 | Report a Bug | By Email