IETF Logo Mail Archive

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

Zach Shelby <zach@sensinode.com> Fri, 02 July 2010 08:04 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 9BF773A6863 for <autoconf@core3.amsl.com>; Fri, 2 Jul 2010 01:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.873
X-Spam-Level:
X-Spam-Status: No, score=-2.873 tagged_above=-999 required=5 tests=[AWL=0.726, 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 xnOShtqo2uyK for <autoconf@core3.amsl.com>; Fri, 2 Jul 2010 01:04: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 939D03A6847 for <autoconf@ietf.org>; Fri, 2 Jul 2010 01:04: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 o6284d1B015558 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Jul 2010 11:04:39 +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: <9B013BAF-D5BE-470E-9498-4EF4A1DD2C2F@inf-net.nl>
Date: Fri, 2 Jul 2010 11:04:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9070BBB2-5228-4C9B-8040-2FF25D0824B1@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> <9B013BAF-D5BE-470E-9498-4EF4A1DD2C2F@inf-net.nl>
To: Teco Boot <teco@inf-net.nl>
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: Fri, 02 Jul 2010 08:04:33 -0000

Hi Teco,

On Jul 2, 2010, at 10:36 AM, Teco Boot wrote:

> Zach Shelby:
>> There the approach is to enable autoconfiguration with either DHCP or using a multihop DAD technique. 
> 
> RFC 3315: client SHOULD perform DAD, so I would not say "or".
> I prefer the draft charter text, where DAD is out of scope for now. 

Ahh, I wasn't suggesting that you do that in Autoconf. Just some background info on the solution in 6LoWPAN. There DAD is also not performed on EUI-64 based addresses. Over there the situation is different as there are sometimes 16-bit short MAC addresses to deal with which require either DHCPv6 or random generation with DAD to use.

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.8.7 | Report a Bug | By Email