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

"Mattias Pettersson L \(LD/EAB\)" <mattias.l.pettersson@ericsson.com> Tue, 14 February 2006 16:09 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 1F92k6-0005JO-9a; Tue, 14 Feb 2006 11:09:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F92k5-0005Ip-CS for nemo@megatron.ietf.org; Tue, 14 Feb 2006 11:09:29 -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 LAA07355 for <nemo@ietf.org>; Tue, 14 Feb 2006 11:07:43 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F92xv-0006vi-Mv for nemo@ietf.org; Tue, 14 Feb 2006 11:23:48 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 5A4004F0002; Tue, 14 Feb 2006 17:09:27 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Feb 2006 17:09:27 +0100
Received: from esealmw103.eemea.ericsson.se ([153.88.200.66]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Feb 2006 17:09:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nemo] RE: draft-ietf-nemo-home-network-models-05
Date: Tue, 14 Feb 2006 17:09:25 +0100
Message-ID: <2D8B78375B46EF4C85EE21B9EB64350A01DA1559@esealmw103.eemea.ericsson.se>
Thread-Topic: [nemo] RE: draft-ietf-nemo-home-network-models-05
Thread-Index: AcYv+/HAKE1aH4taSSyuhNC9/w6PRgAuVNsQACcTWeAABgrM8AAFYPig
From: "Mattias Pettersson L (LD/EAB)" <mattias.l.pettersson@ericsson.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 14 Feb 2006 16:09:26.0800 (UTC) FILETIME=[07339100:01C63181]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, tj@kniveton.com, Margaret Wasserman <MRW@devicescape.com>, vijay.devarapalli@nokia.com, ryuji@sfc.wide.ad.jp, ernst@sfc.wide.ad.jp
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 Pascal,

> Yes, the idea is that the prefix is generally shorter than /64. 
> 
> We had long discussions in this ML about autoconfigs with 
> shorter prefixes (Alex?). But yes, NEMO should work in theory 
> with a shorter prefix assigned to the Home Link. 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. 

I'm not sure that ND will work for anything but /64. Maybe the intention
was so, but as you say, not all implementations support different prefix
lengths.

Still you will need the address resolution parts of ND, even though the
HA and MRs doesn't autoconfigure addresses on the home link.

The big issue is the ambiguity of which link/subnet a specific address
belongs to. For instance, given a packet destined to a specific MNN,
does the HA know if it should route (via an MR) or send directly to the
MNN (by using ND address resolution to get the MAC address)?

ND proxy/MLSR according to Thaler extends a /64 subnet across multiple
links. But the suggested behaviour here is different.

/Mattias