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

"Teco Boot" <teco@inf-net.nl> Fri, 19 December 2008 13:34 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 2216A3A6883; Fri, 19 Dec 2008 05:34: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 733C63A6883 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 05:34:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.765
X-Spam-Level:
X-Spam-Status: No, score=-0.765 tagged_above=-999 required=5 tests=[AWL=-0.579, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 Aw41k0nOZ1TC for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 05:34:08 -0800 (PST)
Received: from hpsmtp-eml20.kpnxchange.com (hpsmtp-eml20.KPNXCHANGE.COM [213.75.38.85]) by core3.amsl.com (Postfix) with ESMTP id 3FF683A6808 for <autoconf@ietf.org>; Fri, 19 Dec 2008 05:34:07 -0800 (PST)
Received: from cpsmtp-eml101.kpnxchange.com ([213.75.84.101]) by hpsmtp-eml20.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Dec 2008 14:33:59 +0100
Received: from M90Teco ([86.83.9.22]) by cpsmtp-eml101.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Dec 2008 14:33:59 +0100
From: Teco Boot <teco@inf-net.nl>
To: 'Emmanuel Baccelli' <Emmanuel.Baccelli@inria.fr>, autoconf@ietf.org
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <005101c961d2$8c7f4ff0$a57defd0$@nl> <be8c8d780812190511t31bb9a3co32c53ba4b1be9e5a@mail.gmail.com>
In-Reply-To: <be8c8d780812190511t31bb9a3co32c53ba4b1be9e5a@mail.gmail.com>
Date: Fri, 19 Dec 2008 14:33:55 +0100
Message-ID: <006b01c961de$708c80e0$51a582a0$@nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aclh20rzZmiluIqwTHmOY6SWqDJC9AAAroVg
Content-Language: nl
X-OriginalArrivalTime: 19 Dec 2008 13:33:59.0128 (UTC) FILETIME=[72AC0580:01C961DE]
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="===============0427652428=="
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

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

 

 

OK, I think I see what you mean: you are saying that since B hears A, the
text should rather be:

"A is neighbor of router B, and there is no guarantee that router B is a
neighbor of router A"

Am I correct?

 

Yes, but others could prefer the original text. 

If so, I am interested in the protocol that implement such.

If there is no such implementation, please update the text.

 

Teco.

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