Re: Questions about server's use of giaddr

lowell@epilogue.com Mon, 05 February 1996 20:56 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08114; 5 Feb 96 15:56 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08110; 5 Feb 96 15:56 EST
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa14072; 5 Feb 96 15:56 EST
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA17702; Mon, 5 Feb 1996 15:48:18 -0500
Date: Mon, 5 Feb 1996 15:48:18 -0500
Message-Id: <9602051216.aa27479@kehleyr.epilogue.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: lowell@epilogue.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

[Ralph Droms:]
> Ouch.  This sounds like an ugly problem.  I think you're right - relay
> agents, especially those not running in a router - could very easily
> receive server responses for which the relay agnent has no corresponding
> interface.
> 
> Anybody have a better suggestions?

Afraid not.  Even on the graceful-renumbering stuff, I've basically
been assuming that a relay agent has to be configured to speak on a
subnet in order to handle passing requests back to that subnet.  It's
clear that the router has to be configured for that subnet to make it
worth assigning an address on that subnet, so I think the combined
router-and-relay-agent case is the *most* obvious example.

Be well.
        Lowell Gilbert
--
(1) If it ain't broke, don't fix it.
(2) If you can't fix it, don't break it.
(2) Just because it works don't mean it ain't broke.