IETF Logo Mail Archive

Re: [dhcwg] status of draft-ietf-dhc-agent-subnet-selection

Thomas Narten <narten@us.ibm.com> Wed, 09 October 2002 19:44 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01311 for <dhcwg-archive@odin.ietf.org>; Wed, 9 Oct 2002 15:44:22 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99Jk3313387 for dhcwg-archive@odin.ietf.org; Wed, 9 Oct 2002 15:46:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Jk3v13384 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 9 Oct 2002 15:46:03 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01285 for <dhcwg-web-archive@ietf.org>; Wed, 9 Oct 2002 15:43:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99JhNv13303; Wed, 9 Oct 2002 15:43:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99JgUv13272 for <dhcwg@optimus.ietf.org>; Wed, 9 Oct 2002 15:42:30 -0400
Received: from e31.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01187 for <dhcwg@ietf.org>; Wed, 9 Oct 2002 15:40:17 -0400 (EDT)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24]) by e31.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id g99Jg9nL017228; Wed, 9 Oct 2002 15:42:09 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14]) by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g99Jg8HY228616; Wed, 9 Oct 2002 13:42:08 -0600
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g99JeLt32363; Wed, 9 Oct 2002 15:40:21 -0400
Message-Id: <200210091940.g99JeLt32363@rotala.raleigh.ibm.com>
To: Ralph Droms <rdroms@cisco.com>
cc: Ted Lemon <Ted.Lemon@nominum.com>, "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>, Kim Kinnear <kkinnear@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] status of draft-ietf-dhc-agent-subnet-selection
In-Reply-To: Message from Ralph Droms <rdroms@cisco.com> of "Wed, 09 Oct 2002 14:58:58 EDT." <4.3.2.7.2.20021009144203.03622970@funnel.cisco.com>
Date: Wed, 09 Oct 2002 15:40:21 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

> The message from the relay agent to the server uses the relay agent's 
> address as the source address.  The relay agent modifies and sends the DHCP 
> message as the payload in a UDP message that appears to originate from the 
> relay agent.  Section 4 of RFC1542 gives more details.  The difference 
> between DHCPv4 and DHCPv6 is in the way in which the client message is 
> processed by the relay agent (in DHCPv6, the message is encapsulated in a 
> new message generated by the relay agent).

OK. I misunderstood how this worked. Because the relay agent mucks
with the giaddr field, I had never understood that the relay agent is
in fact sourcing a packet with its own source address (which contains
the same info as the giaddr field). I guess back then, getting the
source address of a packet out of the API was deemed to hard or
something?

So yes, I agree IPsec could be used to secure the relay-agent - server
path.

Thomas
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email