Re: [nemo] WG Last Call on draft-ietf-nemo-terminology
Chan-Wah Ng <chanwah.ng@sg.panasonic.com> Fri, 18 November 2005 02:20 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 1EcvrO-0000Zh-K9; Thu, 17 Nov 2005 21:20:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcvrN-0000Zc-4C for nemo@megatron.ietf.org; Thu, 17 Nov 2005 21:20:17 -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 VAA12955 for <nemo@ietf.org>; Thu, 17 Nov 2005 21:19:41 -0500 (EST)
Received: from smtp.mei.co.jp ([133.183.129.25] helo=smtp1.mei.co.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ecw96-0004GB-MC for nemo@ietf.org; Thu, 17 Nov 2005 21:38:38 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150]) by smtp1.mei.co.jp (8.12.10/3.7W/bulls) with ESMTP id jAI2K3FM003680; Fri, 18 Nov 2005 11:20:03 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id jAI2K5V16761; Fri, 18 Nov 2005 11:20:05 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/indians) with ESMTP id jAI2K1308419; Fri, 18 Nov 2005 11:20:02 +0900 (JST)
Received: from bach.psl.com.sg ([10.81.113.99]) by pslexc01.psl.local with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 Nov 2005 10:16:58 +0800
Received: by bach.psl.com.sg (Postfix, from userid 1000) id B8BA6D560C; Fri, 18 Nov 2005 10:26:47 +0800 (SGT)
Subject: Re: [nemo] WG Last Call on draft-ietf-nemo-terminology
From: Chan-Wah Ng <chanwah.ng@sg.panasonic.com>
To: Romain KUNTZ <kuntz@sfc.wide.ad.jp>
In-Reply-To: <437D339F.3010305@sfc.wide.ad.jp>
References: <E1EV94s-0000Iv-L1@newodin.ietf.org> <20051028155154.719167e5.ernst@sfc.wide.ad.jp> <20051117192750.7b7688d8.ernst@sfc.wide.ad.jp> <437D339F.3010305@sfc.wide.ad.jp>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Nov 2005 10:26:47 +0800
Message-Id: <1132280807.4927.14.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
X-OriginalArrivalTime: 18 Nov 2005 02:16:58.0258 (UTC) FILETIME=[2732E720:01C5EBE6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Cc: nemo <nemo@ietf.org>
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
On Fri, 2005-11-18 at 10:51 +0900, Romain KUNTZ wrote:
> Hello,
>
> Thierry Ernst wrote:
> > - A25 (split NEMO)
>
> I propose the following draft definition:
>
> A split NEMO occurs when a single mobile subnet connected to multiple
> Mobile Routers, or multiple mobile subnets interconnected with routers,
> become two or more independant mobile subnets.
"independent".
Anyway, "multiple mobile subnets interconnected with routers" is not
very accurate and leads to controversy. Consider
MR1 MR1
| |
---+-+--- => --+--- MR2
| |
MR2 --+--
|
---+----
It fits your definition but does not falls into the normal sense of
split NEMO.
>
> | | | |
> MR1 MR2 MR1 MR2
> | | -> | |
> ---------- ----- -----
>
The above I agree, the one below needs a bit of further exploration.
>
> | | | |
> MR1 Router MR2 MR1 MR2
> | | | | -> | |
> -------- ------- ----- -----
>
With a router, presumably a LFR, in between, the two links are separate
subnets. So, MR1 and MR2 are handling different prefixes. When the
two links goes separate way, what would happens is that the LFR would no
longer function as a router, since it loses its at least one of its link
for forwarding.
As far as NEMO-BS is concerned, this situation also does not fall into
the normal sense of split-NEMO problem, because MR1 and MR2 are handling
different prefixes, even when they split, there is no ambiguity in the
HA(s) on who to forward a packet destined for one of the MNPs to.
Unless the router in the figure is not a router but a bridge/switch/...,
a layer 2 device. Which should not reflected, and thus reducing this
case to be equivalent to the first diagram you draw, from a layer 3
perspective.
It all depends on what is the motivation for the inclusion of the
split-NEMO definition. I thought the motivation was to assist in
illustrating the problem of split NEMO as documented in
draft-ietf-nemo-multihoming-issues. If this is indeed the case, then
the definition of split-NEMO should define cases only when the problem
of split NEMO occurs.
/rgds
/cwng
- [nemo] I-D ACTION:draft-ietf-nemo-terminology-04.… Internet-Drafts
- [nemo] WG Last Call on draft-ietf-nemo-terminology Thierry Ernst
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Masafumi Watari
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Thierry Ernst
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Thierry Ernst
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Romain KUNTZ
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Chan-Wah Ng
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Masafumi Watari
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Alexandru Petrescu
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Romain KUNTZ
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Thierry Ernst
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Chan-Wah Ng
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Alexandru Petrescu
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Romain KUNTZ
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Chan-Wah Ng
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Romain KUNTZ
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Chan-Wah Ng
- Re: [nemo] WG Last Call on draft-ietf-nemo-termin… Romain KUNTZ