Re: [Autoconf] new charter

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 02 March 2009 16:04 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 1ACF33A6452 for <autoconf@core3.amsl.com>; Mon, 2 Mar 2009 08:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.194
X-Spam-Level:
X-Spam-Status: No, score=-2.194 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, 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 WLFJ55drEOcg for <autoconf@core3.amsl.com>; Mon, 2 Mar 2009 08:04:00 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.166.172.107]) by core3.amsl.com (Postfix) with ESMTP id 9BCA13A694A for <autoconf@ietf.org>; Mon, 2 Mar 2009 08:04:00 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-1.2) with ESMTP id n22G4Jps019345; Mon, 2 Mar 2009 17:04:19 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by nephilia.intra.cea.fr (8.13.8/8.13.8) with ESMTP id n22G4JG6031171; Mon, 2 Mar 2009 17:04:19 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id n22G4Isj025332; Mon, 2 Mar 2009 17:04:18 +0100
Message-ID: <49AC0382.3060205@gmail.com>
Date: Mon, 02 Mar 2009 17:04:18 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
References: <499F0BA7.90501@piuha.net> <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com> <49A6D436.7020505@gmail.com><000001c99845$1dc56190$595024b0$@nl> <49A6F125.40400@gmail.com><1235680887.4585.5.camel@localhost><49A7BB89.5040807@gmail.com><003901c998cb$42b71e90$c8255bb0$@nl><49A7E97A.2010503@gmail.com><006801c998fd$06c5bd60$14513820$@nl> <49A8272D.2060400@gmail.com><7FB7EE0A621BA44B8B69E5F0A09DC76407AD0C48@xmb-rtp-208.amer.cisco.com> <49A83172.70105@gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D019FDF3F@GLKMS2100.GREENLNK.NET>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D019FDF3F@GLKMS2100.GREENLNK.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] new charter
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: Mon, 02 Mar 2009 16:04:02 -0000

Dearlove, Christopher (UK) a écrit :
> Alexander Petrescu
>> But I would disagree with a Charter saying we deal with all 
>> wireless links ranging from personal area to sattellite and 
>> everything in between and the generic addressing model is the 
>> following...
> 
> Why?
> 
> I think the onus is on you to provide a good technical reason why 
> this wouldn't work. (I stress technical, as motivationally, Stan 
> Ratliff and others have the motivation, so there is a good reason to 
> do it if we can.)

Not sure which argumentation is expected from me.

In general, wireless links differ largely in the way they form their
IPv6 link-local addresses, depending on whether they're ptp or shared.

An IPv6 addressing scheme designed for WiFi wouldn't work for WMAN
802.16 for example.

Also, some wireless links use some address autoconf mechanisms which
aren't provided by others (e.g. IPv6-over-802154 has a fancy means to
assign an IPv6 address with RR/RC (Router Reg/Router Conf'n)).

Alex