[dhcwg] Question on Relay address field

"Vijay Bhaskar A K" <vijayak@india.hp.com> Fri, 21 September 2001 06:26 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14133; Fri, 21 Sep 2001 02:26:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA03543; Fri, 21 Sep 2001 02:25:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA03523 for <dhcwg@optimus.ietf.org>; Fri, 21 Sep 2001 02:25:28 -0400 (EDT)
Received: from atlrel6.hp.com (atlrel6.hp.com [192.151.27.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14081 for <dhcwg@ietf.org>; Fri, 21 Sep 2001 02:25:25 -0400 (EDT)
Received: from hpuxsrv.india.hp.com (hpuxsrv.india.hp.com [15.10.45.132]) by atlrel6.hp.com (Postfix) with ESMTP id 91ED01F5DD for <dhcwg@ietf.org>; Fri, 21 Sep 2001 02:24:13 -0400 (EDT)
Received: from nt4147 (nt4147.india.hp.com [15.10.41.47]) by hpuxsrv.india.hp.com with SMTP (8.8.6 (PHNE_17135)/8.8.6 SMKit7.02) id LAA05608 for <dhcwg@ietf.org>; Fri, 21 Sep 2001 11:50:48 +0530 (IST)
Reply-To: <vijayak@india.hp.com>
From: "Vijay Bhaskar A K" <vijayak@india.hp.com>
To: "Dhcwg (E-mail)" <dhcwg@ietf.org>
Date: Fri, 21 Sep 2001 11:54:09 +0530
Message-ID: <004401c14266$06810260$2f290a0f@india.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Question on Relay address field
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

The latest draft on DHCPv6 says that, the client sends the
request to All Agents multicast address. The Agents put its
own address of the interface in which the client packet is
recieved, in the Relay-forward packet.

Assume the configuration one of the interface of the Agent is as follows.

lan0   -  A link local address
lan0:1 -  A site local address
lan0:2 -  A gloabal address

Assume the packet is received from the client in the lan0 interface of the
agent.
Using our latest IPv6 APIs, we can identify this.
But, we CANT identify at what alias interface ( lan0 or lan0:1 or lan0:2)
in which the packet is received.

Here the problem is, the relay cannot put its own link local address
in the relay address field in the relay forward packet, since this
info is useless.

The question, SHOULD the relay put the address in lan0:1 (site local
address) or lan0:2 (global address)in the relay address field?
The DECISION of the relay is very important that depending up on the
address it is sending the relay address field only, the server can
allocate address to the client. Is there any solution to this
problem?
~Vijay



____Vijay_Bhaskar_A_K____
______Inet_Services______
________HP_ISO___________
_____Phone:_2051424______
___Pager:_9624_371137____


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