Re: [Autoconf] new charter

Jari Arkko <jari.arkko@piuha.net> Fri, 20 February 2009 20:56 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 264E43A6988 for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 12:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048, 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 AcCKExywh1V2 for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 12:56:56 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id B8FDF3A63D3 for <autoconf@ietf.org>; Fri, 20 Feb 2009 12:56:55 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 169B119876C; Fri, 20 Feb 2009 22:57:09 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id B65B01986EE; Fri, 20 Feb 2009 22:57:08 +0200 (EET)
Message-ID: <499F1924.8090801@piuha.net>
Date: Fri, 20 Feb 2009 22:57:08 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: cjbc@it.uc3m.es
References: <499F0BA7.90501@piuha.net> <1235161786.4633.73.camel@localhost>
In-Reply-To: <1235161786.4633.73.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: autoconf@ietf.org
Subject: Re: [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 20:56:57 -0000

I intentionally made the new charter not say anything about that. My 
belief is that the type of architecture document that we are looking at 
can easily talk about both IPv4 and IPv6.

Jari

Carlos Jesús Bernardos Cano wrote:
> Hi Jari,
>
> 	One quick comment (I haven't read the proposed text in detail yet): are
> we considering IPv6 only? IPv6 and IPv4? IPv4 only? previous charter
> focused only on IPv6 solutions...
>
> 	Kind Regards,
>
> 	Carlos
>
> El vie, 20-02-2009 a las 21:59 +0200, Jari Arkko escribió:
>   
>> In the light of the new direction for the working group,
>> we are planning to update the charter as follows. Comments
>> appreciated.
>>
>> 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 
>>  
>> Chair(s): 
>> 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 
>> Archive: 
>> http://www.ietf.org/mail-archive/web/autoconf/current/maillist.html 
>>
>> 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
>>
>> _______________________________________________
>> Autoconf mailing list
>> Autoconf@ietf.org
>> https://www.ietf.org/mailman/listinfo/autoconf
>>