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

Alexandru Petrescu <alexandru.petrescu@motorola.com> Tue, 14 February 2006 16:32 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 1F9368-0004lj-Ex; Tue, 14 Feb 2006 11:32:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9366-0004lE-VL for nemo@megatron.ietf.org; Tue, 14 Feb 2006 11:32:15 -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 LAA08873 for <nemo@ietf.org>; Tue, 14 Feb 2006 11:30:28 -0500 (EST)
Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F93Jv-0007c3-4m for nemo@ietf.org; Tue, 14 Feb 2006 11:46:32 -0500
Received: from az33exr02.mot.com ([10.64.251.232]) by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id k1EH0PCL017720; Tue, 14 Feb 2006 10:00:25 -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 k1EGhB84021839; Tue, 14 Feb 2006 10:43:12 -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 D5559865980; Tue, 14 Feb 2006 17:32:03 +0100 (CET)
Message-ID: <43F20601.1040705@motorola.com>
Date: Tue, 14 Feb 2006 17:32:01 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Pascal Thubert \\(pthubert\\)" <pthubert@cisco.com>
Subject: Re: [nemo] RE: draft-ietf-nemo-home-network-models-05
References: <7892795E1A87F04CADFCCF41FADD00FC01D297BA@xmb-ams-337.emea.cisco.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC01D297BA@xmb-ams-337.emea.cisco.com>
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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, "Mattias Pettersson L \\\\(LD/EAB\\\\)" <mattias.l.pettersson@ericsson.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

Pascal Thubert \(pthubert\) wrote:
> 
>> 
>>> Note that NEMO does not require autoconf operations; and last 
>>> that I know, a Cisco router will not auto-configure an address on
>>>  a prefix that is shorter than 64.
>> 
>> You seem to imply that a router _will_ auto-configure an address 
>> from an RA with prefix /64.  YEs?  A "router" fixed or mobile 
>> shouldn't statelessly auto-configure an IPv6 address at all, be it 
>> prefix /64 or shorter, no?
>> 
> [Pascal] Alex, the Mobile Router needs to auto-configure an address 
> on its egress interface as it roams...

Right... I meant so too... my remark was not necessary in this context.

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.

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.

Otherwise I agree with you.

Alex