IETF Logo Mail Archive

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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 December 2008 17:58 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 A404E28C14C; Fri, 19 Dec 2008 09:58:37 -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 52DD828C14C for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 09:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.128
X-Spam-Level:
X-Spam-Status: No, score=-6.128 tagged_above=-999 required=5 tests=[AWL=0.471, 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 y2hLsIAtgO09 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 09:58:35 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id 834BB28C136 for <autoconf@ietf.org>; Fri, 19 Dec 2008 09:58:35 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-14.tower-128.messagelabs.com!1229709506!24453333!1
X-StarScan-Version: 6.0.0; banners=.,-,-
X-Originating-IP: [136.182.1.15]
Received: (qmail 9468 invoked from network); 19 Dec 2008 17:58:26 -0000
Received: from unknown (HELO motgate5.mot.com) (136.182.1.15) by server-14.tower-128.messagelabs.com with SMTP; 19 Dec 2008 17:58:26 -0000
Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72]) by motgate5.mot.com (8.12.11/Motorola) with ESMTP id mBJHwQ1C020856; Fri, 19 Dec 2008 10:58:26 -0700 (MST)
Received: from il27vts03 (il27vts03.cig.mot.com [10.17.196.87]) by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id mBJHwPna013893; Fri, 19 Dec 2008 11:58:25 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.88]) by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id mBJHwO6x013869; Fri, 19 Dec 2008 11:58:24 -0600 (CST)
Message-ID: <494BE0BF.5060606@gmail.com>
Date: Fri, 19 Dec 2008 18:58:23 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Rex Buddenberg <budden@nps.navy.mil>
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <494B8E7C.7000505@gmail.com> <be8c8d780812190504x98496egc37c25b21a799ceb@mail.gmail.com> <494BB75E.4050206@gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D016C3E14@GLKMS2100.GREENLNK.NET> <494BBBCB.4080804@gmail.com> <1229709208.29772.146.camel@localhost.localdomain>
In-Reply-To: <1229709208.29772.146.camel@localhost.localdomain>
X-Antivirus: avast! (VPS 081218-0, 18/12/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: autoconf@ietf.org, Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
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

Rex Buddenberg wrote:
> You haven't been watching ... both US Army and US Marine Corps are
> filling up the space between brigade and company with IEEE 802.16 gear.
> And routing it all together.

IETF has specs for IPv6 over 802.16 gear.  It works, it's been 
experimented.  The A-B-C terminal problem wasn't mentioned.

> For military, WiFi is a bauble.  Army worked through a proposal to
> implement it in command centers (think tents in the desert) and finally
> scrapped the proposal.  Because you could indeed clip the ethernet wire
> but not the power cord, so not much payback.  And in order to get that
> niggardly payback they were going to pay a lot for a layer 2 encryption
> solution.  Spent the money on .16 gear instead ...
> 
> This is wide of the MANET issues.  But MANET (and autoconf) is
> applicable to a lot of wireless LAN and radio-WAN problems well beyond
> WiFi.

AS above, IPv6 over 802.16 works has been implemented, from emulators to 
the real link layer.

What other link layer?

Alex

> On Fri, 2008-12-19 at 16:20 +0100, Alexandru Petrescu wrote:
>> Dearlove, Christopher (UK) wrote:
>>>> I think some solutions exist at PHY and MAC layers in the case of
>>>> 802.11.
>>> As has been said many times before, MANET is not just
>>> about 802.11.
>> I may have missed something.  What other than 802.11 is it about?
>>
>> 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
> 
> 


______________________________________________________________________
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

v2.23.0 | Report a Bug | By Email