[Autoconf] new charter

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Wed, 10 November 2010 07:25 UTC

Return-Path: <ryuji.wakikawa@gmail.com>
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 56E103A6A75 for <autoconf@core3.amsl.com>; Tue, 9 Nov 2010 23:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Zm5BgT8q0BIl for <autoconf@core3.amsl.com>; Tue, 9 Nov 2010 23:25:36 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com []) by core3.amsl.com (Postfix) with ESMTP id 9850D3A6A36 for <autoconf@ietf.org>; Tue, 9 Nov 2010 23:24:45 -0800 (PST)
Received: by ywp6 with SMTP id 6so174467ywp.31 for <autoconf@ietf.org>; Tue, 09 Nov 2010 23:25:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=GTfqByy3TZpeA1yJLMbl56w18GbWI9uuxs7Q2q5MB0s=; b=lNsynk4jRpEQheyfiMY9Prl1Yx2piIT+c0T3TUGixAB8Cbyvf3OxJCGna9iBRiDS8t ETFji4W5t8DCCOOZD1wXz+vMR6m2B+jhJ78Jh8/t2KQaRMlg94JNmq57XLqE6AO/rVWF lp+qcVP2MGoe6oOcRrc1ld6zYtxo42q+gx4cU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=o7JB+PgLM0fOpiRZKUjeaVl9nnirR0QwPLYMosarOMI21msrDkRdEPXzPj7p4CmdcU w59jb2OT3cKA063DCsSDppJy9kzwfi2XEz5JyDhD1Vbd5aVdq+wclRDlxCaLo/PMCScA G8g4plu1VFPO8/aVjE2sR5ZhsNlFI0zUgJvwU=
Received: by with SMTP id v20mr4539338anv.152.1289373911559; Tue, 09 Nov 2010 23:25:11 -0800 (PST)
Received: from dhcp-81f0.meeting.ietf.org (dhcp-81f0.meeting.ietf.org []) by mx.google.com with ESMTPS id w3sm481947anw.25.2010. (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Nov 2010 23:25:10 -0800 (PST)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Nov 2010 15:25:05 +0800
Message-Id: <86A2091E-A92B-4485-A7F8-7A9829A39073@gmail.com>
To: "Autoconf autoconf@ietf.org" <autoconf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
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: Wed, 10 Nov 2010 07:25:38 -0000

Hi all,

Here is the last charter sent to IESG. 


Ad-Hoc Network Autoconfiguration (autoconf)

Current Status: Active

Ryuji Wakikawa <ryuji.wakikawa@gmail.com
Thomas Clausen <T.Clausen@computer.org

Internet Area Directors:
Ralph Droms <rdroms.ietf@gmail.com
Jari Arkko <jari.arkko@piuha.net

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:

RFC 5889 presents one possible IPv6 addressing model for ad hoc
nodes. In this model the ad hoc routers need to configure their
network interface(s) with addresses valid in the ad hoc network, and
may configure additional prefixes for use by attached nodes.

After completing the work on RFC 5889, the main purpose of the
AUTOCONF WG is to standardize how existing IPv6 address configuration
tools can be used for address configuration.

1. DHCPv6 operation over MANET, including:

- A DHCPv6-based mechanism for configuring required interface
 addresses for the routers in the ad hoc network. This mechanism
 is expected to produce addresses with properties outlined in RFC
 5889. This mechanism uses the existing DHCPv6 protocol unchanged,
 and assumes a central node that can allocate addresses on a
 first-come-first-served basis. Other nodes in the ad hoc network
 will relay messages to the central node in order to help a new
 node get an address for itself. This mechanism is only suitable
 for deployments were a central node can be set up. It should be
 noted that many existing deployments employ Internet gateways
 that can act as such a central node as well. Future extensions
 such as central node election may make this mechanism suitable
 for also for stand-alone ad hoc networks.

- A DHCPv6-based mechanism for delegating a prefix(es) to each
 router for use by applications running on the routers themselves,
 or for configuration of attached hosts/networks. This mechanism
 works in a similar manner to the one above, but allocates
 prefixes instead of addresses.

Both mechanisms should be independent from operation of any specific
MANET routing protocol, although may exploit information maintained by
such a routing protocol, if available.

The working group will adapt and/or reuse existing protocols whenever
reasonable and possible. No new duplicate address detection mechanisms
are will be specified; it is expected that address uniqueness is
guaranteed by the central node alone.

2. Analysis of Problem Space for distributed address configuration and
service discovery.

The working group plans to establish design teams for rapidly advancing
towards initial submissions for these two work items.

Goals and Milestones:

- Jan 2011 First working group draft of the "DHCPv6 operation over MANET"
- Jan 2011 First working group draft of the "Analysis of Problem Space"
-Sep 2011 Submission of the "DHCPv6 operation over MANET" to the IESG for publication as BCP
-Sep 2011 Submission of the "Analysis of Problem Space" the IESG for publication as Informational RFC
-Sep 2011 Rechartering or Closing WG