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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 18:39 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 467113A6A63; Fri, 19 Dec 2008 10:39:35 -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 114203A6A63 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 10:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level:
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.057, 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 NHVewz8LtAlI for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 10:39:33 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id 374AF3A6A24 for <autoconf@ietf.org>; Fri, 19 Dec 2008 10:39:33 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-128.messagelabs.com!1229711964!3772878!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 14308 invoked from network); 19 Dec 2008 18:39:25 -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 18:39:25 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id mBJIdJT2020085; Fri, 19 Dec 2008 11:39:19 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id mBJIdJBa014650; Fri, 19 Dec 2008 12:39:19 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.75]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id mBJIdHCU014628; Fri, 19 Dec 2008 12:39:18 -0600 (CST)
Message-ID: <494BEA55.3080304@gmail.com>
Date: Fri, 19 Dec 2008 19:39:17 +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> <494BCFEF.2010100@gmail.com> <494BD45A.2090106@earthlink.net> <494BE0D8.4070509@gmail.com> <494BE5A5.4020205@earthlink.net>
In-Reply-To: <494BE5A5.4020205@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 E. Perkins wrote:
> 
> Hello Alex,
> 
> Alexandru Petrescu wrote:
>>
>>>
>>> IP is a solution that puts together different links.
>>
>> Yes, provided IP knows what are those links, each one in particular 
>> detail.
> 
> Actually, all that is needed is for IP to have a useful interface to the
> device driver.

I agree.  Device driver interfaces are known for several wireless link 
layers.  I think there isn't one special for the A-B-C hidden terminal 
problem.  I may be wrong, but I think.

>>> 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.
>>
>> YEs, I'm explicit: it's wifi.
> 
> That restriction is not in the charter.  Do you want to campaign
> for a charter revision?

Right... No, no, I don't want to restrict to wifi.  I think the A-B-C 
hidden terminal problem was mentioned in the wifi context.  I haven't 
seen it elsewhere.

I agree for a solution IP to run over several link layers, for example 
wifi and 802.16.

When a router needs to route between a wifi and a 802.16 link it never 
has the hidden terminal problem.

>>> 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?
>>
>> WE need to be able to know over what is IP supposed to run.  If we 
>> don't have a good under-IP then it can't run.  Actually we could think 
>> as much it will run as we think it won't run.  Sorry, I can't be 
>> clearer than that.
> 
> But is does run.  I guess that's also pretty clear.
> 
> I'd like for it to run using standard protocols.
> 
> And not just for WiFi.

Yes, I'd like to help with a protocol for wireless links, like wifi and 
802.16.  But routing between these two doesn't expose the hidden 
terminal problem.  I'm pretty sure about it, I can say that because I 
have experience with IP over wifi and over 802.16 (emulated) links.

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