Re: [v6tc] v6tc draft charter discussion

Pekka Savola <pekkas@netcore.fi> Fri, 12 November 2004 15:57 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 KAA14620; Fri, 12 Nov 2004 10:57:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSdp8-0003GA-5O; Fri, 12 Nov 2004 10:58:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSdf8-0005jB-3y; Fri, 12 Nov 2004 10:48:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSdS2-0002qt-8h for v6tc@megatron.ietf.org; Fri, 12 Nov 2004 10:35:02 -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 KAA13036 for <v6tc@ietf.org>; Fri, 12 Nov 2004 10:34:59 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSdTQ-0002nX-E0 for v6tc@ietf.org; Fri, 12 Nov 2004 10:36:29 -0500
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id iACFYOY22646; Fri, 12 Nov 2004 17:34:26 +0200
Date: Fri, 12 Nov 2004 17:34:24 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Jeroen Massar <jeroen@unfix.org>
Subject: Re: [v6tc] v6tc draft charter discussion
In-Reply-To: <1100272598.22942.29.camel@firenze.zurich.ibm.com>
Message-ID: <Pine.LNX.4.61.0411121727090.21561@netcore.fi>
References: <Pine.LNX.4.61.0411121554090.20003@netcore.fi> <1100272598.22942.29.camel@firenze.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8

On Fri, 12 Nov 2004, Jeroen Massar wrote:
> On Fri, 2004-11-12 at 16:06 +0200, Pekka Savola wrote:
>> Hi,
>>
>> (If folks don't mind, I'll try to ensure that the process is moving
>> forward until WG chair(s) is appointed or someone else steps up..)
>
> Pekka, you are already doing a great job for v6ops, and as this WG is a
> spin-off and mostly related to v6ops it would be IMHO a good idea to
> have the same chairs, so that they can better overview the work.
> Of course, if you have the time etc to do it.

Let's make this straight: I *don't* want to chair this working group 
:).  I'll rather be a technical contributor only.

At this point, I was just trying to make sure that something keeps 
happening with this proposed WG until someone gets the more official 
responsibility to do that..

> <SNIP>
>>   (1) Based on the input documents, gain rough consensus on at most
>>       *one* to-be-standardized approach to fit these goals.
>>
>>   (2) Work on two components of the solution:
>>          a) method to discover the tunnel end-point; and
>>          b) the specification of the tunnel set-up protocol.
>
> psst, you forget:
>
> c) The specification of the tunneling protocol (when it is a new one)

Hmm. Maybe the charter should use a bit more generic language to make 
it possible to include an encapsulation as well, if that's deemed 
necessary.. without having to call it out explicitly, conditionally as 
you suggested.

> also I assume with "set-up" you mean "optional negotiation and
> configuration".

That may mean negotiation or configuration; that is not a requirement 
for the solution.  Basically b) was meant to mean "how a v6-in-v4[udp] 
is set up at the both endpoints of the tunnel".

That might also include specification or guidance on how to get IPv6 
addresses and possibly other information on top of that link.  Again, 
there are multiple ways to achieve that, so the charter wording should
probably be sufficiently generic.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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