IETF Logo Mail Archive

Re: [nemo] Re: comments on draft-ietf-nemo-dhcpv6-pd-00.txt

Vijay Devarapalli <vijayd@iprg.nokia.com> Wed, 07 September 2005 02:14 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECpSh-00013x-A6; Tue, 06 Sep 2005 22:14:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECpSc-000135-RG for nemo@megatron.ietf.org; Tue, 06 Sep 2005 22:14:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21132 for <nemo@ietf.org>; Tue, 6 Sep 2005 22:14:48 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECpVc-0004pu-Uz for nemo@ietf.org; Tue, 06 Sep 2005 22:18:02 -0400
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j871fmv05681; Tue, 6 Sep 2005 18:41:48 -0700
X-mProtect: <200509070141> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40, claiming to be "[205.226.2.40]") by darkstar.iprg.nokia.com smtpdOa5C7t; Tue, 06 Sep 2005 18:41:46 PDT
Message-ID: <431E4CFC.6010108@iprg.nokia.com>
Date: Tue, 06 Sep 2005 19:14:20 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [nemo] Re: comments on draft-ietf-nemo-dhcpv6-pd-00.txt
References: <7892795E1A87F04CADFCCF41FADD00FC01356158@xmb-ams-337.emea.cisco.com> <4314A955.5050906@iprg.nokia.com> <77B28091-FE92-4D33-964C-3D0D6D57F6C7@sfc.wide.ad.jp>
In-Reply-To: <77B28091-FE92-4D33-964C-3D0D6D57F6C7@sfc.wide.ad.jp>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Ralph Droms (rdroms)" <rdroms@cisco.com>
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org

Ryuji Wakikawa wrote:

> Can MR can skip DHCP server discovery sending message to FF02::1:2 ?
> If MR knows the HA, MR can send request message to the HA without DR  
> discovery.

yes, this should be supported.

> On the other hand, If MR does not know the HA, can MR use DHCP6PD as  an 
> alternative HA discovery mechanism?

no. the MR can't reach the DHCPv6 server on the home link. are you
suggesting using the DHCP server on the visited link to allocate
a HA from the home link?

> Or, MR rather do DHAAD to know a HA first, then it sends an address  
> request message to the known HA?

yes. or use DNS to discover the HA as described in 
draft-ietf-mip6-bootstrap-split

> When there are multiple HAs available at a home link, do you assume  
> only one of HA supports DR?

whats the issue in having all HAs as DHCP relay agents?

Vijay

v2.43.4 | Report a Bug | By Email | System Status