Re: [nemo] RE: draft-ietf-nemo-home-network-models-05
Ryuji Wakikawa <ryuji@sfc.wide.ad.jp> Wed, 15 February 2006 16:56 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9Px4-0005lO-IS; Wed, 15 Feb 2006 11:56:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9Px2-0005hT-HV for nemo@megatron.ietf.org; Wed, 15 Feb 2006 11:56:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11504 for <nemo@ietf.org>; Wed, 15 Feb 2006 11:54:38 -0500 (EST)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9QB1-0007My-4b for nemo@ietf.org; Wed, 15 Feb 2006 12:10:56 -0500
Received: from [IPv6:2001:200::8801:211:24ff:fe79:8e82] (unknown [IPv6:2001:200:0:8801:211:24ff:fe79:8e82]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id CAEE64DAB9; Thu, 16 Feb 2006 01:56:08 +0900 (JST)
In-Reply-To: <20060215121222.1dc6385f.ernst@sfc.wide.ad.jp>
References: <7892795E1A87F04CADFCCF41FADD00FC01D297BA@xmb-ams-337.emea.cisco.com> <43F20601.1040705@motorola.com> <20060215121222.1dc6385f.ernst@sfc.wide.ad.jp>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A7C9E235-63A9-4835-A1EC-06C57797D758@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: Thu, 16 Feb 2006 01:56:07 +0900
To: Thierry Ernst <ernst@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, pthubert@cisco.com, mattias.l.pettersson@ericsson.com, Alexandru Petrescu <alexandru.petrescu@motorola.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
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. " 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. regards, ryuji On 2006/02/15, at 12:12, Thierry Ernst wrote: > >> What stays clear to me about the aggregated mode is the following. >> >> The aggregated mode is something not supported by RFC3963 because >> RFC3963 works when the Home Address is derived from the prefix on the >> home link. > > According to me, this is not so clear. RFC 3963 is a result of merging > several ideas, including the idea from Ryuji that the MR's HoA can be > taken from the MNP. This said, I don't have the technical deepth that > you have to evaluate if RFC 3963 allow it ort not. > > So, I cced Ryuji regarding this point. > >> draft-ietf-nemo-home-network-models-xx.txt: >> "it makes sense for a Mobile Router to register using a Home Address >> from one of its own MNPs." >> >> No, it makes no sense. > > Well, to Alex it may not make sense. But it makes some sense for other > authors of RFC 3963. > >> Otherwise I agree with you. > > Thierry. >
- [nemo] RE: draft-ietf-nemo-home-network-models-05 Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Mattias Pettersson L (LD/EAB)
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Mattias Pettersson L (LD/EAB)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Thierry Ernst
- RE: [nemo] RE: draft-ietf-nemo-home-network-model… Pascal Thubert (pthubert)
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Ryuji Wakikawa
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Ryuji Wakikawa
- Re: [nemo] RE: draft-ietf-nemo-home-network-model… Alexandru Petrescu