Re: [Autoconf] new charter

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Mon, 23 February 2009 16:23 UTC

Return-Path: <ryuji.wakikawa@gmail.com>
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 7188628C142 for <autoconf@core3.amsl.com>; Mon, 23 Feb 2009 08:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 VARgg8i-UOBv for <autoconf@core3.amsl.com>; Mon, 23 Feb 2009 08:23:07 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.187]) by core3.amsl.com (Postfix) with ESMTP id 1F1E428C13E for <autoconf@ietf.org>; Mon, 23 Feb 2009 08:23:06 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id 11so1476405tim.25 for <autoconf@ietf.org>; Mon, 23 Feb 2009 08:23:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:subject :references:message-id:content-type:content-transfer-encoding :mime-version:date:cc:x-mailer; bh=w8e00VbASbcdCGUOJIaiNHsEYRlSt1rZRpiGXXOl2CI=; b=ioJUBIj5XapozOS8TtgwenqAPZb7Czo19NRzjp8W8T4kHnw0ggeP7pk3HKK+8sTMSn L0dOAtcRamu1bnGo7CyqCMa10TiC0J0hwekRy8kuyV4CQV99PLZyzey8DdUsEGYzw3uD a5Myj8H70b3qDqaNvkjFLxS2dq8gcjLy0lwes=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc:x-mailer; b=hoFmGMr+f0CZo2eRM7YPd29DaUCPdfkZCImBSMpMISWmt8AZGw8wukCmuZ3FBnXRtg rBmVbB0PUFdqAJcUdka45iFU/+LuOmEBD/Mxm0WH4H/CTRtcpJ0SE1hTXcA8nAOCw0X7 ATbXZrF1V0CnXLYZv2dUJpHabX8aYIZFd7ZCk=
Received: by 10.110.40.8 with SMTP id n8mr6023167tin.41.1235406203909; Mon, 23 Feb 2009 08:23:23 -0800 (PST)
Received: from ?10.0.1.198? (h219-110-221-065.catv02.itscom.jp [219.110.221.65]) by mx.google.com with ESMTPS id d4sm949402tib.28.2009.02.23.08.23.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 08:23:22 -0800 (PST)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
To: autoconf@ietf.org
In-Reply-To: <499F0BA7.90501@piuha.net>
References: <499F0BA7.90501@piuha.net>
Message-Id: <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 24 Feb 2009 01:23:19 +0900
X-Mailer: Apple Mail (2.930.3)
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: Mon, 23 Feb 2009 16:23:08 -0000

Hi all,

It seems the line break is missed from Jari's mail.
so, resend the new charter.

regards,
ryuji





Ad-Hoc Network Autoconfiguration (autoconf)

Last Modified: 2009-02-18

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.




On 2009/02/21, at 4:59, Jari Arkko wrote:

> 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