Re: [Autoconf] new charter

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Fri, 20 February 2009 20:29 UTC

Return-Path: <cjbc@it.uc3m.es>
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 B4BFE3A6959 for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 12:29:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.303
X-Spam-Level:
X-Spam-Status: No, score=-4.303 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 hBux2AcIX+jD for <autoconf@core3.amsl.com>; Fri, 20 Feb 2009 12:29:34 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 5AC573A66B4 for <autoconf@ietf.org>; Fri, 20 Feb 2009 12:29:33 -0800 (PST)
Received: from [163.117.139.72] (acorde.it.uc3m.es [163.117.139.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id 328C4BA00EA; Fri, 20 Feb 2009 21:29:47 +0100 (CET)
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <499F0BA7.90501@piuha.net>
References: <499F0BA7.90501@piuha.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ANEy28oMZR/4pQNHN1C8"
Organization: Universidad Carlos III de Madrid
Date: Fri, 20 Feb 2009 21:29:46 +0100
Message-Id: <1235161786.4633.73.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16476.000
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] new charter
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: cjbc@it.uc3m.es
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:29:35 -0000

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
-- 
 Carlos Jesús Bernardos Cano     http://www.netcoms.net
 GPG FP: D29B 0A6A 639A A561 93CA  4D55 35DC BA4D D170 4F67
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  WEEDEV 2009: 2nd Workshop on Experimental Evaluation and
        Deployment Experiences on Vehicular networks
                  http://www.weedev.org/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++