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

Basavaraj.Patil@nokia.com Fri, 01 April 2005 15:50 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 KAA06546 for <nemo-archive@lists.ietf.org>; Fri, 1 Apr 2005 10:50:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOHv-0002lO-83; Fri, 01 Apr 2005 10:42:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOHt-0002lG-Id; Fri, 01 Apr 2005 10:42:21 -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 KAA05935; Fri, 1 Apr 2005 10:42:19 -0500 (EST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHOPE-0006tZ-1B; Fri, 01 Apr 2005 10:49:57 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j31FgBG00745; Fri, 1 Apr 2005 18:42:11 +0300 (EET DST)
X-Scanned: Fri, 1 Apr 2005 18:41:44 +0300 Nokia Message Protector V1.3.34 2004121512 - RELEASE
Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id j31FfhqP026783; Fri, 1 Apr 2005 18:41:44 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks002.ntc.nokia.com 00UZphws; Fri, 01 Apr 2005 18:41:23 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com [10.241.35.121]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j31FfKM23613; Fri, 1 Apr 2005 18:41:20 +0300 (EET DST)
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 1 Apr 2005 09:40:46 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 01 Apr 2005 09:40:45 -0600
Message-ID: <456943D540CFC14A8D7138E64843F8535BAD50@daebe101.NOE.Nokia.com>
Thread-Topic: [Mip6] Consensus call on making IDdraft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
Thread-Index: AcU2v5I6v6wC3vU1ROuQO8Y2kW4a4QADu+tQ
To: mip6@ietf.org, nemo@ietf.org
X-OriginalArrivalTime: 01 Apr 2005 15:40:46.0000 (UTC) FILETIME=[2BC01300:01C536D1]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: quoted-printable
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: quoted-printable

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.)

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.

-Basavaraj