RE: [Mip6] Consensus call on making ID draft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
Sri Gundavelli <sgundave@cisco.com> Fri, 01 April 2005 17:47 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 MAA20515 for <mip6-web-archive@ietf.org>; Fri, 1 Apr 2005 12:47:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHQMn-0004G5-Rl for mip6-web-archive@ietf.org; Fri, 01 Apr 2005 12:55:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHQCf-0002vC-Jq; Fri, 01 Apr 2005 12:45:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHQCc-0002tO-UD; Fri, 01 Apr 2005 12:45:03 -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 MAA20346; Fri, 1 Apr 2005 12:45:00 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHQJy-00049y-Rc; Fri, 01 Apr 2005 12:52:40 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-1.cisco.com with ESMTP; 01 Apr 2005 09:44:52 -0800
X-IronPort-AV: i="3.91,141,1110182400"; d="scan'208"; a="625079417:sNHT560487066"
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j31HiogF025597; Fri, 1 Apr 2005 09:44:50 -0800 (PST)
Date: Fri, 01 Apr 2005 09:44:50 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Basavaraj.Patil@nokia.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>
Message-ID: <Pine.GSO.4.58.0504010939190.17502@irp-view7.cisco.com>
References: <456943D540CFC14A8D7138E64843F8535BAD50@daebe101.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Raj, We do want to solve the IPv4 traversal, however NAT/PAT traversal support is the critical requirement for that. Based on our Mobile IPv4 deployment experience, we have seen lot of interest for NAT Traversal and MIPv4 WG standardised on RFC 3519. The same requirement is central to the problem statement here. On your question, if we can adopt draft-wakikawa-nemo-v4tunnel as the basis for the solution, my answer to that is "NO". There are other solution documents out there and we need to review them as well. Regards. Sri On Fri, 1 Apr 2005 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 > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
- [Mip6] Consensus call on making ID draft-wakikawa… Basavaraj.Patil
- Re: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- Re: [Mip6] Consensus call on making ID draft-waki… Vijay Devarapalli
- Re: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Carl Williams
- Re: [Mip6] Consensus call on making ID draft-waki… Pekka Savola
- Re: [Mip6] Consensus call on making ID draft-waki… Vijay Devarapalli
- Re: [Mip6] Consensus call on making ID draft-waki… Henrik Levkowetz
- Re: [Mip6] Consensus call on making ID draft-waki… James Kempf
- Re: [Mip6] Consensus call on making ID draft-waki… Samita Chakrabarti
- Re: [Mip6] Consensus call on making ID draft-waki… Vijay Devarapalli
- Re: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Alexandru Petrescu
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Alexandru Petrescu
- Re: [Mip6] Consensus call on making ID draft-waki… Vijay Devarapalli
- Re: [Mip6] Consensus call on making ID draft-waki… Keiichi SHIMA
- Re: [Mip6] Consensus call on making ID draft-waki… Pekka Savola
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pascal Thubert (pthubert)
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pascal Thubert (pthubert)
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pekka Savola
- RE: [Mip6] Consensus call on making ID draft-waki… Basavaraj.Patil
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pascal Thubert (pthubert)
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pascal Thubert (pthubert)
- Re: [nemo] RE: [Mip6] Consensus call on making ID… Alexandru Petrescu
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Sri Gundavelli
- RE: [Mip6] Consensus call on making ID draft-waki… Alpesh
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pekka Savola
- RE: [Mip6] Consensus call on making ID draft-waki… Alpesh
- RE: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Sri Gundavelli
- RE: [Mip6] Consensus call on making ID draft-waki… Kent Leung
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Henrik Levkowetz
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Pekka Savola
- RE: [nemo] Re: [Mip6] Consensus call on making ID… Pascal Thubert (pthubert)
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Ryuji Wakikawa
- Re: [Mip6] Consensus call on making ID draft-waki… Sri Gundavelli
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Alexandru Petrescu
- Re: [nemo] Re: [Mip6] Consensus call on making ID… Pekka Savola
- Re: [Mip6] Consensus call on making ID draft-waki… Ryuji Wakikawa