Re: [Autoconf] new charter

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 27 February 2009 20:55 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 BBF4D3A67D0 for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 12:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level:
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.084, 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 44180iOIismA for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 12:55:02 -0800 (PST)
Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3]) by core3.amsl.com (Postfix) with ESMTP id DD5873A67AE for <autoconf@ietf.org>; Fri, 27 Feb 2009 12:55:00 -0800 (PST)
Received: from smtp3-g21.free.fr (localhost [127.0.0.1]) by smtp3-g21.free.fr (Postfix) with ESMTP id 001B881818E; Fri, 27 Feb 2009 21:55:18 +0100 (CET)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp3-g21.free.fr (Postfix) with ESMTP id 6562A8180BA; Fri, 27 Feb 2009 21:55:15 +0100 (CET)
Message-ID: <49A8531A.3020404@gmail.com>
Date: Fri, 27 Feb 2009 21:54:50 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Rex Buddenberg <budden@nps.navy.mil>
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> <7FB7EE0A621BA44B8B69E5F0A09DC76407AD0C70@xmb-rtp-208.amer.cisco.com> <49A84285.5030103@nps.navy.mil>
In-Reply-To: <49A84285.5030103@nps.navy.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 090227-0, 27/02/2009), Outbound message
X-Antivirus-Status: Clean
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: Fri, 27 Feb 2009 20:55:02 -0000

Rex Buddenberg a écrit :
> Stan,
> 
> The difference is not geo footprint (you got that right).  Rather the 
> difference is between LAN (at fringe of network) and WAN (in the 
> interior).  A WAN will always be at least one router away from end systems.
> While we're at it, references to SSIDs is not proper -- that's 
> 802.11-specific.

802.11-specific because that's what many people actually mean.  "Ad-hoc" 
type of SSID is there for same reason.  Many MANET experiments happened 
with 802.11 links.  Wireless LANs, WaveLAN, all are in scope and deserve 
mentioning.  They're the building blocks out of which MANETs can come up.

For LOS satcom communications: if I knew the precise names then I could 
find the manner in which they (or their admins) configure their IPv6 
addresses.

I'm specifically keeping out of MANET 802.15.4 (akin to WPAN) because 
there seems to be an IPv6 ND draft for this link which already has its 
own address autoconfiguration quirks.

For WMAN: I'm aware of 802.16 and it has its own already IETF specified 
means of forming IPv6 addresses.

In this landscape, I'm not sure how could Autoconf practical way of 
forming addresses not mention WiFi.

Alex