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

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 19 December 2008 16:27 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 6C06128C142; Fri, 19 Dec 2008 08:27:04 -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 6AFBF28C140 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:27:03 -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 n1ZsfbsNvaJQ for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:27:02 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id 7D0D728C12B for <autoconf@ietf.org>; Fri, 19 Dec 2008 08:27:02 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=bvhNi1ydM5PpnBIShPi+mELbC68jjFHWxrVtepdMhZgT1y1josX0+hzC/zYvK9Cf; 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-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1LDiBg-0006xT-I4; Fri, 19 Dec 2008 11:26:52 -0500
Message-ID: <494BCB4A.9090700@earthlink.net>
Date: Fri, 19 Dec 2008 08:26:50 -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>
In-Reply-To: <494BC360.1000109@gmail.com>
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52e1b66689469af32231ed3beabbf03cb2350badd9bab72f9c350badd9bab72f9c
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 have to object!!

Alexandru Petrescu wrote:
> Observation should report the name of the link layer, otherwise a peer
> may think the author logically extends what s/he sees on one link layer
> to another (instead of experiencing same phenomena on each link layer
> individually).

Not really.  We've observed that various link technologies exhibit
some or all of the communication problems under consideration.  I do
not want to write a document specific to a particular link technology.
>
> The scientist orders the frog to jump, who so does.  Then cuts its legs,
> orders it again to jump; the frog obviously can't jump.  Scientist
> deduces the frog can no longer hear.  However, if the order were issued
> to the legs (instead of ears) in the first place then maybe the false
> conclusion could have been avoided.

Interesting story, but not characteristic of the abilities of the people
involved here.  I think we're a bit beyond such knee-jerk reactions
or frog-jumping contests.

>
>> The draft is not saying "there is a need for a solution". The draft 
>> is saying "this is what is often observed". That's it. I think we can
>>  agree on this ;)
>
> I agree one may have observed this behaviour.  I don't agree it is an
> often observed behaviour - I didn't.  I often observed wifi works ok in
> the types of deployments described in the draft (R1,R2,A).

First, you have to be kidding about nontransitivity.  That's obvious.
It even has a famous name -- "hidden terminal" problem.  You can
read about that in a google of places.

Second, take a look at the MIT Roofnet project papers.  That project
was a very strong re-verification of the well-known properties discussed
in the draft, along with numerous implications drawn out for IP routing
protocol behaviors.

I'd be very curious if you could find anyone who has seriously studied
the matter (e.g., refereed publications) to support your position.

Regards,
Charlie P.


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