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

"Seung Yi" <scicarus@iname.com> Sun, 21 December 2008 23:00 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 6AC583A694E; Sun, 21 Dec 2008 15:00:29 -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 5A8053A694E for <autoconf@core3.amsl.com>; Sun, 21 Dec 2008 15:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.827
X-Spam-Level:
X-Spam-Status: No, score=-0.827 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MANGLED_PILL=2.3]
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 meUC-Ujq7Uvq for <autoconf@core3.amsl.com>; Sun, 21 Dec 2008 15:00:27 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by core3.amsl.com (Postfix) with ESMTP id 4CF933A6889 for <autoconf@ietf.org>; Sun, 21 Dec 2008 15:00:27 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id c5so659511anc.4 for <autoconf@ietf.org>; Sun, 21 Dec 2008 15:00:17 -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 :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=rE5WWukEGr83GSiRsrhRyYDG7vqIAsEgVa6Mtp6XrDs=; b=r71QU6VUlgZ+cv/HD83ijUFwX6l7n9Nwbm1fTOg1A3qbkeJB7L8Or+l+X+rivyMKmS frb4tQnUcMM14bYlwcF+ye6UvT0R2JebBD/LZ5TQ/KVsYaLuaDiaGzuWVPUbd6Oydsud 909z7ErEEQTcdSpBjWv3umadGR23JHyuXk/4A=
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:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Nh52C1sGc6VSRy1fIQKjUKu7ZqLXTaL6+6xkoxOcC3SFBbP66WLgo3pO4E48R1XcRu 4Rc1UyHxWVU549T3tURkzMoZgHZ9W10No3wJGA4tM/g6icQ5J07q+qIDY/LzdKFsHUEF TimaqMrpQ/9lFMeNPARxlmNAWihtp5i1pG+T8=
Received: by 10.100.191.9 with SMTP id o9mr3507291anf.63.1229900417612; Sun, 21 Dec 2008 15:00:17 -0800 (PST)
Received: by 10.100.138.7 with HTTP; Sun, 21 Dec 2008 15:00:17 -0800 (PST)
Message-ID: <af6d5faa0812211500se96b728l6e86cca702214e27@mail.gmail.com>
Date: Sun, 21 Dec 2008 15:00:17 -0800
From: Seung Yi <scicarus@iname.com>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <000d01c96363$9b42fae0$d1c8f0a0$@nl>
MIME-Version: 1.0
Content-Disposition: inline
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <af6d5faa0812201648p291bd896nc0af69d73a62c922@mail.gmail.com> <494D9768.3040903@earthlink.net> <000d01c96363$9b42fae0$d1c8f0a0$@nl>
X-Google-Sender-Auth: 092033a68e0ff40a
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

I'm sorry but it sounds even more confusing to me.

I'm not sure what to call it but it seems to describe the hidden
terminal problem to me. Or, it's simply saying that the link (or
whatever you want to call the "S") is of non-broadcast flavor because
R1 and R2 can expect to hear each other only when the medium itself
provides broadcast capability as in the Ethernet.

- Seung

On Sun, Dec 21, 2008 at 3:59 AM, Teco Boot <teco@inf-net.nl> wrote:
> What about a small adjustment:
>
>   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 have symmetric communication with 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".  Such non-
>   transitivity is often observed on multi-hop ad hoc wireless networks,
>   due to well-known properties of wireless communication.
>
>
> Now it says: "If R1->A and A->R2, there is no guarantee for R1->R2".
> And the second behavior is not mixed up with the first one.
>
> Teco.
>
> |-----Oorspronkelijk bericht-----
> |Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] Namens
> |Charles E. Perkins
> |Verzonden: zondag 21 december 2008 2:10
> |Aan: Seung Yi
> |CC: autoconf@ietf.org
> |Onderwerp: Re: [Autoconf] aspects of multi-hop wireless communication
> |
> |
> |Hello Seung,
> |
> |Yes, of course you are right (embarrassment).
> |
> |What is a good name for the property under discussion?
> |
> |Regards,
> |Charlie P.
> |
> |
> |Seung Yi wrote:
> |> Just one simple comment unrelated to the ongoing interesting
> |discussion threads.
> |>
> |> Isn't the definition of transitivity "If A->B and B->C, then A->C"?
> |> This document seems to use the term to mean "if A->B and A->C, then
> |> B->C" in Section 2, second point.
> |>
> |> - Seung
> |>
> |> 2008/12/19 Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>:
> |>
> |>> Hi all,
> |>> here's a draft that aims at describing important aspects of multi-hop
> |>> wireless communication, as observed over the past decade of
> |experience with
> |>> such networks.
> |>> The goal of this document is to identify a consensus about this
> |topic, and
> |>> then use this to move on quicker with the working group documents.
> |>>
> |>> Please review it, and provide feedback as soon as possible.
> |>> http://tools.ietf.org/html/draft-baccelli-multi-hop-wireless-
> |communication-00
> |>>
> |>> cheers
> |>> Emmanuel
> |>> _______________________________________________
> |>> Autoconf mailing list
> |>> Autoconf@ietf.org
> |>> https://www.ietf.org/mailman/listinfo/autoconf
> |>>
> |>>
> |>>
> |> _______________________________________________
> |> Autoconf mailing list
> |> Autoconf@ietf.org
> |> https://www.ietf.org/mailman/listinfo/autoconf
> |>
> |>
> |>
> |
> |_______________________________________________
> |Autoconf mailing list
> |Autoconf@ietf.org
> |https://www.ietf.org/mailman/listinfo/autoconf
>
>
_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf