Re: [Autoconf] new charter

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 26 February 2009 17:40 UTC

Return-Path: <alexandru.petrescu@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 F1D263A681D for <autoconf@core3.amsl.com>; Thu, 26 Feb 2009 09:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level:
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 3oz0wq8BI38f for <autoconf@core3.amsl.com>; Thu, 26 Feb 2009 09:40:51 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id EEB2A3A68C1 for <autoconf@ietf.org>; Thu, 26 Feb 2009 09:40:50 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-1.2) with ESMTP id n1QHdQQK029876; Thu, 26 Feb 2009 18:39:26 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by nephilia.intra.cea.fr (8.13.8/8.13.8) with ESMTP id n1QHfApY015661; Thu, 26 Feb 2009 18:41:10 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id n1QHfAfn012423; Thu, 26 Feb 2009 18:41:10 +0100
Message-ID: <49A6D436.7020505@gmail.com>
Date: Thu, 26 Feb 2009 18:41:10 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
References: <499F0BA7.90501@piuha.net> <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com>
In-Reply-To: <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
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: Thu, 26 Feb 2009 17:40:52 -0000

Ryuji Wakikawa a écrit :
[gracefully re-formatted]
> Ad-Hoc Network Autoconfiguration (autoconf)
> 
> Last Modified: 2009-02-18
> 
> Additional information is available at tools.ietf.org/wg/autoconf
[snipped]
> 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.

Would a straightforward addressing model along the following lines fit 
the bill?:

         -----  wifi "adhoc1"  ------  wifi "adhoc2"  -----
        |Host1|---------------|Router|---------------|Host2|
         ----- LL1         LL2 ------ LL3        LL4  -----
               G1                                G4



        "adhoc1" and "adhoc2": 802.11 ESSIDs in "ad-hoc" mode.
                               Each is an IPv6 subnet.
        LL1...4: IPv6 link-local addresses.
                 Self-formed according to rfc2464.
        G1, G4:  IPv6 global addresses, for example
                 2001:db8::1/64 and 2001:db8::4/64.
                 Manually assigned, or pre-configured with SNMP
                 or according to stateless autoconf rfc4862.

Alex