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

Kent Leung <kleung@cisco.com> Sat, 02 April 2005 07:06 UTC

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 CAA11219 for <mip6-web-archive@ietf.org>; Sat, 2 Apr 2005 02:06:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHcpy-0006WH-QP for mip6-web-archive@ietf.org; Sat, 02 Apr 2005 02:14:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHcf6-0004GF-Es; Sat, 02 Apr 2005 02:03:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHcf2-0004EA-Ln; Sat, 02 Apr 2005 02:03:12 -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 CAA07618; Sat, 2 Apr 2005 02:03:10 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHcmU-0006Ow-Kz; Sat, 02 Apr 2005 02:10:55 -0500
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 01 Apr 2005 23:03:01 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j3272qgU010321; Fri, 1 Apr 2005 23:02:53 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn6-582.cisco.com [10.21.122.70]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDO76920; Fri, 1 Apr 2005 23:02:51 -0800 (PST)
Message-Id: <4.3.2.7.2.20050401170850.03088ea0@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 01 Apr 2005 17:13:18 -0800
To: Basavaraj.Patil@nokia.com
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip6] Consensus call on making ID draft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
In-Reply-To: <456943D540CFC14A8D7138E64843F8535BAD50@daebe101.NOE.Nokia. com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: nemo@ietf.org, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

My vote.

#1 Yes.

#2 No. PS is needed.  Then baseline draft can be selected or written up.

Kent

At 09:40 AM 4/1/2005 -0600, Basavaraj.Patil@nokia.com wrote:

>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
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6