Re: [nemo] RE: draft-ietf-nemo-home-network-models-05

Ryuji Wakikawa <ryuji@sfc.wide.ad.jp> Sun, 19 February 2006 19:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1-ext.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAuIv-0006ZY-Cq; Sun, 19 Feb 2006 14:33:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAuAL-0006LN-JX for nemo@ietf.org; Sun, 19 Feb 2006 14:24:17 -0500
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAtxl-0002Cv-Vq for nemo@ietf.org; Sun, 19 Feb 2006 14:11:19 -0500
Received: from [192.168.0.8] (p2112-ipbf601marunouchi.tokyo.ocn.ne.jp [222.145.139.112]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id BDC814DE67; Mon, 20 Feb 2006 04:11:15 +0900 (JST)
In-Reply-To: <43F4AA5F.9040602@motorola.com>
References: <7892795E1A87F04CADFCCF41FADD00FC01D297BA@xmb-ams-337.emea.cisco.com> <43F20601.1040705@motorola.com> <20060215121222.1dc6385f.ernst@sfc.wide.ad.jp> <A7C9E235-63A9-4835-A1EC-06C57797D758@sfc.wide.ad.jp> <43F4AA5F.9040602@motorola.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <F6C58576-AB31-4B92-AC4D-DAA26697C42E@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [nemo] RE: draft-ietf-nemo-home-network-models-05
Date: Mon, 20 Feb 2006 04:11:15 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: nemo@ietf.org, Thierry Ernst <ernst@sfc.wide.ad.jp>, mattias.l.pettersson@ericsson.com, pthubert@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>
Errors-To: nemo-bounces@ietf.org

Alex

On 2006/02/17, at 1:37, Alexandru Petrescu wrote:

> Ryuji Wakikawa wrote:
>> Hi Alex and Thierry
>> Please check the RFC3964 section3 We said "A Mobile Router has a
>> unique Home Address through which it is reachable when it is
>> registered with its Home Agent.  The Home Address is configured from
>> a prefix aggregated and advertised by its Home Agent.  The prefix
>> could be either the prefix advertised on the home link or the prefix
>> delegated to the Mobile Router. "
>
> Hi Ryuji, there can be no implementation that derives the HoA from MNP
> and simultaneously is defended by proxy ND by HA.  Is there any?

I don't know how you can conclude like this..

SHISA can generate HoA from MNP.
MR can return home in some configuration.
When MR returns home, HA does not remove network route of MNP pointed  
to MR.
Thus, without proxy ND, MR can return home.

>> Some advantages using HoA derived from MNP. The operators do not
>> suffer from matching HoA from the home link and assigned MNP. We can
>> save a prefix/64 for just assigning HoA to MRs.
>
> I'm not sure I understand how the matching hurts the operators.
>
> I don't think addresses or prefixes are saved, can you explain?

You need /64 or shorter prefix to assign HoA.

regards,
ryuji