IETF Logo Mail Archive

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

Alexandru Petrescu <alexandru.petrescu@motorola.com> Thu, 16 February 2006 16:38 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 1F9m95-0001j2-PG; Thu, 16 Feb 2006 11:38:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9m94-0001ij-5k for nemo@megatron.ietf.org; Thu, 16 Feb 2006 11:38:18 -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 LAA10390 for <nemo@ietf.org>; Thu, 16 Feb 2006 11:36:31 -0500 (EST)
Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9mNG-0004Sp-35 for nemo@ietf.org; Thu, 16 Feb 2006 11:53:02 -0500
Received: from az33exr02.mot.com ([10.64.251.232]) by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id k1GH6NLQ022961; Thu, 16 Feb 2006 10:06:23 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k1GGn8dw023420; Thu, 16 Feb 2006 10:49:09 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id C2DB7865980; Thu, 16 Feb 2006 17:37:55 +0100 (CET)
Message-ID: <43F4AA5F.9040602@motorola.com>
Date: Thu, 16 Feb 2006 17:37:51 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [nemo] RE: draft-ietf-nemo-home-network-models-05
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>
In-Reply-To: <A7C9E235-63A9-4835-A1EC-06C57797D758@sfc.wide.ad.jp>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
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>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org

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?

> 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?

Alex

v2.23.0 | Report a Bug | By Email