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

"Teco Boot" <teco@inf-net.nl> Fri, 19 December 2008 12:10 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 CCA033A687B; Fri, 19 Dec 2008 04:10:56 -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 966453A687B for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 04:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[AWL=0.388, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
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 eR7AYlD8RpBN for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 04:10:50 -0800 (PST)
Received: from hpsmtp-eml15.kpnxchange.com (hpsmtp-eml15.KPNXCHANGE.COM [213.75.38.115]) by core3.amsl.com (Postfix) with ESMTP id 4D60D3A68A2 for <autoconf@ietf.org>; Fri, 19 Dec 2008 04:10:50 -0800 (PST)
Received: from cpsmtp-eml101.kpnxchange.com ([213.75.84.101]) by hpsmtp-eml15.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Dec 2008 13:08:51 +0100
Received: from M90Teco ([86.83.9.22]) by cpsmtp-eml101.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Dec 2008 13:08:51 +0100
From: Teco Boot <teco@inf-net.nl>
To: 'Emmanuel Baccelli' <Emmanuel.Baccelli@inria.fr>, charliep@wichorus.com
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com>
In-Reply-To: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com>
Date: Fri, 19 Dec 2008 13:08:48 +0100
Message-ID: <005101c961d2$8c7f4ff0$a57defd0$@nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AclhuuDL8V9a4x81S4iEDg1TVsZyCwADq79Q
Content-Language: nl
X-OriginalArrivalTime: 19 Dec 2008 12:08:51.0949 (UTC) FILETIME=[8E8E59D0:01C961D2]
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

Hi Emmanual and Charles,

Thanks for the efforts. 
I like the compactness of the draft.


Maybe mention alternate terminology “uni-directional” for "asymmetric" ?
As discussed before, asymmetry is also used for different link qualities
for A to B and B to A, where A and B have a symmetric relation.


> - We may say that router B is a neighbor of router A. In this
>   terminology, there is no guarantee that router A is a neighbor of
>   router B.

In this case, the neighbor table of router B would list router A.
So I say router A is neighbor of router B, and there is no guarantee
that router B is a neighbor of router A.
Or I say the relation between neighbors is symmetric, but some neighbors 
may not be aware of this.


Regards, Teco


===
Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] Namens
Emmanuel Baccelli
Verzonden: vrijdag 19 december 2008 10:19
Aan: autoconf@ietf.org
Onderwerp: [Autoconf] aspects of multi-hop wireless communication

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-0
0

cheers
Emmanuel

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