[Autoconf] Fwd: WG Review: Recharter of Ad-Hoc Network Autoconfiguration (autoconf)

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Tue, 30 November 2010 21:51 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 E2F6A3A6C31 for <autoconf@core3.amsl.com>; Tue, 30 Nov 2010 13:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level:
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AplifW2A97rB for <autoconf@core3.amsl.com>; Tue, 30 Nov 2010 13:51:45 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 9A62C3A6BB4 for <autoconf@ietf.org>; Tue, 30 Nov 2010 13:51:45 -0800 (PST)
Received: by ywh2 with SMTP id 2so3316318ywh.31 for <autoconf@ietf.org>; Tue, 30 Nov 2010 13:52:57 -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:references:to:message-id :mime-version:x-mailer; bh=jvc39jkLIULY2xtKNqtEIbRkqcRa0hPqDS5TAXfOgLM=; b=BfXA9/CM3YVqJLvE/j2Tufyd6Eg23J905jgjbF+8sMksQumNqvIhIyYuLIYsVF8Tcs 2Wus8Glx5AjvcIFWwXfqawa+KDJDryz8gmbGz0ACVzqwPyhQ2jxuLMGDdzBjz7zIvJJP KAyXq4zCDf0CgjYRLakItZxU/89Hs+JuQIiRs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer; b=TNEcHg9mR9kPW3yOor6DLjGSfmwY3L/IkC+5ILy3g+wkwXaAD/uyK/BuYCTj8y5s0S ptrnfGWuzsofqZ5TxErMps7Zy47x5GSuHdp5Hm9B3LJuJkxK/FFbslzxFGNG+ypL12yP iXVJQvAwGx4+2H1sJ4xoUCH7QFqkXtf1rncss=
Received: by 10.150.196.11 with SMTP id t11mr13616350ybf.194.1291153976987; Tue, 30 Nov 2010 13:52:56 -0800 (PST)
Received: from macbookpro-ryuji.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id x39sm7450926ana.6.2010.11.30.13.52.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 30 Nov 2010 13:52:55 -0800 (PST)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Nov 2010 13:52:53 -0800
References: <20101130174257.9343928C0D9@core3.amsl.com>
To: "Autoconf autoconf@ietf.org" <autoconf@ietf.org>
Message-Id: <7E066FA7-AA84-4042-9DE0-D274602EB794@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [Autoconf] Fwd: WG Review: Recharter of Ad-Hoc Network Autoconfiguration (autoconf)
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: Tue, 30 Nov 2010 21:51:47 -0000

Hi All,

Just FYI.
Our new charter is in review. 

As soon as the charter is approved, we need to jump start our activity.

Charlie, Teco, we have two documents about legacy host support. Thanks Teco for the new ID.
http://www.ietf.org/id/draft-boot-autoconf-support4hosts-00.txt
http://www.ietf.org/id/draft-perkins-autoconf-leghost-00.txt

The list of IDs submitted to AUTOCONF WG can be found here. 
https://datatracker.ietf.org/doc/search/?name=autoconf&rfcs=on&activeDrafts=on

The charter said the design team formation, but we expect individual submissions before that.
Specially I would solicit the DHCP operation document.

If you have idea or problem statement for our charter items, please write and submit a draft.

thanks!
ryuji

Begin forwarded message:

> From: IESG Secretary <iesg-secretary@ietf.org>;
> Date: 2010/11/30 09:42:57GMT-08:00
> To: IETF Announcement list <ietf-announce@ietf.org>;
> Cc: ryuji.wakikawa@gmail.com, T.Clausen@computer.org, autoconf@ietf.org
> Subject: WG Review: Recharter of Ad-Hoc Network Autoconfiguration (autoconf) 
> Reply-To: iesg@ietf.org
> 
> A modified charter has been submitted for the Ad-Hoc Network
> Autoconfiguration (autoconf) working group in the Internet Area of the
> IETF.  The IESG has not made any determination as yet.  The modified
> charter is provided below for informational purposes only.  Please send
> your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
> December 7, 2010.
> 
> Ad-Hoc Network Autoconfiguration (autoconf)
> -------------------------------------------
> Last modified: 2010-11-30
> Current Status: Active
> 
> Chairs:
>  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. This analysis is necessary in order to understand
> what type of distributed solution(s) can be standardized. There is
> already quite a lot of material about possible solutions in the
> literature.
> 
> The working group plans to establish design teams for rapidly advancing
> towards initial submissions for these two work items. The group shall
> also work with the 6LOWPAN and ROLL working group to ensure that
> the results from AUTOCONF working group are useful for the larger
> community and do not overlap with work already in progress in these
> other working groups.
> 
> 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
> - Oct 2011 First working group draft of the "Distributed Solution"
> - Jun 2012 Submission of the "Distributed Solution" to the IESG for 
>  publication as an Proposed Standard RFC
> - Jun 2012 Rechartering or Closing WG