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

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 19 December 2008 17:05 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 0B4343A6A63; Fri, 19 Dec 2008 09:05:48 -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 4F1F43A6A63 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 09:05:46 -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=[AWL=0.000, 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 kZpM60+LkhpJ for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 09:05:45 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by core3.amsl.com (Postfix) with ESMTP id 6869F3A6A61 for <autoconf@ietf.org>; Fri, 19 Dec 2008 09:05:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ke9ZGcSinMjkzkx2+hEooQ46aSMmVxJKAoUwfbKa6hf+gBinTpxwMv3tzMsCBUjp; 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 [99.51.74.16] (helo=[192.168.1.100]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1LDinB-0002sK-0C; Fri, 19 Dec 2008 12:05:37 -0500
Message-ID: <494BD45A.2090106@earthlink.net>
Date: Fri, 19 Dec 2008 09:05:30 -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>
In-Reply-To: <494BCFEF.2010100@gmail.com>
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52862e399afc47aae8d0c1dd552eb105a3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.74.16
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,

I think we're approaching the point of having
to agree to disagree.

Alexandru Petrescu wrote:
>
> Errr... somehow yes, if I'm permitted.  I simply suggest a link-layer
> solution to a link-layer problem.

IP is a solution that puts together different links.

If you would like to suggest limiting the applicability of IP to
_only_ be allowed to work for links with specific characteristics,
then I think you should be explicit about it.  Perhaps you would
get some support, but I'm guessing it would not arise from the
community of engineers and developers within autoconf or
manet.


>
>> What if I want to join a working ad hoc network of devices using 
>> solutions that have already been developed without bridging?  Why is
>>  this bad?
>
> It's not bad.

Whew!

>
> One would first deploy bridges in networks that are partitioned and in
> need of bridges.  Then any new terminal needing to join could do so,
> without needing to be itself a bridge.
>
> The question is why does one refuse the use of bridges when the network
> is partitioned at link-layer?

That's not a question I have raised, nor do I think that the
answer would be illuminating.  But my answer is that no one
is making any such refusal.

The question is, why can't we use IP as a good tool to solve
problems of connecting together wireless links into a network,
even when bridging solutions are not available?

>
>> What if there is a hurricane and some of the relief workers forgot to
>>  put their wireless bridging devices in their backpacks?
>
> No no... they won't, because they're trained to never forget these
> things at home.  And if they do, then there exist other super-reliefs
> aids sending them trucks full of these devices.

Well, here is where we have stark disagreement.  I am surprised if
you truly suggest that IP should not be engineered to work because
it is an "error condition" to not have truckloads of equipment.


Regards,
Charlie P.


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