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

"Emmanuel Baccelli" <Emmanuel.Baccelli@inria.fr> Fri, 19 December 2008 13:49 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 474CB3A69A4; Fri, 19 Dec 2008 05:49:16 -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 A6C633A69A4 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 05:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.064, 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 l-B-GDiq-1NU for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 05:49:14 -0800 (PST)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by core3.amsl.com (Postfix) with ESMTP id 833983A6842 for <autoconf@ietf.org>; Fri, 19 Dec 2008 05:49:13 -0800 (PST)
Received: by fk-out-0910.google.com with SMTP id 18so528940fkq.5 for <autoconf@ietf.org>; Fri, 19 Dec 2008 05:49:05 -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=iAupQrJdt7axiLLR/uCGGKHpbsWu9xcuKtPCdxrTTsc=; b=MoRwXURynv7wyUU/VPpuRGAFYgCh89dK42oRNhipt+c7Tt4LrTODoXrt9TTNGDC1Hi Hvla6Ua8/n914h9htCb31bN64nh0f6h/NGopk8G0SevyjHU+DifDV6xmoN9MqrgDhMLJ ZkV43UB976FjJWf5siKABiciTqKXOdWOfat0o=
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=eJ/IIg6Fo3H7o9ldp5ZeGoAg/IDunuGSlao+HrgK6mqF9H7jBwaYjKVXRF5q8SwfTE aQf+HhGCtfuvLv/bgUxwPmzwxmz+l7Kex6THRxwHbcyOSIfSrlZ4gQmlUywZ+IA1LR/T V7kljuy4HDHYfxcip/hphpUVyzIRS7XH75B9o=
Received: by 10.103.49.12 with SMTP id b12mr1236469muk.65.1229694544941; Fri, 19 Dec 2008 05:49:04 -0800 (PST)
Received: by 10.103.248.12 with HTTP; Fri, 19 Dec 2008 05:49:04 -0800 (PST)
Message-ID: <be8c8d780812190549q30e93e9cg73ff9e5852a3b7be@mail.gmail.com>
Date: Fri, 19 Dec 2008 14:49:04 +0100
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <006b01c961de$708c80e0$51a582a0$@nl>
MIME-Version: 1.0
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <005101c961d2$8c7f4ff0$a57defd0$@nl> <be8c8d780812190511t31bb9a3co32c53ba4b1be9e5a@mail.gmail.com> <006b01c961de$708c80e0$51a582a0$@nl>
X-Google-Sender-Auth: 263b6387bca7aa8f
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="===============0313865486=="
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

OK ;) As far as I'm concerned, I think we should update the text; Should be
in -01.Emmanuel


On Fri, Dec 19, 2008 at 2:33 PM, Teco Boot <teco@inf-net.nl> wrote:

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