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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 16:46 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 7567A3A696C; Fri, 19 Dec 2008 08:46:51 -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 85C2D3A696C for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level:
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aO+YPbEOviQV for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:46:49 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id B787A3A68EC for <autoconf@ietf.org>; Fri, 19 Dec 2008 08:46:49 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-128.messagelabs.com!1229705201!3767378!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 32728 invoked from network); 19 Dec 2008 16:46:41 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-7.tower-128.messagelabs.com with SMTP; 19 Dec 2008 16:46:41 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id mBJGkf9k022879; Fri, 19 Dec 2008 09:46:41 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id mBJGkfDR020592; Fri, 19 Dec 2008 10:46:41 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id mBJGkeN6020581; Fri, 19 Dec 2008 10:46:40 -0600 (CST)
Message-ID: <494BCFEF.2010100@gmail.com>
Date: Fri, 19 Dec 2008 17:46:39 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
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>
In-Reply-To: <494BCCCC.6050206@earthlink.net>
X-Antivirus: avast! (VPS 081218-0, 18/12/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
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

Charles, hi, thanks for the reply,

Charles E. Perkins wrote:
> 
> Hello again Alex,
> 
> Alexandru Petrescu wrote:
>> 
>> All I could do, and I already offered to do, is to describe the 
>> A-B-C wifi deployment which works ok with MAC bridging.
> 
> Do you mean to say that we should stop engineering solutions to ad 
> hoc network problems, and instead all deployments must install MAC 
> bridging hardware?

Errr... somehow yes, if I'm permitted.  I simply suggest a link-layer
solution to a link-layer problem.

> 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.

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?

> 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.

Alex

> 
> Regards, Charlie P.
> 
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf