[dhcwg] Re: I-D ACTION:draft-ietf-dhc-agent-vpn-id-02.txt

Thomas Narten <narten@us.ibm.com> Wed, 06 November 2002 20:59 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12114 for <dhcwg-archive@odin.ietf.org>; Wed, 6 Nov 2002 15:59:35 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA6L1dZ11598 for dhcwg-archive@odin.ietf.org; Wed, 6 Nov 2002 16:01:39 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6L1cv11595 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 16:01:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12097 for <dhcwg-web-archive@ietf.org>; Wed, 6 Nov 2002 15:59:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6KxDv11443; Wed, 6 Nov 2002 15:59:13 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6KwGv11388 for <dhcwg@optimus.ietf.org>; Wed, 6 Nov 2002 15:58:16 -0500
Received: from e31.co.us.ibm.com (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11954 for <dhcwg@ietf.org>; Wed, 6 Nov 2002 15:55:42 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com []) by e31.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id gA6Kw9Jw013650 for <dhcwg@ietf.org>; Wed, 6 Nov 2002 15:58:09 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com []) by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id gA6Kw9u3114350 for <dhcwg@ietf.org>; Wed, 6 Nov 2002 13:58:09 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id gA6KsGY18958 for <dhcwg@ietf.org>; Wed, 6 Nov 2002 15:54:16 -0500
Message-Id: <200211062054.gA6KsGY18958@rotala.raleigh.ibm.com>
To: dhcwg@ietf.org
In-Reply-To: Message from Internet-Drafts@ietf.org of "Wed, 06 Nov 2002 06:27:45 EST." <200211061127.GAA11867@ietf.org>
Date: Wed, 06 Nov 2002 15:54:16 -0500
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] Re: I-D ACTION:draft-ietf-dhc-agent-vpn-id-02.txt
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>

Looking  through this document, could someone explain what problem
this ID is solving?

In particular, it seems to me that DHCP servers/relay agents shouldn't
and don't need to understand about VPNs.  I.e., when a node joins the
network, it is assigned a VPN. This ID proposes that a relay agent
include a string or other identifier in the relay agent option to
indicate the VPN the client is assigned to. But, it seems to me that
the relay agent could just as easily be assigned an IP address on each
VPN, and then just stuff that address into the giaddr field of the
packets. This is normal DHC, using existing protocols and standards.
In this case, neither the relay agent nor the DHC server need to know
about VPNs in any way other than they already do. I.e, the giaddr
field indicates a VPN, and existing standard DHC config technique can
be used to assign addresses and other paramaters to the client.

What is it that I'm not understanding here?

dhcwg mailing list