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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 30 June 2010 07:45 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 BA9A03A6C00 for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 00:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.618
X-Spam-Level:
X-Spam-Status: No, score=-0.618 tagged_above=-999 required=5 tests=[AWL=-0.228, BAYES_20=-0.74, 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 JfOHoDQWbO-k for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 00:45:51 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id AF5663A6A83 for <autoconf@ietf.org>; Wed, 30 Jun 2010 00:45:50 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o5U7jxv7011528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 Jun 2010 09:45:59 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o5U7jx0s007123; Wed, 30 Jun 2010 09:45:59 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o5U7jwFx006142; Wed, 30 Jun 2010 09:45:59 +0200
Message-ID: <4C2AF636.1060007@gmail.com>
Date: Wed, 30 Jun 2010 09:45:58 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: autoconf@ietf.org
References: <BFD8FF22-FD36-436E-9985-7BFA2E234081@gmail.com> <201006290803.34192.henning.rogge@fkie.fraunhofer.de> <ABE739C5ADAC9A41ACCC72DF366B719D0333F14C@GLKMS2100.GREENLNK.NET> <4C2A723E.3020806@piuha.net> <DF7E20A3-2F4C-4F37-A3D5-9C17C5B22856@sensinode.com>
In-Reply-To: <DF7E20A3-2F4C-4F37-A3D5-9C17C5B22856@sensinode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [Autoconf] Call for comments to a new AUTOCONF charter proposal.
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, 30 Jun 2010 07:45:51 -0000

Le 30/06/2010 08:41, Zach Shelby a écrit :
>
> On Jun 30, 2010, at 1:22 AM, Jari Arkko wrote:
>
>> I do get that a solution with a central node (and perhaps any
>> solution with DHCP) does not solve all needs. Would you be happier
>> if the charter had four work items:
>>
>> 1. Design space survey (Informational) 2. The simple solution (such
>> as DHCP) (PS) 3. Limitations of the simple solution
>> (Informational) 4. Recharter for work on the more general solution
>
>
> +1. I support this approach. As Ryuji mentioned, we are almost
> finished with work in 6LoWPAN on optimizing ND so that it works in
> such a low-power and lossy network.

Well I need RA-based prefix exchanges and route updates not only on 
low-power and lossy networks.  I don't consider 6LoWPAN neither RoLL 
appropriate for RA-based prefix exchanges. (not to paint them in a 
corner but their applicability domain is not WiFi neither Mobile Router).

Alex

  There the approach is to enable
> autoconfiguration with either DHCP or using a multihop DAD technique.
> Autoconf might be able to extend or reference that work in item 2.
> above and consider both DHCP and ND as parts of a simple solution.
> For now I think it is enough to say in the charter that DHCP and ND
> mechanisms will be applied (with minimal extensions) for the simple
> solution.
>
> Zach
>