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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 15:02 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 C84403A6A05; Fri, 19 Dec 2008 07:02:08 -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 9D3523A6A05 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 07:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level:
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.068, 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 3VpSFtKL4ZgT for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 07:02:06 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id CE43C3A6968 for <autoconf@ietf.org>; Fri, 19 Dec 2008 07:02:06 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-11.tower-128.messagelabs.com!1229698917!2865859!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 17692 invoked from network); 19 Dec 2008 15:01:57 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-11.tower-128.messagelabs.com with SMTP; 19 Dec 2008 15:01:57 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id mBJF1pXB025147; Fri, 19 Dec 2008 08:01:51 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id mBJF1pOK017263; Fri, 19 Dec 2008 09:01:51 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id mBJF1o8x017254; Fri, 19 Dec 2008 09:01:51 -0600 (CST)
Message-ID: <494BB75E.4050206@gmail.com>
Date: Fri, 19 Dec 2008 16:01:50 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <494B8E7C.7000505@gmail.com> <be8c8d780812190504x98496egc37c25b21a799ceb@mail.gmail.com>
In-Reply-To: <be8c8d780812190504x98496egc37c25b21a799ceb@mail.gmail.com>
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

Emmanuel Baccelli wrote:

>>> Second, there is no guarantee that two given routers within S can
>>> directly communicate with one another.  In other words, even 
>>> though two routers R1 and R2 can both "hear" packets from router 
>>> A, there is no guarantee that R1 can hear packets from R2, and
>>> there is likewise no guarantee that R2 can hear packets from R1.
>>> Thus, multi-hop ad hoc wireless communications may be
>>> "non-transitive".
>> 
>> It is of paramount important for me to understand what is meant by 
>> "hearing".  Is it MAC level or IP level.
>> 
>> It is very possible for R1 to not receive from R2 (although the 
>> intermediary A receives from both) and this does not represent a
>> problem at all, even less a particular problem of wireless
>> communications.  When R1 doesn't hear from R2 it's because it's too
>> "far" from it; the solution could be A to bridge R1 to R2.  It is
>> the same problem in wired communication.
> 
> Actually this is out of the question because, as stated in the
> previous paragraph in the draft, there is no guarantee that A can
> hear either R1, or R2... (all we know is that R1 and R2 can hear A).

So this second issue is tightly bound to the first, it seems.

I agree a radio-through-air system may behave that way.

I think some solutions exist at PHY and MAC layers in the case of 802.11.

I doubt a solution is necessary at IP layer.

Maybe there's a need to discuss this radio-through-air problem more in 
terms of what IP could do for it.

Alex


______________________________________________________________________
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