Re: multihoming topics (was: [nemo] Preparing NEMO Slot for Vancouver)

Thierry Ernst <ernst@sfc.wide.ad.jp> Wed, 26 October 2005 10:31 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiZS-0005fK-HP; Wed, 26 Oct 2005 06:31:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiZQ-0005fF-VK for nemo@megatron.ietf.org; Wed, 26 Oct 2005 06:31:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10223 for <nemo@ietf.org>; Wed, 26 Oct 2005 06:31:33 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUimZ-0004dL-Tr for nemo@ietf.org; Wed, 26 Oct 2005 06:45:24 -0400
Received: from iseran.local (jules.nautilus6.org [203.178.138.2]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 5FC494C7C0 for <nemo@ietf.org>; Wed, 26 Oct 2005 19:31:39 +0900 (JST)
Date: Wed, 26 Oct 2005 19:31:44 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: nemo@ietf.org
Subject: Re: multihoming topics (was: [nemo] Preparing NEMO Slot for Vancouver)
Message-Id: <20051026193144.6dc78e8b.ernst@sfc.wide.ad.jp>
In-Reply-To: <435F540D.2080105@motorola.com>
References: <20051021102624.66cd4a10.ernst@sfc.wide.ad.jp> <435F540D.2080105@motorola.com>
Organization: Keio University
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
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


Thanks Alex for rising this up !

> > The NEMO WG will meet at Vancouver for a 2 hours session.
> > 
> > In Paris, we mentioned about rechartering the WG, so I think this
> > will be one of the important discussion: how are we 
> > 
> > So, the main topics will be:
> > 1. status of WG documents
> > 2. RO PB Statement
> > 3. RO issues we should work on, and where
> > 4. Multihoming: what issues we should work on, and where
> > 5. Rechartering (mainly based on point 3 & 4)
> 
> Thierry, just a question.  I agree with most points in the agenda.
 
> Isn't the 4th topic dealt with in Monami6 WG?  I mean, we already had
> extensive discussion slots at several NEMO meetings about what are the
> multi-homing issues and where should they be worked on.  And then
> there was Monami6 BoF, and now Monami6 is created so they should
> logically be worked there, no?

We still didn't come to a conclusion about which of the issues should be
dealt with in each WG. The corresponding text (i.e. suggestion by draft
authors) has been clarified in the new version (not announced yet,
but it's available from 
http://www.nautilus6.org/doc/drafts/draft-ietf-nemo-multihoming-issues-04.txt
http://www.nautilus6.org/doc/drafts/draft-ietf-nemo-multihoming-issues-04.html
See Figure 10: Matrix of NEMO Multihoming Issues 
)

We need this discussion to happen now before the meeting in order to
conclude in Vancouver. 

So, Monami6 has not been chartered to solve these issues, besides the
multiple CoA registration. This means that most of the issues are
WG-orphan. If the issues are important to be solved, and can be solved
in a reasonable way, we should discuss which WG should take care of
them, and go in these WGs to make them consider these new topics. We do
think that some should be dealt with Monami6.

Can we start the debate on this so that ChanWah doesn't have the
impression to repeat himself in Vancouver ?

Thanks,
Thierry.