IETF Logo Mail Archive

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

Zach Shelby <zach@sensinode.com> Wed, 30 June 2010 06:41 UTC

Return-Path: <zach@sensinode.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 9B3CD3A6A8B for <autoconf@core3.amsl.com>; Tue, 29 Jun 2010 23:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.514
X-Spam-Level:
X-Spam-Status: No, score=-1.514 tagged_above=-999 required=5 tests=[AWL=-0.329, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
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 ZqS3XE9a0k5Z for <autoconf@core3.amsl.com>; Tue, 29 Jun 2010 23:41:32 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id E7C093A6835 for <autoconf@ietf.org>; Tue, 29 Jun 2010 23:41:31 -0700 (PDT)
Received: from [62.145.172.52] ([62.145.172.52]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id o5U6fFEH008826 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jun 2010 09:41:15 +0300
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <4C2A723E.3020806@piuha.net>
Date: Wed, 30 Jun 2010 09:41:17 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1081)
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 06:41:33 -0000

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.

Zach

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297

v2.23.0 | Report a Bug | By Email