Re: [Autoconf] aspects of multi-hop wireless communication

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 19 December 2008 23:06 UTC

Return-Path: <autoconf-bounces@ietf.org>
X-Original-To: autoconf-archive@megatron.ietf.org
Delivered-To: ietfarch-autoconf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B34723A67E5; Fri, 19 Dec 2008 15:06:47 -0800 (PST)
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 33EFE3A67E5 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 15:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 RqKrZRs2HU4e for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 15:06:43 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 2DD393A63EC for <autoconf@ietf.org>; Fri, 19 Dec 2008 15:06:43 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=C5xaaS76+hfceZTZafFTeMiaNNzy6KDnFBhs/ksy0HV2yJxpFE9oq++pISPm585F; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [75.26.137.116] (helo=[10.166.254.43]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1LDoQV-0004Ou-5s; Fri, 19 Dec 2008 18:06:35 -0500
Message-ID: <494C28FA.8030805@earthlink.net>
Date: Fri, 19 Dec 2008 15:06:34 -0800
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <494B8E7C.7000505@gmail.com> <be8c8d780812190504x98496egc37c25b21a799ceb@mail.gmail.com> <494BB75E.4050206@gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D016C3E14@GLKMS2100.GREENLNK.NET> <be8c8d780812190721r7ea9c43aif8aff7c83f44f43@mail.gmail.com> <494BC360.1000109@gmail.com> <be8c8d780812190810y4d891c44tfbec9cce43c3cee9@mail.gmail.com> <494BC927.1020400@gmail.com> <494BCCCC.6050206@earthlink.net> <494BCFEF.2010100@gmail.com> <494BD45A.2090106@earthlink.net> <494BE0D8.4070509@gmail.com> <494BE5A5.4020205@earthlink.net> <494BEA55.3080304@gmail.com> <494BEDD0.9020708@earthlink.net> <494BFF7D.40804@motorola.com> <494C0986.9020404@earthlink.net> <494C1E2F.2010000@gmail.com>
In-Reply-To: <494C1E2F.2010000@gmail.com>
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f5288cd28976ef03680da9e1318dc2948d5350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 75.26.137.116
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] aspects of multi-hop wireless communication
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

Hello Alex,

Alexandru Petrescu wrote:
>
> Well I'm not looking at brute force solutions, but solutions to simpler
> problems.  The advertising you mention - could work without taking into
> considerations the asymmetricity/nontransitivity, if we think it's 
> about Router Advertisements.

This is the crux of the discussion, and what I claim you have
to decide about.  Either you want to restrict the effort to
only links which are unaffected by asymmetry/nontransitivity,
or not.  If you want to make the restriction, and yet the
group is chartered to create solutions for networks that
do not adhere to the restrictions, then I think it means that
you need to charter another group or build support for
rechartering [autoconf].
>
>> But, on the other hand, if a solution that works for 802.{11*,16,...}
>>  is created in a way that is cognizant of the wireless 
>> characteristics as we have described in our Internet Draft, then it 
>> is _more likely_ to work for the other unspecified but presumably 
>> similar media.
>>
>> Which is why we wrote it.
>>
>> Do you disagree with this motivation?
>
> No, I don't disagree with that motivation - supposedly if it works for 
> non-transitive links it will work for transitive links too.  I just 
> look at it as something which may be too much for simpler needs.

This is the same point, reformulated.  You would like to deal
only with simpler networks, and seem to claim that is sufficient.
Perhaps at the cost of truckloads of repeaters for disaster
situations?


Regards,
Charlie P.

_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf