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

Ulrich Herberg <ulrich@herberg.name> Wed, 30 June 2010 07:49 UTC

Return-Path: <ulrich@herberg.name>
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 C1ADF3A6AC1 for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 00:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.305
X-Spam-Level:
X-Spam-Status: No, score=-0.305 tagged_above=-999 required=5 tests=[AWL=-0.187, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622]
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 Am4foQodkKHa for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 00:49:30 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id B868F3A6A1E for <autoconf@ietf.org>; Wed, 30 Jun 2010 00:49:29 -0700 (PDT)
Received: by bwz7 with SMTP id 7so259862bwz.31 for <autoconf@ietf.org>; Wed, 30 Jun 2010 00:49:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.68.8 with SMTP id t8mr1700447bki.72.1277884176728; Wed, 30 Jun 2010 00:49:36 -0700 (PDT)
Received: by 10.204.68.13 with HTTP; Wed, 30 Jun 2010 00:49:36 -0700 (PDT)
In-Reply-To: <DF7E20A3-2F4C-4F37-A3D5-9C17C5B22856@sensinode.com>
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>
Date: Wed, 30 Jun 2010 09:49:36 +0200
Message-ID: <AANLkTilkYI94oC3exxZyLxyesHLI0gn5RJgfXnuRVAc8@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: Zach Shelby <zach@sensinode.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: autoconf@ietf.org, "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
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:49:30 -0000

Hi,

On Wed, Jun 30, 2010 at 8:41 AM, Zach Shelby <zach@sensinode.com> wrote:
>
> 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. 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.


I also agree with Jari's proposition. While I personally think that we
eventually have to work on a more general solution, it may be a good
start rechartering for a simple solution now. Considering how much
time has passed for the address architecture document, we should aim
to progress in small, doable steps rather than aiming for a
"all-in-one" solution right now. As we already have a few ideas that
could be integrated (e.g. Teco's and Zach's documents), the time frame
seems to be doable for me.

I will still continue do work on my distributed approach in the
meantime, though, so that it progresses and could be considered once
we will recharter again.

Ulrich