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

Zach Shelby <zach@sensinode.com> Wed, 30 June 2010 08:09 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 DB1273A63EC for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 01:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.694
X-Spam-Level:
X-Spam-Status: No, score=-2.694 tagged_above=-999 required=5 tests=[AWL=0.906, BAYES_00=-2.599, 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 Fhp5M3WufRLd for <autoconf@core3.amsl.com>; Wed, 30 Jun 2010 01:09:10 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 64E5D3A686E for <autoconf@ietf.org>; Wed, 30 Jun 2010 01:09:09 -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 o5U89GBg021681 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jun 2010 11:09:16 +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: <4C2AF636.1060007@gmail.com>
Date: Wed, 30 Jun 2010 11:09:18 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC71E277-F76A-4E9D-B704-1F9444316E25@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> <4C2AF636.1060007@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: autoconf@ietf.org
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 08:09:12 -0000

On Jun 30, 2010, at 10:45 AM, Alexandru Petrescu wrote:

>> +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).

Exactly, which is why that work is just an example of optimizing ND for such an environment. Obviously in some MANETs you also have prefix delegation to worry about, which we don't have in a LoWPAN. 

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