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

"Charles E. Perkins" <charles.perkins@earthlink.net> Mon, 22 December 2008 03:36 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 00DF43A68C6; Sun, 21 Dec 2008 19:36:05 -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 48B1B3A68C6 for <autoconf@core3.amsl.com>; Sun, 21 Dec 2008 19:36:04 -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 UHtuzadE+7qr for <autoconf@core3.amsl.com>; Sun, 21 Dec 2008 19:36:03 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 5A5113A67E4 for <autoconf@ietf.org>; Sun, 21 Dec 2008 19:36:03 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Fur3gbs8MJuFCR6qDyI+RdzAEjlheVMPZw8uN5RUPI6hoAaPq0/hINad+JeaoPZ6; 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-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1LEbaE-0004tD-Kl; Sun, 21 Dec 2008 22:35:54 -0500
Message-ID: <494F0B17.8070806@earthlink.net>
Date: Sun, 21 Dec 2008 19:35:51 -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: Breno Jacinto <breno@freeunix.com.br>
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <494BCCCC.6050206@earthlink.net> <494BCFEF.2010100@gmail.com> <494BD45A.2090106@earthlink.net> <494BE0D8.4070509@gmail.com> <00ae01c96208$aa2ebd20$fe8c3760$@nl> <494BEAB1.3040700@gmail.com> <00af01c96211$e2c97770$a85c6650$@nl> <494BFE4B.9000601@gmail.com> <000001c96285$b050af60$10f20e20$@nl> <2ced936d0812211653v61161e4dp7f1ba79e81c61124@mail.gmail.com>
In-Reply-To: <2ced936d0812211653v61161e4dp7f1ba79e81c61124@mail.gmail.com>
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f5254cda3ef4a882ebe2caa6622079a8621350badd9bab72f9c350badd9bab72f9c
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 Breno,

Breno Jacinto wrote:
> - Should Mult-hop communications happen at the IP layer, really? I
> think that this decision was taken just because 802.11 b/g standard
> become popular and could not do multi-hop at layer 2. So, everyone
> thought, let's do it at layer 3, because it is possible to emulate
> multi-hop then.
>   

I think this is not an accurate reflection of the evolution of thought
on the subject.  At least for me, it was clear that one could easily
make a routing solution by revising RIP to get rid of poison reverse
and other hacks, so that we could have just the next-hop routing
as needed.  This was a very long time before 802.11.

Your word "should" is loaded.  IP is, I think, great at stitching together
links into a network.  They don't even have to be the same physical
media.  That's a major plus compared to layer 2 solutions.  Plus,
the same layer 3 solution works for a lot of different wireless physical
media.  That's better than blasting away with different solutions for
each different medium.

I just don't see what's wrong with it.

> - If multi-hopping is done at layer 2, isn't that a good thing? I
> mean, you can deal with problems specific to the link layer (including
> the aforementioned hidden node problem, or whatever
> next-popular-link-layer for multi-hop become available in the future)
> and make IP more neutral. I think that would conserve the initial aim
> of IP, which is simply to glue heterogeneous networks, not fixing a
> particular link-layer problem as it is being done with 802.11 b/g.
>   

There is no free lunch.  You are going to solve those problems at layer 3,
or you are going to solve them at layer 2.  And, even if the latter, you may
still have to worry about it at layer 3 unless you impose some very strong
regularity conditions (I'm still puzzling over truckloads of repeaters).

> - Now, if we could assume that multi-hop is done at layer 2; to layer
> 3 (such as IP), a broadcast should reach (be flooded to) everyone in
> the network. Now, IP sees the network as a single broadcast domain and
> issues in the "real" network should be dealt there. We may then shift
> to the problem of connecting multiple ad hoc networks at the IP layer,
> doing inter-domain routing etc.

There's that "should" again.  In fact, your very example of broadcast
disproves your point: what if the best broadcast used multiple media?

Regards,
Charlie P.


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