Re: [nemo] WG Last Call on draft-ietf-nemo-terminology

Chan-Wah Ng <chanwah.ng@sg.panasonic.com> Mon, 21 November 2005 03:12 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 1Ee26Y-0004an-KI; Sun, 20 Nov 2005 22:12:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ee26X-0004ai-MD for nemo@megatron.ietf.org; Sun, 20 Nov 2005 22:12: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 WAA28809 for <nemo@ietf.org>; Sun, 20 Nov 2005 22:11:52 -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 1Ee2Ot-0004HU-I4 for nemo@ietf.org; Sun, 20 Nov 2005 22:31:29 -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 jAL3BqtN005739; Mon, 21 Nov 2005 12:11:52 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id jAL3BsZ23216; Mon, 21 Nov 2005 12:11:54 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/whitesox) with ESMTP id jAL3Bnu26927; Mon, 21 Nov 2005 12:11:49 +0900 (JST)
Received: from bach.psl.com.sg ([10.81.113.99]) by pslexc01.psl.local with Microsoft SMTPSVC(6.0.3790.1830); Mon, 21 Nov 2005 11:08:45 +0800
Received: by bach.psl.com.sg (Postfix, from userid 1000) id 193E1D54FC; Mon, 21 Nov 2005 11:16:31 +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: <43813545.9070804@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> <1132280807.4927.14.camel@localhost> <43813545.9070804@sfc.wide.ad.jp>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Mon, 21 Nov 2005 11:16:31 +0800
Message-Id: <1132542991.31961.14.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
X-OriginalArrivalTime: 21 Nov 2005 03:08:45.0426 (UTC) FILETIME=[E2745D20:01C5EE48]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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 Mon, 2005-11-21 at 11:47 +0900, Romain KUNTZ wrote:
> Hello Chan-Wah,
> 
> Chan-Wah Ng wrote:
> >>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.
> > 
> > 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.
> 
> I agree. So do you see other case than (n,1,1) with the following topology:
> 
> 
>      |    |             |      |
>     MR1  MR2           MR1    MR2
>      |    |      ->     |      |
>    ----------         -----  -----
> 
> (ie multiple MRs attached to the same mobile subnet on their ingress 
> interface, registering the same prefix to the same HA)
> 
> where split NEMO is a problem?
> 

No, I do not at this moment.  Although strictly speaking , all
(n,>=1,>=1) networks will face the same problem, but these can always be
decomposed to multiple (n,1,1)s.

Hence, I would modify the definition of split-NEMO to:

        Split-NEMO refers to case where a mobile network that has
        multiple mobile routers handling the same MNP (or MNPs) becoming
        two or more independent mobile networks.

One can go on to be more specific, such as adding "where the
aforementioned group of mobile routers handling the same MNP(s) are no
longer all residing in the same mobile network".  That may seems messy,
but is more accurate.

The above definition avoids the use of mobile subnet, in case someone in
the future, against all odds, come up with a split-NEMO configuration
that has a LFR in between, the definition still fits :).

/rgds
/cwng