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

"Emmanuel Baccelli" <Emmanuel.Baccelli@inria.fr> Fri, 19 December 2008 16:11 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 7449D3A6A42; Fri, 19 Dec 2008 08:11:10 -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 EBBC93A6A57 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.056, 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 i5l2XqKcgahm for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 08:11:06 -0800 (PST)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by core3.amsl.com (Postfix) with ESMTP id EEF993A6A56 for <autoconf@ietf.org>; Fri, 19 Dec 2008 08:11:03 -0800 (PST)
Received: by fk-out-0910.google.com with SMTP id 18so566393fkq.5 for <autoconf@ietf.org>; Fri, 19 Dec 2008 08:10:55 -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:cc:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=H8d9vmtPgasz5TfjhKiFYrrSXZHTVHBgj6SAfvkCoUk=; b=Hj9aDtly9Nr+xuYKRw9pHxOUryIgNXQFjvyXaDMzAFHjSIsQJIlPP2igxM6mc48gxQ JyGdQXgdOnaObotv2TmGDpJ1v2GsSD0BnbDcZ7pEQ6sSM5vfRDa2ymx4oGR1T5wlPgbf ylDJ7AuQBWFUjfjcKTByctAgiebotMYTKVx/4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=D1MgTNNL4MxnBlIj7QvXv8nl7Z3m4J2tocBYEugngl/akTvkqk3ckYptJcPSHWzttr rX/xOAgLWLhXhYzqy6PicMsapAFtIMf/+aweNNyz9JtKj374ld1TjzWsAN+joKT1ZK76 ZNLXTQ3giV2B8oYG07dOnGRyYw5JPiB4r6bv4=
Received: by 10.103.165.18 with SMTP id s18mr1277589muo.124.1229703055136; Fri, 19 Dec 2008 08:10:55 -0800 (PST)
Received: by 10.103.248.12 with HTTP; Fri, 19 Dec 2008 08:10:55 -0800 (PST)
Message-ID: <be8c8d780812190810y4d891c44tfbec9cce43c3cee9@mail.gmail.com>
Date: Fri, 19 Dec 2008 17:10:55 +0100
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <494BC360.1000109@gmail.com>
MIME-Version: 1.0
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>
X-Google-Sender-Auth: b2bb1fa9977ea8d4
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-Type: multipart/mixed; boundary="===============1487522055=="
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

On Fri, Dec 19, 2008 at 4:53 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Emmanuel Baccelli wrote:
>
>>
>>
>> On Fri, Dec 19, 2008 at 4:06 PM, Dearlove, Christopher (UK) <
>> chris.dearlove@baesystems.com <mailto:chris.dearlove@baesystems.com>>
>> wrote:
>>
>>
>>  I think some solutions exist at PHY and MAC layers in the case of
>>>
>> 802.11.
>>
>> As has been said many times before, MANET is not just about 802.11.
>>
>>
>> I think Chris makes an important point here. We are discussing things
>>  experienced at the IP layer.
>>
>
> 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).
>
> 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.
>


I knew this joke with a spider instead of a frog. Funny.


>
>  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).
>


Well Alex, you are the only one I know that has had such unbelievable luck
with radio links (wifi or any other type of radio) during the last decade. I
guess this is says a lot about reality ;)
Emmanuel




>
> Alex
>
>
>> Emmanuel
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> _______________________________________________ Autoconf mailing list
>>  Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf
>>
>
>
> ______________________________________________________________________
> 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