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

"Emmanuel Baccelli" <Emmanuel.Baccelli@inria.fr> Mon, 22 December 2008 08:47 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 7F74C3A686C; Mon, 22 Dec 2008 00:47:52 -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 F28EB3A686C for <autoconf@core3.amsl.com>; Mon, 22 Dec 2008 00:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level:
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 bUdEbVAPKei0 for <autoconf@core3.amsl.com>; Mon, 22 Dec 2008 00:47:50 -0800 (PST)
Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id A152A3A6774 for <autoconf@ietf.org>; Mon, 22 Dec 2008 00:47:49 -0800 (PST)
Received: by bwz14 with SMTP id 14so7635064bwz.13 for <autoconf@ietf.org>; Mon, 22 Dec 2008 00:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=7pBAZFFVwoN8ULcDOM3m4BBwHBqF+wPXtJLzsDAHlKI=; b=tyiSI4hyOk4JCdvgMEsS30vEQrt3JcA9ZlnobQDrMBhZbTNMuNzH9NoP+UuU/xNV3A GiKA0WqYwaTLcOpjP/ESeEenmcpCMSqqk9Pe8ktn1t3Swjs2GY//ADje5+L1+ZRnF93k MxzKLF4c3ea+GMw5g+6IbRWqDrLCrSXKQPNjE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=P/k47E292axXdrLMK5weI5yJi0VW2upCjnCenC4PECzML4z3Iqux3RcIvzUmvEbsLq zAeCdVmBqFnBETpT1djMnaVQgLZz2GAubFhqDXTeUNWlMK+2LkdGqTghhwTF7KWAQacN 7yCVv7+JzekHKzRenhHUdvGqlgQnN2mUzz2n4=
Received: by 10.103.247.14 with SMTP id z14mr2203666mur.70.1229935659800; Mon, 22 Dec 2008 00:47:39 -0800 (PST)
Received: by 10.103.248.12 with HTTP; Mon, 22 Dec 2008 00:47:39 -0800 (PST)
Message-ID: <be8c8d780812220047w5bbfbdb6v71c557e15cbd58@mail.gmail.com>
Date: Mon, 22 Dec 2008 09:47:39 +0100
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: autoconf@ietf.org
In-Reply-To: <494F0B17.8070806@earthlink.net>
MIME-Version: 1.0
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.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> <494F0B17.8070806@earthlink.net>
X-Google-Sender-Auth: 5d05ef58e4da1066
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-Type: multipart/mixed; boundary="===============0611715957=="
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

On Mon, Dec 22, 2008 at 4:35 AM, Charles E. Perkins <
charles.perkins@earthlink.net> wrote:
>
>
>
>  - 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).



First, this is not just about 802.11 b/g. The same behavior was observed
with other radio MAC, such as simple proprietary sensor "MAC" layers for
example, and there are many other examples. One can also anticipate some
future L2 standards that will have the same properties.

We are dealing with a specific _category_ of networks here. And thus, this
would not be the first time that something special is done at L3 to cope
with a specific category of L2 networks. Lets recall different OSPF
interface types, for instance.

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