[Autoconf] New plan for the Autoconf WG

Jari Arkko <jari.arkko@piuha.net> Tue, 17 February 2009 12:58 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46F093A6974 for <autoconf@core3.amsl.com>; Tue, 17 Feb 2009 04:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.501
X-Spam-Level:
X-Spam-Status: No, score=-2.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFGNwtfmepHl for <autoconf@core3.amsl.com>; Tue, 17 Feb 2009 04:58:24 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 3D9483A68B5 for <autoconf@ietf.org>; Tue, 17 Feb 2009 04:58:24 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 8FF1D19876C; Tue, 17 Feb 2009 14:58:34 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 52C1A1986E2; Tue, 17 Feb 2009 14:58:34 +0200 (EET)
Message-ID: <499AB479.70906@piuha.net>
Date: Tue, 17 Feb 2009 14:58:33 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: autoconf@ietf.org, Shubhranshu <shubranshu@gmail.com>, Thomas Clausen <Thomas.Clausen@polytechnique.fr>, RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Autoconf] New plan for the Autoconf WG
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 12:58:25 -0000

I have tried to figure out what to do with the WG, because we weren't 
getting anywhere. The main problems we have are these:

- after three years even the principles of the architecture document 
were not agreed upon
- danger of attempting to fix the document based on feedback and still 
coming back to the above point
- the state of the other work items in the group is even worse
- chairs having to edit documents
- overall lack of energy and progress

All this is very frustrating, because I know Manet networks can be 
configured and successfully operated, and many people are interested in 
this technology. How can it be so hard to describe this? I don't want to 
assign blame to anyone about this bad situation, except for all of us 
together. We screwed up. But I do want to give the WG another chance, 
with a different setup and goals, and see if we can move forward. If 
not, the WG will be closed in a matter of months. Here's what we are 
going to do:

We will have a new team. Thomas Clausen and Ryuji Wakikawa will be 
chairs of the WG. A new person will become the editor of the main document.

We will have a different scope for the WG. The WG will focus solely on 
one deliverable. We have previously been attempting to describe THE 
architecture; from now on the idea is to write a document that explains 
a practical way of configuring Manet networks. All existing documents 
are essentially abandoned at this point. However, if the WG successfully 
completes the new document you will be able to take on additional work 
items.

The chairs are now searching for a small set of key experts to form a 
design team. The design team will write a first rough draft of the 
document, at which point we can open it up for wider discussion in the 
WG. The plan is that this can be done before San Francisco, where the WG 
is meeting.

Finally, the most important thing: the WG members need to donate their 
cycles for this effort as well. I think the above plan has a good chance 
of success -- please contact the chairs to volunteer as editors, design 
team members, document reviewers, and once we get something out, please 
engage in a timely discussion about the document on the list.

I would also like to thank everyone who has been involved so far, 
Shubhranshu in particular as he is leaving the chair team. While we have 
not succeeded, I know that you all have tried really hard...

Jari Arkko