Re: [dhcwg] Link Address filed in Relay Messages

"David W. Hankins" <David_Hankins@isc.org> Mon, 19 March 2007 08:55 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTDel-0005gt-8z; Mon, 19 Mar 2007 04:55:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTDei-0005bv-Ag for dhcwg@ietf.org; Mon, 19 Mar 2007 04:55:52 -0400
Received: from the.hankinsfamily.info ([204.152.186.148] helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTDee-0003me-UR for dhcwg@ietf.org; Mon, 19 Mar 2007 04:55:52 -0400
Received: from hcf.isc.org (dhcp-1545.ietf68.org [130.129.21.69]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l2J8tVav005681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Mar 2007 01:55:33 -0700
Received: by hcf.isc.org (Postfix, from userid 10200) id 6DB425EE04; Mon, 19 Mar 2007 09:55:31 +0100 (CET)
Date: Mon, 19 Mar 2007 09:55:30 +0100
From: "David W. Hankins" <David_Hankins@isc.org>
To: punit shah <punithsshah@gmail.com>
Subject: Re: [dhcwg] Link Address filed in Relay Messages
Message-ID: <20070319085530.GJ3685@isc.org>
References: <6904c3ec0703142232y79aca71ge8adab0172b6fd58@mail.gmail.com>
Mime-Version: 1.0
In-Reply-To: <6904c3ec0703142232y79aca71ge8adab0172b6fd58@mail.gmail.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Content-Type: multipart/mixed; boundary="===============2063015434=="
Errors-To: dhcwg-bounces@ietf.org

On Thu, Mar 15, 2007 at 11:02:59AM +0530, punit shah wrote:
> The RFC says Relay Agent must fill the RElay-Forward messages with a
> global/site local(now deprecated) address belonging to the same
> link as that of the user who needs to be allocated IPv6 address. But the
> problem is our sware has no means of knowing which link (or even MAC
> address) of the
> user and IPv6 addresses on the users link.
> 
> Is it possible to solve this problem in a rfc compliant manner and how?

I do not think so.

The MAC address is unimportant to a DHCPv6 server.  So long as the
DUID and IAID combine together to form one unique binding for one
unique client, the mechanics of those identifiers are irrelevant.

Not knowing at least one global address that resides on the link
the client is connected to is a big problem.

> Also would link local address be acceptable or alternatively a fictitious
> global address not neccesarily on the usre's l;ink?

I do not think so.

I think the best you can do is fill the link address field with
zeroes and hope for the best, but this requires some very strange
DHCPv6 server configuration - where the server is expected to
know where all clients are singly attached (this is very odd for
a DHCP server...the expectation is always that they move between
networks), and can give such addresses despite lack of hints from
the relay agents.

-- 
ISC Training!  http://www.isc.org/training/  training@isc.org
Washington DC area, April 16-20 2007.  DNS & BIND, DDNS & DHCP.
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		you'll just have to do it again."
Internet Systems Consortium, Inc.	-- Jack T. Hankins
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg