[nemo] Re: [Mip6] Consensus call on making ID draft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document

Henrik Levkowetz <henrik@levkowetz.com> Sun, 03 April 2005 13:54 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25109 for <nemo-archive@lists.ietf.org>; Sun, 3 Apr 2005 09:54:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DI5Qi-0002vv-77; Sun, 03 Apr 2005 09:46:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DI5Qf-0002vi-E5; Sun, 03 Apr 2005 09:46:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24669; Sun, 3 Apr 2005 09:46:15 -0400 (EDT)
Received: from av4-1-sn3.vrr.skanova.net ([81.228.9.111]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DI5YP-0006iJ-8W; Sun, 03 Apr 2005 09:54:17 -0400
Received: by av4-1-sn3.vrr.skanova.net (Postfix, from userid 502) id DB66B37E52; Sun, 3 Apr 2005 15:46:04 +0200 (CEST)
Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av4-1-sn3.vrr.skanova.net (Postfix) with ESMTP id CA5B937E42; Sun, 3 Apr 2005 15:46:04 +0200 (CEST)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com [213.64.174.195]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id B8E0D38008; Sun, 3 Apr 2005 15:46:04 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.50) id 1DI5QO-0003ze-Uq; Sun, 03 Apr 2005 15:46:00 +0200
Message-ID: <424FF398.6060006@levkowetz.com>
Date: Sun, 03 Apr 2005 15:46:00 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <456943D540CFC14A8D7138E64843F8535BAD50@daebe101.NOE.Nokia.com>
In-Reply-To: <456943D540CFC14A8D7138E64843F8535BAD50@daebe101.NOE.Nokia.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [nemo] Re: [Mip6] Consensus call on making ID draft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
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
Content-Transfer-Encoding: 7bit

on 2005-04-01 5:40 pm Basavaraj.Patil@nokia.com said the following:
> A couple of clarifications regarding the consensus call:
> 
> 1. The intention is to address the following scenario:
> "MIPv6 and NEMO capable Mobile hosts/routers attaching to an IPv4
> access network need the capability to create a tunnel and be connected
> to their MIP6 home agents."
> This is the scenario that is most applicable for MIP6 deployment.
> There are plenty of other scenarios as well. But they are much more
> of academic interest at this time and hence not really in the scope
> of this discussion. So I would suggst that we do not go off on a tangent
> discussing all these other scenarios.
> 
> Do you agree/disagree that the above scenario is the one that needs
> to be solved ASAP?
> (Note: It does not imply that other scenarios are irrelevant. It simply
> means that this is the scenario worth working on and has the most 
> significant priority or value for MIP6 deployment.)


1. - I agree on what you specify above, but also think this is so wide,
or general in nature if you wish, that it doesn't work as a problem
statement.  

> 2. ID:  draft-wakikawa-nemo-v4tunnel can be used as the baseline. It
> does not imply that we are ruling out draft-soliman-v4v6-mipv6 or any
> other. The IDs can be combined w.r.t the parts that address this scenario.
> Additionally once it is a WG document, what goes into the ID is decided
> by the WG. So lets not get into arguments of what or whose draft is the
> one that should be made the WG document.

2. - I think it's premature to pick a particular document as baseline.
I don't see an agreement on a sufficiently detailed problem statement
currently, so how can we sensibly pick a particular solution?


	Henrik