IETF Logo Mail Archive

Re: [Autoconf] Next steps?

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 23 March 2010 21:15 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 443C33A6BD1 for <autoconf@core3.amsl.com>; Tue, 23 Mar 2010 14:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.481
X-Spam-Level: *
X-Spam-Status: No, score=1.481 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 B29P0Fe8DUey for <autoconf@core3.amsl.com>; Tue, 23 Mar 2010 14:15:06 -0700 (PDT)
Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by core3.amsl.com (Postfix) with ESMTP id 046743A6B0C for <autoconf@ietf.org>; Tue, 23 Mar 2010 14:14:58 -0700 (PDT)
Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id D69ABD480F3; Tue, 23 Mar 2010 22:15:13 +0100 (CET)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp5-g21.free.fr (Postfix) with ESMTP id A950FD4803C; Tue, 23 Mar 2010 22:15:10 +0100 (CET)
Message-ID: <4BA92F5C.80201@gmail.com>
Date: Tue, 23 Mar 2010 22:15:08 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <1266925311.4036.71.camel@acorde.it.uc3m.es> <4B882EB5.4070605@gmail.com> <4BA7E52C.9050403@piuha.net>
In-Reply-To: <4BA7E52C.9050403@piuha.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 100323-1, 23/03/2010), Outbound message
X-Antivirus-Status: Clean
Cc: "autoconf@ietf.org" <autoconf@ietf.org>
Subject: Re: [Autoconf] Next steps?
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: Tue, 23 Mar 2010 21:15:09 -0000

Le 22/03/2010 22:46, Jari Arkko a écrit :
> Alex,
>
>> In the solution space I am interested in the use of link-local
>> addresses and of multicast link-scoped addresses.
>>
>> I hope these are not forbidden by the IPv6 addressing architecture
>> document, which seems to be sent to the IESG now.
>
> Actually, I *do* want to see the working group's solutions build on
> top of the address model that we have just completed. And it does
> discourage the use of link-local addresses. Lets not return to that
> discussion, I would be more interested in discussing what gaps we
> have the technology and what possible solutions we might need to do.

WEll yes let's discuss gaps in technology but for which deployment?
Anything simply labelled "MANET" is way too vague to understand for me.

-personal area networks for commercial PDAs and phones?
-vehicular settings?
-mobile Client to Access Point configuration? (bonjour)
-WiFi AP fixed on street poles?
-any other?

I am throwing this list just like that.  Maybe identifying deployments
is not important at all.  I really don't know what should we discuss
about technology gaps.

Alex

>
> Jari
>
>

v2.8.7 | Report a Bug | By Email