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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 22:20 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 D141C28C130; Fri, 19 Dec 2008 14:20:48 -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 12CB628C130 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 14:20:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.218
X-Spam-Level:
X-Spam-Status: No, score=-6.218 tagged_above=-999 required=5 tests=[AWL=0.381, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 X5Yc2CJh1c4W for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 14:20:46 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id 4DE5D28C0EE for <autoconf@ietf.org>; Fri, 19 Dec 2008 14:20:46 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1229725236!6436978!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [136.182.1.12]
Received: (qmail 17015 invoked from network); 19 Dec 2008 22:20:36 -0000
Received: from unknown (HELO motgate2.mot.com) (136.182.1.12) by server-2.tower-128.messagelabs.com with SMTP; 19 Dec 2008 22:20:36 -0000
Received: from il27exr01.cig.mot.com (il27exr01.mot.com [10.17.196.70]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id mBJMKYFM009308; Fri, 19 Dec 2008 15:20:34 -0700 (MST)
Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88]) by il27exr01.cig.mot.com (8.13.1/Vontu) with SMTP id mBJMKY08028661; Fri, 19 Dec 2008 16:20:34 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.63]) by il27exr01.cig.mot.com (8.13.1/8.13.0) with ESMTP id mBJMKWML028652; Fri, 19 Dec 2008 16:20:33 -0600 (CST)
Message-ID: <494C1E2F.2010000@gmail.com>
Date: Fri, 19 Dec 2008 23:20:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
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> <be8c8d780812190810y4d891c44tfbec9cce43c3cee9@mail.gmail.com> <494BC927.1020400@gmail.com> <494BCCCC.6050206@earthlink.net> <494BCFEF.2010100@gmail.com> <494BD45A.2090106@earthlink.net> <494BE0D8.4070509@gmail.com> <494BE5A5.4020205@earthlink.net> <494BEA55.3080304@gmail.com> <494BEDD0.9020708@earthlink.net> <494BFF7D.40804@motorola.com> <494C0986.9020404@earthlink.net>
In-Reply-To: <494C0986.9020404@earthlink.net>
X-Antivirus: avast! (VPS 081218-0, 18/12/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

Hello Charles,

Charles E. Perkins wrote:
[..]
>> I think in AUTOCONF WG we don't do work that applies _only_ to 
>> DYMO, nor to OLSR, nor to DSR.
> 
> Actually, I'd say the same thing about [manet] wg.  And, the authors
>  of TBRPF and many others would bristle that you didn't mention them.
> 
Sorry, it wasn't intentional.  TBRPF too for MANET.

[...]
> I'm also of the opinion that there is going to be some overlap 
> between the mechanisms for address assignment, and the routing 
> protocols.  For instance, it is very reasonable to use a multi-hop 
> gateway beacon to advertise information relevant to address 
> assignment.  I do not say that it is absolutely required to be this 
> way, but on the other hand solutions that take care to avoid the 
> pitfalls under discussion are, in my opinion, more likely to succeed
>  than other more brute force solutions.

Well I'm not looking at brute force solutions, but solutions to simpler
problems.  The advertising you mention - could work without taking into
considerations the asymmetricity/nontransitivity, if we think it's about 
Router Advertisements.

> But, on the other hand, if a solution that works for 802.{11*,16,...}
>  is created in a way that is cognizant of the wireless 
> characteristics as we have described in our Internet Draft, then it 
> is _more likely_ to work for the other unspecified but presumably 
> similar media.
> 
> Which is why we wrote it.
> 
> Do you disagree with this motivation?

No, I don't disagree with that motivation - supposedly if it works for 
non-transitive links it will work for transitive links too.  I just look 
at it as something which may be too much for simpler needs.

Alex


______________________________________________________________________
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