[Autoconf] new charter

Jari Arkko <jari.arkko@piuha.net> Fri, 20 February 2009 19:59 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4E4C63A67B4 for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 11:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ik4tigwuAuGE for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 11:59:22 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 4A4C73A6359 for <autoconf@ietf.org>; Fri, 20 Feb 2009 11:59:22 -0800 (PST)
Received: from smtp.piuha.net (localhost []) by smtp.piuha.net (Postfix) with ESMTP id 13F8C198770 for <autoconf@ietf.org>; Fri, 20 Feb 2009 21:59:36 +0200 (EET)
Received: from [] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id C20B11986EF for <autoconf@ietf.org>; Fri, 20 Feb 2009 21:59:35 +0200 (EET)
Message-ID: <499F0BA7.90501@piuha.net>
Date: Fri, 20 Feb 2009 21:59:35 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird (X11/20090105)
MIME-Version: 1.0
To: autoconf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Autoconf] new charter
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: Fri, 20 Feb 2009 19:59:23 -0000

In the light of the new direction for the working group,
we are planning to update the charter as follows. Comments

Jari & the chairs


Ad-Hoc Network Autoconfiguration (autoconf) 
Last Modified: 2009-02-18 
Cuurent Status: Active Working Group 
Additional information is available at tools.ietf.org/wg/autoconf 
Ryuji Wakikawa [ryuji.wakikawa@gmail.com] 
Thomas Clausen [T.Clausen@computer.org] 
Internet Area Director(s): 
Jari Arkko [jari.arkko@piuha.net] 
Mark Townsley [townsley@cisco.com] 
Internet Area Advisor: 
Jari Arkko [jari.arkko@piuha.net] 
Mailing Lists: 
General Discussion: autoconf@ietf.org 
To Subscribe: https://www.ietf.org/mailman/listinfo/autoconf 
Description of Working Group: 
In order to communicate among themselves, ad hoc nodes (refer to RFC 
2501) need to configure their network interface(s) with local addresses 
that are valid within an ad hoc network. Ad hoc nodes may also need to 
configure globally routable addresses, in order to communicate with 
devices on the Internet. From the IP layer perspective, an ad hoc 
network presents itself as a L3 multi-hop network formed over a 
collection of links. 
The main purpose of the AUTOCONF WG is to describe the addressing model 
for ad hoc networks and how nodes in these networks configure their 
addresses. It is required that such models do not cause problems for ad 
hoc-unaware parts of the system, such as standard applications running 
on an ad hoc node or regular Internet nodes attached to the ad hoc 
nodes. This group's effort may include the development of new protocol 
mechanisms, should the existing IP autoconfiguration mechanisms be found 
inadequate. However, the first task of the working group is to describe 
one practical addressing model for ad hoc networks. 
Once this sole work item is completed, the group can be rechartered to 
work on additional issues. 
Goals and Milestones: 
Apr 2009 Submit initial draft on address configuration in ad hoc networks
Sep 2009 Submit address configuration draft to IESG as Informational or 
close WG