Re: Questions about server's use of giaddr

"Michael J. Lewis" <hosmjl@chevron.com> Fri, 19 April 1996 23:04 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23773; 19 Apr 96 19:04 EDT
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa23768; 19 Apr 96 19:04 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa17646; 19 Apr 96 19:04 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA22108; Fri, 19 Apr 1996 19:00:28 -0400
Date: Fri, 19 Apr 1996 19:00:28 -0400
Message-Id: <31781180.7332@chevron.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Michael J. Lewis" <hosmjl@chevron.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Questions about server's use of giaddr
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: Mozilla 2.0 (Win95; I)

Awhile back, there was some activity regarding DHCP servers handling 
multiple subnets on the same physical wire.  The included note suggested 
that there may be an update to the DHCP specifications to cover this 
case although the consensus seemed to be that individual servers should 
handle this case.  Was there ever a resolution to this issue regarding 
whether the specifications will be updated or whether we need to contact 
vendors to get them to handle these cases?  As we roll out DHCP in 
Chevron, we are finding more and more situations where we have multiple 
subnets per physical wire and we've been having difficulties getting 
DHCP services to perform properly.

Thanks.

Ralph Droms wrote:
> 
> At 11:05 AM 1/29/96, Jim Fletcher wrote:
> >There are some statements that lead me
> >to assume that a server uses giaddr to decide which subnet
> >to assign addresses from for clients.  If this is true, then how
> >are clients handled which live on a LAN which has multiple subnets
> >assigned to it?
> 
> Good question.  Your're not the only one with this question - we discussed
> just this issue at the last IETF meeting.
> 
> It seems that, because the initial DHCPDISCOVER message is broadcast, some
> piece of code somewhere is going to have to a) be aware of the network
> architecture that has multiple subnets on a physical segment and b) allow
> the local netadmin to describe how to handle DHCP clients from that
> segment.  Keeping in mind the goal of "mechanism not policy", we need to
> give netadmins the ability to choose the strategy for allocating addresses
> among logical subnets on a wire.
> 
> I think the prevailing opinion is that this function will need to be
> provided by DHCP servers.  The relay agents could also make a choice of
> which address to insert into 'giaddr'; to date, we've tried to make the
> requirements on relay agents as simple as possible and so relay agents
> don't look like good candidates.
> 
> The idea, then, would be to include with DHCP servers some knowledge of how
> to select a client address based on 'giaddr'.  I.e., given a specific
> 'giaddr', the server has a pool of available subnets to choose from (all of
> the logical subnets that share the wire with the address in 'giaddr') and a
> policy for how to choose from that pool.
> 
> If the WG is in agreement about this solution, perhaps it should be written
> down in the DHCP spec somewhere.  I've posted this note back to the DHCP
> mailing lists in case there is any further comment on the issue...
> 
> - Ralph