Re: [v6tc] v6tc - is there life

Alain Durand <Alain.Durand@Sun.COM> Wed, 17 November 2004 17:50 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 MAA24239; Wed, 17 Nov 2004 12:50:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTyu-0007Yu-OV; Wed, 17 Nov 2004 12:52:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTqM-0002wB-2S; Wed, 17 Nov 2004 12:43:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUToB-0002OO-Nj for v6tc@megatron.ietf.org; Wed, 17 Nov 2004 12:41:34 -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 MAA23530 for <v6tc@ietf.org>; Wed, 17 Nov 2004 12:41:28 -0500 (EST)
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTqR-0007N3-Ko for v6tc@ietf.org; Wed, 17 Nov 2004 12:44:04 -0500
Received: from esunmail ([129.147.156.34]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iAHHfINH012665 for <v6tc@ietf.org>; Wed, 17 Nov 2004 10:41:18 -0700 (MST)
Received: from fe8 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0I7C00AQF3STKW@edgemail1.Central.Sun.COM> for v6tc@ietf.org; Wed, 17 Nov 2004 10:41:17 -0700 (MST)
Received: from [192.168.1.2] ([66.93.39.75]) by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTPSA id <0I7C00AQY3SSY8@mail.sun.net> for v6tc@ietf.org; Wed, 17 Nov 2004 10:41:17 -0700 (MST)
Date: Wed, 17 Nov 2004 09:41:14 -0800
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: [v6tc] v6tc - is there life
In-reply-to: <1100675319.13315.16.camel@essrv103nok15564.ntc.nokia.com>
To: "Soininen Jonne (Nokia-NET/Helsinki)" <jonne.soininen@nokia.com>
Message-id: <E0EA934C-38BF-11D9-9D63-00039376A6AA@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
References: <1100605147.10092.23.camel@essrv103nok15564.ntc.nokia.com> <5DFA372B-37FC-11D9-96B1-00039376A6AA@sun.com> <20041116192132.GN4961@login.ecs.soton.ac.uk> <Pine.LNX.4.61.0411162232140.23785@netcore.fi> <1100675319.13315.16.camel@essrv103nok15564.ntc.nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7BIT
Cc: v6tc@ietf.org
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7BIT

On Nov 16, 2004, at 11:08 PM, Soininen Jonne (Nokia-NET/Helsinki) wrote:

> Hello,
>
> in the interest of time, I would propose that a *simple* goals document
> is written that comprises the requirements from all three requirements
> documents. This is then used as a guideline when designing the 
> protocol.
> Also I'm a bit afraid if we start elaborated requirements/analysis/gap
> analysis/etc. this project will take number of years or we don't even 
> wg
> started as we cannot show that we really need this new protocol.
>
> Basically, I propose that we combine the current requirements to a
> single document that the authors of the current document do together -
> in fairly short time. Parallel to that people would submit their
> protocol proposals as Internet-Drafts.

This is the process I have described in my previous mail, where things
will get done in parallel. However, one should not confuse speed with 
rush,
and there are serious tradeoff to consider in the different avenues in 
the solution
space, and it is worth spending some time (a couple months at most) 
looking at them.
This, of course, should not stop people from submitting their protocol 
proposal
as individual ID.

> Then we just do a quick analysis on the mailing list of the protocols
> vs. the requirements and choose the one that seems to be the best fit 
> as
> a *baseline* document.

There is no such thing as a "quick analysis on the mailing list", you 
know that.

	- Alain.


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