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

Henrik Levkowetz <henrik@levkowetz.com> Fri, 01 April 2005 01:41 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 UAA04317 for <nemo-archive@lists.ietf.org>; Thu, 31 Mar 2005 20:41:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHB0J-00035X-51; Thu, 31 Mar 2005 20:31:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DH4Fm-0005eJ-5m; Thu, 31 Mar 2005 13:18:50 -0500
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 NAA19256; Thu, 31 Mar 2005 13:18:47 -0500 (EST)
Received: from av5-2-sn1.fre.skanova.net ([81.228.11.112]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DH4Mw-00016m-AM; Thu, 31 Mar 2005 13:26:14 -0500
Received: by av5-2-sn1.fre.skanova.net (Postfix, from userid 502) id 184E837E4F; Thu, 31 Mar 2005 20:18:39 +0200 (CEST)
Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net [81.228.11.164]) by av5-2-sn1.fre.skanova.net (Postfix) with ESMTP id 0811337E42; Thu, 31 Mar 2005 20:18:39 +0200 (CEST)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com [213.64.174.195]) by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id E091537E43; Thu, 31 Mar 2005 20:18:38 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.50) id 1DH4FV-0005IY-Su; Thu, 31 Mar 2005 20:18:35 +0200
Message-ID: <424C3EF8.5050507@levkowetz.com>
Date: Thu, 31 Mar 2005 20:18:32 +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
To: Basavaraj.Patil@nokia.com
References: <456943D540CFC14A8D7138E64843F8535BAD25@daebe101.NOE.Nokia.com>
In-Reply-To: <456943D540CFC14A8D7138E64843F8535BAD25@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: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 31 Mar 2005 20:31:16 -0500
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

Hi,

On 2005-03-30 9:33 pm Basavaraj.Patil@nokia.com said the following:
[...]
> A number of transition scenarios have been identified in IDs: 
> 1. draft-larsson-v6ops-mip-scenarios-01
> 2. draft-tsirtsis-dsmip-problem-03
> While discussion of these scenarios in the larger scope makes sense,
> there is a need to focus on the most critical scenario that would
> address the MIP6 host and router problem. The problem in a single
> sentence can be stated as: "Mobile IPv6 hosts and routers (NEMO) need
> to be able to reach its (IPv6) home agent and services when roaming in
> and attached to an IPv4 access network."
> It makes sense to focus on just this one scenario and solve the
> problem immediately. 

Given that there already exists at least 3 solution drafts in this area:

  draft-thubert-nemo-ipv4-traversal
  draft-soliman-v4v6-mipv6
  draft-wakikawa-nemo-v4tunnel

and Sri clearly indicates that there are requirements which these
don't cover, I think it would be good to have a clear and agreed
upon statement of what to achieve before adopting an approach and
draft.  So I'm not for adopting draft-wakikawa before there is an
agreed upon problem statement.

That said, I'm very much in favour of doing this work; and doing
it by extensions to MIP6 (and MIP4) rather than trying to adapt
any of the other approaches which would mix MIP6 with non-MIP tunnels,
as listed in draft-larsson-v6ops-mip-scenarios-01.

If the decision is to write a problem statement, I'd be willing to
work on such a draft, and I also have a potential co-editor who have
indicated willingness.

> The ID: draft-wakikawa-nemo-v4tunnel-01 solves the problem of a MIPv6 
> mobile node or a NEMO mobile router roaming onto a IPv4 only access
> network in a simple manner. 
> It is intended that the standardization of this solution in the IETFs
> MIP6 and/or NEMO working groups proceed. The working group chairs have
> reviewed and discussed this work item. It has also been presented at
> the MIP6 and NEMO WGs at IETF62. 
> 
> The chairs would like to hear your thoughts in order to see if there
> is consensus to make it a WG document and progress it as a standards
> track RFC. Comments should be sent to both the NEMO and MIP6 WGs. 
> 
> If we have consensus, then the document will be pursued as a dual WG
> item and called draft-ietf-mip6-nemo-v4tunnel-xx.txt 
> 
> Make I-D draft-wakikawa-nemo-v4tunnel a MIP6/NEMO WG ID:
> 	For 		[  ]
> 	Against 	[  ]
> 

	Not currently	[ X ]


Henrik