Re: [nemo] Re: multihoming topics

Thierry Ernst <ernst@sfc.wide.ad.jp> Fri, 28 October 2005 01:12 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVInT-0008BI-JD; Thu, 27 Oct 2005 21:12:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVInR-0008BD-QL for nemo@megatron.ietf.org; Thu, 27 Oct 2005 21:12:41 -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 VAA09311 for <nemo@ietf.org>; Thu, 27 Oct 2005 21:12:24 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVJ0s-00026h-3o for nemo@ietf.org; Thu, 27 Oct 2005 21:26:37 -0400
Received: from iseran.local (p8040-ipad28hodogaya.kanagawa.ocn.ne.jp [220.104.102.40]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 2BF9D4CD47 for <nemo@ietf.org>; Fri, 28 Oct 2005 10:12:29 +0900 (JST)
Date: Fri, 28 Oct 2005 10:12:35 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: nemo@ietf.org
Subject: Re: [nemo] Re: multihoming topics
Message-Id: <20051028101235.06bda3e3.ernst@sfc.wide.ad.jp>
In-Reply-To: <4360E491.9010307@motorola.com>
References: <20051021102624.66cd4a10.ernst@sfc.wide.ad.jp> <435F540D.2080105@motorola.com> <1130323515.11457.16.camel@localhost> <20051027104143.00d4dc34.ernst@sfc.wide.ad.jp> <4360E491.9010307@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.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
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

Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:

> >>>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?
> >>>
> >>
> >>In the upcoming -04 [*] of draft-ietf-nemo-multihoming-issues, I
> >have>clearly recommended which issues to be worked on by which WG. 
> >There>are two points of considerations for the NEMO WG.  I would
> >definitely>like to use the slot in Vancouver to clear this two
> >points.
> > 
> > 
> > We also need to clear the other points: we cannot just say, well,
> > this is a task for IPv6, or a task for DNA, or a task for monami6
> > and doing nothing. So,
> > 1. do we think as a WG that the issue is important enough to be
> > solved ?
> 
> Could a NEMO Chair just ask a Monami6 Chair to deal with HAHA within
> its scope, and publicly discuss adoption within the Monami6 group?

I think I could do that ;-)
But, as a NEMO chair, I need to make sure it's a consensus of the NEMO
WG that:
1. Monami6 is the best place, according to the NEMO WG
2. The NEMO WG is not willing to work on the topic in the NEMO WG (for
some reasons, like rechartering, and above all work efficiency and
complementarity)

So, if we can discuss now on NEMO ML if we think a solution like HAHA
must be standardized, and that this should be done in Monami6, may be we
can discuss this point in Vancouver (in the NEMO WG or MONAMI6 or both
depending on the progress of the discussion).

> > 2. if yes, where ?
> > 3. if "where" is identified, we need to rise the discussion in the
> > given WG which will decide if it's solvable in a reasonable amount
> > of time and possibly add a new item.
> 
> Could you please raise the HAHA discussion on Monami6, 
See my comment above.

> I agree with
> that.  In this way probably more slots will be available during the
> NEMO meeting for other-than-HAHA discussions?  HAHA discussions and
> presentations on NEMO happened twice (Washington and San Diego).  If
> it still appears in the Vancouver agenda it should be relatively short
> I believe.

Agree it should be short, in the meeting. So, we have 1 week to drive a
WG consensus on this point on the ML.

> > => but it's our responsability as the NEMO WG members to push for
> > the relevant discussion to happen on the designed WGs.
> 
> Thierry, is this with the NEMO Chair hat on or as a NEMO WG member? 
> If you believe that NEMO responsability is to do something then, as a
> Chair you have the maximum responsibility, please do it.

I would say it's a personal message with a NEMO chair profiled hat, but
I didn't sync with TJ, so this may not be a "NEMO chairs" view.

To answer your question, responsability of chairs is to make this
discussion happen and to drive the conclusions, possibly report the
conclusion to other chairs or IESG. But it's not the chair
responsability to decide. It's the WG's. And, for this, we need the
discussion to be happening on NEMO ML right now. (actually, we need to
discuss the entire process or rechartering NEMO, I guess TJ and me need
to initiate this debate on a separate thread)

> If on the other hand the NEMO WG believes HAHA is local NEMO scope,
> then let's just ask that prior to the meeting: there have already been
> two meetings with HAHA slots.

My personal feeling is that it''s both MIP6 and NEMO scope, and could
address some of the multihoming concerns (though I know motivations come
from a RO point of view), so Monami6 would be a good place. Just my
point of view. I would like to conclude what is the NEMO WG point of
view.

Alex, what's yours ? 

Thierry