Re: Questions about server's use of giaddr

Ralph Droms <droms@bucknell.edu> Mon, 05 February 1996 20:58 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08189; 5 Feb 96 15:58 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08185; 5 Feb 96 15:58 EST
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa14101; 5 Feb 96 15:58 EST
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA17951; Mon, 5 Feb 1996 15:51:43 -0500
Date: Mon, 5 Feb 1996 15:51:43 -0500
Message-Id: <v02120d0aad3bf251f7ca@[134.82.7.155]>
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: Ralph Droms <droms@bucknell.edu>
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

At 11:46 AM 2/5/96, Shawn Mamros wrote:
>"A relay agent MUST NOT use yiaddr to determine the interface on
>which to relay a message from a DHCP or BOOTP server to a client; it MUST
>use giaddr solely instead.  yiaddr MUST only be used as the destination
>IP address when relaying a message from a server to a client (when the
>broadcast bit is not set).  A relay agent MUST NOT send server responses
>through a router, even if yiaddr and giaddr appear to be on different
>logical networks, because the server could have knowledge about the
>topology of the network that is unknown to the relay agent (e.g., the
>logical networks indicated by yiaddr and giaddr may both reside on the
>same physical network)."

Is this implementable, in practice?

- Ralph