Re: [Autoconf] Call for comments to a new AUTOCONF charter proposal.

Hi all,

I also support a "walk-before-run" approach. To focus on the specific case
where a DHCP server is reachable somewhere in the MANET is somewhat
restrictive, but to me, it makes sense to solve this particular "simple"
case before tackling "hairy" cases.

I want however to point out that an informational RFC documenting the
observed weird characteristics of ad hoc wireless communications would be a
useful companion document for the solution to be designed for AUTOCONF (as
well as for other mechanisms currently being designed in other working
groups, including 6lowpan, ROLL). In that respect, the draft we have worked
on with Charlie is a candidate to consider:

http://ietfreport.isoc.org/all-ids/draft-baccelli-multi-hop-wireless-communication-04.txt

Regards,

Emmanuel

On Tue, Jun 29, 2010 at 6:20 AM, Ryuji Wakikawa <ryuji.wakikawa@gmail.com>wrote:

> Hi all,
>
> Please find a proposal of a new AUTOCONF charter attached below.
> We need to define our new charter carefully to avoid yet-another 5 years
> discussion.
> Jari and chairs agreed to narrow down the charter items and go straight to
> solution space.
>
> This charter is not the final version. Please review it and provide us your
> comments.
> The discussion before the coming IETF is very important to set our charter
> ready soon.
>
> Please give us your feedback before July 9th.
>
> thanks,
> ryuji
>
> Ad-Hoc Network Autoconfiguration (autoconf)
> -------------------------------------------
>
> 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. 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.
>
> 2. 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 on 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 as a part of the first item; it is expected that address
> uniqueness is guaranteed by the central node alone.
>
> Goals and Milestones:
>
> Dec 2010 First working group draft of the address configuration mechanism
> Apr 2011 First working group draft of the prefix configuration mechanism
> Sep 2011 Submission of the address configuration mechanism to the IESG for
> publication as a Proposed Standard
> Sep 2011 Submission of the prefix configuration mechanism to the IESG for
> publication as a Proposed Standard
> _______________________________________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/autoconf
>