Re: [Autoconf] aspects of multi-hop wireless communication
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 20:12 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 2B16E28C160; Fri, 19 Dec 2008 12:12:33 -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 C8E3B3A6A80 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 12:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level:
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 3rZ7FuIwTRpd for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 12:12:31 -0800 (PST)
Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id D61583A6A6B for <autoconf@ietf.org>; Fri, 19 Dec 2008 12:12:30 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-6.tower-153.messagelabs.com!1229717542!6503741!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 11908 invoked from network); 19 Dec 2008 20:12:22 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-6.tower-153.messagelabs.com with SMTP; 19 Dec 2008 20:12:22 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id mBJKCLPD011571; Fri, 19 Dec 2008 13:12:21 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id mBJKCLvX004161; Fri, 19 Dec 2008 14:12:21 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.67]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id mBJKCK0f004146; Fri, 19 Dec 2008 14:12:20 -0600 (CST)
Message-ID: <494C0023.9030004@gmail.com>
Date: Fri, 19 Dec 2008 21:12:19 +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>
In-Reply-To: <494BEDD0.9020708@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
Charles please let me bring forward a clarifying point, which is your last point, and sorry for too long emails. > Do you think that routing protocol work should only be chartered for > links that conform to certain regularity assumptions like symmetry > and transitivity? Is this a MANET WG question? I think in AUTOCONF WG we don't do work that applies _only_ to DYMO, nor to OLSR, nor to DSR. In this case, an AUTOCONF address and prefix configuration mechanism would be used too by something else than DYMO, other than OLSR, other than DSR. It could be used by two Mobile Routers not running DYMO, nor OLSR, nor DSR. It's very straightforward to clarify this particular point, people could and have expressed opinions. If the AUTOCONF mechanism is to be only for DYMO/OLSR/DSR exclusively then I just say ok for the draft titled 'aspects of multi-hop...'. The points I mainly agree with you follow below... Charles E. Perkins wrote: > > Hello again Alex, > > Alexandru Petrescu wrote: >> >>> >>> Actually, all that is needed is for IP to have a useful interface >>> to the device driver. >> >> I agree. Device driver interfaces are known for several wireless >> link layers. I think there isn't one special for the A-B-C hidden >> terminal problem. I may be wrong, but I think. > > That's because IP doesn't need to know whether the link has problems > with hidden terminals. I fully agree. >> Yes, I'd like to help with a protocol for wireless links, like wifi >> and 802.16. But routing between these two doesn't expose the >> hidden terminal problem. I'm pretty sure about it, I can say that >> because I have experience with IP over wifi and over 802.16 >> (emulated) links. > > Again, routing doesn't need to know about that. And, in fact, I > believe that IP doesn't have to know about asymmetry, > nontransitivity, or the time of day. It just has to know about the > next hop. I partially agree (may need link quality params, maybe expressed as TOS in OSPF, for better decisions) but in this discussion context I fully agree. > You seem to claim that we shouldn't worry about them because the link > layer has to solve problems like asymmetry and hidden terminal > problems. I'm of the opinion that routing protocols have to be > engineered in some circumstances to avoid making unwarranted > inferences about symmetry and transitivity. Maybe yes, but maybe in MANET WG? > I think it would be nice to identify exactly what your concern is. > Once it was WiFi only, now it's not. Sorry, to make myself clear: in this discussion wifi and 802.16 were mentioned. I agree both should be dealt with. I don't agree to deal with a link-layer whose name I don't know. 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
- [Autoconf] aspects of multi-hop wireless communic… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Dearlove, Christopher (UK)
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Dearlove, Christopher (UK)
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Dearlove, Christopher (UK)
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Dearlove, Christopher (UK)
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Rex Buddenberg
- Re: [Autoconf] aspects of multi-hop wireless comm… Rex Buddenberg
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Paul Lambert
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Seung Yi
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Seung Yi
- Re: [Autoconf] aspects of multi-hop wireless comm… Breno Jacinto
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Emmanuel Baccelli
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Alexandru Petrescu
- Re: [Autoconf] aspects of multi-hop wireless comm… Teco Boot
- Re: [Autoconf] aspects of multi-hop wireless comm… Rex Buddenberg
- Re: [Autoconf] aspects of multi-hop wireless comm… Rex Buddenberg
- Re: [Autoconf] aspects of multi-hop wireless comm… Rex Buddenberg
- Re: [Autoconf] aspects of multi-hop wireless comm… Breno Jacinto
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins
- Re: [Autoconf] aspects of multi-hop wireless comm… Breno Jacinto
- Re: [Autoconf] aspects of multi-hop wireless comm… Charles E. Perkins