[nemo] Recharter items: multihoming - HAHA ?

Thierry Ernst <ernst@sfc.wide.ad.jp> Fri, 04 November 2005 08:49 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 1EXxGU-0007CX-3a; Fri, 04 Nov 2005 03:49:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EXxGS-0007CI-Lv for nemo@megatron.ietf.org; Fri, 04 Nov 2005 03:49:36 -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 DAA02688 for <nemo@ietf.org>; Fri, 4 Nov 2005 03:49:13 -0500 (EST)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EXxVM-0006cR-NW for nemo@ietf.org; Fri, 04 Nov 2005 04:05:04 -0500
Received: from iseran.local (jules.nautilus6.org [203.178.138.2]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 9EB324C0E9 for <nemo@ietf.org>; Fri, 4 Nov 2005 17:49:16 +0900 (JST)
Date: Fri, 04 Nov 2005 17:49:19 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: ml-nemo <nemo@ietf.org>
Message-Id: <20051104174919.119a888c.ernst@sfc.wide.ad.jp>
In-Reply-To: <4361FF66.4030107@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> <20051028101235.06bda3e3.ernst@sfc.wide.ad.jp> <4361FF66.4030107@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: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Subject: [nemo] Recharter items: multihoming - HAHA ?
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


I missed this mail.  Comments inline.

On Fri, 28 Oct 2005 12:37:26 +0200
Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:

> Thierry Ernst wrote:
> > 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)
> 
> I personally am not willing to work on HAHA types of protocols, not at
> this time, for reasons of reachartering and work efficiency.
> 
> > 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
> 
> Yes, best starting discuss now; but we've already said that.  Why
> don't we start with authors giving their oppinion about what their
> intentions are with respect to which WG?  Or some technical advantage
> of HAHA for NEMO?
> 
> > (in the NEMO WG or MONAMI6 or both depending on the progress of the 
> > discussion).
> 
> It would be nice if we could avoid same topic presented in several
> meetings.  And it's already been presented here.
> 
> >>> 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.
> 
> IMHO - not in NEMO, not now in NEMO.
> 
> >> 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.
> 
> I said _if_ it still appears...
> 
> >>> => 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)
> 
> Right.
> 
> Until Charter discussion starts, do you want me to send message to
> Monami6 about HAHA?

Well, I don't know. I would say any list is fine, but probably NEMO is
better to start with so that we could come up with a conclusion on this
point in the NEMO WG first. Let me point out the HAHA is documented as
issue 4.4
http://www.mobilenetworks.org/nemo/drafts/draft-ietf-nemo-multihoming-issues-04.html#sec:problem.hasync
in draft-ietf-nemo-multihoming-issues-04.txt


> If I start reviewing the HAHA documents posting on Monami6 do you
> think I raise any chance that other people will review documents I'm
> currently interested in (FMIP, RO, v4 traversal and v4 in general)?

I'm not sure what you mean, here. Particularly, what FMIP has to do
with NEMO ?

Thierry