Re: [v6tc] v6tc - is there life

Alain Durand <Alain.Durand@Sun.COM> Tue, 16 November 2004 18:45 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 NAA28693; Tue, 16 Nov 2004 13:45:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU8N0-0004cj-JS; Tue, 16 Nov 2004 13:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU85H-0003AJ-7u; Tue, 16 Nov 2004 13:29:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU7xn-0001j5-Nk for v6tc@megatron.ietf.org; Tue, 16 Nov 2004 13:21:59 -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 NAA26751 for <v6tc@ietf.org>; Tue, 16 Nov 2004 13:21:57 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7zy-00044a-L8 for v6tc@ietf.org; Tue, 16 Nov 2004 13:24:20 -0500
Received: from esunmail ([129.147.156.34]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id iAGILnui026614 for <v6tc@ietf.org>; Tue, 16 Nov 2004 11:21:49 -0700 (MST)
Received: from xpa-fe2 (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 <0I7A00MG7B0CT1@edgemail1.Central.Sun.COM> for v6tc@ietf.org; Tue, 16 Nov 2004 11:21:49 -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 <0I7A00H8BB08H4@mail.sun.net> for v6tc@ietf.org; Tue, 16 Nov 2004 11:21:45 -0700 (MST)
Date: Tue, 16 Nov 2004 10:21:43 -0800
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: [v6tc] v6tc - is there life
In-reply-to: <1100605147.10092.23.camel@essrv103nok15564.ntc.nokia.com>
To: "Soininen Jonne (Nokia-NET/Helsinki)" <jonne.soininen@nokia.com>
Message-id: <5DFA372B-37FC-11D9-96B1-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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7BIT

On Nov 16, 2004, at 3:39 AM, Soininen Jonne (Nokia-NET/Helsinki) wrote:

> 1) Should we still work on the requirements or do the current three
> requirements shape the goal enough?
> (draft-ietf-v6ops-assisted-tunneling-requirements,
> draft-nielsen-v6ops-3GPP-zeroconf-goals,
> draft-suryanarayanan-v6ops-zeroconf-reqs)

I think those 3 documents have served their purpose as is, that is, 
explain
the need for the new wg, so no further work is needed on each one of 
them separately.
However, the new wg would benefit from a combined goals document,
as the above docs shared a lot in common and as we discovered the 
differences
are in the access media properties.
We should get something soon, before the end of the calendar year,
but this should not stop the work in the solution space to start.

Parallel to that, the work on the tunnel-end-point discovery goals 
should advance and integrate
the latest proposal so we can have a meaningful discussion on how to 
implement it.

> 2) Do people have proposals for solutions?

Yes, there are already severals. However, before jumping the gun and 
pushing one particular
solution, what we need to do is look at the different general avenues 
and understand
the tradeoffs in the solution space. As Pekka mentioned, some people 
have started analysis work
(follow up to what we did in San Diego) and preliminary results should 
be published
as individual submission before January 05.

	- Alain.


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