Re: [v6tc] v6tc - is there life

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 16 November 2004 19:39 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 OAA03711; Tue, 16 Nov 2004 14:39:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU9Cj-0005xP-1Z; Tue, 16 Nov 2004 14:41:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU92n-0004fT-B5; Tue, 16 Nov 2004 14:31:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU8td-0003KZ-0O for v6tc@megatron.ietf.org; Tue, 16 Nov 2004 14:21:45 -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 OAA01793 for <v6tc@ietf.org>; Tue, 16 Nov 2004 14:21:43 -0500 (EST)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU8vr-0005Rk-S6 for v6tc@ietf.org; Tue, 16 Nov 2004 14:24:05 -0500
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131]) by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id iAGJLaGn017774 for <v6tc@ietf.org>; Tue, 16 Nov 2004 19:21:36 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162]) by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id TAA04359 for <v6tc@ietf.org>; Tue, 16 Nov 2004 19:21:32 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.11.6/8.11.6) id iAGJLWJ06099 for v6tc@ietf.org; Tue, 16 Nov 2004 19:21:32 GMT
Date: Tue, 16 Nov 2004 19:21:32 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6tc@ietf.org
Subject: Re: [v6tc] v6tc - is there life
Message-ID: <20041116192132.GN4961@login.ecs.soton.ac.uk>
Mail-Followup-To: v6tc@ietf.org
References: <1100605147.10092.23.camel@essrv103nok15564.ntc.nokia.com> <5DFA372B-37FC-11D9-96B1-00039376A6AA@sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5DFA372B-37FC-11D9-96B1-00039376A6AA@sun.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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: d0bdc596f8dd1c226c458f0b4df27a88

I agree with Alain.

I think the single doc should be split into

Intro
Assumptions
Requirements (all)
Scenarios (including 3gpp)

with the Scenarios stating which requirements are applicable, and whether
the requirements are may/should/must.

We shouldn't repeat the "confusion" of scattering requirements in the
scenarios text.

Tim

On Tue, Nov 16, 2004 at 10:21:43AM -0800, Alain Durand wrote:
> 
> 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

-- 
Tim



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