From manet-bounces@ietf.org Tue Feb 1 00:47:51 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27931 for ; Tue, 1 Feb 2005 00:47:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvrBM-0006ke-1G for manet-web-archive@ietf.org; Tue, 01 Feb 2005 01:06:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvqgE-0006r2-7h; Tue, 01 Feb 2005 00:34:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvqaJ-0005OI-LW for manet@megatron.ietf.org; Tue, 01 Feb 2005 00:28:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25407 for ; Tue, 1 Feb 2005 00:28:16 -0500 (EST) Received: from web52908.mail.yahoo.com ([206.190.39.185]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CvqsO-00068D-59 for manet@ietf.org; Tue, 01 Feb 2005 00:47:01 -0500 Received: (qmail 66109 invoked by uid 60001); 1 Feb 2005 05:27:47 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=mb9xnsZrvB011tEnDW0UYxwJZqWisShx5V6yZeaNGf5IDwVdkXcH8jbI9AlAekRnzcGIjpjT73br6dShil9lg5WGeqwYpsOOGLmpM+4hwNVCF1+GxaFz237IkqrDKyskM0y7j1lKysMzbxo8u0i7LdUvzuJDj8FDHEJvZP49sig= ; Message-ID: <20050201052747.66107.qmail@web52908.mail.yahoo.com> Received: from [61.1.252.230] by web52908.mail.yahoo.com via HTTP; Mon, 31 Jan 2005 21:27:46 PST Date: Mon, 31 Jan 2005 21:27:46 -0800 (PST) From: Siva Reddy To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: [manet] doubt regarding installation of DMAC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 hi friends, if any boby working on Data-gathering MAC in sensor networks, please give me an idea about how to install the code for DMAC given by the author in his site.i tried a lot to install the code but i am getting lot of errors.please help me... thanks in advance... siva reddy. __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 1 05:01:28 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08974 for ; Tue, 1 Feb 2005 05:01:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvv8n-0004UW-OY for manet-web-archive@ietf.org; Tue, 01 Feb 2005 05:20:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvump-0005LY-4i; Tue, 01 Feb 2005 04:57:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvulv-0005FH-Kw for manet@megatron.ietf.org; Tue, 01 Feb 2005 04:56:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08626 for ; Tue, 1 Feb 2005 04:56:34 -0500 (EST) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvv42-0004Oj-RJ for manet@ietf.org; Tue, 01 Feb 2005 05:15:20 -0500 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j119u2NR007982 for ; Tue, 1 Feb 2005 10:56:02 +0100 (CET) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id 2B1843C318 for ; Tue, 1 Feb 2005 10:56:02 +0100 (MET) Message-ID: <41FF5231.6060206@eurecom.fr> Date: Tue, 01 Feb 2005 10:56:01 +0100 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Subject: [manet] How to cause and measure the hidden terminal (or collisions)? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7bit Hello you MANET guys, I have a challenging question for you: I am running some tests on a MANET testbed composed of 4 nodes equipped of Dell Truemobile 1150 WLAN cards and routed with OLSR. I would like to do some performance measurements in presence of the hidden terminal problem. Now I believe that causing the hidden terminal problem with 4 nodes is almost impossible. Is there anyone that knows how I could provoke the hidden terminal problem in such conditions and measure its effects? Is there a way to measure collisions that happen during a 802.11 communication? I hope my question is clear enough. Any contribution would be greatly appreciated. Thx Claudio _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 1 05:27:03 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11090 for ; Tue, 1 Feb 2005 05:27:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvvXZ-00055O-QM for manet-web-archive@ietf.org; Tue, 01 Feb 2005 05:45:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvvCI-00009b-HC; Tue, 01 Feb 2005 05:23:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvv9m-0008Il-1I for manet@megatron.ietf.org; Tue, 01 Feb 2005 05:21:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10630 for ; Tue, 1 Feb 2005 05:21:12 -0500 (EST) Received: from waldorf.cs.uni-dortmund.de ([129.217.4.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvvRu-0004wM-8z for manet@ietf.org; Tue, 01 Feb 2005 05:39:58 -0500 Received: from postamt.cs.uni-dortmund.de (postamt [129.217.4.40]) by waldorf.cs.uni-dortmund.de with ESMTP id j11AKcF0027155 for ; Tue, 1 Feb 2005 11:20:39 +0100 (MET) Received: from reagan (reagan [129.217.16.88]) by postamt.cs.uni-dortmund.de (8.12.5/8.12.5) with ESMTP id j11AKciQ014723 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 1 Feb 2005 11:20:38 +0100 (MET) From: "Sherif M. ElRakabawy" To: Subject: Re: [manet] How to cause and measure the hidden terminal (orcollisions)? Date: Tue, 1 Feb 2005 11:20:38 +0100 Message-ID: <000301c50847$acf78510$5810d981@reagan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: Normal In-Reply-To: <41FF5231.6060206@eurecom.fr> X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: quoted-printable Hi, If you disable RTS/CTS you can get hidden terminals with only 3 nodes .. You can Measure the collisions on the MAC layer by counting the number of unsuccessful data packet transmissions, i.e. 4 transmissions without receiving a MAC ACK. You may compare the values you get with a case where there are no=20 hidden terminals, i.e. RTS/CTS is enabled. Regards Sherif -------------------------------------------- Sherif M. ElRakabawy University of Dortmund Department of Computer Science Tel. +49 231 755 2690 Mobile Computing Systems Group Fax. +49 231 755 2417 August-Schmidt-Str. 12 44227 Dortmund / Germany WWW: http://mobicom.cs.uni-dortmund.de/~moustafa/ > -----Urspr=FCngliche Nachricht----- > Von: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]=20 > Im Auftrag von Claudio Lavecchia > Gesendet: Tuesday, February 01, 2005 10:56 AM > An: manet@ietf.org > Betreff: [manet] How to cause and measure the hidden terminal=20 > (orcollisions)? >=20 >=20 > Hello you MANET guys, >=20 > I have a challenging question for you: I am running some tests on a=20 > MANET testbed composed of 4 nodes equipped of Dell Truemobile=20 > 1150 WLAN=20 > cards and routed with OLSR. > I would like to do some performance measurements in presence of the=20 > hidden terminal problem. Now I believe that causing the=20 > hidden terminal=20 > problem with 4 nodes is almost impossible. > Is there anyone that knows how I could provoke the hidden terminal=20 > problem in such conditions and measure its effects? Is there=20 > a way to=20 > measure collisions that happen during a 802.11 communication? >=20 > I hope my question is clear enough. Any contribution would be greatly=20 > appreciated. >=20 > Thx >=20 > Claudio >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 1 05:37:41 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12274 for ; Tue, 1 Feb 2005 05:37:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvvhr-0005MI-CN for manet-web-archive@ietf.org; Tue, 01 Feb 2005 05:56:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvvIu-0001JX-9j; Tue, 01 Feb 2005 05:30:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvvFk-0000Z6-RQ for manet@megatron.ietf.org; Tue, 01 Feb 2005 05:27:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11153 for ; Tue, 1 Feb 2005 05:27:23 -0500 (EST) Received: from icalxsrv11.epfl.ch ([128.178.156.143]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvvXr-000557-6s for manet@ietf.org; Tue, 01 Feb 2005 05:46:09 -0500 Received: from localhost (localhost [127.0.0.1]) by icalxsrv11.epfl.ch (Postfix) with ESMTP id 5CCDBE4AD7; Tue, 1 Feb 2005 11:26:45 +0100 (CET) Date: Tue, 1 Feb 2005 11:26:45 +0100 (CET) From: Imad Aad X-X-Sender: aad@icalxsrv11.epfl.ch To: Claudio Lavecchia Subject: Re: [manet] How to cause and measure the hidden terminal (or collisions)? In-Reply-To: <41FF5231.6060206@eurecom.fr> Message-ID: References: <41FF5231.6060206@eurecom.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Imad Aad List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d On Tue, 1 Feb 2005, Claudio Lavecchia wrote: > Hello you MANET guys, > > I have a challenging question for you: I am running some tests on a MANET > testbed composed of 4 nodes equipped of Dell Truemobile 1150 WLAN cards and > routed with OLSR. > I would like to do some performance measurements in presence of the hidden > terminal problem. Now I believe that causing the hidden terminal problem with > 4 nodes is almost impossible. Why?! 3 stations far enough from each other would make a good hidden node scenario, am I missing something? (don't forget to take the carrier sense threshold/range into consideration) > Is there anyone that knows how I could provoke the hidden terminal problem in > such conditions and measure its effects? Is there a way to measure > collisions that happen during a 802.11 communication? On a high level: measure the throughput drop with respect to a scenario with no hidden stations (but the same number of stations and connections) On a low level: use a station in monitor mode (if your card and card driver permit this), you'll be able to see which packets got ACKed and which ones did not. I'm sure there's plenty of other ways to monitor what's happening on the channel. imad _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 1 05:55:15 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13890 for ; Tue, 1 Feb 2005 05:55:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvvyr-0005pK-65 for manet-web-archive@ietf.org; Tue, 01 Feb 2005 06:14:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvve6-0004r4-OV; Tue, 01 Feb 2005 05:52:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvvZT-00042k-Fu for manet@megatron.ietf.org; Tue, 01 Feb 2005 05:47:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13262 for ; Tue, 1 Feb 2005 05:47:46 -0500 (EST) Received: from ovest.cce.unipr.it ([160.78.48.173] helo=smtp.unipr.it) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvvrb-0005dP-3P for manet@ietf.org; Tue, 01 Feb 2005 06:06:32 -0500 Received: from indio.tlc.unipr.it (indio.tlc.unipr.it [160.78.29.3]) by smtp.unipr.it (8.11.6/8.11.6) with ESMTP id j11Ainq04540 for ; Tue, 1 Feb 2005 11:44:49 +0100 From: Marco Date: Tue, 1 Feb 2005 11:49:51 +0100 User-Agent: KMail/1.5.1 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200502011149.51265.bragalini_m@tiscali.it> X-CCE-UniPR-MailScanner: Found to be clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Subject: [manet] Fwd: change Pt_ X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: quoted-printable =2D--------- Messaggio inoltrato ---------- Subject: change Pt_ Date: 11:49, marted=EC 1 febbraio 2005 =46rom: Marco To: ns-users@isi.edu Hy ns-users, I want modify Pt_ for a determined node, in C++' code. In Mac802.11 i have made a routine which compute the distance between tx no= de and rx node. For every distance, I have a corresponding value of power(pot). In wirelessphy I have made a second routine who set Pt_: inline double setPt(double pot){Pt_=3Dpot; return Pt_;} I call it in Mac802.11::send WirelessPhy* power; * * * pot=3D0.002; power->setPt(pot); * * * But when I run the simulations, I obtain a segmentation fault! Why? Thanks in advance, Marco =2D------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 1 09:49:44 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10727 for ; Tue, 1 Feb 2005 09:49:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvzdo-0003zO-I1 for manet-web-archive@ietf.org; Tue, 01 Feb 2005 10:08:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvzIe-00079C-2D; Tue, 01 Feb 2005 09:46:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvz8Z-0004oG-LG for manet@megatron.ietf.org; Tue, 01 Feb 2005 09:36:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09319 for ; Tue, 1 Feb 2005 09:36:14 -0500 (EST) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvzQk-0003Yo-61 for manet@ietf.org; Tue, 01 Feb 2005 09:55:02 -0500 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j11EZh6D007734; Tue, 1 Feb 2005 15:35:43 +0100 (CET) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id E048D3C31A; Tue, 1 Feb 2005 15:35:42 +0100 (MET) Message-ID: <41FF93BE.50807@eurecom.fr> Date: Tue, 01 Feb 2005 15:35:42 +0100 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Sherif M. ElRakabawy" Subject: Re: [manet] How to cause and measure the hidden terminal (orcollisions)? References: <000301c50847$acf78510$5810d981@reagan> In-Reply-To: <000301c50847$acf78510$5810d981@reagan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.eurecom.fr id j11EZh6D007734 X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Content-Transfer-Encoding: quoted-printable Thx Sherif, Your idea of disabling the RTS is interesting and leads me further in my=20 reasoning. Let me try to explain you what I would like to achieve: Let's imagine that I have three nodes in a row, say A,B and C. Node B=20 acts as a relay for traffic between A and C. Then we have a fourth node,=20 say node D. Node D is disturbing the communication between A and C by trying to jam=20 node B. What I would like to have is node B that from time to time fails in=20 forwarding packets that are directed from A to C. I tought that it would=20 be possible to achieve this using node D. If node A sends a packet to node B, but node B does not receive it=20 because node D starts talking to node B at the same time, that would be=20 enough for my purposes. In this sense I do not strictly need to mount an "hidden terminal"=20 scenario in the sense that for me physical separation of devices is not=20 mandatory. Now, if I understand correctly, if I apply your suggestion to the=20 scenario I just described, I could have node A talking to node C through=20 the relay of node B. Node D has disabled the RTS and hence it starts=20 talking to node B without sensing the media. What do I have to do to make sure that node B privileges reception of=20 packets from node D (the interfering node)? Do I have to play with the=20 transmission power? How do I measure the number of MAC ACKs received? is there any statistic=20 tool provided with WLAN cards? How do I disable RTS? I guess that this is an option of iwconfig? If you (or anyone else) could help me to advance on those questions that=20 would be of great help. Ciao Claudio Sherif M. ElRakabawy wrote: >Hi, > >If you disable RTS/CTS you can get hidden terminals with only 3 nodes .. >You can Measure the collisions on the MAC layer by counting the number >of >unsuccessful data packet transmissions, i.e. 4 transmissions without >receiving a >MAC ACK. You may compare the values you get with a case where there are >no=20 >hidden terminals, i.e. RTS/CTS is enabled. > >Regards > >Sherif > >-------------------------------------------- >Sherif M. ElRakabawy >University of Dortmund >Department of Computer Science Tel. +49 231 755 2690 >Mobile Computing Systems Group Fax. +49 231 755 2417 >August-Schmidt-Str. 12 >44227 Dortmund / Germany >WWW: http://mobicom.cs.uni-dortmund.de/~moustafa/ > > > =20 > >>-----Urspr=FCngliche Nachricht----- >>Von: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]=20 >>Im Auftrag von Claudio Lavecchia >>Gesendet: Tuesday, February 01, 2005 10:56 AM >>An: manet@ietf.org >>Betreff: [manet] How to cause and measure the hidden terminal=20 >>(orcollisions)? >> >> >>Hello you MANET guys, >> >>I have a challenging question for you: I am running some tests on a=20 >>MANET testbed composed of 4 nodes equipped of Dell Truemobile=20 >>1150 WLAN=20 >>cards and routed with OLSR. >>I would like to do some performance measurements in presence of the=20 >>hidden terminal problem. Now I believe that causing the=20 >>hidden terminal=20 >>problem with 4 nodes is almost impossible. >>Is there anyone that knows how I could provoke the hidden terminal=20 >>problem in such conditions and measure its effects? Is there=20 >>a way to=20 >>measure collisions that happen during a 802.11 communication? >> >>I hope my question is clear enough. Any contribution would be greatly=20 >>appreciated. >> >>Thx >> >>Claudio >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> =20 >> > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 00:01:55 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26825 for ; Wed, 2 Feb 2005 00:01:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwCwd-0003Oq-So for manet-web-archive@ietf.org; Wed, 02 Feb 2005 00:20:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwCbx-0005ow-W2; Tue, 01 Feb 2005 23:59:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwCb1-0005Uj-6b for manet@megatron.ietf.org; Tue, 01 Feb 2005 23:58:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26609 for ; Tue, 1 Feb 2005 23:58:29 -0500 (EST) From: vkumar@ece.iisc.ernet.in Received: from ece.iisc.ernet.in ([144.16.64.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwCtH-0003Kr-Pn for manet@ietf.org; Wed, 02 Feb 2005 00:17:25 -0500 Received: from sandbox.ece.iisc.ernet.in (sandbox.ece.iisc.ernet.in [144.16.64.8]) by ece.iisc.ernet.in (8.12.6/8.12.6) with ESMTP id j124xuSC049374; Wed, 2 Feb 2005 10:29:56 +0530 (IST) (envelope-from vkumar@ece.iisc.ernet.in) Received: from sandbox.ece.iisc.ernet.in (localhost.localdomain [127.0.0.1]) by sandbox.ece.iisc.ernet.in (8.12.10/8.12.10) with ESMTP id j124vuaa017554; Wed, 2 Feb 2005 10:27:56 +0530 Received: from localhost (vkumar@localhost) by sandbox.ece.iisc.ernet.in (8.12.10/8.12.10/Submit) with ESMTP id j124vurZ017550; Wed, 2 Feb 2005 10:27:56 +0530 X-Authentication-Warning: sandbox.ece.iisc.ernet.in: vkumar owned process doing -bs Date: Wed, 2 Feb 2005 10:27:56 +0530 (IST) To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.3 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: george@ece.iisc.ernet.in Subject: [manet] question in IEEE 802.11 std X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 What is "post backoff"? (I have found something about it in "IEEE 802.11e Wireless LAN for Quality of Service", Stefan Mangold etal., Proc. European Wireless (EW 2002)) Does 802.11 standard mention something about "post-backoff"? If so where? Also does NS2.27 implement "post-backoff"? What will happen if there is two backoffs (post-backoff and a pre-backoff)? i.e. If a node has already finished post-backoff and a packet arrives into its empty queue from higher layer and this packet finds the channel idle, then should it do another backoff before transmitting the packet OR should it transmit the packets without any backkoff ? Vinod Kumar M.E. Telecommunication IISc _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 00:56:57 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01844 for ; Wed, 2 Feb 2005 00:56:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwDnu-0004Tg-Ak for manet-web-archive@ietf.org; Wed, 02 Feb 2005 01:15:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwDQP-0003AH-NP; Wed, 02 Feb 2005 00:51:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwDPo-0002ue-RO for manet@megatron.ietf.org; Wed, 02 Feb 2005 00:51:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01301 for ; Wed, 2 Feb 2005 00:50:58 -0500 (EST) Received: from web60007.mail.yahoo.com ([216.109.116.245]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CwDi6-0004M1-GG for manet@ietf.org; Wed, 02 Feb 2005 01:09:55 -0500 Received: (qmail 95755 invoked by uid 60001); 2 Feb 2005 05:50:27 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=5CMrNmKLWROlqj9y42UmWwWVTsAB6JbUCrzLjQGo+5W/bTdDPtVQjMS3VIzt3+Md15Fzn+VMqAmN6eSGCgNK0HgV0dKjthbdIUgS+8Q7jrcgJ7O5s62Jvn7/cNSniX4tlbrer7OgFDBbjR8WA9TuMacXuEK5rlDKFuttbd9N2FU= ; Message-ID: <20050202055027.95753.qmail@web60007.mail.yahoo.com> Received: from [202.141.142.23] by web60007.mail.yahoo.com via HTTP; Tue, 01 Feb 2005 21:50:27 PST Date: Tue, 1 Feb 2005 21:50:27 -0800 (PST) From: Shahriar Shamil Uulu To: ns-users@isi.edu, manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA01301 Subject: [manet] Routing load X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: quoted-printable Dear All, I have written the perl script to calculate the normalized routing load but my results are very strange.Can anybody tell me is it right formula for my calculation which is given below? Note: i am using old format of tracing=20 ------------------------------------------------=20 1. I am getting the receives like: if the flags are "r" and "AGT" and "cbr" then recieves++. 2.I am getting routing packets like: if the flags are ("s" or "f") and "RTR" and ( "aodv" or "dsr" or "message") then routing++; 3. And i am getting nrload=3Drouting/receives 4. I am putting the results in to the file and drawing with xgraph, the x-axis it TIME(simulation time), and y-axis is nrload.=20 ------------------------------------------------=20 Please help me to clear this doubt=20 Thank you in advance ...=20 =3D=3D=3D=3D=3D Shahriar Shamil Uulu=20 Hyderabad Central University=20 M.Tech(Computer Science) email:shamilsons@yahoo.com website: http://shamilson.narod.ru =20 =09 __________________________________=20 Do you Yahoo!?=20 All your favorites on one personal page =96 Try My Yahoo! http://my.yahoo.com=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 10:52:05 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19892 for ; Wed, 2 Feb 2005 10:52:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwN5x-0003FD-C4 for manet-web-archive@ietf.org; Wed, 02 Feb 2005 11:11:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMgz-0007yx-BM; Wed, 02 Feb 2005 10:45:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMdw-0006qJ-FJ for manet@megatron.ietf.org; Wed, 02 Feb 2005 10:42:12 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18516 for ; Wed, 2 Feb 2005 10:42:07 -0500 (EST) Received: from nemo.cce.unipr.it ([160.78.48.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwMwI-0002rY-Nq for manet@ietf.org; Wed, 02 Feb 2005 11:01:12 -0500 Received: from eolo.tlc.unipr.it (eolo.tlc.unipr.it [160.78.29.95]) by smtp.unipr.it (8.11.6/8.11.6) with ESMTP id j12FfTD09161 for ; Wed, 2 Feb 2005 16:41:29 +0100 From: Marco Date: Wed, 2 Feb 2005 16:25:43 +0100 User-Agent: KMail/1.5.1 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200502021625.43181.bragalini_m@tiscali.it> X-CCE-UniPR-MailScanner: Found to be clean X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: quoted-printable Subject: [manet] Fwd: power control in mac X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: quoted-printable =2D--------- Messaggio inoltrato ---------- Subject: power control in mac Date: 16:25, mercoled=EC 2 febbraio 2005 =46rom: Marco To: ns-users@isi.edu Hi ns-users, i need a power control routine for mac802.11. Someone can help me,please? Thanks, Marco =2D------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 11:26:16 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23986 for ; Wed, 2 Feb 2005 11:26:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNd3-0004Ng-Vk for manet-web-archive@ietf.org; Wed, 02 Feb 2005 11:45:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwNA6-0000wX-Co; Wed, 02 Feb 2005 11:15:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwN6J-0007JA-8u for manet@megatron.ietf.org; Wed, 02 Feb 2005 11:11:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22230 for ; Wed, 2 Feb 2005 11:11:21 -0500 (EST) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNOc-0003se-Lu for manet@ietf.org; Wed, 02 Feb 2005 11:30:26 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j12GBEFe009424; Wed, 2 Feb 2005 11:11:14 -0500 (EST) Received: (from gateway [129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005020211111322740 ; Wed, 02 Feb 2005 11:11:13 -0500 Date: Wed, 2 Feb 2005 11:11:14 -0500 (EST) From: Yue Fang To: vkumar@ece.iisc.ernet.in Subject: Re: [manet] question in IEEE 802.11 std In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: manet@ietf.org, george@ece.iisc.ernet.in X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Hello, Vinod: In my understanding, there is just one backoff scheme in the standard and Ns2.27 do imprlent it. Ppl refer it to "post backoff" as the backoff after a packet has been transmitted in order to avoid the capture of the channel. while "pre backoff" refers to the backoff a node execute when it has packet to send but find channel is not idle. For the case you described, when the node find that the backoff counter is 0 and the channel is idle for DIFS, it can transmit immediately. Hope this helps Regards ----------------------------------- Yue Fang 227 Egan Research Building Dept. of Electrical & Computer Eng. Northeastern University Boston, MA, 02115 (tel) 617-373-3009 ----------------------------------- On Wed, 2 Feb 2005 vkumar@ece.iisc.ernet.in wrote: > What is "post backoff"? (I have found something about it in "IEEE 802.11e > Wireless LAN for Quality of Service", Stefan Mangold etal., Proc. European > Wireless (EW 2002)) > Does 802.11 standard mention something about "post-backoff"? If so where? > Also does NS2.27 implement "post-backoff"? What will happen if there is > two backoffs (post-backoff and a pre-backoff)? i.e. If a node has already > finished post-backoff and a packet arrives into its empty queue from > higher layer and this packet finds the channel idle, then should it do > another backoff before transmitting the packet OR should it transmit the > packets without any backkoff ? > > Vinod Kumar > M.E. Telecommunication > IISc > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 13:10:07 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07221 for ; Wed, 2 Feb 2005 13:10:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwPFZ-000803-2a for manet-web-archive@ietf.org; Wed, 02 Feb 2005 13:29:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwOsE-00039L-HV; Wed, 02 Feb 2005 13:05:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwOmh-0001gI-IR for manet@megatron.ietf.org; Wed, 02 Feb 2005 12:59:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06188 for ; Wed, 2 Feb 2005 12:59:18 -0500 (EST) Received: from mailg.surrey.ac.uk ([131.227.102.21]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CwP56-0007bu-05 for manet@ietf.org; Wed, 02 Feb 2005 13:18:25 -0500 Received: from ads33.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP) with ESMTP; Wed, 2 Feb 2005 17:40:36 +0000 Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136]) by ads33.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211); Wed, 2 Feb 2005 17:40:35 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 2 Feb 2005 17:40:35 -0000 Message-ID: <4A7C6FA2AB31194E80E13FE585F6A21232D609@EVS-EC1-NODE1.surrey.ac.uk> Thread-Topic: Java implementation of MANET routing protocols Thread-Index: AcUJTk0Wn/8iezTiRU6PFq269qCiUQ== From: "A.Malatras" To: manet X-OriginalArrivalTime: 02 Feb 2005 17:40:35.0874 (UTC) FILETIME=[4D4A4820:01C5094E] X-Spam-Score: 1.0 (+) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Subject: [manet] Java implementation of MANET routing protocols X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1186924326==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 This is a multi-part message in MIME format. --===============1186924326== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5094E.4D2930F3" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5094E.4D2930F3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, =20 I am looking for any Java implementations of MANET routing protocols = such as AODV, DSDV, OLSR etc. Having searched through google = extensively, the only one I could find was JAdhoc, Java AODV = implementation of University of Bremen.=20 =20 Could you give me some pointers to other related projects or inform me = of their inexistence? =20 Thanks in advance, =20 Apostolis =20 ---------------------------- Mr. Apostolos Malatras a.malatras@surrey.ac.uk=20 PhD Candidate Department of Electronic Engineering University Of Surrey ------_=_NextPart_001_01C5094E.4D2930F3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A=
Hi all,
=0A=
 
=0A=
I am looking for any Java implementations of MANET routing = protocols such =0A= as AODV, DSDV, OLSR etc. Having searched through google extensively, the = only =0A= one I could find was JAdhoc, Java AODV implementation of University of = Bremen. =0A=
=0A=
 
=0A=
Could you give me some pointers to other related projects or inform = me of =0A= their inexistence?
=0A=
 
=0A=
Thanks in advance,
=0A=
 
=0A=
Apostolis
=0A=
 
=0A=
----------------------------
=0A=
Mr. Apostolos Malatras
=0A= =0A=
PhD Candidate
=0A=
Department of Electronic Engineering
=0A=
University Of Surrey
=0A= =0A= =0A= ------_=_NextPart_001_01C5094E.4D2930F3-- --===============1186924326== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1186924326==-- From manet-bounces@ietf.org Wed Feb 2 13:23:03 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09163 for ; Wed, 2 Feb 2005 13:23:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwPS5-000089-UV for manet-web-archive@ietf.org; Wed, 02 Feb 2005 13:42:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwP3o-0006oj-C9; Wed, 02 Feb 2005 13:17:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwOvW-0003sE-2f for manet@megatron.ietf.org; Wed, 02 Feb 2005 13:08:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07050 for ; Wed, 2 Feb 2005 13:08:24 -0500 (EST) Received: from mailer.cacs.louisiana.edu ([130.70.72.22]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwPDt-0007vx-SW for manet@ietf.org; Wed, 02 Feb 2005 13:27:31 -0500 Received: from swamp450.cacs.louisiana.edu (swamp450.cacs.louisiana.edu [130.70.75.99]) by mailer.cacs.louisiana.edu (8.11.3/8.11.3) with ESMTP id j12I89414668 for ; Wed, 2 Feb 2005 12:08:10 -0600 (CST) Date: Wed, 2 Feb 2005 12:08:09 -0600 (CST) From: "Dr. Hongyi Wu" To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.1 (/) X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c Subject: [manet] ACM MONET Special Issue on SOFT RADIO-ENABLED HETEROGENEOUS WIRELESS NETWORKS X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172 [Apologies if you receive multiple copies of this CFP] ============================================================== ACM Mobile Networks and Applications (MONET) Special Issue On SOFT RADIO-ENABLED HETEROGENEOUS WIRELESS NETWORKS =============================================================== ********** Paper submission deadline: March 1, 2005 ********** With Guest Editors Dr. Guohong Cao Dept. of Computer Science and Engineering The Pennsylvania State University TEL: 814-863-1241 FAX: 814-865-3176 E-mail: gcao@cse.psu.edu Dr. Dapeng Wu Dept. of Electrical & Computer Engineering University of Florida TEL: 352-392-4954 FAX: 352-392-0044 E-mail: wu@ece.ufl.edu Dr. Hongyi Wu (contact) The Center for Advanced Computer Studies University of Louisiana at Lafayette TEL: 337-482-5779 FAX: 337-482-5791 E-mail: wu@cacs.louisiana.edu Dr. Junshan Zhang Department of Electrical Engineering Arizona State University TEL: 480-727-7389 FAX: 480-965-8325 E-mail: Junshan.Zhang@asu.edu With various network characteristics, a number of wireless systems have been developed over past years, targeting at different applications. While most of these wireless technologies are deployed independently for now, the service providers surely intend to own and operate overlaid heterogeneous wireless systems, which integrate multiple wireless technologies with partially overlapped coverage areas and provide ubiquitous network service to mobile users. Recent advances in reconfigurable computing have greatly advanced the design of soft radios, which enable the communication with many different radios with only a reconfiguration in software parameters. The maturation of soft radio technology is becoming one of the most important milestones for seamless integration of the heterogeneous wireless network. Serving as the "glue", the soft radio technology has its niche in in two folds: (1) the network infrastructure can be built upon soft radio, where the base stations are tunable to different frequency bands and serve as general access points for various mobile hosts (MHs), e.g., cellular handsets, laptops, and PDA's (Personal Digital Assistants); and (2) the MHs may employ soft radio, and accordingly, get access to various wireless systems (such as wireless LAN, cellular, IEEE 802.20, and IEEE 802.16), providing ubiquitous service for mobile users. An important design issue is to capitalize on the recent achievement in soft radio technology for providing improved and more efficient connectivity and service in heterogeneous wireless networks. With this special issue we aim at bringing together state-of-the-art contributions in this emerging area of soft radio-enabled heterogeneous wireless networks. We are seeking for papers reporting novel research or commercial/industrial experiences. These papers should be original, unpublished, and not currently under review by other conference, workshop, or journal. Topics of interest include, but are not limited to the following: - System optimization - Efficient spectrum allocation and management - Dynamic network topology discovery and optimization - Smart handoff and inter-system signaling - Quality of service in the heterogeneous networks - Routing and load balancing - Mobility management - System modeling and performance evaluation - Cognitive radio and testbed design * PUBLICATION SCHEDULE: o MANUSCRIPT DUE: March 1, 2005 o ACCEPTANCE NOTIFICATION: May 31, 2005 o FINAL MANUSCRIPT DUE: July 1, 2005 o EXPECTED PUBLICATION DATE: First Quarter, 2006 * SUBMISSION GUIDELINES: Authors should email an electronic (Postscript or PDF) copy of their papers to Dr. Hongyi Wu, wu@cacs.louisiana.edu, by March 1, 2005. Submissions should be limited to 20 double space pages excluding figures, graphs and illustrations. If email submission is impossible then six (6) copies of the paper (double-sided if possible) should be sent by the due date to: Dr. Hongyi Wu The Center for Advanced Computer Studies (CACS) University of Louisiana at Lafayette P.O. Box 44330 Lafayette, LA 70504-4330 Tel: 337-482-5779 All submissions will be reviewed following the standard procedure. --Hongyi ======================================================================== Dr. Hongyi Wu, Assistant Professor The Center for Advanced Computer Studies (CACS) University of Louisiana (UL) at Lafayette P.O. Box 44330, Lafayette, LA 70504-4330, U.S.A. Tel: 337-482-5779, Fax: 337-482-5791 E-mail: wu@cacs.louisiana.edu http://www.cacs.louisiana.edu/~wu ======================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 2 22:39:41 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18104 for ; Wed, 2 Feb 2005 22:39:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwY8q-0005au-Ry for manet-web-archive@ietf.org; Wed, 02 Feb 2005 22:58:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwXo5-0001SO-Iv; Wed, 02 Feb 2005 22:37:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwXm9-0000m2-0h for manet@megatron.ietf.org; Wed, 02 Feb 2005 22:35:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17720 for ; Wed, 2 Feb 2005 22:35:20 -0500 (EST) Received: from web20822.mail.yahoo.com ([216.136.227.135]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CwY4b-0005U0-66 for manet@ietf.org; Wed, 02 Feb 2005 22:54:31 -0500 Received: (qmail 92639 invoked by uid 60001); 3 Feb 2005 03:35:21 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=QQrYJ8Gcpau32J6C1J+2ziFj7RPWV69QilG2RYET00kWuLZI00GtY+PlcmqTbgzliY5+ea2N/BSocOsSDAeSgHk5VDrDQzAgp6Tmhehawx9AfN08ppPODO7GYjwb4BhJFs/YpaH9bCB9pi9l5SuKGtkx4DIahA37q58G+pSLfhY= ; Message-ID: <20050203033521.92637.qmail@web20822.mail.yahoo.com> Received: from [161.200.255.162] by web20822.mail.yahoo.com via HTTP; Wed, 02 Feb 2005 19:35:20 PST Date: Wed, 2 Feb 2005 19:35:20 -0800 (PST) From: Sigit Basuki Wibowo To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: [manet] Jitter simulation X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Dear All, I want to investigate jitter and routing in manet. I am confused in choosing the tools. Which one is the most suitable and easy among omnet++, ns, or pure C++ ? Thank you, Sigit B. Wibowo __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 00:51:52 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00230 for ; Thu, 3 Feb 2005 00:51:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwaCm-00018W-2a for manet-web-archive@ietf.org; Thu, 03 Feb 2005 01:11:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwZp4-0007t7-P2; Thu, 03 Feb 2005 00:46:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwZoj-0007g8-KM for manet@megatron.ietf.org; Thu, 03 Feb 2005 00:46:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29862 for ; Thu, 3 Feb 2005 00:46:08 -0500 (EST) Received: from web8406.mail.in.yahoo.com ([202.43.219.154]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cwa7B-0000z6-Qg for manet@ietf.org; Thu, 03 Feb 2005 01:05:21 -0500 Received: (qmail 15779 invoked by uid 60001); 3 Feb 2005 05:45:33 -0000 Message-ID: <20050203054532.15777.qmail@web8406.mail.in.yahoo.com> Received: from [210.212.228.8] by web8406.mail.in.yahoo.com via HTTP; Thu, 03 Feb 2005 05:45:32 GMT Date: Thu, 3 Feb 2005 05:45:32 +0000 (GMT) From: M koteswara rao To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 3.0 (+++) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 8bit Subject: [manet] doubt on LMS.... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mkoteswararao@gmail.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.0 (+++) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 8bit Hai, Iam doing project on LMS..in that i have created binary topology..but the problem is with lmssender..it's not generating any pkts.. ..plz send me your valuable suggestions ..for this problem.. waiting for your reply... urs koteswara rao. ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 05:45:30 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08847 for ; Thu, 3 Feb 2005 05:45:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwemw-0001AA-Pi for manet-web-archive@ietf.org; Thu, 03 Feb 2005 06:04:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CweOp-0005OE-0E; Thu, 03 Feb 2005 05:39:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CweI3-0003xg-52 for manet@megatron.ietf.org; Thu, 03 Feb 2005 05:32:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07882 for ; Thu, 3 Feb 2005 05:32:44 -0500 (EST) Received: from web61106.mail.yahoo.com ([216.155.196.108]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CweaZ-0000mY-PX for manet@ietf.org; Thu, 03 Feb 2005 05:51:57 -0500 Received: (qmail 40180 invoked by uid 60001); 3 Feb 2005 10:32:14 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KiVaF/kNxE+lPE53xFp9KxwrBSsEM0agnUElgFyTYsmW4wA4iL5c0qH+85ubxEDcrobU/X7forQ/4pILhWAdKjPW5khJ6KrO6E7t6CjnUcAqExjDw2sevAWKnKvEy5kAK4SGgOh3lrw6dVfR763jXd4rSAkv+Xulds/zDEbCzsI= ; Message-ID: <20050203103214.40178.qmail@web61106.mail.yahoo.com> Received: from [203.197.138.163] by web61106.mail.yahoo.com via HTTP; Thu, 03 Feb 2005 02:32:14 PST Date: Thu, 3 Feb 2005 02:32:14 -0800 (PST) From: ADHOC To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Subject: [manet] Routing in manets X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Hello!!! I've got few queries regarding routing in MANETs.... 1. How to find the lifetime of the nodes dynamically during simulation using GloMoSim? 2. How to send multiple multimedia packets from different sources to different destinations without dropping them? Is there any specific traffic generator for multimedia traffic? 3. How to preemptively discard lower precedence traffic? Your suggestions are welcome....Any links or reference to any web material would be appreciated too.. Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 06:27:34 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11836 for ; Thu, 3 Feb 2005 06:27:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwfRf-0002EP-Fk for manet-web-archive@ietf.org; Thu, 03 Feb 2005 06:46:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwf5D-0000C2-6C; Thu, 03 Feb 2005 06:23:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwf3p-0008F6-1h for manet@megatron.ietf.org; Thu, 03 Feb 2005 06:22:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11393 for ; Thu, 3 Feb 2005 06:22:06 -0500 (EST) Received: from berlin.ucdavis.edu ([169.237.104.158]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwfMN-00025i-17 for manet@ietf.org; Thu, 03 Feb 2005 06:41:19 -0500 Received: from tremex.ucdavis.edu (tremex.ucdavis.edu [169.237.104.172]) by berlin.ucdavis.edu (8.12.10/8.12.9/it-defang-5.2.0) with ESMTP id j13BM34Z020976 for ; Thu, 3 Feb 2005 03:22:03 -0800 (PST) Received: from tremex.ucdavis.edu (localhost [127.0.0.1]) by tremex.ucdavis.edu (8.12.10/8.12.9/UCD5.2.0) with ESMTP id j13BM3Xr021771 for ; Thu, 3 Feb 2005 03:22:03 -0800 (PST) Received: (from www@localhost) by tremex.ucdavis.edu (8.12.10/8.12.9/Submit) id j13BM3da021770; Thu, 3 Feb 2005 03:22:03 -0800 (PST) Date: Thu, 3 Feb 2005 03:22:03 -0800 (PST) Message-Id: <200502031122.j13BM3da021770@tremex.ucdavis.edu> To: manet@ietf.org From: "Fan Zhao" X-Errors-To: fanzhao@blue.ucdavis.edu X-Mailer: Geckomail-b16 X-Originating-IP: [128.120.178.196] X-User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Scanned-By: MIMEDefang 2.49 on 169.237.104.195 X-Spam-Score: 0.0 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Subject: [manet] Call for Paper: JSAC-MRNM X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES CALL FOR PAPERS IEEE Journal on Selected Areas in Communications MOBILE ROUTERS AND NETWORK MOBILITY http://www.argreenhouse.com/society/J-SAC/Calls/mobile_routers.html Network mobility support is concerned with managing the mobility of an entire network that is changing its point of attachment to the Internet and thus its reachability in the Internet topology. If network mobility is not explicitly supported by some mechanisms, existing sessions break and connectivity to the global Internet is lost. A mobile network is composed of Mobile Router(s) (MR) and Mobile Network Nodes (MNN) that can be fixed or mobile. There has been rapid development in network mobility support, i.e., providing Internet connectivity to the networks that move using mobile routers since the inception of Mobile IPv4 in 1996. Seamless Internet access in public transportation such as in trains and busses can be possible if mobile routers are used. Cars with low-power sensors seamlessly connected to the Internet constitute yet another example of networks which move. To date, some airline companies announced Internet connectivity support during commercial flights and this trend is expected to accelerate and cover most if not all flights. This issue is focused on modeling, analysis, and simulation of network mobility support protocols. We solicit papers presenting original and unpublished work including, but not limited to the following topics: * Modeling and Analysis of Network Mobility o Modeling, analysis and simulation of mobile router o Protocols for route optimization o Mobility issues inside a mobile network o Mobile IPv6 extensions for route optimization o Nested mobile networks o Multihomed mobile networks o Operational issues to deploy mobile networks o Auto-configuration for mobile networks o Mobile router support on cellular phone platforms * Services in the Networks that Move o Service advertisement and discovery protocols in networks that move o Specifications nad models of services for network mobility o Encryption and authentication in service access for network mobility * Security Issues in Network Mobility o Security analysis of present network mobility support protocols o Applications of AAA and EAP to network mobility o Interaction with security-enhanced modules in other layers (vertically) or other middle boxes (horizontally) Prospective authors should follow the IEEE J-SAC manuscript format described in the Information for Authors. Authors MUST submit their draft manuscripts through the EDAS peer review website, together with a short abstract (approximately 150 words) in the EDAS website form. Please note potential authors should create their own accounts through the EDAS peer review website before submitting manuscript(s). EDAS will accept manuscripts in PDF format only. There will be one round of reviewers and acceptance will be limited to those papers requiring only moderate revisions. The following timetable applies: Manuscript Submission: JUNE 1, 2005 Acceptance Notification: December 1, 2005 Final Manuscript Due: March 1, 2006 Publication: 3rd Quarter 2006 Guest Editorial Board: Behcet Sarikaya Computer Science Dept Univ of Northern British Columbia Prince George, BC Canada V2N 4Z9 sarikaya@unbc.ca S. Felix Wu Dept of Computer Science Univ of California at Davis Davis, CA 95616 USA wu@cs.ucdavis.edu Gopal Dommety Cisco Systems, Inc 170 West Tasman Dr San Jose, CA 95134-1706 USA gdommety@cisco.com Claude Castelluccia INRIA Rhône-Alpes ZIRST 655 Ave de l'Europe Montbonnot 38334 Saint Ismier cedex France claude.castelluccia@inria.fr Thierry Ernst Jun Murai Lab Keio Univ K-square Town Campus 1488-8 Ogura, Saiwai-ku, Kawasaki, Kanagawa 212-0054 Japan ernst@sfc.wide.ad.jp Charles E. Perkins Communication Systems Lab Nokia Research Center 313 Fairchild Dr Mountain View, CA 94943 USA charliep@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 08:08:54 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19276 for ; Thu, 3 Feb 2005 08:08:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwh1h-0005Dp-Qc for manet-web-archive@ietf.org; Thu, 03 Feb 2005 08:28:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwghH-0007Sf-UG; Thu, 03 Feb 2005 08:06:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwgbh-00066T-S6 for manet@megatron.ietf.org; Thu, 03 Feb 2005 08:01:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18139 for ; Thu, 3 Feb 2005 08:01:12 -0500 (EST) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwguG-0004rR-3M for manet@ietf.org; Thu, 03 Feb 2005 08:20:25 -0500 Received: from gw-out2.thalesgroup.com (200.3.3.6) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 41FC63A5001B5974 for manet@ietf.org; Thu, 3 Feb 2005 13:59:47 +0100 Received: from thalescan.corp.thales ([200.3.2.3]) by gw-out2 with InterScan Messaging Security Suite; Thu, 03 Feb 2005 13:59:36 +0100 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Thu, 03 Feb 2005 13:59:37 +0100 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 41EE6C7E000B8851 for manet@ietf.org; Thu, 3 Feb 2005 13:59:37 +0100 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Thu, 03 Feb 2005 13:59:37 +0100 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 41F0FA0100084162 for manet@ietf.org; Thu, 3 Feb 2005 13:59:11 +0100 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Thu, 03 Feb 2005 13:59:11 +0100 Received: by nodalnet.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Thu, 3 Feb 2005 14:01:32 +0100 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224EBFD@khephren.clb.tcfr.thales> To: manet@ietf.org Date: Thu, 3 Feb 2005 14:01:30 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.3 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: quoted-printable Subject: [manet] IEEE802.11 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: quoted-printable Hi all, Here is probably a dumb question but can anybody tell me if in = infrastructure mode the access point must compete with other stations = before relaying to its destination a frame just received ? More precisely, let's consider a 802.11 network with 2 stations and one = access point (every equipment "see" each other) : S1 --- AP --- S2 At time t0 : S1 needs to send a frame to S2. Before doing this, S1 uses = DCF to access the air interface. At time t1 : S1 sends its frame to AP. Now, when the AP has finished receiving the frame from S1, does it need = to use DCF to access the air interface and to relay this frame to S2 ? Or can the AP immediately relay the frame to S2 without competing for = access (using DCF) ? Rapha=EBl MASSIN _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 11:04:51 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09358 for ; Thu, 3 Feb 2005 11:04:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwjm1-0002xk-HE for manet-web-archive@ietf.org; Thu, 03 Feb 2005 11:24:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwjG5-0007Z7-9S; Thu, 03 Feb 2005 10:51:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwjBF-0004AQ-2O for manet@megatron.ietf.org; Thu, 03 Feb 2005 10:46:05 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06292 for ; Thu, 3 Feb 2005 10:46:02 -0500 (EST) Received: from aplesliberty.dom1.jhuapl.edu ([128.244.198.134]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwjTo-000263-Q7 for manet@ietf.org; Thu, 03 Feb 2005 11:05:18 -0500 X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] IEEE802.11 Date: Thu, 3 Feb 2005 10:45:24 -0500 Message-ID: <0F5AC32D8E455545AD0349BA8400A3CA1B04D1@aplesliberty.dom1.jhuapl.edu> Thread-Topic: [manet] IEEE802.11 Thread-Index: AcUJ8Ynap+hg4ZNrRQa/752pt+pSuAAFYz6Q From: "Farrag, Osama" To: , X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: quoted-printable The AP uses PCF instead of DCF, which gives the AP priority over other = nodes required to use DCF. Osama Farrag -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Thursday, February 03, 2005 8:02 AM To: manet@ietf.org Subject: [manet] IEEE802.11 Hi all, Here is probably a dumb question but can anybody tell me if in = infrastructure mode the access point must compete with other stations = before relaying to its destination a frame just received ? More precisely, let's consider a 802.11 network with 2 stations and one = access point (every equipment "see" each other) : S1 --- AP --- S2 At time t0 : S1 needs to send a frame to S2. Before doing this, S1 uses = DCF to access the air interface. At time t1 : S1 sends its frame to AP. Now, when the AP has finished receiving the frame from S1, does it need = to use DCF to access the air interface and to relay this frame to S2 ? Or can the AP immediately relay the frame to S2 without competing for = access (using DCF) ? Rapha=EBl MASSIN _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 11:20:16 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10995 for ; Thu, 3 Feb 2005 11:20:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwk0v-0003Ws-Kw for manet-web-archive@ietf.org; Thu, 03 Feb 2005 11:39:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwjXi-0000O6-SM; Thu, 03 Feb 2005 11:09:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwjMV-00056G-W8 for manet@megatron.ietf.org; Thu, 03 Feb 2005 10:57:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07889 for ; Thu, 3 Feb 2005 10:57:41 -0500 (EST) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwjf5-0002fh-Sq for manet@ietf.org; Thu, 03 Feb 2005 11:16:57 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 3 Feb 2005 16:57:28 +0100 Message-ID: <9F1223587A755D47805AECAB7ECAF5D901F53BE7@swing.cefriel.it> Thread-Topic: Transmission buffer size Thread-Index: AcUKCQ1UjIlUa6thSiqj8wzyX941nw== From: "Giorgio Mulas" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable Subject: [manet] Transmission buffer size X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: quoted-printable Hi, Is it possible to measure the size and the load of the transmission buffer in PCMCIA WLAN cards under Linux? Any help appreciated Giorgio ------------------------------------------ Giorgio Mulas | Researcher CEFRIEL - Politecnico di Milano Via Fucini, 2 * 20133 Milano (Italy) p. +39 02 23954 265 f. +39 02 23954 465 e. giorgio.mulas@cefriel.it _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 12:22:52 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17712 for ; Thu, 3 Feb 2005 12:22:52 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwkzY-0005jX-8d for manet-web-archive@ietf.org; Thu, 03 Feb 2005 12:42:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwkUH-00042F-KC; Thu, 03 Feb 2005 12:09:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwk8X-00051m-Ao for manet@megatron.ietf.org; Thu, 03 Feb 2005 11:47:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14153 for ; Thu, 3 Feb 2005 11:47:18 -0500 (EST) Received: from panther.mail.utk.edu ([160.36.178.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwkR6-0004Wg-Dz for manet@ietf.org; Thu, 03 Feb 2005 12:06:34 -0500 Received: from [160.36.248.52] (pigeon.nomad.utk.edu [160.36.248.52]) (authenticated bits=0) by panther.mail.utk.edu (8.13.3/8.13.3) with ESMTP id j13GlDMU020403; Thu, 3 Feb 2005 11:47:13 -0500 Message-ID: <4202553B.4030101@utk.edu> Date: Thu, 03 Feb 2005 11:45:47 -0500 From: Hairong Qi User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: tccc@cs.columbia.edu, manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Auth: auth_authen=hqi X-Spam-Status: Message recipients not local. X-Scanned-By: MIMEDefang 2.45 X-Spam-Score: 0.0 (/) X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196 Content-Transfer-Encoding: 7bit Subject: [manet] Deadline Extension (02/10/05) - WICON Workshop on Information Fusion and Dissemination in Wireless Sensor Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Content-Transfer-Encoding: 7bit [Apologies if you receive multiple copies of this email] =========================================================== WICON Workshop on Information Fusion and Dissemination in Wireless Sensor Networks July 10 - 14, 2005 Budapest, Hungary http://www.sensorfusion.org =========================================================== *** Deadline extended to Feb. 10, 2005. *** Workshop Chair: Dr. Pratik K. Biswas Penn State University / Applied Research Laboratory (ARL)/ pkb3@psu.edu The convergence of internet, wireless communications, and information processing technologies with techniques for miniaturization has opened up new vistas of research for sensor networks. Emerging technologies for sensing and pervasive computing have placed sensor networks at the threshold of a period of major growth. It has extended information fusion and dissemination in sensor networks from data aggregation, association and monitoring of interactions among hardware and software entities in ubiquitous computing environments to intelligent information processing for the next generation wireless internet. For the emerging hybrid sensor networks, information fusion can help in the seamless integration of smart sensors and actuators, devices and capabilities, software and hardware agents, sensor network applications and sensor nodes, distributed and collaborative algorithms, different communication technologies, different networking architectures, etc., all over wireless or wire-line backbones. The Wireless Internet Conference (WICON 2005) has planned a special workshop devoted to information fusion and dissemination in the broader context of emerging sensor networks. The aim of this workshop is to provide a focal point for recent advances in this foundational area of information fusion and dissemination for sensor networks across different paradigms, disciplines and technologies. Submitted papers should report new contributions underpinning fusion of data and knowledge in distributed sensor networks from various perspectives. Papers will be fully refereed and accepted papers will be published in the conference proceedings. Selected papers from this workshop will also be recommended for possible publication in Information Fusion, an Elsevier Publication. Topics appropriate for this workshop include (but are not necessarily restricted to): . Programmable architectures and infrastructure for sensor networks . Scalable, adaptive, self-organizing and self-healing architectures for sensor networks . Multi-sensor, multi-source information networking architectures for sensor networks . Intelligent, autonomous, seamless, pervasive, multi-sensor information processing over wireless or wire-line internet backbone for distributed sensor networks . Information fusion and dissemination in mesh networks . Data collection, compression/decompression and mining strategies in sensor networks . Distributed database processing in sensor networks . In-network processing, aggregation and data association in sensor networks . Transport, Routing, Physical and Link layer protocol development using information fusion . Cross layer protocol design and development using information fusion . Energy and mobility management algorithms for sensor networks . Node localization in sensor networks . Information fusion for resource allocation and Quality of Service in sensor networks . Integration of fusion and learning in sensor networks . Integration of software and hardware agents for sensor network applications . Service discovery, creation and provisioning for sensor networks through wireless or wire-line internet . Mechanisms for authenticated, secure communication and data fusion in sensor networks . Integrated test-beds, experiments, algorithms and measurements . Real-world sensor network applications addressing fusion of data and knowledge Authors should prepare the manuscript as per the guidelines for authors described in the frame under "Submission" at the conference website (http://www.wicon.org). Manuscript submission should be done electronically through the conference website. Deadline for Submission: January 30, 2005 (extended to Feb. 10, 2005) Workshop Committees General Chair: Pratik Biswas (Penn State University /Applied Research Laboratory, USA) Organizing/Steering Committee: Buyurman Baykal (Middle East Technical University, Turkey) Pratik Biswas (Penn State University/Applied Research Laboratory, USA) Krishnendu Chakraborty (Duke University, USA) Hairong Qi (University of Tennessee at Knoxville, USA) Yi Zou (Duke University, USA) Technical Program Committee: Buyurman Baykal (Middle East Technical University, Turkey) Christian Bettstetter (DoCoMo Euro-Labs, Germany) Steve Buckley (IBM T.J. Watson Research Center, USA) Andrew Campbell (Columbia University, USA) Krishnendu Chakraborty (Duke University, USA) Imrich Chlamtac (Create-Net /University of Trento/ University of Texas at Dallas, Italy/USA) Marco Conti (Institute for Informatics and Telematics (IIT/CNR), Italy) Belur V. Dasarathy (Information Fusion Consultant, USA) Suprakash Datta (York, Canada) Stephen Hailes (University College London, UK) Jennifer Hou (University of Illinois at Urbana Champaign, USA) Dinesh Kumar (Royal Melbourne Institute of Technology, Australia) Subrata Mazumdar (Avaya Labs, USA) Frank Mueller (North Carolina State University at Raleigh, USA) Yuji Oie (Kyushu Institute of Technology, Japan) Himanshu Pota (University of New South Wales, Australia) Hairong Qi (University of Tennessee at Knoxville, USA) Nageswara Rao (Oak Ridge National Laboratory, USA) Csaba Szabo (Budapest University of Technology and Economics, Hungary) Jie Wu (Florida Atlantic University, USA) Yanyong Zhang (Rutgers University, USA) Taieb Znati (University of Pittsburgh, USA) -- Hairong Qi, Assistant Professor Electrical and Computer Engineering Department University of Tennessee Knoxville, TN 37996 Tel: 865-974-8527, Fax: 865-974-5483 http://panda.ece.utk.edu/~hqi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 3 18:53:00 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08761 for ; Thu, 3 Feb 2005 18:53:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwr59-0004do-Ak for manet-web-archive@ietf.org; Thu, 03 Feb 2005 19:12:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwqU7-0003oR-1m; Thu, 03 Feb 2005 18:34:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwqPA-000221-5l for manet@megatron.ietf.org; Thu, 03 Feb 2005 18:28:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06352 for ; Thu, 3 Feb 2005 18:28:52 -0500 (EST) Received: from evaki.its.uow.edu.au ([130.130.68.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwqhn-0003x1-RT for manet@ietf.org; Thu, 03 Feb 2005 18:48:12 -0500 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by evaki.its.uow.edu.au with esmtp (Exim 4.43) id 1CwqOz-0001kZ-7v; Fri, 04 Feb 2005 10:28:45 +1100 Received: from eros.snrc.uow.edu.au (eros.snrc.uow.edu.au [130.130.10.74]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AQL11607; Fri, 4 Feb 2005 10:28:44 +1100 (EST) From: Mehran Abolhasan To: manet@ietf.org Subject: Re: [manet] Routing in manets Date: Fri, 4 Feb 2005 10:28:44 +1100 User-Agent: KMail/1.7.1 References: <20050203103214.40178.qmail@web61106.mail.yahoo.com> In-Reply-To: <20050203103214.40178.qmail@web61106.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502041028.44683.mehrana@uow.edu.au> X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit On Thu, 3 Feb 2005 09:32 pm, ADHOC wrote: > Hello!!! > > I've got few queries regarding routing in MANETs.... > > 1. How to find the lifetime of the nodes dynamically > during simulation using GloMoSim? Not sure what you mean exactly by lifetime? if you mean battery power, then you have to set a limit yourself in glomosim, by default there is no limit. If you mean how long a node has been turned on, then you would have to create a lifetime (on and off time) yourself. > > 2. How to send multiple multimedia packets from > different sources to different destinations without > dropping them? Is there any specific traffic generator > for multimedia traffic? There is a number of example files in the scenario directory in glomosim, they show you how to set different types of traffic, such as CBR in the app.config file. If you want any specific types of traffic you have to create a traffic generating file youself. Go to the applications folder and implement it there. > > 3. How to preemptively discard lower precedence > traffic? Again you have to implement a strategy yourself in glomosim. you could do this at the networking layer or MAC layer, depending on what you want to do. Hope that helped. Regards, -- Mehran Abolhasan B.E Computer, PhD Research Fellow Telecommunications and IT Research Institute (TITR) University of Wollongong Northfields Avenue, NSW, 2522, Australia Phone: +61 2 4221 3347 Fax: +61 2 4221 3277 http://www.titr.uow.edu.au/~mehran Email 1: mehrana@uow.edu.au Email 2: mehran@titr.uow.edu.au _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 4 07:52:42 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21544 for ; Fri, 4 Feb 2005 07:52:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx3Fm-000076-UI for manet-web-archive@ietf.org; Fri, 04 Feb 2005 08:12:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx2tL-0007tq-IZ; Fri, 04 Feb 2005 07:48:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx2eG-0004PO-MX for manet@megatron.ietf.org; Fri, 04 Feb 2005 07:33:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20286 for ; Fri, 4 Feb 2005 07:33:19 -0500 (EST) Received: from web20922.mail.yahoo.com ([216.136.224.136]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cx2x1-0007ur-J8 for manet@irtf.org; Fri, 04 Feb 2005 07:52:45 -0500 Received: (qmail 32109 invoked by uid 60001); 4 Feb 2005 12:33:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=X+zvZHpZ07NCy4iBcdT+gLjBjx6gbxn0VYmNsPnhsh/oTr9e5/sIvuWfAAKqhy2TLZAa6iO+l1bgakdAHu4HhKJML+QQXyzG/VsmmUJDoLGRtqmJsOfXvDqKn7O8qxr67bPj9aM2laLa5E0Z5dedoHytl6qLVmwZbpeYVkqyXGk= ; Message-ID: <20050204123317.32107.qmail@web20922.mail.yahoo.com> Received: from [203.208.193.197] by web20922.mail.yahoo.com via HTTP; Fri, 04 Feb 2005 04:33:17 PST Date: Fri, 4 Feb 2005 04:33:17 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] Pervasive computing and Sensor networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0982629924==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 --===============0982629924== Content-Type: multipart/alternative; boundary="0-2032743253-1107520397=:31167" --0-2032743253-1107520397=:31167 Content-Type: text/plain; charset=us-ascii Hi, Can anybody give me some references to research groups working in this area. Even I searched for publications in digital libraries. I found very few publications. I am working on a research problem in this area. If you are working in a closely related area, please let me know. Sincerely, Praveen. --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' --0-2032743253-1107520397=:31167 Content-Type: text/html; charset=us-ascii
Hi,
 Can anybody give me some references to research groups working in this area. Even I searched for publications in digital libraries. I found very few publications. I am working on a research problem in this area. If you are working in a closely related area, please let me know.
 
Sincerely,
Praveen.

Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term' --0-2032743253-1107520397=:31167-- --===============0982629924== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0982629924==-- From manet-bounces@ietf.org Sat Feb 5 06:28:44 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22010 for ; Sat, 5 Feb 2005 06:28:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxOQI-0005Lc-8l for manet-web-archive@ietf.org; Sat, 05 Feb 2005 06:48:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxO54-00061B-Rn; Sat, 05 Feb 2005 06:26:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxNyL-0004Xg-EN for manet@megatron.ietf.org; Sat, 05 Feb 2005 06:19:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21447 for ; Sat, 5 Feb 2005 06:19:26 -0500 (EST) Received: from web60005.mail.yahoo.com ([216.109.116.228]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CxOHG-0005Ar-E1 for manet@ietf.org; Sat, 05 Feb 2005 06:39:05 -0500 Received: (qmail 38615 invoked by uid 60001); 5 Feb 2005 11:18:54 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=eW3aPH7GtU41soUgaVZbPHpypln0uVZgUMamHbJwsRQWP+R8SIujRLhomdA7VPpOuFCZwtNSIEWx/nOZ8FZv4pCVDo/TSOd203GFxatBdI3nqrpri0iFg+qqAPeBgohQmK2E/VChZckmwLTuDbv5Hp+vmnwtSbHqb4HaF2gIukw= ; Message-ID: <20050205111854.38613.qmail@web60005.mail.yahoo.com> Received: from [202.141.142.23] by web60005.mail.yahoo.com via HTTP; Sat, 05 Feb 2005 03:18:54 PST Date: Sat, 5 Feb 2005 03:18:54 -0800 (PST) From: Shahriar Shamil Uulu To: NS Mailing , Manet Mailing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA21447 Subject: [manet] Performance of DSR and DSDV ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable Dear All, I have simulated DSR and DSDV under (FC-2,P-4, RAM-256 ns-2.27-allinone) the=20 Simulation time is 900 seconds, pause time is: 2-8, rate is 4 p/s max speed is 0-15m/s=20 after getting the trace files i ma claculating the performance metrics like (packet delivary ration, average delay etc.). After drawing the graph for packet delivery ration the DSR performing well for just 100 seconds and after that degrading very fast till 50% and being constant, comming to the DSDV is it performing bad 100 second but after that rising till 60% abd being constant. Can anybody tell me why its like that ? Maybe i have to configure some parameters ? Please if anybody has solved this problem reply me. Thank you in advance =20 =09 __________________________________=20 Do you Yahoo!?=20 All your favorites on one personal page =96 Try My Yahoo! http://my.yahoo.com=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Feb 5 16:59:38 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03109 for ; Sat, 5 Feb 2005 16:59:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxYGw-0000Uz-MJ for manet-web-archive@ietf.org; Sat, 05 Feb 2005 17:19:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxXvi-0006GT-Bf; Sat, 05 Feb 2005 16:57:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxXui-000673-9w for manet@megatron.ietf.org; Sat, 05 Feb 2005 16:56:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02756 for ; Sat, 5 Feb 2005 16:56:21 -0500 (EST) Received: from gehry.upc.es ([147.83.2.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxYDj-0000Pp-CL for manet@ietf.org; Sat, 05 Feb 2005 17:16:05 -0500 Received: from gehry.upc.es (localhost.localdomain [127.0.0.1]) by gehry.upc.es (8.13.0/8.13.0) with ESMTP id j15LtkY0015378 for ; Sat, 5 Feb 2005 22:55:46 +0100 Received: from ackerman.upc.es (ackerman.upcnetadm.upcnet.es [147.83.2.243]) by gehry.upc.es (8.13.0/8.13.0) with ESMTP id j15LpeWB014762 for ; Sat, 5 Feb 2005 22:51:40 +0100 Received: from [127.0.0.1] ([80.102.109.55]) by ackerman.upc.es (Lotus Domino Release 5.0.12) with ESMTP id 2005020522513993:17147 ; Sat, 5 Feb 2005 22:51:39 +0100 Message-ID: <42053FEA.9090903@estudiant.upc.edu> Date: Sat, 05 Feb 2005 22:51:38 +0100 From: =?ISO-8859-1?Q?=22Xavi_Mantec=F3n_=28UPCNet=29=22?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: es-es, es MIME-Version: 1.0 To: manet@ietf.org X-MIMETrack: Itemize by SMTP Server on Ackerman/UPC(Release 5.0.12 |February 13, 2003) at 05/02/2005 22:51:40, Serialize by Router on Ackerman/UPC(Release 5.0.12 |February 13, 2003) at 05/02/2005 22:51:40, Serialize complete at 05/02/2005 22:51:40 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: 1.1 (+) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Subject: [manet] Has anybody worked with FreeBSD ATCP implementation? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit Hi to all, I am trying to implement ATCP in FreeBSD 4.2. Well, I'm in contact with one of the co-authors of the implementation, but he doesn't know how to help me. I've installed it, with and without ALTQ (if I remove ALTQ, I remove the parts of the ATCP code which refers to it), and it doesn't work. When I attempt to stablish a TCP connection, FreeBSD crashes giving me this message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xc0372870 frame pointer = 0x10:0xc0372890 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1 def32 1 ,gran 1 processor eflags = interrupt enabled, rsume, IOPL = 0 current process = idle interrupt mask = trap number =12 panic: page fault rebooting.... Has anybody succesfully implemented ATCP? I am using FreeBSD 4.2, if I implement ALTQ I use the FreeBSD 4.2 patch, and ATCP is implemented in FreeBSD 4.2, so, why it's not working? I've made a google search and it seems that nobody has used ATCP, except simulating in NS2, so I don't know if it has ever really worked fine. Thanks in advance, Xavi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 6 14:39:00 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19749 for ; Sun, 6 Feb 2005 14:39:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxsYZ-0004LW-1H for manet-web-archive@ietf.org; Sun, 06 Feb 2005 14:58:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxsBQ-0006C8-EW; Sun, 06 Feb 2005 14:35:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cxs9d-0005qh-4x for manet@megatron.ietf.org; Sun, 06 Feb 2005 14:33:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18851 for ; Sun, 6 Feb 2005 14:33:08 -0500 (EST) Received: from web20925.mail.yahoo.com ([216.136.224.142]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CxsSr-00049s-6r for manet@irtf.org; Sun, 06 Feb 2005 14:53:02 -0500 Received: (qmail 54853 invoked by uid 60001); 6 Feb 2005 19:33:06 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=qyJo5lMAT+4ciWeVQh4RiXVfdMW+x7eqaT/9lEC8kLzgtDFGRd1wcGSXE4tt912/7ktoIbGxslvR/qTUFC1yAL2RzLNr9BL00ulxUZq/uoDixF4qwbwNzREAVL0Ue6AZYa+23bGCG3POr6BqUsS3DvoRv+UJrtc5xh3Jsywdilk= ; Message-ID: <20050206193305.54851.qmail@web20925.mail.yahoo.com> Received: from [203.208.193.197] by web20925.mail.yahoo.com via HTTP; Sun, 06 Feb 2005 11:33:05 PST Date: Sun, 6 Feb 2005 11:33:05 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 1.0 (+) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Subject: [manet] interesting research problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1355164999==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e --===============1355164999== Content-Type: multipart/alternative; boundary="0-870229515-1107718385=:54780" --0-870229515-1107718385=:54780 Content-Type: text/plain; charset=us-ascii Hi, I am doing research independently. I hope bio-sensing is a potential future commercial application of Mobile and wireless networks. A biosensor is an analytical device composed of a biological sensing element (enzyme, receptor antibody or DNA) in intimate contact with a physical transducer (optical, mass or electrochemical) which together relate the concentration of an analyte to a measurable electrical signal. Consider the problem of integrating bio-sensor nodes into conventional sensor networks. There are salient benefits of using bio-sensors over electronic sensors. 1. Can anybody give me some hints on the research challenges from the networking point of view if we integrate bio-sensors into existing conventional sensor networks. 2. What are the research issues associated with this novel sensor network. Research can be done to provide a model or system architecture for a sensor network which consists of Bio-Sensor nodes. If anybody is interested in this topic and if your time permits, I want to initiate a discussion. Please let me know your opinion on this research problem. Waiting for your comments and suggestions, Sincerely, Praveen. --------------------------------- Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. --0-870229515-1107718385=:54780 Content-Type: text/html; charset=us-ascii

Hi,

 I am doing research independently. I hope bio-sensing is a potential future commercial application of Mobile and wireless networks.

 

A biosensor is an analytical device composed of a biological sensing element (enzyme, receptor antibody or DNA) in intimate contact with a physical transducer (optical, mass or electrochemical) which together relate the concentration of an analyte to a measurable electrical signal. 

 

Consider the problem of integrating bio-sensor nodes into conventional sensor networks. There are salient benefits of using bio-sensors over electronic sensors.

 

1. Can anybody give me some hints on the research challenges from the networking point of view if we integrate bio-sensors into existing conventional sensor networks.

 

2. What are the research issues associated with this novel sensor network.

 

Research can be done to provide a model or system architecture for a sensor network which consists of Bio-Sensor nodes. If anybody is interested in this topic and if your time permits, I want to initiate a discussion. Please let me know your opinion on this research problem.

 

Waiting for your comments and suggestions,

Sincerely,

Praveen.

 

 

 

 

 

 

 

Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard. --0-870229515-1107718385=:54780-- --===============1355164999== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1355164999==-- From manet-bounces@ietf.org Mon Feb 7 02:50:48 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02418 for ; Mon, 7 Feb 2005 02:50:48 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy3yr-0001Ch-UW for manet-web-archive@ietf.org; Mon, 07 Feb 2005 03:10:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy3dJ-0007VX-Ig; Mon, 07 Feb 2005 02:48:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy3c7-0007Jz-Ct for manet@megatron.ietf.org; Mon, 07 Feb 2005 02:47:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02160 for ; Mon, 7 Feb 2005 02:47:17 -0500 (EST) Received: from web52806.mail.yahoo.com ([206.190.39.170]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cy3vQ-00018Q-V7 for manet@irtf.org; Mon, 07 Feb 2005 03:07:19 -0500 Received: (qmail 30686 invoked by uid 60001); 7 Feb 2005 07:46:45 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=4GiT6vDZkgIeQyYn886srq0X63slQ8Jd57PBabr9Oxh7lrKOiKuy+gzOJmQiTa+4NQi0IsuLHaiDAJeiAHvkMuEg2LZ26EoEtQiJPiB307+AO8jGRFm4TEZ/j9bw0hYH49leBxc2/GAWgzSlSALwutf/xZ6MAGKGc3MiVh15zJo= ; Message-ID: <20050207074645.30684.qmail@web52806.mail.yahoo.com> Received: from [161.200.255.163] by web52806.mail.yahoo.com via HTTP; Sun, 06 Feb 2005 23:46:45 PST Date: Sun, 6 Feb 2005 23:46:45 -0800 (PST) From: pakorn kulsirimongkol To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Subject: [manet] the beacon mechanism in network layer X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1792350344==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --===============1792350344== Content-Type: multipart/alternative; boundary="0-384869760-1107762405=:30117" --0-384869760-1107762405=:30117 Content-Type: text/plain; charset=us-ascii Dear, sir pls tell me the beacon mechanism in network layer. Is beacon regularly sent every time? nodes in the network must have a time out for waiting beacon right? what is time out of beacon? what is the information in beacon packet? node, how to know a connectivity of other nodes which it receive beacon is bidirectional link. best regard, add --------------------------------- Do you Yahoo!? Yahoo! Mail - You care about security. So do we. --0-384869760-1107762405=:30117 Content-Type: text/html; charset=us-ascii
Dear, sir
      pls tell me the beacon mechanism in network layer.
      Is beacon regularly sent every time?
      nodes in the network must have a time out for waiting beacon right?
      what is time out of beacon?
      what is the information in beacon packet?
      node, how to know a connectivity of other nodes which it receive beacon is bidirectional link.
 
best regard,
add


Do you Yahoo!?
Yahoo! Mail - You care about security. So do we. --0-384869760-1107762405=:30117-- --===============1792350344== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1792350344==-- From manet-bounces@ietf.org Mon Feb 7 03:43:03 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06318 for ; Mon, 7 Feb 2005 03:43:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy4nS-0002Sf-8z for manet-web-archive@ietf.org; Mon, 07 Feb 2005 04:03:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy4RS-0005uL-32; Mon, 07 Feb 2005 03:40:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy4JI-0004xM-Hm for manet@megatron.ietf.org; Mon, 07 Feb 2005 03:31:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05695 for ; Mon, 7 Feb 2005 03:31:53 -0500 (EST) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy4cb-00026c-HQ for manet@irtf.org; Mon, 07 Feb 2005 03:51:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] the beacon mechanism in network layer Date: Mon, 7 Feb 2005 09:31:39 +0100 Message-ID: <9F1223587A755D47805AECAB7ECAF5D901F53EC0@swing.cefriel.it> Thread-Topic: [manet] the beacon mechanism in network layer Thread-Index: AcUM6oabsYd7dKd7Si2AD7u4lgKRZAAAyQfA From: "Giorgio Mulas" To: "pakorn kulsirimongkol" , X-Spam-Score: 0.5 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0018390214==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff This is a multi-part message in MIME format. --===============0018390214== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C50CEF.733FDB8D" This is a multi-part message in MIME format. ------_=_NextPart_001_01C50CEF.733FDB8D Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, hereunder some considerations about your questions. - beaconing mechanisms are needed in order to discover network topology, = especially when topology may change in an unpredictable way. - of course beacons are sent on a regular basis. A rule of thumb should = be: the higher the topology change rate (due e.g. to nodes' mobility) = the higher the beaconing rate. - the simplest information in the beacon packet is "here I am!" =3D> you = can translate it, for example, in an IP address. - In theory wireless links are bi-directional, in practice no. An = acknowledgment mechanism could be a solution. =20 hope this helps =20 Giorgio -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of pakorn kulsirimongkol Sent: luned=EC 7 febbraio 2005 8.47 To: manet@irtf.org Subject: [manet] the beacon mechanism in network layer Dear, sir pls tell me the beacon mechanism in network layer.=20 Is beacon regularly sent every time? nodes in the network must have a time out for waiting beacon = right? what is time out of beacon? what is the information in beacon packet? node, how to know a connectivity of other nodes which it receive = beacon is bidirectional link. =20 best regard, add _____ =20 Do you Yahoo!? Yahoo! = Mail - You care about security. = So do we. ------_=_NextPart_001_01C50CEF.733FDB8D Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Hi,
hereunder=20 some considerations about your questions.
- beaconing mechanisms are needed in order to = discover=20 network topology, especially when topology may change in an = unpredictable=20 way.
- of = course=20 beacons are sent on a regular basis. A rule of thumb should = be: the=20 higher the topology change rate (due e.g. to = nodes' mobility) the=20 higher the beaconing rate.
- the simplest information in the beacon = packet is "here=20 I am!" =3D> you can translate it, for example, in an IP=20 address.
- In theory wireless links are bi-directional, = in=20 practice no. An acknowledgment mechanism could be a=20 solution.
 
hope=20 this helps
 
    = Giorgio
-----Original Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of = pakorn kulsirimongkol
Sent: luned=EC 7 febbraio 2005=20 8.47
To: manet@irtf.org
Subject: [manet] the = beacon=20 mechanism in network layer

Dear, sir
      pls tell me the beacon mechanism = in=20 network layer.
      Is beacon regularly sent every = time?
      nodes in the network must have a = time out=20 for waiting beacon right?
      what is time out of beacon?
      what is the information in beacon=20 packet?
      node, how to know a connectivity = of other=20 nodes which it receive beacon is bidirectional link.
 
best regard,
add


Do you Yahoo!?
Yahoo!=20 Mail - You care about security. So do = we. ------_=_NextPart_001_01C50CEF.733FDB8D-- --===============0018390214== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0018390214==-- From manet-bounces@ietf.org Mon Feb 7 05:15:24 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12678 for ; Mon, 7 Feb 2005 05:15:24 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy6Ep-0004MD-PX for manet-web-archive@ietf.org; Mon, 07 Feb 2005 05:35:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy5pq-0008Cv-4k; Mon, 07 Feb 2005 05:09:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy5lP-0007mp-8F for manet@megatron.ietf.org; Mon, 07 Feb 2005 05:05:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12053 for ; Mon, 7 Feb 2005 05:05:00 -0500 (EST) Received: from web52803.mail.yahoo.com ([206.190.39.167]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cy64l-00048d-94 for manet@irtf.org; Mon, 07 Feb 2005 05:25:04 -0500 Received: (qmail 21234 invoked by uid 60001); 7 Feb 2005 10:04:31 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=VyU5DLX6ZyrpfKDEviZbcrXCT4pzhdOgUXIlYJwmNJ5D08twF1AAZ/z4lQzPVNNkRUpQ0CjNRNOQ1r1i5Ai9SmNTCmQRo/7X5PstBAngWL4kgUpeeWflswzbBlUrn5dER0a3uGVm6GPog7SPzp6YF0ubcLy/z0sBOcA6231QCTc= ; Message-ID: <20050207100431.21232.qmail@web52803.mail.yahoo.com> Received: from [161.200.255.163] by web52803.mail.yahoo.com via HTTP; Mon, 07 Feb 2005 02:04:31 PST Date: Mon, 7 Feb 2005 02:04:31 -0800 (PST) From: pakorn kulsirimongkol Subject: RE: [manet] the beacon mechanism in network layer To: manet@irtf.org In-Reply-To: <9F1223587A755D47805AECAB7ECAF5D901F53EC0@swing.cefriel.it> MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1801352860==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 --===============1801352860== Content-Type: multipart/alternative; boundary="0-635250428-1107770671=:19698" --0-635250428-1107770671=:19698 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA12053 Content-Transfer-Encoding: quoted-printable Thank you for your helping However, I am confused a little bit. From you answer, nodes = will broadcast a beacon and then wait for its neighbor ack right. =20 How long node which haven't received its neighbor beacon deci= de its neighbor disconneted. In some my simulation, there is less time ou= t than it should be because that simulation is much traffic.=20 Giorgio Mulas wrote: Hi, hereunder some considerations about your questions. - beaconing mechanisms are needed in order to discover network topology, = especially when topology may change in an unpredictable way. - of course beacons are sent on a regular basis. A rule of thumb should b= e: the higher the topology change rate (due e.g. to nodes' mobility) the = higher the beaconing rate. - the simplest information in the beacon packet is "here I am!" =3D> you = can translate it, for example, in an IP address. - In theory wireless links are bi-directional, in practice no. An acknowl= edgment mechanism could be a solution. =20 hope this helps =20 Giorgio -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of= pakorn kulsirimongkol Sent: luned=EC 7 febbraio 2005 8.47 To: manet@irtf.org Subject: [manet] the beacon mechanism in network layer Dear, sir pls tell me the beacon mechanism in network layer.=20 Is beacon regularly sent every time? nodes in the network must have a time out for waiting beacon right? what is time out of beacon? what is the information in beacon packet? node, how to know a connectivity of other nodes which it receive be= acon is bidirectional link. =20 best regard, add --------------------------------- Do you Yahoo!? Yahoo! Mail - You care about security. So do we. =09 --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' --0-635250428-1107770671=:19698 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA12053 Content-Transfer-Encoding: quoted-printable
Thank you for your helping
           &n= bsp;However,  I am confused a little bit. From you answer,= nodes will broadcast a beacon and then wait for its neighbor ack ri= ght.   
        &nbs= p;   How long node which haven't received its neighbor beacon d= ecide its neighbor disconneted. In some my simulation, there is less time= out than it should be because that simulation is much traffic.
Giorgio Mulas <giorgio.mulas@cefriel.it> wrote:
Hi,
hereunder some considerations about your questions.
- beaconing mechanisms are needed in order to discover netw= ork topology, especially when topology may change in an unpredictable way= .
- of course beacons= are sent on a regular basis. A rule of thumb should be: the hi= gher the topology change rate (due e.g. to nodes' mobility) the= higher the beaconing rate.
- the simplest information in the beacon packet is "here I = am!" =3D> you can translate it, for example, in an IP address.
- In theory wireless links are bi-directional, in practice = no. An acknowledgment mechanism could be a solution.=
 
hope this helps
 
    Giorgio
-----Original Message-----
From: mane= t-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of pa= korn kkulsirimongkol
Sent: luned=EC 7 febbraio 2005 8.47
= To: manet@irtf.org
Subject: [manet] the beacon mechanism in= network layer

Dear, sir
      pls tell me the beacon mechanism in n= etwork layer.
      Is beacon regularly sent every time?<= /DIV>
      nodes in the network must have a time= out for waiting beacon right?
      what is time out of beacon?
      what is the information in beacon pac= ket?
      node, how to know a connectivity of o= ther nodes which it receive beacon is bidirectional link.
 
best regard,
add


Do you Yahoo!?
Yahoo!= Mail - You care about security. So do we.
<= p>
Do you Yahoo!?
=20 Yahoo! Search presents - Jib Jab's 'Se= cond Term' --0-635250428-1107770671=:19698-- --===============1801352860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1801352860==-- From manet-bounces@ietf.org Mon Feb 7 10:53:28 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11279 for ; Mon, 7 Feb 2005 10:53:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyBW2-0003Z2-FJ for manet-web-archive@ietf.org; Mon, 07 Feb 2005 11:13:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyB6w-0001wf-8t; Mon, 07 Feb 2005 10:47:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyB3g-0001DS-8b for manet@megatron.ietf.org; Mon, 07 Feb 2005 10:44:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10348 for ; Mon, 7 Feb 2005 10:44:12 -0500 (EST) Received: from daimi.au.dk ([130.225.16.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyBN3-0003JN-6O for manet@irtf.org; Mon, 07 Feb 2005 11:04:19 -0500 Received: from daimi.au.dk (alex [130.225.16.45]) by daimi.au.dk (8.12.11/8.12.11) with ESMTP id j17Fi5FH030878 for ; Mon, 7 Feb 2005 16:44:06 +0100 Message-ID: <42078CC5.4040508@daimi.au.dk> Date: Mon, 07 Feb 2005 16:44:05 +0100 From: =?ISO-8859-1?Q?Kari_Rye_Schougaard_N=F8rgaard?= User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@irtf.org Subject: Re: [manet] Pervasive computing and Sensor networks References: <20050204123317.32107.qmail@web20922.mail.yahoo.com> In-Reply-To: <20050204123317.32107.qmail@web20922.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-DAIMI-Spam-Score: -2.791 () ALL_TRUSTED,LOTS_OF_STUFF X-Scanned-By: MIMEDefang 2.44 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by daimi.au.dk id j17Fi5FH030878 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable Hi Praveen, DSG at Trinity College Dubling works with sensor networks: http://www.dsg.cs.tcd.ie/ OOSS at University of Aarhus works with pervasive computing: http://www.pervasive.dk/ These are only two out of many, but I hope it will help you start your search. Cheers, Kari Praveen Choudary wrote: > Hi, > Can anybody give me some references to research groups working in this= =20 > area. Even I searched for publications in digital libraries. I found=20 > very few publications. I am working on a research problem in this area.= =20 > If you are working in a closely related area, please let me know. > =20 > Sincerely, > Praveen. >=20 > -----------------------------------------------------------------------= - > Do you Yahoo!? > Yahoo! Search presents - Jib Jab's 'Second Term'=20 > =20 >=20 >=20 >=20 > -----------------------------------------------------------------------= - >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 Kari Rye Schougaard N=F8rgaard, PhD stud. Center for Pervasive Computing Department of Computer Science University of Aarhus http://www.daimi.au.dk/~kari _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 7 11:34:55 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14538 for ; Mon, 7 Feb 2005 11:34:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyCA9-0004TZ-VA for manet-web-archive@ietf.org; Mon, 07 Feb 2005 11:55:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyBoN-00026z-PL; Mon, 07 Feb 2005 11:32:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyBmA-0001GU-6G for manet@megatron.ietf.org; Mon, 07 Feb 2005 11:30:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14135 for ; Mon, 7 Feb 2005 11:30:10 -0500 (EST) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyC5Y-0004Kz-NQ for manet@irtf.org; Mon, 07 Feb 2005 11:50:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: R: [manet] the beacon mechanism in network layer Date: Mon, 7 Feb 2005 17:30:04 +0100 Message-ID: <9F1223587A755D47805AECAB7ECAF5D912C827@swing.cefriel.it> Thread-Topic: [manet] the beacon mechanism in network layer Thread-Index: AcUM/k/AeMIWp906QQqrBkYA30Gi7AAMraCU From: "Giorgio Mulas" To: "pakorn kulsirimongkol" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: quoted-printable In this hypotethical acknowledgment mechanism I would set the timeout = considering mainly network topology change rate: if the network is quite = static, nodes can lose a higher number of beacons before arguing = something is going wrong (Time out =3D n * beacon_rate, where n =3D = number of beacons could be quite high). Vice-versa if network topology = changes rapidly, if a node misses a beacon likely the neighbor has gone = (n low). =20 You can also use data traffic as a sort of beaconing: if you receive = data you don't need to receive also beacons to verify neighbor's = connectivity... ________________________________ Da: manet-bounces@ietf.org per conto di pakorn kulsirimongkol Inviato: lun 07/02/2005 11.04 A: manet@irtf.org Oggetto: RE: [manet] the beacon mechanism in network layer Thank you for your helping However, I am confused a little bit. From you answer, nodes = will broadcast a beacon and then wait for its neighbor ack right. =20 How long node which haven't received its neighbor beacon = decide its neighbor disconneted. In some my simulation, there is less = time out than it should be because that simulation is much traffic.=20 Giorgio Mulas wrote: Hi, hereunder some considerations about your questions. - beaconing mechanisms are needed in order to discover network = topology, especially when topology may change in an unpredictable way. - of course beacons are sent on a regular basis. A rule of thumb should = be: the higher the topology change rate (due e.g. to nodes' mobility) = the higher the beaconing rate. - the simplest information in the beacon packet is "here I am!" =3D> = you can translate it, for example, in an IP address. - In theory wireless links are bi-directional, in practice no. An = acknowledgment mechanism could be a solution. =20 hope this helps =20 Giorgio -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of pakorn kkulsirimongkol Sent: luned=EC 7 febbraio 2005 8.47 To: manet@irtf.org Subject: [manet] the beacon mechanism in network layer =09 =09 Dear, sir pls tell me the beacon mechanism in network layer.=20 Is beacon regularly sent every time? nodes in the network must have a time out for waiting beacon = right? what is time out of beacon? what is the information in beacon packet? node, how to know a connectivity of other nodes which it receive = beacon is bidirectional link. =20 best regard, add =09 ________________________________ Do you Yahoo!? Yahoo! Mail = - You care about security. So do = we. ________________________________ Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' = =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 7 13:08:14 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25027 for ; Mon, 7 Feb 2005 13:08:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyDcS-00072c-SK for manet-web-archive@ietf.org; Mon, 07 Feb 2005 13:28:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDD5-0003hP-Hj; Mon, 07 Feb 2005 13:02:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyD3I-00020U-5V for manet@megatron.ietf.org; Mon, 07 Feb 2005 12:52:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23770 for ; Mon, 7 Feb 2005 12:51:56 -0500 (EST) Received: from web61301.mail.yahoo.com ([216.155.196.144]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CyDMe-0006hT-8a for manet@ietf.org; Mon, 07 Feb 2005 13:12:05 -0500 Received: (qmail 81142 invoked by uid 60001); 7 Feb 2005 17:51:23 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=dG71qZbHsszq27EpIVmM5tI7+kBOTs3GmNWai9KFsduOpLGtbfZwWgDVejSwCQ3ebxm+ChAwkNY3MKxT7cZGQ/UxjcEr3e+8gqDhYBuMS1OVxi85hkZ/BDy9+VTVkCxSur4FdxlT6cQdBpDhX+0nUiVsg13gBunhYFsN9uwaNk0= ; Message-ID: <20050207175123.81140.qmail@web61301.mail.yahoo.com> Received: from [137.73.11.9] by web61301.mail.yahoo.com via HTTP; Mon, 07 Feb 2005 09:51:23 PST Date: Mon, 7 Feb 2005 09:51:23 -0800 (PST) From: Robert Frank To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 3.0 (+++) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [manet] MANET autoconfiguration in the presence of IGW: performance evaluation metrics X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0336031839==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.0 (+++) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca --===============0336031839== Content-Type: multipart/alternative; boundary="0-2072132512-1107798683=:80957" --0-2072132512-1107798683=:80957 Content-Type: text/plain; charset=us-ascii Hi I am working in the auto-configuration of MANET's in the presence of Internet Gateway (IGW). I am using Passive autoconfiguration techniques for my research. What are the possible set of analysis i can do in the MANET auto-conf?. Can any one please suggest me a set of performance metrics to evaluate the autoconfiguration mechanisms. Any suggestions or pointers to any papers is highly appreciatable Many thanks Rob --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' --0-2072132512-1107798683=:80957 Content-Type: text/html; charset=us-ascii
Hi
 
I am working in the auto-configuration of MANET's in the presence of Internet Gateway (IGW). I am using Passive autoconfiguration techniques for my research. What are the possible set of analysis i can do in the MANET auto-conf?. Can any one please suggest me a set of performance metrics to evaluate the autoconfiguration mechanisms. Any suggestions or pointers to any papers is highly appreciatable
 
Many thanks
 
Rob

Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term' --0-2072132512-1107798683=:80957-- --===============0336031839== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0336031839==-- From manet-bounces@ietf.org Mon Feb 7 17:15:11 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04652 for ; Mon, 7 Feb 2005 17:15:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyHTW-0001Ff-3k for manet-web-archive@ietf.org; Mon, 07 Feb 2005 17:35:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyGRY-0001cV-6H; Mon, 07 Feb 2005 16:29:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyGGW-0008MO-1D for manet@megatron.ietf.org; Mon, 07 Feb 2005 16:17:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20162 for ; Mon, 7 Feb 2005 16:17:49 -0500 (EST) Received: from carrierpigeon.cs.umd.edu ([128.8.129.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyGZx-0004x3-0U for manet@ietf.org; Mon, 07 Feb 2005 16:37:57 -0500 Received: from MINDLAP2 (177-62.mam.umd.edu [129.2.177.62]) (authenticated bits=0) by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id j17LHGOf002312 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 7 Feb 2005 16:17:18 -0500 (EST) Message-Id: <200502072117.j17LHGOf002312@carrierpigeon.cs.umd.edu> From: "Moustafa Youssef" To: Date: Mon, 7 Feb 2005 16:17:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: 7bit Subject: [manet] CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 7bit (Our apologies if you receive multiple copies of this CFP) ------------------------------------------------------------- Second Call for Papers Symposium on Mobile Computing http://www.csee.umbc.edu/~younis/WC_MobCom05.htm as part of IEEE WirelessCom 2005 Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/05/ June 13-16, 2005 Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC Recent years have witnessed an enormous growth in the development and applications of mobile computing environments and devices. Many practitioners envision a future empowered with context and location aware computation and communication infrastructure that allow users to access data and receive service at any place and any time. Compared to conventional platforms, the mobility of computing nodes introduces many challenges to the design of almost all systems components. This symposium will foster a forum for discussing and presenting recent research results on mobile computer systems. Original papers are invited in the broader area of mobile computing. Papers must report high-quality and previously unpublished work. Topics of interest include, but are not limited to, the following: - Architecture and infrastructure support - Middleware and operating systems services - Development platforms and environments - Adaptive resource management schemes - Pervasive and Context-aware Computing - Performance metrics and studies - Power aware computation and communication - Data consistency and synchronization protocols - Fault-tolerant architectural and operation models - Wearable computing devices and systems - Time constrained mobile systems - Robust ad-hoc networking techniques - Efficient localization techniques - Wireless sensor networks - Mobile peer to peer systems - Quality of service provisioning - Context-conscious computing - Web caching and services - Emerging applications and systems - Mobile agents - Mobile commerce - Security and privacy issues Submission Guidelines --------------------- Prospective authors should submit their paper electronically to younis@csee.umbc.edu. All papers are limited to 6 pages in MS-Word, PS or PDF using standard IEEE double-column format. The first page should include title, authors' contact information, an abstract and five keywords. Authors should attach the paper abstract to their message. Important Dates --------------- Paper Submission Deadline: March 15, 2005 Notification of Acceptance: April 15, 2005 Camera-Ready Papers: May 1, 2005 Symposium Co-Chairs ------------------- Mohamed Younis Department of Computer Science and Electrical Engineering University of Maryland Baltimore County, E-mail: younis@csee.umbc.edu Hesham El-Rewini Department of Computer Science and Engineering Southern Methodist University E-mail: rewini@engr.smu.edu Publicity Chair ---------------- Moustafa Youssef Department of Computer Science University of Maryland at College Park, E-mail: moustafa@cs.umd.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 9 11:56:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16627 for ; Wed, 9 Feb 2005 11:56:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyvSe-0003G8-Be for manet-web-archive@ietf.org; Wed, 09 Feb 2005 12:17:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyv6c-0003fV-SW; Wed, 09 Feb 2005 11:54:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyv5c-0003PC-5K for manet@megatron.ietf.org; Wed, 09 Feb 2005 11:53:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16322 for ; Wed, 9 Feb 2005 11:53:17 -0500 (EST) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyvPQ-00039w-VQ for manet@ietf.org; Wed, 09 Feb 2005 12:13:50 -0500 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j19Gqhsi024655 for ; Wed, 9 Feb 2005 17:52:44 +0100 (CET) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id 8F4053C2D9 for ; Wed, 9 Feb 2005 17:52:43 +0100 (MET) Message-ID: <420A3FDB.3080608@eurecom.fr> Date: Wed, 09 Feb 2005 17:52:43 +0100 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Subject: [manet] 802.11, infrastructure and ad-hoc modes X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7bit Hello you MANET people, I have a short but in my opinion interesting question: Let's consider a 802.11 network made of an access point and several stations that generate a "normal" rate of traffic. Let's focus on 2 stations and the access point (every equipment "see" each other): S1 --- AP --- S2 If S1 wants to send a message to S2, is there any motivation (performances? Media Access Control?), other than the security/encryption issues, to use infrastructure mode instead of ad-hoc mode? Thx Claudio _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 9 12:26:26 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18983 for ; Wed, 9 Feb 2005 12:26:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyvvV-0003xE-Mo for manet-web-archive@ietf.org; Wed, 09 Feb 2005 12:47:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyvTg-00080X-Pu; Wed, 09 Feb 2005 12:18:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyvMR-0007XP-K5 for manet@megatron.ietf.org; Wed, 09 Feb 2005 12:10:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17474 for ; Wed, 9 Feb 2005 12:10:37 -0500 (EST) Received: from primary.vmtllc.com ([216.64.2.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyvgD-0003ZT-MD for manet@ietf.org; Wed, 09 Feb 2005 12:31:11 -0500 Received: from herblaptop (localhost.localdomain [127.0.0.1]) by primary.vmtllc.com (8.11.6/8.11.6) with ESMTP id j19HA4f25943; Wed, 9 Feb 2005 12:10:04 -0500 From: "Herbert Rubens" To: "'Claudio Lavecchia'" , Subject: RE: [manet] 802.11, infrastructure and ad-hoc modes Date: Wed, 9 Feb 2005 12:10:26 -0500 Message-ID: <003101c50eca$4009e4a0$99dcdc80@herblaptop> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <420A3FDB.3080608@eurecom.fr> X-Spam-Score: 0.1 (/) X-Scan-Signature: 7f3077fcbbd2d4a1504dfa044ebcf773 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: herb@cnds.jhu.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1775065537==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 94375f06b91351a23b2e62bbf6b5a18c This is a multi-part message in MIME format. --===============1775065537== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0032_01C50EA0.5733DCA0" This is a multi-part message in MIME format. ------=_NextPart_000_0032_01C50EA0.5733DCA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This is an interesting question. Most 802.11 devices operate at multiple rates, so the answer to your question will depend on the link speeds and the network configuration. 11 11 Mbps S1 ---- AP ---- S2 |-------------- | 1 Mbps I've added possible link speeds to the example you mentioned. In the above configuration it would be 2-3 times faster for S1 to send packets to S2 through the access point. Another possible network configuration could be: 1 Mbps S1----------------AP | | 11 | | | | S2-----------------| 1 Mbps In this second configuration it would be much faster for S1 to send packets directly to S2 and not relay them through the access point. So if S1 and S2 were in ad hoc mode, they would achieve higher performance in this case. So it really depends on the network configuration and the current link speeds. We have a paper that talks about these issues which you might find interesting: http://www.cnds.jhu.edu/research/networks/archipelago/publications/AHR-M ediumTimeMetric-TechnicalReport.pdf Regards, Herb ------------------------ Johns Hopkins University Dept. of Computer Science Herb@cs.jhu.edu http://www.cnds.jhu.edu/archipelago/ -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Claudio Lavecchia Sent: Wednesday, February 09, 2005 11:53 AM To: manet@ietf.org Subject: [manet] 802.11, infrastructure and ad-hoc modes Hello you MANET people, I have a short but in my opinion interesting question: Let's consider a 802.11 network made of an access point and several stations that generate a "normal" rate of traffic. Let's focus on 2 stations and the access point (every equipment "see" each other): S1 --- AP --- S2 If S1 wants to send a message to S2, is there any motivation (performances? Media Access Control?), other than the security/encryption issues, to use infrastructure mode instead of ad-hoc mode? Thx Claudio _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------=_NextPart_000_0032_01C50EA0.5733DCA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This is an interesting question. Most 802.11 devices operate at multiple rates, so the answer to your question will depend on the link = speeds and the network configuration.

 

 

    11      11 Mbps

S1 ---- AP ---- S2

 |-------------- = |

       1 Mbps

 

I've added possible link speeds to the example you mentioned. In = the above configuration it would be 2-3 times faster for S1 to send packets = to S2 through the access point.

 

Another possible network configuration could = be:

 

       &nbs= p;  1 Mbps

   = S1----------------AP

    = |       &nbs= p;         |

11  = |       &nbs= p;         |

    = |             &nbs= p;   |   =

   = S2-----------------|

       &nbs= p;         &nbs= p; 1 Mbps

 

 

In this second configuration it would be much faster for S1 to = send packets directly to S2 and not relay them through the access point. So = if S1 and S2 were in ad hoc mode, they would achieve higher performance in = this case.

 

So it really depends on the network configuration and the = current link speeds. We have a paper that talks about these issues which you might = find interesting:

 

http://www.cnds.jhu.edu/resea= rch/networks/archipelago/publications/AHR-MediumTimeMetric-TechnicalRepor= t.pdf

 

 

Regards,

 

Herb

 

 

 

------------------------

Johns = Hopkins University

Dept. of Computer Science

Herb@cs.jhu.edu

http://www.cnds.jhu.edu/arc= hipelago/

 

 

 

 

-----Original Message-----
From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of Claudio Lavecchia
Sent: Wednesday, February 09, 2005 11:53 = AM
To: manet@ietf.org
Subject: [manet] 802.11, infrastructure and = ad-hoc modes

 

Hello you MANET people,

 

I have a short but in my opinion interesting = question:

 

Let's consider a 802.11 network made of an access point and  several stations that generate = a "normal" rate of traffic. Let's focus on 2 stations and the =

access point (every equipment "see" each = other):

 

 

S1 --- AP --- S2

 

If S1 wants to send a message to S2, is there any motivation (performances? Media Access Control?), other than the = security/encryption issues, to use

infrastructure mode instead of ad-hoc = mode?

 

Thx

 

Claudio

 

 

 

 

_______________________________________________=

manet mailing list

manet@ietf.org

https://www1.ietf.org/mailman/listinfo/manet

------=_NextPart_000_0032_01C50EA0.5733DCA0-- --===============1775065537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1775065537==-- From manet-bounces@ietf.org Wed Feb 9 14:27:56 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01929 for ; Wed, 9 Feb 2005 14:27:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyxp4-0007hy-8j for manet-web-archive@ietf.org; Wed, 09 Feb 2005 14:48:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyxED-0007G2-BC; Wed, 09 Feb 2005 14:10:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyxAo-0006DA-2g for manet@megatron.ietf.org; Wed, 09 Feb 2005 14:06:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27809 for ; Wed, 9 Feb 2005 14:06:48 -0500 (EST) Received: from smtp.ono.com ([62.42.230.12] helo=resmta03.ono.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyxUZ-0006ZE-Lc for manet@ietf.org; Wed, 09 Feb 2005 14:27:21 -0500 Received: from [192.168.123.101] (81.202.67.249) by resmta03.ono.com (7.2.052) id 4207435900049975; Wed, 9 Feb 2005 20:05:37 +0100 Message-ID: <420A5FF5.5010909@ono.com> Date: Wed, 09 Feb 2005 20:09:41 +0100 From: Miguel Sanchez User-Agent: Mozilla Thunderbird 1.0 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: herb@cnds.jhu.edu Subject: Re: [manet] 802.11, infrastructure and ad-hoc modes References: <003101c50eca$4009e4a0$99dcdc80@herblaptop> In-Reply-To: <003101c50eca$4009e4a0$99dcdc80@herblaptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: Quoted-Printable X-Spam-Score: 0.1 (/) X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221 Content-Transfer-Encoding: Quoted-Printable Cc: manet@ietf.org, "'Claudio Lavecchia'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c Content-Transfer-Encoding: Quoted-Printable Absolutely Herbert. I think the main point of infrastructure mode is to include station=20 authorization, which is missing if you use ad-hoc mode. So you get something and you may lose something by using ad-hoc mode as=20 your second example shows. @Claudio, The way nodes are laid out on your example the AP could help nodes S1 &=20 S2 to talk to each other when they are not in range of each other. You may switch your card operating mode at will, so you can try to to=20 use ad-hoc mode first then give up to infrastructure mode ... or the=20 opposite. Cheers, Miguel S=E1nchez Herbert Rubens wrote: > > This is an interesting question. Most 802.11 devices operate at=20 > multiple rates, so the answer to your question will depend on the link=20 > speeds and the network configuration. > > =20 > > =20 > > 11 11 Mbps > > S1 ---- AP ---- S2 > > |-------------- | > > 1 Mbps > > =20 > > I've added possible link speeds to the example you mentioned. In the=20 > above configuration it would be 2-3 times faster for S1 to send=20 > packets to S2 through the access point. > > =20 > > Another possible network configuration could be: > > =20 > > 1 Mbps > > S1----------------AP > > | | > > 11 | | > > | | =20 > > S2-----------------| > > 1 Mbps > > =20 > > =20 > > In this second configuration it would be much faster for S1 to send=20 > packets directly to S2 and not relay them through the access point. So=20 > if S1 and S2 were in ad hoc mode, they would achieve higher=20 > performance in this case. > > =20 > > So it really depends on the network configuration and the current link=20 > speeds. We have a paper that talks about these issues which you might=20 > find interesting: > > =20 > > http://www.cnds.jhu.edu/research/networks/archipelago/publications/AHR-= MediumTimeMetric-TechnicalReport.pdf > > =20 > > =20 > > Regards, > > =20 > > Herb > > =20 > > =20 > > =20 > > ------------------------ > > Johns Hopkins University > > Dept. of Computer Science > > Herb@cs.jhu.edu > > http://www.cnds.jhu.edu/archipelago/ > > =20 > > =20 > > =20 > > =20 > > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf=20 > Of Claudio Lavecchia > Sent: Wednesday, February 09, 2005 11:53 AM > To: manet@ietf.org > Subject: [manet] 802.11, infrastructure and ad-hoc modes > > =20 > > Hello you MANET people, > > =20 > > I have a short but in my opinion interesting question: > > =20 > > Let's consider a 802.11 network made of an access point and several=20 > stations that generate a "normal" rate of traffic. Let's focus on 2=20 > stations and the > > access point (every equipment "see" each other): > > =20 > > =20 > > S1 --- AP --- S2 > > =20 > > If S1 wants to send a message to S2, is there any motivation=20 > (performances? Media Access Control?), other than the=20 > security/encryption issues, to use > > infrastructure mode instead of ad-hoc mode? > > =20 > > Thx > > =20 > > Claudio > > =20 > > =20 > > =20 > > =20 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > >------------------------------------------------------------------------ > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 10 03:20:04 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05424 for ; Thu, 10 Feb 2005 03:20:04 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cz9sS-00051u-MJ for manet-web-archive@ietf.org; Thu, 10 Feb 2005 03:40:45 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cz9W8-0002Gp-3k; Thu, 10 Feb 2005 03:17:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cz9LI-0004My-SB for manet@megatron.ietf.org; Thu, 10 Feb 2005 03:06:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04447 for ; Thu, 10 Feb 2005 03:06:27 -0500 (EST) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cz9fH-0004iI-4A for manet@ietf.org; Thu, 10 Feb 2005 03:27:07 -0500 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j1A85CkK004946; Thu, 10 Feb 2005 09:05:13 +0100 (CET) Received: from [172.17.20.172] (caume.eurecom.fr [172.17.20.172]) by monza.eurecom.fr (Postfix) with ESMTP id E24983C2D9; Thu, 10 Feb 2005 09:05:11 +0100 (MET) Message-ID: <420B15B7.5000303@eurecom.fr> Date: Thu, 10 Feb 2005 09:05:11 +0100 From: Fethi Filali Organization: http://www.eurecom.fr User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Miguel Sanchez Subject: Re: [manet] 802.11, infrastructure and ad-hoc modes References: <003101c50eca$4009e4a0$99dcdc80@herblaptop> <420A5FF5.5010909@ono.com> In-Reply-To: <420A5FF5.5010909@ono.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.eurecom.fr id j1A85CkK004946 X-Spam-Score: 0.0 (/) X-Scan-Signature: a743e34ab8eb08259de9a7307caed594 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org, herb@cnds.jhu.edu, "'Claudio Lavecchia'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1 Content-Transfer-Encoding: quoted-printable Direct communication between S1 and S2 is possible in 802.11e using the=20 DLP (Direct Link Protocol). Using DLP signaling messages S1 asks direct=20 link authorisation to AP and the AP sends back to S1 the MAC address of S= 2. FF. Miguel Sanchez wrote: > Absolutely Herbert. >=20 > I think the main point of infrastructure mode is to include station=20 > authorization, which is missing if you use ad-hoc mode. >=20 > So you get something and you may lose something by using ad-hoc mode as= =20 > your second example shows. >=20 > @Claudio, >=20 > The way nodes are laid out on your example the AP could help nodes S1 &= =20 > S2 to talk to each other when they are not in range of each other. >=20 > You may switch your card operating mode at will, so you can try to to=20 > use ad-hoc mode first then give up to infrastructure mode ... or the=20 > opposite. >=20 > Cheers, >=20 > Miguel S=E1nchez >=20 >=20 > Herbert Rubens wrote: >=20 >> >> This is an interesting question. Most 802.11 devices operate at=20 >> multiple rates, so the answer to your question will depend on the link= =20 >> speeds and the network configuration. >> >> =20 >> >> =20 >> >> 11 11 Mbps >> >> S1 ---- AP ---- S2 >> >> |-------------- | >> >> 1 Mbps >> >> =20 >> >> I've added possible link speeds to the example you mentioned. In the=20 >> above configuration it would be 2-3 times faster for S1 to send=20 >> packets to S2 through the access point. >> >> =20 >> >> Another possible network configuration could be: >> >> =20 >> >> 1 Mbps >> >> S1----------------AP >> >> | | >> >> 11 | | >> >> | |=20 >> S2-----------------| >> >> 1 Mbps >> >> =20 >> >> =20 >> >> In this second configuration it would be much faster for S1 to send=20 >> packets directly to S2 and not relay them through the access point. So= =20 >> if S1 and S2 were in ad hoc mode, they would achieve higher=20 >> performance in this case. >> >> =20 >> >> So it really depends on the network configuration and the current link= =20 >> speeds. We have a paper that talks about these issues which you might=20 >> find interesting: >> >> =20 >> >> http://www.cnds.jhu.edu/research/networks/archipelago/publications/AHR= -MediumTimeMetric-TechnicalReport.pdf=20 >> >> >> =20 >> >> =20 >> >> Regards, >> >> =20 >> >> Herb >> >> =20 >> >> =20 >> >> =20 >> >> ------------------------ >> >> Johns Hopkins University >> >> Dept. of Computer Science >> >> Herb@cs.jhu.edu >> >> http://www.cnds.jhu.edu/archipelago/ >> >> =20 >> >> =20 >> >> =20 >> >> =20 >> >> -----Original Message----- >> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf= =20 >> Of Claudio Lavecchia >> Sent: Wednesday, February 09, 2005 11:53 AM >> To: manet@ietf.org >> Subject: [manet] 802.11, infrastructure and ad-hoc modes >> >> =20 >> >> Hello you MANET people, >> >> =20 >> >> I have a short but in my opinion interesting question: >> >> =20 >> >> Let's consider a 802.11 network made of an access point and several=20 >> stations that generate a "normal" rate of traffic. Let's focus on 2=20 >> stations and the >> >> access point (every equipment "see" each other): >> >> =20 >> >> =20 >> >> S1 --- AP --- S2 >> >> =20 >> >> If S1 wants to send a message to S2, is there any motivation=20 >> (performances? Media Access Control?), other than the=20 >> security/encryption issues, to use >> >> infrastructure mode instead of ad-hoc mode? >> >> =20 >> >> Thx >> >> =20 >> >> Claudio >> >> =20 >> >> =20 >> >> =20 >> >> =20 >> >> _______________________________________________ >> >> manet mailing list >> >> manet@ietf.org >> >> https://www1.ietf.org/mailman/listinfo/manet >> >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> =20 >=20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 10 09:29:11 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03248 for ; Thu, 10 Feb 2005 09:29:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzFdi-0004z5-Vd for manet-web-archive@ietf.org; Thu, 10 Feb 2005 09:49:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzF6H-0002sA-IL; Thu, 10 Feb 2005 09:15:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzEvl-0008Jl-16 for manet@megatron.ietf.org; Thu, 10 Feb 2005 09:04:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01627 for ; Thu, 10 Feb 2005 09:04:27 -0500 (EST) Received: from [128.121.115.108] (helo=aimetrix.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzFFm-0004SK-BZ for manet@ietf.org; Thu, 10 Feb 2005 09:25:10 -0500 Received: from yellowfin ([199.72.117.75]) by aimetrix.com (8.12.11/8.12.11) with SMTP id j1AE4QFr077522 for ; Thu, 10 Feb 2005 06:04:26 -0800 (PST) From: "jcrowder" To: Date: Thu, 10 Feb 2005 09:03:23 -0500 Message-ID: <001001c50f79$49cfc5e0$b900a8c0@yellowfin> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200502081713.j18HDSoT005856@aimetrix.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b Content-Transfer-Encoding: 7bit Subject: [manet] RE: manet Digest, Vol 10, Issue 9 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32 Content-Transfer-Encoding: 7bit Would the metrics included here be helpful??? http://www.globalsecurity.org/intell/systems/disn.htm r/ Jana Crowder AiMetrix, Inc./NeuralStar -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf Of manet-request@ietf.org Sent: Tuesday, February 08, 2005 12:13 PM To: manet@ietf.org Subject: manet Digest, Vol 10, Issue 9 Send manet mailing list submissions to manet@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www1.ietf.org/mailman/listinfo/manet or, via email, send a message with subject or body 'help' to manet-request@ietf.org You can reach the person managing the list at manet-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of manet digest..." Today's Topics: 1. MANET autoconfiguration in the presence of IGW: performance evaluation metrics (Robert Frank) 2. CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 (Moustafa Youssef) ------------------------------------------------------------ ---------- Message: 1 Date: Mon, 7 Feb 2005 09:51:23 -0800 (PST) From: Robert Frank Subject: [manet] MANET autoconfiguration in the presence of IGW: performance evaluation metrics To: manet@ietf.org Message-ID: <20050207175123.81140.qmail@web61301.mail.yahoo.com> Content-Type: text/plain; charset="us-ascii" Hi I am working in the auto-configuration of MANET's in the presence of Internet Gateway (IGW). I am using Passive autoconfiguration techniques for my research. What are the possible set of analysis i can do in the MANET auto-conf?. Can any one please suggest me a set of performance metrics to evaluate the autoconfiguration mechanisms. Any suggestions or pointers to any papers is highly appreciatable Many thanks Rob --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www1.ietf.org/pipermail/manet/attachments/20050207/28 4fd79b/attachment.htm ------------------------------ Message: 2 Date: Mon, 7 Feb 2005 16:17:05 -0500 From: "Moustafa Youssef" Subject: [manet] CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 To: Message-ID: <200502072117.j17LHGOf002312@carrierpigeon.cs.umd.edu> Content-Type: text/plain; charset="iso-8859-1" (Our apologies if you receive multiple copies of this CFP) ------------------------------------------------------------ - Second Call for Papers Symposium on Mobile Computing http://www.csee.umbc.edu/~younis/WC_MobCom05.htm as part of IEEE WirelessCom 2005 Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/ 05/ June 13-16, 2005 Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC Recent years have witnessed an enormous growth in the development and applications of mobile computing environments and devices. Many practitioners envision a future empowered with context and location aware computation and communication infrastructure that allow users to access data and receive service at any place and any time. Compared to conventional platforms, the mobility of computing nodes introduces many challenges to the design of almost all systems components. This symposium will foster a forum for discussing and presenting recent research results on mobile computer systems. Original papers are invited in the broader area of mobile computing. Papers must report high-quality and previously unpublished work. Topics of interest include, but are not limited to, the following: - Architecture and infrastructure support - Middleware and operating systems services - Development platforms and environments - Adaptive resource management schemes - Pervasive and Context-aware Computing - Performance metrics and studies - Power aware computation and communication - Data consistency and synchronization protocols - Fault-tolerant architectural and operation models - Wearable computing devices and systems - Time constrained mobile systems - Robust ad-hoc networking techniques - Efficient localization techniques - Wireless sensor networks - Mobile peer to peer systems - Quality of service provisioning - Context-conscious computing - Web caching and services - Emerging applications and systems - Mobile agents - Mobile commerce - Security and privacy issues Submission Guidelines --------------------- Prospective authors should submit their paper electronically to younis@csee.umbc.edu. All papers are limited to 6 pages in MS-Word, PS or PDF using standard IEEE double-column format. The first page should include title, authors' contact information, an abstract and five keywords. Authors should attach the paper abstract to their message. Important Dates --------------- Paper Submission Deadline: March 15, 2005 Notification of Acceptance: April 15, 2005 Camera-Ready Papers: May 1, 2005 Symposium Co-Chairs ------------------- Mohamed Younis Department of Computer Science and Electrical Engineering University of Maryland Baltimore County, E-mail: younis@csee.umbc.edu Hesham El-Rewini Department of Computer Science and Engineering Southern Methodist University E-mail: rewini@engr.smu.edu Publicity Chair ---------------- Moustafa Youssef Department of Computer Science University of Maryland at College Park, E-mail: moustafa@cs.umd.edu ------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet End of manet Digest, Vol 10, Issue 9 ************************************ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 10 12:54:51 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21006 for ; Thu, 10 Feb 2005 12:54:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzIqn-0001Pi-G1 for manet-web-archive@ietf.org; Thu, 10 Feb 2005 13:15:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzIVA-00072Y-1I; Thu, 10 Feb 2005 12:53:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzIO6-0005FW-I3 for manet@megatron.ietf.org; Thu, 10 Feb 2005 12:45:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20424 for ; Thu, 10 Feb 2005 12:45:55 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzIiA-0001DX-0L for manet@ietf.org; Thu, 10 Feb 2005 13:06:42 -0500 Received: by rproxy.gmail.com with SMTP id a41so162183rng for ; Thu, 10 Feb 2005 09:45:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Kbi6g0lf/gg5cmjWy8k3MqfSLl5ScO/0Mta5NP6iQ1QZf1RK0cBnvFfr+kJDyhKALxcOrYIPXlIyvGutAJRCR1s1Qpxxb3cb+cspyTmUm21XNiQ//+9iD7jYQVgPpmfdxrDnW6kD/uJ4GX5TK5ZtBzJGpE13sLe8+ovBnPyTtvo= Received: by 10.38.151.41 with SMTP id y41mr117611rnd; Thu, 10 Feb 2005 09:45:54 -0800 (PST) Received: by 10.38.151.74 with HTTP; Thu, 10 Feb 2005 09:45:54 -0800 (PST) Message-ID: <35dd2291050210094557e68d1@mail.gmail.com> Date: Thu, 10 Feb 2005 09:45:54 -0800 From: Kui Wu To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Content-Transfer-Encoding: 7bit Subject: [manet] CFP - International Symposium on Wireless Local and Personal Area Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kui Wu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Content-Transfer-Encoding: 7bit Call For Papers International Symposium on Wireless Local and Personal Area Networks (part of WirelessCom 2005) Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA, June 13-16th, 2005 Scope and Topics of Interest Original papers are invited on emerging architectures and technologies in the design of wireless local area networks (WLANs) and wireless personal area networks (WPANs) with emphasis on the use of such networks in diverse areas of applications such as supporting ubiquitous mobile Internet access, and the design of ad-hoc networks, and sensor networks. The symposium solicits high quality and previously unpublished work in the field. Topics of interest include, but are not limited to: * Medium access techniques and protocols for WLANs/WPANs * Emerging standards and testbeds for WLANs/WPANs * WLANs/WPANs protocols for smart antennas * Energy efficiency in protocol and systems design * Resource assignment and sharing in WLANs/WPANs * Self configuration in WLANs/WPANs * Provisioning quality of service in WLANs/WPANs * Multimedia networking architectures and protocols for WLANs/WPANs * Integration and interoperability of WLANs/WPANs and 3G (and beyond) networks * Interoperability issues between wireless standards/protocols and the Internet * User mobility and workload modeling * Security issues in WLANs/WPANs Paper Submission and Important Dates Please see the WirelessCom'05 submission page for guidelines. Note that all papers are limited to six pages, and must be in standard IEEE double-column format. All submissions will be handled electronically and must be in PDF format. The conference has designated best papers awards. Manuscript Submission: March 15, 2005 Acceptance Notification: April 15, 2005 Camera-Ready Papers Due: May 1, 2005 Organizing Committee Symposium Co-Chairs Ehab S. Elmallah Department of Computing Science, University of Alberta, Edmonton, Alberta Canada, T6G 2E8 ehab@cs.ualberta.ca Yang Xiao Computer Science Division The University of Memphis, 373 Dunn Hall, Memphis, TN 38152, USA yangxiao@ieee.org Technical Program Committee * Imad Aad, EPFL, Switzerland * Giuseppe Bianchi, University of Roma Tor Vergata, Italy * Azzedine Boukerche, SITE, University of Ottawa, Canada * Jiannong Cao, Hong Kong Polytechnic University, Hong Kong * Liang Cheng, Lehigh University, USA * Sunghyun Choi, Seoul National University, Korea * Jing Deng, University of New Orleans, USA * Christos Douligeris, University of Piraeus, Greece * Xiaojiang (James) Du, North Dakota State University, USA * Nelson Fonseca, State University of Campinas, Brazil * Daqing Gu, MERL, USA * Xingang Guo, Intel, USA * Janelle Harms, University of Alberta, Canada * Ekram Hossain, University of Manitoba, Canada * Antonio Iera, University Mediterranea of Reggio Calabria, Italy * Weijia Jia, City University of Hong Kong, Hong Kong * Xiaohua Jia, City University of Hong Kong , Hong Kong * Victor Leung, University of British Columbia, Canada * Haizhon Li, University of Memphis, USA * Ting-Yu Lin, National Chiao-Tung University, Taiwan * Jiangchuan Liu, Simon Fraser University, Canada * Xiang-Yang Li, Illinois Institute of Technology, USA * Mike MacGregor, University of Alberta, Canada * Jelena Misic, University of Manitoba, Canada * Vojislav B Misic, University of Manitoba, Canada * Qiang Ni, National University of Ireland, Ireland * Jianping Pan, NTT MCL, USA * Yi Qian, University of Puerto Rico, USA * Daji Qiao, Iowa State University, USA * Bo Sun, Lamar University, USA * Ilenia Tinnirello, University of Palermo, Italy * Dimitrios Vergados, University of the Aegean, Greece * Feiyi Wang, Cisco Systems Inc, USA * Lan Wang, University of Memphis, USA * Li-Chun Wang, National Chiao Tung University, Taiwan * Wenye Wang, North Carolina State University, USA * Xudong Wang, Kiyon Inc., USA * Yu Wang, University of California, Santa Cruz, USA * Vincent Wong, University of British Columbia, Canada * Haitao Wu, Microsoft Research, China * Hongyi Wu, University of Louisiana at Lafayette, USA * Jie Wu, Florida Atlantic University , USA * Kui Wu, University of Victoria, Canada * Surong Zeng, Motorola, USA * Hao Zhu, Florida International University, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 10 21:41:33 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20271 for ; Thu, 10 Feb 2005 21:41:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzR4Y-0001uo-Dn for manet-web-archive@ietf.org; Thu, 10 Feb 2005 22:02:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzQi5-0003aG-Sr; Thu, 10 Feb 2005 21:39:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzQh1-0003Et-N8 for manet@megatron.ietf.org; Thu, 10 Feb 2005 21:38:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20116 for ; Thu, 10 Feb 2005 21:38:01 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.196]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzR19-0001pq-3v for manet@ietf.org; Thu, 10 Feb 2005 21:58:52 -0500 Received: by rproxy.gmail.com with SMTP id a41so236422rng for ; Thu, 10 Feb 2005 18:37:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=D8gqcf6b6FoP49znYV70kkOqqM3QdCfmvXwb6DHj7ss+qRVFE5pNgcia02SSs/dN7Pvyizu55Zcete5C5ejogoRUbJQiZx0Pox/sXsQYn7OhzbEjDlzCwfvJgou5dYAMmqJcA1/lIltD+3OSxyOlarwRtDaasqI9xLKoOjZVDHU= Received: by 10.38.24.17 with SMTP id 17mr153531rnx; Thu, 10 Feb 2005 18:37:59 -0800 (PST) Received: by 10.38.152.52 with HTTP; Thu, 10 Feb 2005 18:37:59 -0800 (PST) Message-ID: <645d37c50502101837d3de95@mail.gmail.com> Date: Thu, 10 Feb 2005 20:37:59 -0600 From: Vivek raghunathan To: Claudio Lavecchia Subject: Re: [manet] Require address auto-configuration implementation or simulation code! In-Reply-To: <41F8CE30.6070806@eurecom.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3b75be3e050126052464c56c44@mail.gmail.com> <41F8CE30.6070806@eurecom.fr> X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: 7bit Cc: zhang zhi , manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vivek raghunathan List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: 7bit At Prof P. R. Kumar's group at UIUC, we have an implementation of an address auto-configuration service and a distributed name service. Both of these are provided as part of the Core Services Layer (CSL) for wireless networks. The link is: http://decision.csl.uiuc.edu/~wireless/csl/ -Vivek On Thu, 27 Jan 2005 12:19:12 +0100, Claudio Lavecchia wrote: > zhang zhi wrote: > > >Hi,all > > I plan to implement an address auto-configuration protocol for > >MANET. Does anyone know any exisiting implementation codes or > >simulation package(s) written in ns2 or Qualnet?If you have please let > >me know! > >Thanks a lot! > > > > > > > > > I heard of another existing implementation, please check the link below. > http://pacman-autoconf.sourceforge.net/ > This implemtation has been done at the university of Karlsrhue. > > Regards > > Claudio Lavecchia > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 11 10:23:28 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06634 for ; Fri, 11 Feb 2005 10:23:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Czcy1-0000sP-Gb for manet-web-archive@ietf.org; Fri, 11 Feb 2005 10:44:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzcY5-0000Ew-MU; Fri, 11 Feb 2005 10:17:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzcSn-00076M-Vg for manet@megatron.ietf.org; Fri, 11 Feb 2005 10:12:10 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05078 for ; Fri, 11 Feb 2005 10:12:07 -0500 (EST) Received: from [128.121.115.108] (helo=aimetrix.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Czcn2-0000aC-E1 for manet@ietf.org; Fri, 11 Feb 2005 10:33:04 -0500 Received: from yellowfin ([199.72.117.75]) by aimetrix.com (8.12.11/8.12.11) with SMTP id j1BFC33L063741 for ; Fri, 11 Feb 2005 07:12:03 -0800 (PST) From: "jcrowder" To: Date: Fri, 11 Feb 2005 10:10:59 -0500 Message-ID: <002301c5104b$e5029330$b900a8c0@yellowfin> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <200502081713.j18HDSoT005856@aimetrix.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96 Content-Transfer-Encoding: 7bit Subject: [manet] evaluation metrics response to Robert Frank's question X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665 Content-Transfer-Encoding: 7bit Would the metrics included here be helpful??? http://www.globalsecurity.org/intell/systems/disn.htm Jana Crowder AiMetrix/ NeuralStar -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf Of manet-request@ietf.org Sent: Tuesday, February 08, 2005 12:13 PM To: manet@ietf.org Subject: manet Digest, Vol 10, Issue 9 Send manet mailing list submissions to manet@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www1.ietf.org/mailman/listinfo/manet or, via email, send a message with subject or body 'help' to manet-request@ietf.org You can reach the person managing the list at manet-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of manet digest..." Today's Topics: 1. MANET autoconfiguration in the presence of IGW: performance evaluation metrics (Robert Frank) 2. CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 (Moustafa Youssef) ------------------------------------------------------------ ---------- Message: 1 Date: Mon, 7 Feb 2005 09:51:23 -0800 (PST) From: Robert Frank Subject: [manet] MANET autoconfiguration in the presence of IGW: performance evaluation metrics To: manet@ietf.org Message-ID: <20050207175123.81140.qmail@web61301.mail.yahoo.com> Content-Type: text/plain; charset="us-ascii" Hi I am working in the auto-configuration of MANET's in the presence of Internet Gateway (IGW). I am using Passive autoconfiguration techniques for my research. What are the possible set of analysis i can do in the MANET auto-conf?. Can any one please suggest me a set of performance metrics to evaluate the autoconfiguration mechanisms. Any suggestions or pointers to any papers is highly appreciatable Many thanks Rob --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www1.ietf.org/pipermail/manet/attachments/20050207/28 4fd79b/attachment.htm ------------------------------ Message: 2 Date: Mon, 7 Feb 2005 16:17:05 -0500 From: "Moustafa Youssef" Subject: [manet] CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 To: Message-ID: <200502072117.j17LHGOf002312@carrierpigeon.cs.umd.edu> Content-Type: text/plain; charset="iso-8859-1" (Our apologies if you receive multiple copies of this CFP) ------------------------------------------------------------ - Second Call for Papers Symposium on Mobile Computing http://www.csee.umbc.edu/~younis/WC_MobCom05.htm as part of IEEE WirelessCom 2005 Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/ 05/ June 13-16, 2005 Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC Recent years have witnessed an enormous growth in the development and applications of mobile computing environments and devices. Many practitioners envision a future empowered with context and location aware computation and communication infrastructure that allow users to access data and receive service at any place and any time. Compared to conventional platforms, the mobility of computing nodes introduces many challenges to the design of almost all systems components. This symposium will foster a forum for discussing and presenting recent research results on mobile computer systems. Original papers are invited in the broader area of mobile computing. Papers must report high-quality and previously unpublished work. Topics of interest include, but are not limited to, the following: - Architecture and infrastructure support - Middleware and operating systems services - Development platforms and environments - Adaptive resource management schemes - Pervasive and Context-aware Computing - Performance metrics and studies - Power aware computation and communication - Data consistency and synchronization protocols - Fault-tolerant architectural and operation models - Wearable computing devices and systems - Time constrained mobile systems - Robust ad-hoc networking techniques - Efficient localization techniques - Wireless sensor networks - Mobile peer to peer systems - Quality of service provisioning - Context-conscious computing - Web caching and services - Emerging applications and systems - Mobile agents - Mobile commerce - Security and privacy issues Submission Guidelines --------------------- Prospective authors should submit their paper electronically to younis@csee.umbc.edu. All papers are limited to 6 pages in MS-Word, PS or PDF using standard IEEE double-column format. The first page should include title, authors' contact information, an abstract and five keywords. Authors should attach the paper abstract to their message. Important Dates --------------- Paper Submission Deadline: March 15, 2005 Notification of Acceptance: April 15, 2005 Camera-Ready Papers: May 1, 2005 Symposium Co-Chairs ------------------- Mohamed Younis Department of Computer Science and Electrical Engineering University of Maryland Baltimore County, E-mail: younis@csee.umbc.edu Hesham El-Rewini Department of Computer Science and Engineering Southern Methodist University E-mail: rewini@engr.smu.edu Publicity Chair ---------------- Moustafa Youssef Department of Computer Science University of Maryland at College Park, E-mail: moustafa@cs.umd.edu ------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet End of manet Digest, Vol 10, Issue 9 ************************************ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 11 11:09:22 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11098 for ; Fri, 11 Feb 2005 11:09:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzdgR-0002G0-2x for manet-web-archive@ietf.org; Fri, 11 Feb 2005 11:30:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzdIB-00076d-Sx; Fri, 11 Feb 2005 11:05:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzdF3-0005yN-Mk for manet@megatron.ietf.org; Fri, 11 Feb 2005 11:02:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10516 for ; Fri, 11 Feb 2005 11:01:59 -0500 (EST) Received: from web52906.mail.yahoo.com ([206.190.39.183]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CzdZH-00022T-P1 for manet@ietf.org; Fri, 11 Feb 2005 11:22:57 -0500 Received: (qmail 50252 invoked by uid 60001); 11 Feb 2005 16:01:23 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=6TrBTmjZH6fYP955UwiGy6tyWt0TOQ+fFLmgH7a2b3VO+0214S05VZ/v1KLDg64PnMLwTb+Xfomg6K/CLkwQhpQoIDHUpTFKDC4+mENOFTq4wDxCsgTgniMmi5IvNVft1pngAlWLJaqM14m9Dskrm2nvQ1/ZMVPBYuasRM+LA2g= ; Message-ID: <20050211160123.50250.qmail@web52906.mail.yahoo.com> Received: from [210.212.228.7] by web52906.mail.yahoo.com via HTTP; Fri, 11 Feb 2005 08:01:23 PST Date: Fri, 11 Feb 2005 08:01:23 -0800 (PST) From: Siva Reddy To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [manet] doubt regarding macros X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 hi friends, i am trying to include a c++ file in mac folder in ns-2.26.i made the necessary changes to Makefile(like macros and .o files).but here the problem is coming with macros. i was defined the functions what i wrote in c++ file in the part of DEFINE in Makefile.but it is not recognising those and showing error.please any body can tell me how to made necessary changes in macros, is there any other changes required in any files other than Makefile. thanks in advance... siva reddy. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Feb 12 00:34:32 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03542 for ; Sat, 12 Feb 2005 00:34:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzqFk-00011i-HA for manet-web-archive@ietf.org; Sat, 12 Feb 2005 00:55:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Czps9-000199-Mt; Sat, 12 Feb 2005 00:31:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Czpr1-0000XE-G7 for manet@megatron.ietf.org; Sat, 12 Feb 2005 00:30:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03314 for ; Sat, 12 Feb 2005 00:30:00 -0500 (EST) Received: from web52908.mail.yahoo.com ([206.190.39.185]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CzqBM-0000wk-Mf for manet@ietf.org; Sat, 12 Feb 2005 00:51:06 -0500 Received: (qmail 67508 invoked by uid 60001); 12 Feb 2005 05:29:31 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=TETur8DM5BVGzdUzxQ+0hQ9iubqEojfU0t1y5r3IYXJ9A57JBPrlTDri9CqxBYExf8uZHXPWImN6zgELWnsFPq8zfnVYFqEMcnr8OF+khMjk7mkVmNUZ3TCLeG6hroXXiawjGtrKWf48g7EHjzaasdVD87VUHkwDC3hdkZW0uKo= ; Message-ID: <20050212052931.67506.qmail@web52908.mail.yahoo.com> Received: from [210.212.228.7] by web52908.mail.yahoo.com via HTTP; Fri, 11 Feb 2005 21:29:31 PST Date: Fri, 11 Feb 2005 21:29:31 -0800 (PST) From: Siva Reddy To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [manet] doubt regarding macros X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 hi friends, i am trying to include a c++ file in mac folder in ns-2.26.i made the necessary changes to Makefile(like macros and .o files).but here the problem is coming with macros. i was defined the functions what i wrote in c++ file in the part of DEFINE in Makefile.but it is not recognising those and showing error.please any body can tell me how to made necessary changes in macros, is there any other changes required in any files other than Makefile. thanks in advance... siva reddy. __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 13 05:25:07 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10940 for ; Sun, 13 Feb 2005 05:25:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0HGk-00050z-Vq for manet-web-archive@ietf.org; Sun, 13 Feb 2005 05:46:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0Gs1-0002dx-09; Sun, 13 Feb 2005 05:20:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0GpF-0002Ez-GY for manet@megatron.ietf.org; Sun, 13 Feb 2005 05:18:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10422 for ; Sun, 13 Feb 2005 05:17:57 -0500 (EST) Received: from web60003.mail.yahoo.com ([216.109.116.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D0H9o-0004sf-AH for manet@ietf.org; Sun, 13 Feb 2005 05:39:17 -0500 Received: (qmail 20733 invoked by uid 60001); 13 Feb 2005 10:17:27 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=5+qCODSokAQ3u0bXaQ3T+t79CtIV7dCokjsebDE0XUoQNvRUtCBVELQJLn0Qonp68S8P5hD138WsH0h7hWS2EjoOqN9HdRSx+f3BZvTEMj6WwafnYRPc51GIPoxYCmgRJ/pqxs42wlrxYLazRQtvLkPFGP8MpJfJ8iBRcZudKS4= ; Message-ID: <20050213101727.20731.qmail@web60003.mail.yahoo.com> Received: from [202.141.142.23] by web60003.mail.yahoo.com via HTTP; Sun, 13 Feb 2005 02:17:26 PST Date: Sun, 13 Feb 2005 02:17:26 -0800 (PST) From: Shahriar Shamil Uulu To: NS Mailing , Manet Mailing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [manet] Simulation results of DSDV and DSR ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Dear All, I have simulated DSR and DSDV (on FC-2, ns-allinone-2.27, P-4, RAM 256) in all my simulation results of DSR firstly performs better but after some time the performnce of DSR starts degrading drastically even though the results of DSR is worster than DSDV. Is there any reason why ???. I have posted several mails but i couldnot get any reply, if anybody know the reason please show me the path for solving this problem any information will be higly apperciated. Thank you in advance ===== Shahriar Shamil Uulu Hyderabad Central University M.Tech(Computer Science) email:shamilsons@yahoo.com website: http://shamilson.narod.ru __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 13 12:56:14 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11568 for ; Sun, 13 Feb 2005 12:56:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0OJL-0004kE-QH for manet-web-archive@ietf.org; Sun, 13 Feb 2005 13:17:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0Nwd-0006No-E6; Sun, 13 Feb 2005 12:54:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0NvS-0006EU-Al for manet@megatron.ietf.org; Sun, 13 Feb 2005 12:52:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11377 for ; Sun, 13 Feb 2005 12:52:51 -0500 (EST) Received: from smtp1.utdallas.edu ([129.110.10.12]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0OG7-0004fp-Af for manet@ietf.org; Sun, 13 Feb 2005 13:14:16 -0500 Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9]) by smtp1.utdallas.edu (Postfix) with ESMTP id 7FF10388C77; Sun, 13 Feb 2005 11:52:21 -0600 (CST) Received: by apache.utdallas.edu (Postfix, from userid 30625) id 5B7DB18130; Sun, 13 Feb 2005 11:52:21 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by apache.utdallas.edu (Postfix) with ESMTP id 48FAF17281; Sun, 13 Feb 2005 11:52:21 -0600 (CST) Date: Sun, 13 Feb 2005 11:52:21 -0600 (CST) From: Ming Li To: Shahriar Shamil Uulu Subject: Re: [manet] Simulation results of DSDV and DSR ... In-Reply-To: <20050213101727.20731.qmail@web60003.mail.yahoo.com> Message-ID: References: <20050213101727.20731.qmail@web60003.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: NS Mailing , Manet Mailing X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Hi, There is one bug in the new version of DSR (ns-2.1b9 and higher). You can use older versions. Or you can fix it by going to ns2 website for the patch. There is one for DSR. ming On Sun, 13 Feb 2005, Shahriar Shamil Uulu wrote: > Dear All, > I have simulated DSR and DSDV (on FC-2, > ns-allinone-2.27, P-4, RAM 256) in all my simulation > results of DSR firstly performs better but after some > time the performnce of DSR starts degrading > drastically even though the results of DSR is worster > than DSDV. Is there any reason why ???. > I have posted several mails but i couldnot get any > reply, if anybody know the reason please show me the > path for solving this problem any information will be > higly apperciated. > Thank you in advance > > ===== > Shahriar Shamil Uulu > Hyderabad Central University > M.Tech(Computer Science) > email:shamilsons@yahoo.com > website: http://shamilson.narod.ru > > > > > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 03:01:10 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01957 for ; Mon, 14 Feb 2005 03:01:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0bVB-00038M-Ig for manet-web-archive@ietf.org; Mon, 14 Feb 2005 03:22:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0b7X-0000Sf-B2; Mon, 14 Feb 2005 02:58:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0b5t-0000LP-M6 for manet@megatron.ietf.org; Mon, 14 Feb 2005 02:56:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01629 for ; Mon, 14 Feb 2005 02:56:31 -0500 (EST) Received: from x86unx3.comp.nus.edu.sg ([137.132.80.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0bQd-00032h-E9 for manet@ietf.org; Mon, 14 Feb 2005 03:18:03 -0500 Received: from e500d.comp.nus.edu.sg (e500d.comp.nus.edu.sg [137.132.90.69]) by x86unx3.comp.nus.edu.sg (8.9.1-20030924/8.9.1) with SMTP id PAA16797 for ; Mon, 14 Feb 2005 15:55:57 +0800 (GMT-8) Received: from se11.comp.nus.edu.sg(137.132.80.19) by e500d.comp.nus.edu.sg via csmap id 23186b46_7e5f_11d9_962e_0030482985c3_3182; Mon, 14 Feb 2005 16:05:05 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.10+Sun/8.12.5) id j1E7tuFX019250; Mon, 14 Feb 2005 15:55:56 +0800 (SGT) X-Authentication-Warning: se11.comp.nus.edu.sg: http set sender to yapcheew@comp.nus.edu.sg using -f Received: from 168-85.priv21.nus.edu.sg ([172.21.168.85]) (proxying for 172.18.181.72) (SquirrelMail authenticated user yapcheew); by mysoc.nus.edu.sg with HTTP; Mon, 14 Feb 2005 15:55:56 +0800 (SGT) Message-ID: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> Date: Mon, 14 Feb 2005 15:55:56 +0800 (SGT) From: "Alan Yap" To: manet@ietf.org User-Agent: SquirrelMail/1.4.3 X-Mailer: SquirrelMail/1.4.3 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 8bit Subject: [manet] Queries on SAODV fields - Public key and signature X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 8bit Hi, There are no specifications on the public key and the signature fields of the RREQ, RREP, etc extension of SAODV. Is it encoded in ASN.1 and are there any specific encoding to follow? If not, then how does one determine the length of these variable fields? TIA Alan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 06:23:09 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18198 for ; Mon, 14 Feb 2005 06:23:09 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0eeh-0007Ke-S1 for manet-web-archive@ietf.org; Mon, 14 Feb 2005 06:44:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0eDx-00088a-SE; Mon, 14 Feb 2005 06:17:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0eC7-0007ci-My for manet@megatron.ietf.org; Mon, 14 Feb 2005 06:15:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17314 for ; Mon, 14 Feb 2005 06:15:08 -0500 (EST) Received: from piglet.london.ongenie.net ([193.113.160.15] helo=mail.o2.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0eWr-00076S-Dy for manet@ietf.org; Mon, 14 Feb 2005 06:36:42 -0500 Received: from [194.105.99.79] (194.105.99.79) by mail.o2.co.uk (7.0.031.3) id 41FD2D560034EB55 for manet@ietf.org; Mon, 14 Feb 2005 11:16:02 +0000 Received: from 127.0.0.1 (AVG SMTP 7.0.300 [265.8.7]); Mon, 14 Feb 2005 12:13:56 +0100 Message-ID: <421087F3.8080009@nue.et-inf.uni-siegen.de> Date: Mon, 14 Feb 2005 12:13:55 +0100 From: Michael Schmidt Organization: University of Siegen User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: manet@ietf.org X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 7bit Subject: [manet] "wireless" data security specialist looking for new assignment X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Hi, My Name is Michael Schmidt, I will tentatively graduate from the University of Siegen (Germany) with a Ph.D. in April 2005. I am looking for a national (Germany) or international assignment in the areas research (e.g. a postdoc position) and/or development (e.g. project management), possibly including a journalistic component (e.g. publication on a web portal). Both academia and industry are eligible. I have an industry and project experience in data security of over 10 years. My recent research has concentrated on the topic 'data security aspects of wireless data protocols' (Bluetooth etc.). My CV and 'research statement' are available at http://www.mike-schmidt.gmxhome.de/professional.html. I am expecting to be available from May 2005 (at the earliest). Hoping to hear from you soon... Michael -- ============================================ Michael Schmidt -------------------------------------------- Institute for Digital Communications Systems University of Siegen, Germany -------------------------------------------- http: www.dcs.uni-siegen.de e-mail: schmidt@nue.et-inf.uni-siegen.de ============================================ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 10:30:58 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14224 for ; Mon, 14 Feb 2005 10:30:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0iWW-00051K-Rq for manet-web-archive@ietf.org; Mon, 14 Feb 2005 10:52:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0i59-0007EH-96; Mon, 14 Feb 2005 10:24:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0hzv-0006pR-Fr for manet@megatron.ietf.org; Mon, 14 Feb 2005 10:18:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12876 for ; Mon, 14 Feb 2005 10:18:48 -0500 (EST) Received: from dadar.upf.edu ([193.145.39.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0iKl-0004ms-CQ for manet@ietf.org; Mon, 14 Feb 2005 10:40:24 -0500 Received: from dadar.upf.edu (localhost [127.0.0.1]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1EFIENA008784 for ; Mon, 14 Feb 2005 16:18:14 +0100 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1EFI9CT008746; Mon, 14 Feb 2005 16:18:13 +0100 Message-ID: <4210C0EF.7070208@upf.edu> Date: Mon, 14 Feb 2005 16:17:03 +0100 From: Manel Guerrero User-Agent: Mozilla Thunderbird 1.0 (X11/20050111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan Yap Subject: Re: [manet] Queries on SAODV fields - Public key and signature References: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> In-Reply-To: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 7bit Hi Alan :) you are right. In '14.1. SAODV Signatures' there is only this: 8<----------- The block 'Signature Method ... Padding' is included before the 'Signature' field in all the extension messages, and before the 'Signature of the new Lifetime and Originator IP address' field in the RREQ-DSE message. This is the list of possible values of the Signature Method field: RESERVED 0 RSA 1 Elliptic Curve 2 Reserved 3-127 Implementation dependent 128-255 All the implementations MUST support the RSA option. ----------->8 Which is clearly not specific enough. ;) Specifying all this should be, IMO, the main target for the next SAODV draft version. Now I'm thinking that we could use PKCS#1 (Version 2.1) for 'Signature Method' 1 (RSA) and PKCS#13 for 2 (EC) (if it ever gets standarized ;) ). (So, yeah, it would use ASN.1 and the encoding would be the one specified in the respective PKCSs) And if there is people that need other signature methods they could also be added. But I'm completely open to other suggestions. Maybe a more compact method (so that the length of the signature and the length of the encoded public key would be shorter) could be more desirable. Maybe this is a good moment for you guys to tell me how do you thing this should get specified. Best regards, Manel Alan Yap wrote: > Hi, > > There are no specifications on the public key and the signature fields of > the RREQ, RREP, etc extension of SAODV. Is it encoded in ASN.1 and are > there any specific encoding to follow? > > If not, then how does one determine the length of these variable fields? > > TIA > Alan > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 10:53:54 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16254 for ; Mon, 14 Feb 2005 10:53:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0isk-0005SX-DM for manet-web-archive@ietf.org; Mon, 14 Feb 2005 11:15:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0iRQ-0000eQ-3L; Mon, 14 Feb 2005 10:47:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0iOz-0000Pu-GR for manet@megatron.ietf.org; Mon, 14 Feb 2005 10:44:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15567 for ; Mon, 14 Feb 2005 10:44:40 -0500 (EST) Received: from gehry.upc.es ([147.83.2.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0ijn-0005H6-ED for manet@ietf.org; Mon, 14 Feb 2005 11:06:16 -0500 Received: from gehry.upc.es (localhost.localdomain [127.0.0.1]) by gehry.upc.es (8.13.0/8.13.0) with ESMTP id j1EFggra005958 for ; Mon, 14 Feb 2005 16:44:07 +0100 Received: from ackerman.upc.es (ackerman.upcnetadm.upcnet.es [147.83.2.243]) by gehry.upc.es (8.13.0/8.13.0) with ESMTP id j1EFf1E9005422 for ; Mon, 14 Feb 2005 16:41:02 +0100 Received: from [127.0.0.1] ([147.83.118.59]) by ackerman.upc.es (Lotus Domino Release 5.0.12) with ESMTP id 2005021416410122:45487 ; Mon, 14 Feb 2005 16:41:01 +0100 Message-ID: <4210C68D.4030607@estudiant.upc.edu> Date: Mon, 14 Feb 2005 16:41:01 +0100 From: =?ISO-8859-1?Q?Xavi_Mantec=F3n_-_UPCNet?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: es-es, es MIME-Version: 1.0 To: manet@ietf.org X-MIMETrack: Itemize by SMTP Server on Ackerman/UPC(Release 5.0.12 |February 13, 2003) at 14/02/2005 16:41:01, Serialize by Router on Ackerman/UPC(Release 5.0.12 |February 13, 2003) at 14/02/2005 16:41:02, Serialize complete at 14/02/2005 16:41:02 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Subject: [manet] AODV results depending on HELLO_INTERVAL X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Hi to all, I'm studying some results I've obtained with AODV-UU. I've 5 laptops running AODV, and I've seen how many bandwith is loosed depending on HELLO_INTERVAL value, and how much time it takes to detect a route failure (new routes because of link errors). I would like to know if someone else has ever studied this results, so I can compare them. Thanks in advance, Xavi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 13:19:42 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29318 for ; Mon, 14 Feb 2005 13:19:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0l9s-0000OA-Sb for manet-web-archive@ietf.org; Mon, 14 Feb 2005 13:41:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0kim-0000mg-05; Mon, 14 Feb 2005 13:13:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0kdR-0000Cl-7x for manet@megatron.ietf.org; Mon, 14 Feb 2005 13:07:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28546 for ; Mon, 14 Feb 2005 13:07:45 -0500 (EST) Received: from dadar.upf.edu ([193.145.39.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0kyJ-00009x-SF for manet@ietf.org; Mon, 14 Feb 2005 13:29:24 -0500 Received: from dadar.upf.edu (localhost [127.0.0.1]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1EI7GGQ025519 for ; Mon, 14 Feb 2005 19:07:16 +0100 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1EI7FbG025499; Mon, 14 Feb 2005 19:07:16 +0100 Message-ID: <4210E89F.3010105@upf.edu> Date: Mon, 14 Feb 2005 19:06:23 +0100 From: Manel Guerrero User-Agent: Mozilla Thunderbird 1.0 (X11/20050111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan Yap Subject: Re: [manet] Queries on SAODV fields - Public key and signature References: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> <4210C0EF.7070208@upf.edu> In-Reply-To: <4210C0EF.7070208@upf.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Content-Transfer-Encoding: 7bit Hi Alan :) Another possibility would be to use a Signature Method for RSA that would have: Public Key: modulus exponent Signature: signature Where modulus, exponent and signature are encoded in the following way: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Value | ... ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ and Length indicates the number of 32 bit words that occupy both fields (length + value). Manel Manel Guerrero wrote: > Hi Alan :) > > you are right. > > In '14.1. SAODV Signatures' > there is only this: > > 8<----------- > > The block 'Signature Method ... Padding' is included before the > 'Signature' field in all the extension messages, and before the > 'Signature of the new Lifetime and Originator IP address' field in > the RREQ-DSE message. > > This is the list of possible values of the Signature Method field: > > RESERVED 0 > RSA 1 > Elliptic Curve 2 > Reserved 3-127 > Implementation > dependent 128-255 > > All the implementations MUST support the RSA option. > > ----------->8 > > Which is clearly not specific enough. ;) > > Specifying all this should be, IMO, the main target for the next > SAODV draft version. > > Now I'm thinking that we could use PKCS#1 (Version 2.1) for > 'Signature Method' 1 (RSA) and PKCS#13 for 2 (EC) > (if it ever gets standarized ;) ). (So, yeah, it would use ASN.1 > and the encoding would be the one specified in the respective PKCSs) > And if there is people that need other signature methods they could > also be added. > > But I'm completely open to other suggestions. Maybe a more compact method > (so that the length of the signature and the length of the encoded > public key > would be shorter) could be more desirable. > > Maybe this is a good moment for you guys to tell me how do you thing this > should get specified. > > > Best regards, > > Manel > > > Alan Yap wrote: > >> Hi, >> >> There are no specifications on the public key and the signature fields of >> the RREQ, RREP, etc extension of SAODV. Is it encoded in ASN.1 and are >> there any specific encoding to follow? >> >> If not, then how does one determine the length of these variable fields? >> >> TIA >> Alan >> >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 14:17:42 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03817 for ; Mon, 14 Feb 2005 14:17:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0m3y-0001el-Cc for manet-web-archive@ietf.org; Mon, 14 Feb 2005 14:39:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0lex-0008Be-OR; Mon, 14 Feb 2005 14:13:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0lYp-0007bj-Rv for manet@megatron.ietf.org; Mon, 14 Feb 2005 14:07:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03024 for ; Mon, 14 Feb 2005 14:07:06 -0500 (EST) Received: from web20924.mail.yahoo.com ([216.136.224.139]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D0lth-0001Qc-T8 for manet@irtf.org; Mon, 14 Feb 2005 14:28:43 -0500 Received: (qmail 1859 invoked by uid 60001); 14 Feb 2005 19:07:03 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=v4Kgw0nyWOfUwvxIqftgedbXS9/6c2ooS5DooHCRs0tYoifsZ9rMURL8DQ6/DOVGsH9yh1xTaRKWfFssHSG1siJPcYuERAqCr2H9r8jtedc2vRIwx6mw79lp4pDVaJ7a4AKapLayc41ckFhJOUvZoe5mT+fyBLfcl8F1qjJhCkc= ; Message-ID: <20050214190703.1857.qmail@web20924.mail.yahoo.com> Received: from [203.208.193.197] by web20924.mail.yahoo.com via HTTP; Mon, 14 Feb 2005 11:07:03 PST Date: Mon, 14 Feb 2005 11:07:03 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] Research X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0942258208==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 --===============0942258208== Content-Type: multipart/alternative; boundary="0-1081673899-1108408023=:97582" --0-1081673899-1108408023=:97582 Content-Type: text/plain; charset=us-ascii Hi, I am working on an interesting idea. I prepared a write-up of my idea. I feel it has a publication relevance. Will be possible for the researchers in this group to help me in research. If you can review my work and give me your comments, I can target a good conference. Waiting for your reply, Praveen. --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term' --0-1081673899-1108408023=:97582 Content-Type: text/html; charset=us-ascii
Hi,
 I am working on an interesting idea. I prepared a write-up of my idea. I feel it has a publication relevance. Will be possible for the researchers in this group to help me in research. If you can review my work and give me your comments, I can target a good conference.
 
Waiting for your reply,
Praveen.

Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term' --0-1081673899-1108408023=:97582-- --===============0942258208== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0942258208==-- From manet-bounces@ietf.org Mon Feb 14 17:25:45 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26707 for ; Mon, 14 Feb 2005 17:25:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0p01-000718-EE for manet-web-archive@ietf.org; Mon, 14 Feb 2005 17:47:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0oa6-0007zA-Lb; Mon, 14 Feb 2005 17:20:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0oZ4-0007q9-Qc for manet@megatron.ietf.org; Mon, 14 Feb 2005 17:19:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26059 for ; Mon, 14 Feb 2005 17:19:32 -0500 (EST) Received: from web52507.mail.yahoo.com ([206.190.39.132]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D0otx-0006od-PL for manet@ietf.org; Mon, 14 Feb 2005 17:41:12 -0500 Received: (qmail 81902 invoked by uid 60001); 14 Feb 2005 22:19:01 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=V37uN1TgIXkjpYcISdxC+HjEwlhDfqn2GXoLR5xfBkFFX38cTFMY6ro2bJU6vN8MlkCbqsUJe2kCeJUi/sTafI29saSR3Z3cbncRTfs/3Aon1t2jjmLSVWnOhs5KlFPcPqc8K7bElyoxG+929xsp5tlFH9ojIMImwr56RO7cJRI= ; Message-ID: <20050214221901.81900.qmail@web52507.mail.yahoo.com> Received: from [128.175.241.136] by web52507.mail.yahoo.com via HTTP; Mon, 14 Feb 2005 14:19:01 PST Date: Mon, 14 Feb 2005 14:19:01 -0800 (PST) From: Leon Martin To: MANET Newsgroup MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8 Subject: [manet] How to dump routing tables for manets in ns2? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a Hi, I could not figure out how to dump the routing tables for wireless ad hoc networks. The routing protocols I used are DSDV and AODV. I am using ns2.27. I serched the ns-nam mailing list and found this problem had been asked as early as 1998 but no solution has ever been provided. Here is one reply in 1998: (available at http://mailman.isi.edu/pipermail/ns-users/1998-June/001292.html) Two things that are not clearly documented are 1. dump-routes only works with dynamic routing, and we only currently have DV in there (if someone wants to donate their LS code, we'd shamelessly purloin it...hint, hint :-) 2. dump-routes only works after you issue the ``$ns run'' command, because it is that command that sets up all the rtObject instances. and another fresh message was posted on but no answer has been given: Does anyone know how to dump routing tables in wireless simulations? Neither of the following works in DSDV or AODV: $ns dump-routelogic-nh or set dr [$node rtObject?] $dr dump-routes $fh I'm using ns-2.27. (Available at http://mailman.isi.edu/pipermail/ns-users/2004-July/043791.html) In my case, I used two procedures to do the job. The descriptions are as follows. /////////////////////// procedure 1 ////////////////////////////// proc rtdump {} { global ns_ set now [$ns_ now] puts "Routing table at time $now" $ns_ dump-routelogic-nh $ns_ dump-routelogic-distance } And the dumping is executed by: $ns_ at 20.0 "rtdump" In the OUTPUT, the place that is supposed to be for the routing tables is empty, as shown below: num_nodes is set 2 warning: Please use -channel as shown in tcl/ex/wireless-mitf.tcl INITIALIZE THE LIST xListHead Starting Simulation... channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ highestAntennaZ_ = 1.5, distCST_ = 550.0 SORTING LISTS ...DONE! Routing table at time 20 Dumping Routing Table: Next Hop Information NS EXITING... /* Note the blank before NS EXITING... */ //////////////////// procedure 2 ////////////////////////////////////////// I then tried this procedure: proc rtdump2 {node fh} { global ns_ set now [$ns_ now] puts "Routing table of node $node at time $now" set dr [$node rtObject?] $dr dump-routes $fh } The output gives an error message: num_nodes is set 2 warning: Please use -channel as shown in tcl/ex/wireless-mitf.tcl INITIALIZE THE LIST xListHead Starting Simulation... channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ highestAntennaZ_ = 1.5, distCST_ = 550.0 SORTING LISTS ...DONE! Routing table of node _o14 at time 30 ns: rtdump2 _o14 file4: invalid command name "" while executing "$dr dump-routes $fh" (procedure "rtdump2" line 6) invoked from within "rtdump2 _o14 file4" //////////////////// procedures done /////////////////////////////////////// The following is the ns Tcl script, modified from tcl/ex/simple-wireless.tcl. # # simple-wireless.tcl # A simple example for wireless simulation # ====================================================================== # Define options # ====================================================================== set val(chan) Channel/WirelessChannel ;# channel type set val(prop) Propagation/TwoRayGround ;# radio-propagation model set val(netif) Phy/WirelessPhy ;# network interface type set val(mac) Mac/802_11 ;# MAC type set val(ifq) Queue/DropTail/PriQueue ;# interface queue type set val(ll) LL ;# link layer type set val(ant) Antenna/OmniAntenna ;# antenna model set val(ifqlen) 50 ;# max packet in ifq set val(nn) 2 ;# number of mobilenodes set val(rp) DSDV ;# routing protocol # ====================================================================== # Main Program # ====================================================================== # # Initialize Global Variables # set ns_ [new Simulator] set tracefd [open simple.tr w] $ns_ trace-all $tracefd # ///////////// uncomment the line below for procedure 2 /////////////// # set tracert [open tracert.tr w] # set up topography object set topo [new Topography] $topo load_flatgrid 500 500 # # Create God # create-god $val(nn) # # Create the specified number of mobilenodes [$val(nn)] and "attach" them # to the channel. # Here two nodes are created : node(0) and node(1) # configure node $ns_ node-config -adhocRouting $val(rp) \ -llType $val(ll) \ -macType $val(mac) \ -ifqType $val(ifq) \ -ifqLen $val(ifqlen) \ -antType $val(ant) \ -propType $val(prop) \ -phyType $val(netif) \ -channelType $val(chan) \ -topoInstance $topo \ -agentTrace ON \ -routerTrace ON \ -macTrace OFF \ -movementTrace OFF for {set i 0} {$i < $val(nn) } {incr i} { set node_($i) [$ns_ node] $node_($i) random-motion 0 ;# disable random motion } # # Provide initial (X,Y, for now Z=0) co-ordinates for mobilenodes # $node_(0) set X_ 5.0 $node_(0) set Y_ 2.0 $node_(0) set Z_ 0.0 $node_(1) set X_ 390.0 $node_(1) set Y_ 385.0 $node_(1) set Z_ 0.0 # # Now produce some simple node movements # Node_(1) starts to move towards node_(0) # $ns_ at 50.0 "$node_(1) setdest 25.0 20.0 15.0" $ns_ at 10.0 "$node_(0) setdest 20.0 18.0 1.0" # Node_(1) then starts to move away from node_(0) $ns_ at 100.0 "$node_(1) setdest 490.0 480.0 15.0" # Setup traffic flow between nodes # TCP connections between node_(0) and node_(1) set tcp [new Agent/TCP] $tcp set class_ 2 set sink [new Agent/TCPSink] $ns_ attach-agent $node_(0) $tcp $ns_ attach-agent $node_(1) $sink $ns_ connect $tcp $sink set ftp [new Application/FTP] $ftp attach-agent $tcp $ns_ at 10.0 "$ftp start" # # Tell nodes when the simulation ends # for {set i 0} {$i < $val(nn) } {incr i} { $ns_ at 150.0 "$node_($i) reset"; } # /////////// comment the line below for procedure 2 //////////////// $ns_ at 20.0 "rtdump" # ///////// uncomment the line below for procedure 2 /////////////// # $ns_ at 30.0 "rtdump2 $node_(0) $tracert" $ns_ at 150.0 "stop" $ns_ at 150.01 "puts \"NS EXITING...\" ; $ns_ halt" proc rtdump {} { global ns_ set now [$ns_ now] puts "Routing table at time $now" $ns_ dump-routelogic-nh $ns_ dump-routelogic-distance } proc rtdump2 {node fh} { global ns_ set now [$ns_ now] puts "Routing table of node $node at time $now" set dr [$node rtObject?] $dr dump-routes $fh } proc stop {} { global ns_ tracefd $ns_ flush-trace close $tracefd } puts "Starting Simulation..." $ns_ run Thanks in advance. - Leon __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 18:40:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03202 for ; Mon, 14 Feb 2005 18:40:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qAS-0008T2-Vj for manet-web-archive@ietf.org; Mon, 14 Feb 2005 19:02:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0pnI-0000dU-2J; Mon, 14 Feb 2005 18:38:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0plF-0000V0-KL for manet@megatron.ietf.org; Mon, 14 Feb 2005 18:36:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02792 for ; Mon, 14 Feb 2005 18:36:10 -0500 (EST) Received: from web25002.mail.ukl.yahoo.com ([217.12.10.38]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D0q68-0008MH-0b for manet@ietf.org; Mon, 14 Feb 2005 18:57:51 -0500 Received: (qmail 10793 invoked by uid 60001); 14 Feb 2005 23:35:38 -0000 Message-ID: <20050214233538.10791.qmail@web25002.mail.ukl.yahoo.com> Received: from [62.252.0.10] by web25002.mail.ukl.yahoo.com via HTTP; Mon, 14 Feb 2005 23:35:38 GMT Date: Mon, 14 Feb 2005 23:35:38 +0000 (GMT) From: l s To: manet@ietf.org In-Reply-To: <4210E89F.3010105@upf.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.1 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 8bit Subject: [manet] MANET's usage of 3rd Address in 802.11 DATA frame X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 8bit Dear MANET researchers, MANETs are often employed on the 802.11 MAC. In this case only RTS, CTS, DATA, and ACK frames are ever used and much of the frame bits are redundant as they relating to various infrastructure related modes. In the DATA frame in particular, there are three addresses, the Transmit Address, Receive Address, and a 3rd address. Has the 3rd address been utilised in a MANET for any reason? (I can only imagine somehow for gateways or tunneling.) I'd be grateful to know about research in which it has been used in MANETs. Thank you in advance, Lee Speakman CCSR, UniS Guildford UK ___________________________________________________________ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 19:27:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06715 for ; Mon, 14 Feb 2005 19:18:09 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qbt-0000yY-VT for manet-web-archive@ietf.org; Mon, 14 Feb 2005 19:30:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0pzu-0001rQ-Ql; Mon, 14 Feb 2005 18:51:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0pxT-0001ZC-P6 for manet@megatron.ietf.org; Mon, 14 Feb 2005 18:48:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03704 for ; Mon, 14 Feb 2005 18:48:48 -0500 (EST) Received: from wproxy.gmail.com ([64.233.184.197]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qIO-00009E-Kx for manet@ietf.org; Mon, 14 Feb 2005 19:10:29 -0500 Received: by wproxy.gmail.com with SMTP id 71so831279wri for ; Mon, 14 Feb 2005 15:48:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=qs6YNLZNSLzU/bUtuA5EboyjVTP0Qn72N0cYqH/3g4O5OdyEaJUAmMgZwO7yQgUs5Jf3FCQ+BDw+TBfjSbzMB/ZUBJVJbyb72qMTgh9KbKMi0H5GJJGfYLohfH3sek47aS6lQIJH5VGJJUMNWOGNEMiR81dBWkeuWo5pUVNAxK4= Received: by 10.54.24.57 with SMTP id 57mr139089wrx; Mon, 14 Feb 2005 15:48:18 -0800 (PST) Received: by 10.54.30.68 with HTTP; Mon, 14 Feb 2005 15:48:18 -0800 (PST) Message-ID: <1c03219305021415484c4bec8d@mail.gmail.com> Date: Mon, 14 Feb 2005 17:48:18 -0600 From: mark shawn To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Subject: [manet] Home Sensor Network X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mark shawn List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Hi, I want to deploy some sensors so that each area of a home is covered. Also I want some fault tolerance. Which algorithm or Paper might help me. I do not want to concentrate on deployment as my target is different. However, I wanna know a suitable deployment and topology that will help in a home environment. Thanks Sayed http://www.justEtc.com/research _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 14 22:42:30 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21618 for ; Mon, 14 Feb 2005 22:42:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0twb-0000J4-0z for manet-web-archive@ietf.org; Mon, 14 Feb 2005 23:04:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0tZa-0002uQ-6H; Mon, 14 Feb 2005 22:40:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0tYK-0002oQ-Lj for manet@megatron.ietf.org; Mon, 14 Feb 2005 22:39:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21425 for ; Mon, 14 Feb 2005 22:39:05 -0500 (EST) Received: from x86unx3.comp.nus.edu.sg ([137.132.80.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0ttI-0000DI-3f for manet@ietf.org; Mon, 14 Feb 2005 23:00:48 -0500 Received: from e500c.comp.nus.edu.sg (e500c.comp.nus.edu.sg [137.132.90.68]) by x86unx3.comp.nus.edu.sg (8.9.1-20030924/8.9.1) with SMTP id LAA18262; Tue, 15 Feb 2005 11:38:30 +0800 (GMT-8) Received: from sn40.comp.nus.edu.sg(137.132.80.15) by e500c.comp.nus.edu.sg via csmap id 05263e6e_7f05_11d9_893e_003048298555_29512; Tue, 15 Feb 2005 11:52:32 +0800 (SGT) Received: from yapcheew ([172.18.181.164]) (authenticated bits=0) by sn40.comp.nus.edu.sg (8.13.1/8.13.1) with ESMTP id j1F3cSKK012590 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 15 Feb 2005 11:38:29 +0800 (SGT) Message-ID: <003201c5130f$aa1e0b20$a4b512ac@comp.nus.edu.sg> From: "Alan" To: "Manel Guerrero" References: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> <4210C0EF.7070208@upf.edu> <4210E89F.3010105@upf.edu> Subject: Re: [manet] Queries on SAODV fields - Public key and signature Date: Tue, 15 Feb 2005 11:37:12 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: 7bit Hi Manel, This method which you suggested will simplify things. We could save the trouble and additional processing of ASN.1 parsing as the fields in SAODV are essentially a single attribute to single value mapping. We don't need the structural support that is provided by ASN.1 (as of now) Cheers Alan ----- Original Message ----- From: Manel Guerrero To: Alan Yap Cc: manet@ietf.org Sent: Tuesday, February 15, 2005 2:06 AM Subject: Re: [manet] Queries on SAODV fields - Public key and signature Hi Alan :) Another possibility would be to use a Signature Method for RSA that would have: Public Key: modulus exponent Signature: signature Where modulus, exponent and signature are encoded in the following way: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Value | ... ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ and Length indicates the number of 32 bit words that occupy both fields (length + value). Manel Manel Guerrero wrote: > Hi Alan :) > > you are right. > > In '14.1. SAODV Signatures' > there is only this: > > 8<----------- > > The block 'Signature Method ... Padding' is included before the > 'Signature' field in all the extension messages, and before the > 'Signature of the new Lifetime and Originator IP address' field in > the RREQ-DSE message. > > This is the list of possible values of the Signature Method field: > > RESERVED 0 > RSA 1 > Elliptic Curve 2 > Reserved 3-127 > Implementation > dependent 128-255 > > All the implementations MUST support the RSA option. > > ----------->8 > > Which is clearly not specific enough. ;) > > Specifying all this should be, IMO, the main target for the next > SAODV draft version. > > Now I'm thinking that we could use PKCS#1 (Version 2.1) for > 'Signature Method' 1 (RSA) and PKCS#13 for 2 (EC) > (if it ever gets standarized ;) ). (So, yeah, it would use ASN.1 > and the encoding would be the one specified in the respective PKCSs) > And if there is people that need other signature methods they could > also be added. > > But I'm completely open to other suggestions. Maybe a more compact method > (so that the length of the signature and the length of the encoded public > key > would be shorter) could be more desirable. > > Maybe this is a good moment for you guys to tell me how do you thing this > should get specified. > > > Best regards, > > Manel > > > Alan Yap wrote: > >> Hi, >> >> There are no specifications on the public key and the signature fields of >> the RREQ, RREP, etc extension of SAODV. Is it encoded in ASN.1 and are >> there any specific encoding to follow? >> >> If not, then how does one determine the length of these variable fields? >> >> TIA >> Alan >> >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 15 06:54:13 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21544 for ; Tue, 15 Feb 2005 06:54:12 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D11cW-0002Gx-0j for manet-web-archive@ietf.org; Tue, 15 Feb 2005 07:16:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D11EZ-0000Q2-Rd; Tue, 15 Feb 2005 06:51:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D11E5-0000Jc-Nc for manet@megatron.ietf.org; Tue, 15 Feb 2005 06:50:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21266 for ; Tue, 15 Feb 2005 06:50:42 -0500 (EST) Received: from dadar.upf.edu ([193.145.39.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D11Z6-0002Bm-B3 for manet@ietf.org; Tue, 15 Feb 2005 07:12:29 -0500 Received: from dadar.upf.edu (localhost [127.0.0.1]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1FBo9UR031533 for ; Tue, 15 Feb 2005 12:50:09 +0100 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id j1FBo7Pv031524; Tue, 15 Feb 2005 12:50:08 +0100 Message-ID: <4211E18C.8010005@upf.edu> Date: Tue, 15 Feb 2005 12:48:28 +0100 From: Manel Guerrero User-Agent: Mozilla Thunderbird 1.0 (X11/20050111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan Subject: Re: [manet] Queries on SAODV fields - Public key and signature References: <1624.172.21.168.85.1108367756.squirrel@172.21.168.85> <4210C0EF.7070208@upf.edu> <4210E89F.3010105@upf.edu> <003201c5130f$aa1e0b20$a4b512ac@comp.nus.edu.sg> In-Reply-To: <003201c5130f$aa1e0b20$a4b512ac@comp.nus.edu.sg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: 7bit Hi Alan :) Yep. I also thing this format's gonna be better. Let's put it in this way: 8<---------------------------------------- 14.1.1. Signature Method #1 Public Key is composed of: - Modulus - Exponent Signature is composed of: - Signature Where modulus, exponent and signature are encoded in the following way: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Value | ... ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Length The length of the Value field, (not including the Length and Reserved fields) in 32-bit units. Reserved Sent as 0; ignored on reception. ---------------------------------------->8 The reserved field might be used in the future for flags. My intuition tells me we're gonna need them. ;) Regards, Manel Alan wrote: > Hi Manel, > > This method which you suggested will simplify things. We could save the > trouble and additional processing of ASN.1 parsing as the fields in > SAODV are essentially a single attribute to single value mapping. We > don't need the structural support that is provided by ASN.1 (as of now) > > Cheers > Alan > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 15 14:51:16 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01152 for ; Tue, 15 Feb 2005 14:51:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D194D-00079O-SZ for manet-web-archive@ietf.org; Tue, 15 Feb 2005 15:13:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D18HG-0000u4-J2; Tue, 15 Feb 2005 14:22:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D15w8-0002lZ-17 for manet@megatron.ietf.org; Tue, 15 Feb 2005 11:52:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08040 for ; Tue, 15 Feb 2005 11:52:29 -0500 (EST) Received: from [203.199.93.15] (helo=WS0005.indiatimes.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D16H9-00079S-KU for manet@ietf.org; Tue, 15 Feb 2005 12:14:19 -0500 Received: from 192.168.57.15 (a2 [192.168.57.22]) by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id WAA02147 for ; Tue, 15 Feb 2005 22:06:28 +0530 From: "rv72" Message-Id: <200502151636.WAA02147@WS0005.indiatimes.com> To: Date: Tue, 15 Feb 2005 22:22:31 +0530 X-URL: http://indiatimes.com Content-Type: text/plain; charset=us-ascii X-Spam-Score: 3.2 (+++) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Subject: [manet] (no subject) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rv72 List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.2 (+++) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 thank u for including my email id Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 15 14:51:43 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01215 for ; Tue, 15 Feb 2005 14:51:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D194e-0007AS-Kb for manet-web-archive@ietf.org; Tue, 15 Feb 2005 15:13:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D18HJ-000106-Sq; Tue, 15 Feb 2005 14:22:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D15wI-0002sw-FN for manet@megatron.ietf.org; Tue, 15 Feb 2005 11:52:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08121 for ; Tue, 15 Feb 2005 11:52:40 -0500 (EST) Received: from [203.199.93.15] (helo=WS0005.indiatimes.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D16HL-0007Aw-OC for manet@ietf.org; Tue, 15 Feb 2005 12:14:29 -0500 Received: from 192.168.57.15 (a2 [192.168.57.22]) by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id WAA02167 for ; Tue, 15 Feb 2005 22:06:41 +0530 From: "rv72" Message-Id: <200502151636.WAA02167@WS0005.indiatimes.com> To: Date: Tue, 15 Feb 2005 22:22:44 +0530 X-URL: http://indiatimes.com Content-Type: text/plain; charset=us-ascii X-Spam-Score: 3.2 (+++) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [manet] (no subject) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rv72 List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.2 (+++) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 thank u for including my email id Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now! Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 16 10:02:50 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18089 for ; Wed, 16 Feb 2005 10:02:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1R2p-0006aw-D9 for manet-web-archive@ietf.org; Wed, 16 Feb 2005 10:24:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Qcm-00059j-9O; Wed, 16 Feb 2005 09:57:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1QY6-0003Wg-B0 for manet@megatron.ietf.org; Wed, 16 Feb 2005 09:53:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16445 for ; Wed, 16 Feb 2005 09:53:03 -0500 (EST) Received: from web61108.mail.yahoo.com ([216.155.196.110]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1QtH-00068I-0l for manet@ietf.org; Wed, 16 Feb 2005 10:15:05 -0500 Received: (qmail 19374 invoked by uid 60001); 16 Feb 2005 14:52:27 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=TIMToN9t3aGwNZ2QDUVfppUfgmMp9nXBdur4p25XhqQHxPgZVNhb2Rf9fXTSZ690krWfZz7OppoDVplezZihoHpkw05oV+hB1s1wEyNIa5Mw9EGYlQdRwSzEd8CKmNRaoeckh3cuygukUHhySa5X1Yx3/dxmZQRtp0yaoZxu8LI= ; Message-ID: <20050216145227.19372.qmail@web61108.mail.yahoo.com> Received: from [219.65.97.173] by web61108.mail.yahoo.com via HTTP; Wed, 16 Feb 2005 06:52:26 PST Date: Wed, 16 Feb 2005 06:52:26 -0800 (PST) From: Juliana Frederick To: glomosim , manet MIME-Version: 1.0 X-Spam-Score: 1.4 (+) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [manet] G P S R / Position based Routing X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1687014668==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.4 (+) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 --===============1687014668== Content-Type: multipart/alternative; boundary="0-813040754-1108565546=:17606" --0-813040754-1108565546=:17606 Content-Type: text/plain; charset=us-ascii Hi friends, Has anyone got the source code for GPSR (Greedy Perimeter Stateless Routing) or GEOCAST or SAR(Spatially Aware Routing) or position based routing protocol implemented using GloMoSim? Any insight on this topic would be really appreciated. Please reply. Thanks in advance. Regards, Juliana __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-813040754-1108565546=:17606 Content-Type: text/html; charset=us-ascii
Hi friends,
 
Has anyone got the source code for GPSR (Greedy Perimeter Stateless Routing) or GEOCAST or SAR(Spatially Aware Routing) or position based routing protocol implemented using GloMoSim?
 
Any insight on this topic would be really appreciated.

Please reply.
 
Thanks in advance.
 
Regards,
Juliana
 
 
 

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-813040754-1108565546=:17606-- --===============1687014668== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1687014668==-- From manet-bounces@ietf.org Wed Feb 16 14:10:31 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29308 for ; Wed, 16 Feb 2005 14:10:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1UuL-0003hf-I0 for manet-web-archive@ietf.org; Wed, 16 Feb 2005 14:32:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1SpA-0005vp-U7; Wed, 16 Feb 2005 12:18:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1R28-0004k5-TX; Wed, 16 Feb 2005 10:24:09 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22973; Wed, 16 Feb 2005 10:24:05 -0500 (EST) Message-Id: <200502161524.KAA22973@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Wed, 16 Feb 2005 10:24:05 -0500 Cc: manet@ietf.org Subject: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Dynamic MANET On-demand Routing Protocol (DYMO) Author(s) : I. Chakeres, et al. Filename : draft-ietf-manet-dymo-00.txt Pages : 27 Date : 2005-2-15 The Dynamic MANET On-demand (DYMO) routing protocol is intended for use by mobile nodes in wireless multihop networks. It offers quick adaptation to dynamic conditions, low processing and memory overhead, low network utilization, and determines unicast routes between nodes within the network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-dymo-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-manet-dymo-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-manet-dymo-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-16102703.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-dymo-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-dymo-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-16102703.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --NextPart-- From manet-bounces@ietf.org Wed Feb 16 21:53:09 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29694 for ; Wed, 16 Feb 2005 21:53:09 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1c8K-0003gZ-R8 for manet-web-archive@ietf.org; Wed, 16 Feb 2005 22:15:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1bcq-0005HN-Uh; Wed, 16 Feb 2005 21:42:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1bPn-00008E-1A for manet@megatron.ietf.org; Wed, 16 Feb 2005 21:29:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27472 for ; Wed, 16 Feb 2005 21:29:12 -0500 (EST) Received: from smtp106.mail.sc5.yahoo.com ([66.163.169.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1bl8-00034j-AQ for manet@ietf.org; Wed, 16 Feb 2005 21:51:20 -0500 Received: from unknown (HELO pc10835.ml.giti.waseda.ac.jp) (ryujin?ssdt@133.9.108.135 with plain) by smtp106.mail.sc5.yahoo.com with SMTP; 17 Feb 2005 02:29:11 -0000 From: =?utf-8?q?=E9=BE=8D=E7=A5=9E?= To: manet@ietf.org Date: Thu, 17 Feb 2005 20:29:13 +0900 User-Agent: KMail/1.7.92 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502172029.14136.ryujin_ssdt@yahoo.co.jp> X-Spam-Score: 1.9 (+) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Subject: [manet] Lateration vs Min Max localization in WSN's X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ryujin_ssdt@yahoo.co.uk List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit I really don't know where to search or ask this question so if the MANET mailing list is not appropriate please tell me and if possible direct me to the correct place. I did some simple simulations of localization methods in Wireless Sensor Networks using Min Max and Trilateration methods for location estimation. My results are no different from what others have reported: Min Max is more robust to range measurement errors between nodes than trilateration but trilateration is more accurate than min max as long as range measurements errors are low. The interesting thing in my results is that adding anchor nodes to the network have adverse effects in both localization methods. If I add anchor nodes to the sensor network I can see that the accuracy of the location estimates increases in the trilateration case. But for Min Max, as I add anchor nodes the accuracy of the location estimate degrades. So why Min Max accuracy degrades as anchor nodes and ranging errors increase? My simulation settings is a small area with 4 to 90 anchor nodes in the perimeter of the area and 50 nodes within the area (no nodes are outside the convex hull formed by the anchor nodes). There is no communication since I assume all nodes already know the location and distance measurement to all anchors and I add some gaussian noise to the real distances (1 to 60% the real distance variance) to simulate ranging errors. All nodes are within communication range so all nodes have location and distance information from all anchor nodes in the area. Any ideas are appreciated. Also pointers to information about the theory behind lateration and min max are welcome. regards, Ryujin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 17 20:09:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04994 for ; Thu, 17 Feb 2005 20:09:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1wzt-0007Un-FK for manet-web-archive@ietf.org; Thu, 17 Feb 2005 20:31:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1wTN-0005DN-MO; Thu, 17 Feb 2005 19:58:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1wD0-0006ni-1t for manet@megatron.ietf.org; Thu, 17 Feb 2005 19:41:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01728 for ; Thu, 17 Feb 2005 19:41:23 -0500 (EST) Received: from smtp.fusemail.net ([69.31.1.141] helo=fuse1.fusemail.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1wYX-0006Tb-QY for manet@ietf.org; Thu, 17 Feb 2005 20:03:43 -0500 Received: from fusemail.com by fuse1.fusemail.net with asmtp (TLSv1:AES256-SHA:256) (FuseMail extSMTP) id 1D1wCJ-0003ZW-TN for manet@ietf.org; Thu, 17 Feb 2005 18:40:44 -0600 Message-ID: <42153993.8010500@tklogic.net> Date: Thu, 17 Feb 2005 19:40:51 -0500 From: Colin Bell User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit Subject: [manet] Greetings MANET Readers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit Hi all, My name is Colin Bell, I'm a 3rd year student at the University of Waterloo in Waterloo, Ontario, Canada. I am studying Mathematics/Computer Science and have been working in the telecom sector since I was in grade 10 (Nortel and Siemens). Anyway, I just thought I'd introduce myself. I just happened on the working group in my research on a paper I am submitting to the 18th Annual IEEE Canadian Conference on Electrical and Computer Engineering (http://www.ieee.ca/ccece05/). The paper I am authoring is entitled, "Service-Based Tiered Mesh Networks: Bridging the Gaps". However, after reading RFC2501 I have learned that it should be called, "Service-Based Tiered Mobile, Multihop, Wireless Networking: Bridging the Gaps". I have to agree with the RFC though, it is cumbersome that way. I am writing this paper with my friends to play with the idea of having every node in a mobile "mesh" work with every other node to get things done. We know that "Energy-constrained operation" is an issue but we are working under the assumption that, once the routing bugs are sorted out (care of MANET), we'll have seen advances in mobile device technology. Manual chargers, solar panels in backpacks and jackets.... we are assuming (and yes, it is a big assumption) that one day each node on the network will be able to route packets so that dead zones in the, "IP routing fabric", will no longer exist. Does this sound like a reasonable assumption? Do you think I am out to lunch? I would post the abstract for the paper I am working on but I need to check on the IEEE's copyright rules first. ;-) Stingy folks over there at the IEEE (j/k). Anyway, hello and cheers. I look forward to being part of this list, I hope there is still an active community kicking around here. The prospect of one day living in a world with ubiquitous network access enthralls me. Cheers, CB -- Colin Bell http://www.techknowlogic.net _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 18 02:18:04 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24210 for ; Fri, 18 Feb 2005 02:18:04 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D22kT-0007ve-RX for manet-web-archive@ietf.org; Fri, 18 Feb 2005 02:40:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D22IR-000286-2H; Fri, 18 Feb 2005 02:11:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D22Cz-0007Xs-56 for manet@megatron.ietf.org; Fri, 18 Feb 2005 02:05:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12745 for ; Fri, 18 Feb 2005 02:05:48 -0500 (EST) Received: from web60007.mail.yahoo.com ([216.109.116.245]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D22Ya-0007aq-8i for manet@ietf.org; Fri, 18 Feb 2005 02:28:09 -0500 Received: (qmail 53026 invoked by uid 60001); 18 Feb 2005 07:05:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=eIof//IBmN9gkHRM1DkWyTsT5boxnyWzlsjHHTCaP3wwKEVoddUhm+HFVkh2LGfd//3TjsAMCnj3x160UgsjBs14uNZqtmJ2zTc+eT5H8XMHX1GONpvy+sf2ot4zeueIPEiyTujpDZ5qqO++owYbIFH3VgdeeS8U8uinDlhsArw= ; Message-ID: <20050218070517.53024.qmail@web60007.mail.yahoo.com> Received: from [202.141.142.23] by web60007.mail.yahoo.com via HTTP; Thu, 17 Feb 2005 23:05:17 PST Date: Thu, 17 Feb 2005 23:05:17 -0800 (PST) From: Shahriar Shamil Uulu To: NS Mailing , Manet Mailing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Subject: [manet] ns-allione-2.1b8a installation error ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Dear All, i have tried to install ns-allione-2.1b8a (to FC-2) but at the end i am getting this type of error. ---------------------------------------------------- In file included from trace.cc:44: tfrc.h:116: error: friend declaration requires class-key, i.e. `friend class TfrcSendTimer' tfrc.h:117: error: friend declaration requires class-key, i.e. `friend class TfrcNoFeedbackTimer' make: *** [trace.o] Error 1 Ns make failed! ----------------------------------------------------- i have searched in the mailing lists and ns-problem website but i couldnot find relevant answer. Thank you in advance ... __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 18 06:04:19 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18348 for ; Fri, 18 Feb 2005 06:04:19 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D26HU-0004ql-2w for manet-web-archive@ietf.org; Fri, 18 Feb 2005 06:26:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D25qR-0005rM-I9; Fri, 18 Feb 2005 05:58:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D25pY-0005PI-Ju for manet@megatron.ietf.org; Fri, 18 Feb 2005 05:57:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18005 for ; Fri, 18 Feb 2005 05:57:50 -0500 (EST) Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D26BC-0004jV-Cq for manet@ietf.org; Fri, 18 Feb 2005 06:20:14 -0500 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.12.10/8.12.10) with ESMTP id j1IAveTL007562 for ; Fri, 18 Feb 2005 11:57:41 +0100 Message-ID: <4215CA2E.2090209@unibas.ch> Date: Fri, 18 Feb 2005 11:57:50 +0100 From: Christophe Jelger Organization: University of Basel User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 CC: manet@ietf.org Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt References: <200502161524.KAA22973@ietf.org> In-Reply-To: <200502161524.KAA22973@ietf.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.1.8 X-SMTP-Vilter-Virus-Backend: savse X-SMTP-Vilter-Status: clean X-SMTP-Vilter-savse-Virus-Status: clean X-SMTP-Vilter-Unwanted-Backend: attachment X-SMTP-Vilter-attachment-Unwanted-Status: clean X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Content-Transfer-Encoding: 7bit Hi, Just a quick mistake in part 2. Terminology we read : IPBroadcastAddress Transmit the packet to the IP Limited Broadcast address, 255.255.255.255 (IPv4) or FF:FF:FF:FF:FF:FF (IPv6). Actually FF:FF:FF:FF:FF:FF is not an IPv6 address, and even FF:FF:FF:FF:FF:FF:FF:FF is not the IPv6 broadcast address (stricly there is no broadcast address with IPv6). Maybe you should use ff02::1 ? Regards, Christophe Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. > > Title : Dynamic MANET On-demand Routing Protocol (DYMO) > Author(s) : I. Chakeres, et al. > Filename : draft-ietf-manet-dymo-00.txt > Pages : 27 > Date : 2005-2-15 > > The Dynamic MANET On-demand (DYMO) routing protocol is intended for > use by mobile nodes in wireless multihop networks. It offers quick > adaptation to dynamic conditions, low processing and memory overhead, > low network utilization, and determines unicast routes between nodes > within the network. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-manet-dymo-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-manet-dymo-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-manet-dymo-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > ------------------------------------------------------------------------ > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 18 06:12:01 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19094 for ; Fri, 18 Feb 2005 06:12:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D26Ov-00052W-Rq for manet-web-archive@ietf.org; Fri, 18 Feb 2005 06:34:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D25zN-0000zC-0t; Fri, 18 Feb 2005 06:08:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D25wR-00087e-Be for manet@megatron.ietf.org; Fri, 18 Feb 2005 06:04:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18454 for ; Fri, 18 Feb 2005 06:04:56 -0500 (EST) Message-Id: <200502181104.GAA18454@ietf.org> Received: from mail82.messagelabs.com ([195.245.231.67]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D26I4-0004qr-4J for manet@ietf.org; Fri, 18 Feb 2005 06:27:21 -0500 X-VirusChecked: Checked X-Env-Sender: konstantinos.voulgaris@kcl.ac.uk X-Msg-Ref: server-11.tower-82.messagelabs.com!1108660144!13083618!1 X-StarScan-Version: 5.4.11; banners=-,-,- X-Originating-IP: [137.73.2.214] Received: (qmail 19019 invoked from network); 17 Feb 2005 17:09:04 -0000 Received: from outbound.kcl.ac.uk (137.73.2.214) by server-11.tower-82.messagelabs.com with SMTP; 17 Feb 2005 17:09:04 -0000 Received: from relay2.kcl.ac.uk ([137.73.2.210] helo=elder) by outbound.kcl.ac.uk outbound with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) id 1D1p8x-0004EY-DD for manet@ietf.org; Thu, 17 Feb 2005 17:08:47 +0000 Received: from phoenix.eee.kcl.ac.uk ([137.73.10.210] helo=phoenix) by elder smtp with esmtp id 1D1p8l-0003Av-SW for manet@ietf.org; Thu, 17 Feb 2005 17:08:37 +0000 From: "Kostas Voulgaris" To: Date: Thu, 17 Feb 2005 17:08:33 -0000 MIME-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: High Thread-Index: AcUUVDT6fynCsE3QRtOx2IEPOTIxcQAAAHgwAACef2AAAAoVAAAABquAAB9rqVAAACMEcAAAazFgAA8T3GA= X-KCLSpamScore: 20 X-KCLRealSpamScore: 2.0 X-KCLZStatus: 20 X-KCLSpamBar: ++ X-KCLSpamReport: HTML_70_80=0.1, HTML_MESSAGE=0.1, X_MSMAIL_PRIORITY_HIGH=0.5, X_PRIORITY_HIGH=1.305 X-KCL-MailScanner: Found to be clean X-MailScanner-From: konstantinos.voulgaris@kcl.ac.uk X-Spam-Score: 1.1 (+) X-Scan-Signature: 3f4d1621eb481886fab661da14b05487 Subject: [manet] IWWAN 2005 - London 23-26 May 2005 - Call for Papers on Ad Hoc & Sensor Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0796568482==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: b05b48c33ab3cc55d15d1512d45dfce0 This is a multi-part message in MIME format. --===============0796568482== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B7_01C51513.4FD46A50" This is a multi-part message in MIME format. ------=_NextPart_000_01B7_01C51513.4FD46A50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear Colleagues, The 2005 International Workshop on Wireless Ad-hoc Networks is an ideal opportunity to network and present latest results in the vibrant area of ad hoc and sensor networks. This year's attendees are comprised of high-profile professionals and academics from the US, Asia, Australia and Europe. The workshop will be held in London from Monday 23rd - Thursday 26th May 2005. For details, please, consult http://www.ctr.kcl.ac.uk/IWWAN2005. Developing from the first successful event in Oulu in 2004, IWWAN 2005 will highlight the growing applications and power of ad-hoc and sensor networks in achieving ubiquitous, pervasive communications in next generation networks. The workshop will focus on the increasing importance of ad-hoc architectures in next generation networks including interoperation with fixed and cellular networks. The list of topics will include: Theory: - Information theory for wireless ad-hoc networks - Performance bounds, capacity limits - Multiple access and capacity analysis - Capacity of multi-hop networks - Routing strategies in multi-hop networks - Throughput and delay analysis - Heterogeneous wireless networks - Clustering and cooperative strategies - Networks for survivability - Power optimisation strategies - Sensor networks - Antenna & propagation issues Applications: - Positioning and location estimation - Performance of Mobile IPV6 - 802.11 and Bluetooth networks - Interoperation with fixed / cellular networks - Ad-hoc wireless extensions to the Internet - UWB networks - Test-bed performance - Tools for system analysis - Pervasive / ubiquitous systems - Implementation issues - "Value added" services The schedule is as follows: . Monday 23rd May - Tutorials . Tuesday 24th - Regular Sessions . Wednesday 25th - Regular Sessions . Thursday 26th - EU Cluster Day The Cluster Day on Thursday 26th May will include input from 5th and 6th Framework projects including BETSY, ROMANTIK, PULSERS and EYES. If you wish to present research conducted within Europe, America, Asia or Australia, please, contact the technical co-chairs. Important dates are: . Submission deadline - 8 March 2005 . Notification of acceptance: - 11 April 2005 Submission procedures are specified in http://www.ctr.kcl.ac.uk/IWWAN2005. Best wishes Dr. Ian Oppermann IWWAN Technical Chairman Director, CWC University of Oulu, Finland Mobile: +358 407 076 344 Fax: +358 8 553 2845 http://www.cwc.oulu.fi/home Dr. Mischa Dohler IWWAN Technical Chairman Lecturer, CTR King's College London, UK Phone:+44 207 848 2390 Fax: +44 207 848 2664 http://www.ctr.kcl.ac.uk ------=_NextPart_000_01B7_01C51513.4FD46A50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = Colleagues,

 

The 2005 = International Workshop on Wireless Ad-hoc Networks is an ideal opportunity to network = and present latest results in the vibrant area of ad hoc and sensor = networks. This year's attendees are comprised of high-profile professionals and = academics from the US, Asia, = Australia and Europe. The workshop will be held in London from Monday = 23rd – Thursday 26th May 2005. For details, please, consult http://www.ctr.kcl.ac.uk/IWW= AN2005. 

 

Developing from the = first successful event in Oulu in 2004, IWWAN = 2005 will highlight the growing applications and power of ad-hoc and sensor = networks in achieving ubiquitous, pervasive communications in next generation = networks. The workshop will focus on the increasing importance of ad-hoc architectures = in next generation networks including interoperation with fixed and = cellular networks. The list of topics will include:

  =

Theory:

- Information = theory for wireless ad-hoc networks

- Performance = bounds, capacity limits

- Multiple access = and capacity analysis

- Capacity of = multi-hop networks

- Routing = strategies in multi-hop networks

- Throughput and = delay analysis

- Heterogeneous = wireless networks

- Clustering and = cooperative strategies

- Networks for = survivability

- Power = optimisation strategies

- Sensor = networks

- Antenna & = propagation issues

 

Applications:

- Positioning and = location estimation

- Performance of = Mobile IPV6

- 802.11 and = Bluetooth networks

- Interoperation = with fixed / cellular networks

- Ad-hoc wireless = extensions to the Internet

- UWB = networks

- Test-bed = performance

- Tools for system = analysis

- Pervasive / = ubiquitous systems

- Implementation = issues

- “Value = added” services

 

The schedule is as = follows:

•     Monday 23rd May   – Tutorials

•     Tuesday 24th      – Regular = Sessions

•     Wednesday 25th    – Regular Sessions

•     Thursday 26th     – EU Cluster = Day

 

The Cluster Day on = Thursday 26th May will include input from 5th and 6th Framework projects = including BETSY, ROMANTIK, PULSERS and EYES. If you wish to present research = conducted within Europe, America, Asia or Australia, please, contact the technical co-chairs.

 

Important dates = are:

•     Submission deadline           – = 8 March 2005

•     Notification of acceptance:   - 11 April 2005

 

Submission = procedures are specified in http://www.ctr.kcl.ac.uk/IWW= AN2005.

 

Best = wishes

 

Dr. Ian Oppermann

IWWAN Technical = Chairman

Director, = CWC

University of = Oulu, Finland

Mobile: +358 407 076 344

Fax: =   +358 8 553 2845

http://www.cwc.oulu.fi/home&nbs= p;

 

Dr. Mischa Dohler =

IWWAN Technical = Chairman

Lecturer, = CTR

King’s = College London, UK

Phone:+44 207 848 = 2390

Fax: +44 207 848 = 2664

http://www.ctr.kcl.ac.uk

 

 

 

------=_NextPart_000_01B7_01C51513.4FD46A50-- --===============0796568482== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0796568482==-- From manet-bounces@ietf.org Fri Feb 18 18:18:42 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19799 for ; Fri, 18 Feb 2005 18:18:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2HkG-0005iE-QS for manet-web-archive@ietf.org; Fri, 18 Feb 2005 18:41:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2GfM-0001Hb-UF; Fri, 18 Feb 2005 17:32:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2FLc-0004Yt-U8 for manet@megatron.ietf.org; Fri, 18 Feb 2005 16:07:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15335 for ; Fri, 18 Feb 2005 16:07:34 -0500 (EST) Received: from web52502.mail.yahoo.com ([206.190.39.123]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2FhK-0003Bl-50 for manet@ietf.org; Fri, 18 Feb 2005 16:30:03 -0500 Received: (qmail 76695 invoked by uid 60001); 18 Feb 2005 21:07:02 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=wNrUZAyM1fhy3QRRPT4b2yYNcfc3kbOWhxnfQCz4j5jnozFpjLQ76EIMUSj44XmCruRTKvXJHZ93HkMu5iUJAv8PZDeLaJ0MfwJzLIy/p+z1iMc6nZFbcSke5FOASzd5GhLZk9PAdhnUtQ2Ap1U6AMWLeLudbxvRJqkjsOppA88= ; Message-ID: <20050218210702.76693.qmail@web52502.mail.yahoo.com> Received: from [128.4.133.43] by web52502.mail.yahoo.com via HTTP; Fri, 18 Feb 2005 13:07:02 PST Date: Fri, 18 Feb 2005 13:07:02 -0800 (PST) From: Leon Martin To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [manet] Where is forwarding done in ns2? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Hi all, I am trying to do static routing for MANET in ns-2. To do this, I need to know where _forwarding_, instead of _routing_, is implemented in ns2 (2.27). Does anyone know whether the forwarding decision is made by AODV or by IP? Thanks. - Leon __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 18 23:36:33 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23241 for ; Fri, 18 Feb 2005 23:36:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2Mhv-0008TV-13 for manet-web-archive@ietf.org; Fri, 18 Feb 2005 23:59:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2MBS-0008PJ-Uf; Fri, 18 Feb 2005 23:25:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2M6G-0005tB-TR for manet@megatron.ietf.org; Fri, 18 Feb 2005 23:20:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21835 for ; Fri, 18 Feb 2005 23:20:10 -0500 (EST) Received: from web53309.mail.yahoo.com ([206.190.39.238]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2MS1-000818-Py for manet@ietf.org; Fri, 18 Feb 2005 23:42:44 -0500 Received: (qmail 82765 invoked by uid 60001); 19 Feb 2005 04:19:39 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=3nbYNxiYXEw6gUH6zBeHJfbJU42al6JGdJxjWczjiin+7RQfTmpRoJlXWUwMhurDDOG+lqvHGatS9J4gUonyFslgFdzb0JCcpib0MHy60AOSLfSvbiRNmJ07qLT259UukWQvClbSa0/CDK310xaz85+udd0vX9T9HyOkWrZ2/c4= ; Message-ID: <20050219041939.82763.qmail@web53309.mail.yahoo.com> Received: from [61.16.174.51] by web53309.mail.yahoo.com via HTTP; Fri, 18 Feb 2005 20:19:39 PST Date: Fri, 18 Feb 2005 20:19:39 -0800 (PST) From: Jaya Prakash To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Subject: [manet] Regarding glomosim... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0732771910==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 --===============0732771910== Content-Type: multipart/alternative; boundary="0-2142470466-1108786779=:82243" --0-2142470466-1108786779=:82243 Content-Type: text/plain; charset=us-ascii Hello..... I am doing my P.G program.My project title is "An integrated cross layer design for enhanced QoS in mobile adhoc network"..... This is done in Glomosim... I had installed glomosim and made a research in my title. Now i need help , how to make changes in glomosim files(mainly in DSR protocol) ? if possible glomosim manual..... Pls..help for the above regard.... My id is pjp_1947@yahoo.com Thanking you, JP __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-2142470466-1108786779=:82243 Content-Type: text/html; charset=us-ascii
Hello.....
 
I am doing my P.G program.My project title is "An integrated cross layer design for enhanced QoS in mobile adhoc network".....
 
This is done in Glomosim...
 
I had installed glomosim and made a research in my title.
Now i need help , how to make changes in glomosim files(mainly in DSR protocol) ? if possible glomosim manual.....
 
Pls..help for the above regard....
 
Thanking you,
JP
 

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-2142470466-1108786779=:82243-- --===============0732771910== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0732771910==-- From manet-bounces@ietf.org Sat Feb 19 00:40:29 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29121 for ; Sat, 19 Feb 2005 00:40:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2Nhn-0001pF-Re for manet-web-archive@ietf.org; Sat, 19 Feb 2005 01:03:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2NJb-000803-3a; Sat, 19 Feb 2005 00:38:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2NE7-0005d3-56 for manet@megatron.ietf.org; Sat, 19 Feb 2005 00:32:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28541 for ; Sat, 19 Feb 2005 00:32:20 -0500 (EST) Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2NZu-0001bW-BC for manet@ietf.org; Sat, 19 Feb 2005 00:54:55 -0500 Received: from samurai.local.sfc.wide.ad.jp (p4057-ipbf613marunouchi.tokyo.ocn.ne.jp [222.149.227.57]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.10/8.12.0) with ESMTP id j1J5VYFj012962 for ; Sat, 19 Feb 2005 14:31:34 +0900 Date: Sat, 19 Feb 2005 14:31:28 +0900 Message-ID: From: Ryuji Wakikawa To: manet@ietf.org Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt In-Reply-To: <4215CA2E.2090209@unibas.ch> References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin7.2.0) MULE/5.0 (SAKAKI) Organization: Keio University/WIDE MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Spam-Score: 0.1 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 Hi Christophe and Ian We submitted a new draft regarding IPv6 support on MANET. The flooding address is discussed in the draft. http://www.ietf.org/internet-drafts/draft-wakikawa-manet-ipv6-support-00.txt Any comments are appreciated. thanks ryuji At Fri, 18 Feb 2005 11:57:50 +0100, Christophe Jelger wrote: > > Hi, > > Just a quick mistake in part 2. Terminology we read : > > IPBroadcastAddress > Transmit the packet to the IP Limited Broadcast address, > 255.255.255.255 (IPv4) or FF:FF:FF:FF:FF:FF (IPv6). > > Actually FF:FF:FF:FF:FF:FF is not an IPv6 address, and even > FF:FF:FF:FF:FF:FF:FF:FF is not the IPv6 broadcast address (stricly there > is no broadcast address with IPv6). Maybe you should use ff02::1 ? > > Regards, > Christophe > > Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. > > > > Title : Dynamic MANET On-demand Routing Protocol (DYMO) > > Author(s) : I. Chakeres, et al. > > Filename : draft-ietf-manet-dymo-00.txt > > Pages : 27 > > Date : 2005-2-15 > > > > The Dynamic MANET On-demand (DYMO) routing protocol is intended for > > use by mobile nodes in wireless multihop networks. It offers quick > > adaptation to dynamic conditions, low processing and memory overhead, > > low network utilization, and determines unicast routes between nodes > > within the network. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-manet-dymo-00.txt > > > > To remove yourself from the I-D Announcement list, send a message to > > i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. > > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > > > > > > Internet-Drafts are also available by anonymous FTP. Login with the username > > "anonymous" and a password of your e-mail address. After logging in, > > type "cd internet-drafts" and then > > "get draft-ietf-manet-dymo-00.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-manet-dymo-00.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 20 04:36:01 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16553 for ; Sun, 20 Feb 2005 04:36:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2nrW-00086k-4V for manet-web-archive@ietf.org; Sun, 20 Feb 2005 04:58:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2mBK-0002cE-Ud; Sun, 20 Feb 2005 03:11:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2lFG-000570-BP for manet@megatron.ietf.org; Sun, 20 Feb 2005 02:11:10 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26667 for ; Sun, 20 Feb 2005 02:11:03 -0500 (EST) Received: from web60006.mail.yahoo.com ([216.109.116.229]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2lbC-0008Dn-1G for manet@ietf.org; Sun, 20 Feb 2005 02:33:51 -0500 Received: (qmail 46241 invoked by uid 60001); 20 Feb 2005 07:10:32 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=WkRcpyjXm6v0ZEYABNCIPcDlIfjcQsE2jOUwi/jzQ3vH4ImRurx39vcr00632m94NC9DJ0w1pIIdxHyx/E3/qVAxg2NUEdE0dwOPadqKDpvdFvgy0pbgN8naoGyUPsah+cKj0i8Wr+s71r8SgbEAQ3VC6MgQ6wo7p538rOYBCrQ= ; Message-ID: <20050220071032.46239.qmail@web60006.mail.yahoo.com> Received: from [202.141.142.23] by web60006.mail.yahoo.com via HTTP; Sat, 19 Feb 2005 23:10:32 PST Date: Sat, 19 Feb 2005 23:10:32 -0800 (PST) From: Shahriar Shamil Uulu To: NS Mailing , Manet Mailing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [manet] intallation error in ns-allinone-2.1b8a ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Dear All, i am trying to install ns-2.1b8a on FC-2, but in the meanwhile i am getting this error: -------------------------------------------------- simulator.o(.text+0x735): In function `Simulator::populate_hier_classifiers()': : undefined reference to `RouteLogic::elements_in_level(int*, int)' collect2: ld returned 1 exit status make: *** [ns] Error 1 --------------------------------------------------- i have found in the mailing list the answer for this error(i.e we have to remove key word "incline" before "elements_in_level(int*, int)") but the error still preserves, i dont know what to do please help me. Thank you in advance ... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 12:31:33 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23396 for ; Mon, 21 Feb 2005 12:31:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3HlX-0007tF-B8 for manet-web-archive@ietf.org; Mon, 21 Feb 2005 12:54:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3GLf-0000H8-PP; Mon, 21 Feb 2005 11:23:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Fio-0000mE-PC for manet@megatron.ietf.org; Mon, 21 Feb 2005 10:43:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12331 for ; Mon, 21 Feb 2005 10:43:35 -0500 (EST) Received: from bay17-f36.bay17.hotmail.com ([64.4.43.86] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3G51-0005BX-Gf for manet@ietf.org; Mon, 21 Feb 2005 11:06:40 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 21 Feb 2005 07:42:01 -0800 Message-ID: Received: from 62.8.24.95 by by17fd.bay17.hotmail.msn.com with HTTP; Mon, 21 Feb 2005 15:41:32 GMT X-Originating-IP: [62.8.24.95] X-Originating-Email: [yann_eads@hotmail.com] X-Sender: yann_eads@hotmail.com From: "Yann ." To: manet@ietf.org Subject: RE : [manet] Where is forwarding done in ns2? Date: Mon, 21 Feb 2005 16:41:32 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 21 Feb 2005 15:42:01.0414 (UTC) FILETIME=[E2971660:01C5182B] X-Spam-Score: 0.9 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA12331 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: quoted-printable >From what I've seen, both routing decision and forwarding seem to be done= in=20 the routing agent. -----Message d'origine----- De : Leon Martin [mailto:leon70m@yahoo.com] Envoy=E9 : vendredi 18 f=E9vrier 2005 22:07 =C0 : manet@ietf.org Objet : [manet] Where is forwarding done in ns2? Hi all, I am trying to do static routing for MANET in ns-2. To do this, I need to know where _forwarding_, instead of _routing_, is=20 implemented in ns2 (2.27). Does anyone know whether the forwarding decision is made by AODV or by IP? Thanks. - Leon __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Nouveau MSN Hotmail : 250 Mo d'espace de stockage gratuit !=20 http://www.msn.fr/newmsnhotmail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 13:08:06 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26866 for ; Mon, 21 Feb 2005 13:08:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3IKv-0000NO-PE for manet-web-archive@ietf.org; Mon, 21 Feb 2005 13:31:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3GcS-0003Q5-L9; Mon, 21 Feb 2005 11:41:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3FxB-0003sP-H4 for manet@megatron.ietf.org; Mon, 21 Feb 2005 10:58:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13884 for ; Mon, 21 Feb 2005 10:58:16 -0500 (EST) Received: from mailer.cacs.louisiana.edu ([130.70.72.22]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3GJF-0005ay-A2 for manet@ietf.org; Mon, 21 Feb 2005 11:21:21 -0500 Received: from wupc.cacs.louisiana.edu (wupc.cacs.louisiana.edu [130.70.77.10]) by mailer.cacs.louisiana.edu (8.13.1/8.12.11) with ESMTP id j1LFvqrI021998; Mon, 21 Feb 2005 09:57:52 -0600 Date: Mon, 21 Feb 2005 09:57:52 -0600 (CST) From: "Dr. Hongyi Wu" X-X-Sender: To: , , Subject: [manet] ACM MONET Special Issue on SOFT RADIO-ENABLED HETEROGENEOUS WIRELESS NETWORKS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.82/718/Mon Feb 21 04:38:57 2005 on mailer.cacs.louisiana.edu X-Virus-Status: Clean X-Spam-Score: 0.1 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c [Apologies if you receive multiple copies of this CFP] ============================================================== ACM Mobile Networks and Applications (MONET) Special Issue On SOFT RADIO-ENABLED HETEROGENEOUS WIRELESS NETWORKS =============================================================== ********** Paper submission deadline: March 1, 2005 ********** With Guest Editors Dr. Guohong Cao Dept. of Computer Science and Engineering The Pennsylvania State University TEL: 814-863-1241 FAX: 814-865-3176 E-mail: gcao@cse.psu.edu Dr. Dapeng Wu Dept. of Electrical & Computer Engineering University of Florida TEL: 352-392-4954 FAX: 352-392-0044 E-mail: wu@ece.ufl.edu Dr. Hongyi Wu (contact) The Center for Advanced Computer Studies University of Louisiana at Lafayette TEL: 337-482-5779 FAX: 337-482-5791 E-mail: wu@cacs.louisiana.edu Dr. Junshan Zhang Department of Electrical Engineering Arizona State University TEL: 480-727-7389 FAX: 480-965-8325 E-mail: Junshan.Zhang@asu.edu With various network characteristics, a number of wireless systems have been developed over past years, targeting at different applications. While most of these wireless technologies are deployed independently for now, the service providers surely intend to own and operate overlaid heterogeneous wireless systems, which integrate multiple wireless technologies with partially overlapped coverage areas and provide ubiquitous network service to mobile users. Recent advances in reconfigurable computing have greatly advanced the design of soft radios, which enable the communication with many different radios with only a reconfiguration in software parameters. The maturation of soft radio technology is becoming one of the most important milestones for seamless integration of the heterogeneous wireless network. Serving as the "glue", the soft radio technology has its niche in in two folds: (1) the network infrastructure can be built upon soft radio, where the base stations are tunable to different frequency bands and serve as general access points for various mobile hosts (MHs), e.g., cellular handsets, laptops, and PDA's (Personal Digital Assistants); and (2) the MHs may employ soft radio, and accordingly, get access to various wireless systems (such as wireless LAN, cellular, IEEE 802.20, and IEEE 802.16), providing ubiquitous service for mobile users. An important design issue is to capitalize on the recent achievement in soft radio technology for providing improved and more efficient connectivity and service in heterogeneous wireless networks. With this special issue we aim at bringing together state-of-the-art contributions in this emerging area of soft radio-enabled heterogeneous wireless networks. We are seeking for papers reporting novel research or commercial/industrial experiences. These papers should be original, unpublished, and not currently under review by other conference, workshop, or journal. Topics of interest include, but are not limited to the following: - System optimization - Efficient spectrum allocation and management - Dynamic network topology discovery and optimization - Smart handoff and inter-system signaling - Quality of service in the heterogeneous networks - Routing and load balancing - Mobility management - System modeling and performance evaluation - Cognitive radio and testbed design * PUBLICATION SCHEDULE: o MANUSCRIPT DUE: March 1, 2005 o ACCEPTANCE NOTIFICATION: May 31, 2005 o FINAL MANUSCRIPT DUE: July 1, 2005 o EXPECTED PUBLICATION DATE: First Quarter, 2006 * SUBMISSION GUIDELINES: Authors should email an electronic (Postscript or PDF) copy of their papers to Dr. Hongyi Wu, wu@cacs.louisiana.edu, by March 1, 2005. Submissions should be limited to 20 double space pages excluding figures, graphs and illustrations. If email submission is impossible then six (6) copies of the paper (double-sided if possible) should be sent by the due date to: Dr. Hongyi Wu The Center for Advanced Computer Studies (CACS) University of Louisiana at Lafayette P.O. Box 44330 Lafayette, LA 70504-4330 Tel: 337-482-5779 All submissions will be reviewed following the standard procedure. --Hongyi ======================================================================== Dr. Hongyi Wu, Assistant Professor The Center for Advanced Computer Studies (CACS) University of Louisiana (UL) at Lafayette P.O. Box 44330, Lafayette, LA 70504-4330, U.S.A. Tel: 337-482-5779, Fax: 337-482-5791 E-mail: wu@cacs.louisiana.edu http://www.cacs.louisiana.edu/~wu ======================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 15:30:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11617 for ; Mon, 21 Feb 2005 15:30:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3KYs-0003wl-3K for manet-web-archive@ietf.org; Mon, 21 Feb 2005 15:53:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3J4E-00080L-0o; Mon, 21 Feb 2005 14:18:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3GxT-0007aj-9X for manet@megatron.ietf.org; Mon, 21 Feb 2005 12:02:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20845 for ; Mon, 21 Feb 2005 12:02:47 -0500 (EST) Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3HJh-0007H2-1b for manet@ietf.org; Mon, 21 Feb 2005 12:25:54 -0500 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id CC56032893; Mon, 21 Feb 2005 12:02:46 -0500 (EST) Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17]) by mail.eecis.udel.edu (Postfix) with ESMTP id 0D34D32890 for ; Mon, 21 Feb 2005 12:02:44 -0500 (EST) Date: Mon, 21 Feb 2005 12:02:44 -0500 (EST) From: Sonny Rajagopalan X-X-Sender: rajagopa@stimpy.eecis.udel.edu To: manet@ietf.org Message-ID: X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on louie.udel.edu X-Spam-Status: No, hits=-0.5 required=4.1 tests=BAYES_00 autolearn=ham version=2.64 X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm, v 1.64 2002/10/22 MIME-Version: 1.0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] DYMO Internet draft question X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Hello, I went through the Internet draft on DYMO at http://www.ietf.org/internet-drafts/draft-ietf-manet-dymo-00.txt. It made for very interesting reading. However, I had a couple of questions on the draft. In the draft, the authors mention DYMO "offers quick adaptation to dynamic conditions, low processing and memory overhead..." I was wondering what aspect of DYMO makes it more adaptive. Also, how do the authors define the word "adaptive," and exactly what "dynamic conditions" do the authors refer to? Specifically, does DYMO adapt to mobility, topology change, increased collisions, congestion etc.? If so, how does DYMO adapt to each problem? For example, exactly how is congestion detected, and how does DYMO adapt to congestion? Does anyone know of a paper discussing these aspects of DYMO? Please let me know. Any information is greatly appreciated. Cheers, Sonny. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 15:56:03 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14314 for ; Mon, 21 Feb 2005 15:56:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3KxS-0004fj-T9 for manet-web-archive@ietf.org; Mon, 21 Feb 2005 16:19:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3J4T-0008AZ-8S; Mon, 21 Feb 2005 14:18:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3H5Y-0000YH-Kj for manet@megatron.ietf.org; Mon, 21 Feb 2005 12:11:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21698 for ; Mon, 21 Feb 2005 12:11:08 -0500 (EST) Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3HRm-0007TA-Tc for manet@ietf.org; Mon, 21 Feb 2005 12:34:15 -0500 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.12.10/8.12.10) with ESMTP id j1LHB4TL026014; Mon, 21 Feb 2005 18:11:05 +0100 Message-ID: <421A1636.6000208@unibas.ch> Date: Mon, 21 Feb 2005 18:11:18 +0100 From: Christophe Jelger Organization: University of Basel User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ryuji Wakikawa Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.1.8 X-SMTP-Vilter-Virus-Backend: savse X-SMTP-Vilter-Status: clean X-SMTP-Vilter-savse-Virus-Status: clean X-SMTP-Vilter-Unwanted-Backend: attachment X-SMTP-Vilter-attachment-Unwanted-Status: clean X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Content-Transfer-Encoding: 7bit Hello Ryuji, Before I trigger another hot topic of discussion (in a separate email), here are some comments about the draft. As a general comment, I think most of the draft gives a reasonable view of IPv6 networking in a MANET. Some more detailed comments (sorry for the long email). I'm purposely a bit "nasty" sometimes, of course don't take it personnaly, my goal is just to trigger discussions. About the "broadcast" address : shall we use ff02::1 or ff02::2, or even both ? I mean some messages could be sent to all nodes, and other messages can be sent to all_nodes_that_also_do_routing. This triggers the question : do we allow nodes in a MANET not to take part in the routing activity ? If yes, then using ff02::1 and ff02::2 would make sense because we could differentiate between nodes/routers from nodes/non_routers. Section 2.2 : I think using unique local unicast addresses in a MANET makes a lot of sense since they (sort of) replace site-local addresses. However, the BIG problem is that such addresses are not automatically generated. I think that's really annoying, because if there is no special host to advertise such a prefix, the nodes of an autonomous MANET would not create such an address, and would then not be able to communicate since we don't route link-local addresses. Now if each MANET node was allowed to generate the Global ID and subnet ID fields (56 bits, chosen via some random method), then all the nodes could at least have an address routeable in the MANET. Maybe a well-known MANET_Global_ID could even be used and reserved for MANETs. Each node could then compute its own Subnet_ID randomly. So ok all the nodes in the MANET would not use the same prefix, but is it really important ? (as you say in Section 3.1, a node can keep its unique local even when merges/partitions occur). Or do we want prefix continuity ? (as defined in my soon_updated draft ;-) Section 3.2 : I would avoid talking about "foreign" network, as it does not have a clear meaning in a MANET (unless you relate it to MIP). Section 4 : from previous discussions on the autoconf mailing list with C. Perkins and P. Engelstaad, I'm still not sure that such a strict statement is clear/right. As you explain in Section 7.1, top of page 9, a node should sometimes avoid using the tunnel when it uses its home address. I fully agree with that, but is this in agreement with RFC 3484 ? (which says use the home address, which for me means "use the tunnel" because home address is by essence topologically not correct, despite not written explicitely in RFC 3484). I think this is opened to interpretation, so maybe one should be very clear about that. Section 6.1 : By IP flooding, do you mean some sort of multicast routing ? (as broadcast/multicast is the same thing with IPv6). I mean, this forwarding entry would be setup dynamically (by some multicast routing protocol) or would it be a static "well-known" forwarding behavior ? If yes, then one must be careful about leaks : you don't want the flooding to "escape" from the MANET, but that means the gateway must be aware that some of its interfaces are not in the MANET, and as you say in Section 5.1 that "there is no mechanism to detect whether attached network is a MANET or a normal IPv6 network". Moreover, I would remove the statement that the all_manet_multicast address can also be defined for unique local scope, because these addresses have (strictly speaking) a global scope (but are not globally routeable). Section 7.1 : as I said earlier, I agree that the tunnel should of course not be used to communicate with MANET nodes, but in the mean time the home address is somehow meaningless if the tunnel cannot be used. Especially if a unique local address can be used inside the MANET. So I would not defend the use of the home address when global connectivity is not available : use of some MANET-scope addresses is easier. Hope you find these comments useful. Regards, Christophe Ryuji Wakikawa wrote: > Hi Christophe and Ian > > We submitted a new draft regarding IPv6 support on MANET. > The flooding address is discussed in the draft. > > http://www.ietf.org/internet-drafts/draft-wakikawa-manet-ipv6-support-00.txt > > Any comments are appreciated. > > thanks > ryuji > > At Fri, 18 Feb 2005 11:57:50 +0100, > Christophe Jelger wrote: > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 16:08:21 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15304 for ; Mon, 21 Feb 2005 16:08:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3L9N-0004xi-5R for manet-web-archive@ietf.org; Mon, 21 Feb 2005 16:31:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3JAT-0000e8-5O; Mon, 21 Feb 2005 14:24:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3HPU-0003p1-4U for manet@megatron.ietf.org; Mon, 21 Feb 2005 12:31:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23417 for ; Mon, 21 Feb 2005 12:31:44 -0500 (EST) Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Hli-0007uD-SS for manet@ietf.org; Mon, 21 Feb 2005 12:54:51 -0500 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.12.10/8.12.10) with ESMTP id j1LHVhTL026231; Mon, 21 Feb 2005 18:31:44 +0100 Message-ID: <421A1B0D.1040005@unibas.ch> Date: Mon, 21 Feb 2005 18:31:57 +0100 From: Christophe Jelger Organization: University of Basel User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ryuji Wakikawa Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.1.8 X-SMTP-Vilter-Virus-Backend: savse X-SMTP-Vilter-Status: clean X-SMTP-Vilter-savse-Virus-Status: clean X-SMTP-Vilter-Unwanted-Backend: attachment X-SMTP-Vilter-attachment-Unwanted-Status: clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: 7bit Ryuji/all, Well I thought I would post the hot topic issue in a separate email for clarity. ;-) --- Hot topic 1 : I think most of the content of the draft makes sense, as soon as one agrees about the definition of a "link" in a MANET. It's clear that the MANET WG consensus is that a MANET is a multi-hop multi-link network, i.e. the link-layer is composed of multiple links. Well that's one definition which is fine and in full accordance with IETF activities which are targeted above layer 2. But as Ryuji states in Section 2.1, can we see a MANET as a unique layer 2 segment ? I know this is not the WG consensus, but it's a very viable assumption. In particular, usual IPv6 operations can be re-used without modifications since we emulate a broadcast link. Autoconf, neighbor discovery, DAD, everything can be used straightforward. An example is the LUNAR protocol (see http://core.it.uu.se/adhoc), which sits below IP and fools the IP layer by emulating the behavior of a LAN. --- Hot topic 2 : Now I also remember talking on the autoconf mailing list with some people about different things which lead us to the definition of a MANET ... and I was particularly puzzled by statements such as : two inter-connected MANETs. Which leads to the immediate question : how do we define the boundaries of a MANET ? I think this issue should seriously be considered, especially if we want to do global address autoconfiguration with multiple gateways and prefixes. Of course ;-) I still advocate the use of prefix continuity, as a mean to create logical sub-networks inside a MANET. I will hopefully update my draft this week. Hope this will trigger some discussions on the autoconf list which is too quiet since Christmas break. ;-) Best regards, Christophe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 21 17:29:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22848 for ; Mon, 21 Feb 2005 17:29:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3MQ1-000704-O2 for manet-web-archive@ietf.org; Mon, 21 Feb 2005 17:52:48 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Jxa-0007UO-Jh; Mon, 21 Feb 2005 15:15:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3IlN-0005ym-C5 for manet@megatron.ietf.org; Mon, 21 Feb 2005 13:58:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01255 for ; Mon, 21 Feb 2005 13:58:27 -0500 (EST) Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3J7b-0001df-WC for manet@ietf.org; Mon, 21 Feb 2005 14:21:33 -0500 Received: from [192.168.2.19] (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id TAA20964; Mon, 21 Feb 2005 19:58:48 +0100 (MET) Message-ID: <421A2F40.7080902@telecom.lth.se> Date: Mon, 21 Feb 2005 19:58:08 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Yann ." Subject: Re: RE : [manet] Where is forwarding done in ns2? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by anyida.tts.lth.se id TAA20964 X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: quoted-printable Hi, I agree with Yann; in aodv.cc you can find void AODV::forward(aodv_rt_entry *rt, Packet *p, double delay) { which I think is what you're looking for. Kind regards Ali Yann . wrote: >> From what I've seen, both routing decision and forwarding seem to be=20 >> done in=20 > > the routing agent. > > > > -----Message d'origine----- > De : Leon Martin [mailto:leon70m@yahoo.com] > Envoy=E9 : vendredi 18 f=E9vrier 2005 22:07 > =C0 : manet@ietf.org > Objet : [manet] Where is forwarding done in ns2? > > > Hi all, > > I am trying to do static routing for MANET in ns-2. To > do this, I need to know where _forwarding_, instead of _routing_, is=20 > implemented in ns2 (2.27). > > Does anyone know whether the forwarding decision is > made by AODV or by IP? > > Thanks. > > - Leon > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > _________________________________________________________________ > Nouveau MSN Hotmail : 250 Mo d'espace de stockage gratuit !=20 > http://www.msn.fr/newmsnhotmail > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Feb 22 08:59:46 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02171 for ; Tue, 22 Feb 2005 08:59:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3awJ-0005qo-AU for manet-web-archive@ietf.org; Tue, 22 Feb 2005 09:23:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3MN6-000417-Gg; Mon, 21 Feb 2005 17:49:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3KUT-0004qJ-N4 for manet@megatron.ietf.org; Mon, 21 Feb 2005 15:49:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13662 for ; Mon, 21 Feb 2005 15:49:07 -0500 (EST) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Kqj-0004VE-Gc for manet@ietf.org; Mon, 21 Feb 2005 16:12:14 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j1LLIPJ16930; Mon, 21 Feb 2005 13:18:25 -0800 X-mProtect: <200502212118> Nokia Silicon Valley Messaging Protection Received: from danira-pool051114.americas.nokia.com (10.241.51.114, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdPbj7Mc; Mon, 21 Feb 2005 13:18:15 PST Message-ID: <421A4903.4040001@iprg.nokia.com> Date: Mon, 21 Feb 2005 12:48:03 -0800 From: "Charles E. Perkins" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manetautoconf@ml.free.fr Subject: Re: [MANET-AUTOCONF] Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> In-Reply-To: <421A1B0D.1040005@unibas.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, Ryuji Wakikawa X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: 7bit Hello Christophe, Here are some comments on your topics. ext Christophe Jelger wrote: >But as Ryuji states in Section 2.1, can we see a MANET as a unique layer >2 segment ? I know this is not the WG consensus, but it's a very viable >assumption. In particular, usual IPv6 operations can be re-used without >modifications since we emulate a broadcast link. Autoconf, neighbor >discovery, DAD, everything can be used straightforward. An example is >the LUNAR protocol (see http://core.it.uu.se/adhoc), which sits below IP >and fools the IP layer by emulating the behavior of a LAN. > > Surely it's possible, but then it seems to me that you are hiding some multi-hop operations underneath layer 3. For instance, you used the word "fools". I think this strategy goes along the path towards restricting IP to run on top of things that resemble LANs. So, perhaps the argument should be settled according to whatever people think is the appropriate model for a network-layer protocol that purports to route between links. > ....... how do >we define the boundaries of a MANET ? I think this issue should >seriously be considered, especially if we want to do global address >autoconfiguration with multiple gateways and prefixes. > > Yes, I agree it needs serious consideration. I wonder if it has to be solved before we engineer an autoconfiguration protocol for a single MANET. I hope it doesn't, honestly. >Of course ;-) I still advocate the use of prefix continuity, as a mean >to create logical sub-networks inside a MANET. I will hopefully update >my draft this week. > > Do you insist that a router advertising a prefix should offer connectivity to every host addressable by way of that prefix? Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 00:12:09 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08882 for ; Wed, 23 Feb 2005 00:12:09 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3pBP-0001j7-RA for manet-web-archive@ietf.org; Wed, 23 Feb 2005 00:35:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3jAP-00032J-Lz; Tue, 22 Feb 2005 18:10:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3bs3-0000nA-6E for manet@megatron.ietf.org; Tue, 22 Feb 2005 10:22:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11222 for ; Tue, 22 Feb 2005 10:22:31 -0500 (EST) Received: from smtp1ct.adtran.com ([66.0.238.15] helo=adtran.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3cEO-0008Fx-6T for manet@ietf.org; Tue, 22 Feb 2005 10:45:49 -0500 Received: from ([172.22.48.36]) by smtp1.adtran.com with ESMTP id 133020114.12604273; Tue, 22 Feb 2005 09:21:30 -0600 Received: by srv-exchange1.adtran.com with Internet Mail Service (5.5.2657.72) id <156LCA2G>; Tue, 22 Feb 2005 09:17:55 -0600 Message-ID: <39B01E2189D99F4B8C9612462DB3922A153B9892@srv-exchange.adtran.com> From: DANIEL BYRNE To: "'Charles E. Perkins'" , manetautoconf@ml.free.fr Subject: RE: [MANET-AUTOCONF] Re: [manet] I-D ACTION:draft-ietf-manet-dymo -00.txt Date: Tue, 22 Feb 2005 09:27:08 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: manet@ietf.org, Ryuji Wakikawa X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 >But as Ryuji states in Section 2.1, can we see a MANET as a unique layer >2 segment ? I know this is not the WG consensus, but it's a very viable >assumption. In particular, usual IPv6 operations can be re-used without >modifications since we emulate a broadcast link. Autoconf, neighbor >discovery, DAD, everything can be used straightforward. An example is >the LUNAR protocol (see http://core.it.uu.se/adhoc), which sits below IP >and fools the IP layer by emulating the behavior of a LAN. > > What I love about the LUNAR protocol is that it frees the software from having to deal with the complexities of AD Hoc routing by creating virtual tunnels, or linked lists. The current node needs only to know the next hop. At that point Ad-Hoc rounting becomes a simple lookup table which can be implemented in hardware with a SDRAM buffer perhaps on the WiFi card itself. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 01:13:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16719 for ; Wed, 23 Feb 2005 01:13:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3q8u-0003qR-3N for manet-web-archive@ietf.org; Wed, 23 Feb 2005 01:37:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kft-0004Yi-Tu; Tue, 22 Feb 2005 19:46:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3e5l-0007bv-Cs for manet@megatron.ietf.org; Tue, 22 Feb 2005 12:45:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27460 for ; Tue, 22 Feb 2005 12:44:50 -0500 (EST) Received: from mail1.engr.ucsb.edu ([128.111.53.4] helo=smtp.engr.ucsb.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3eS9-0004L6-DB for manet@ietf.org; Tue, 22 Feb 2005 13:08:10 -0500 Received: from joshua.cs.ucsb.edu ([128.111.40.98]:63939) by smtp.engr.ucsb.edu with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1D3e5R-0000wh-6Z; Tue, 22 Feb 2005 09:44:43 -0800 Mime-Version: 1.0 (Apple Message framework v619.2) Message-Id: <82c19e25ca9997c25d83f7891d303c99@cs.ucsb.edu> From: Ian Chakeres Date: Tue, 22 Feb 2005 09:44:42 -0800 To: manet X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: Determined clean by smtp.engr.ucsb.edu using clamd / ClamAV version 0.80 X-SA-Exim-Connect-IP: 128.111.40.98 X-SA-Exim-Mail-From: idc@cs.ucsb.edu Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on smtp.engr.ucsb.edu X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-SA-Exim-Version: 4.1 (built Mon, 13 Dec 2004 10:51:27 -0800) X-SA-Exim-Scanned: Yes (on smtp.engr.ucsb.edu) X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Cc: Joe Macker Subject: [manet] MANET IETF 62 Proposed Agenda X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Here is the proposed agenda for the MANET WG meeting at IETF 62. Please respond with questions and comments. Mobile Ad-hoc Networks (manet) ================================== CHAIRS: Joe Macker Ian Chakeres DRAFT AGENDA: Agenda Bashing and Status 5 min Macker WG Next Stage 20 min Macker DYMO Plans/Discussion 20 min Chakeres MPRP Plans/Discussion 20 min Clausen SMRF Plans/Discussion 20 min Perkins OSPF-MANET? 20 min AUTOCONF BOF? 10 min Open Discussion & Announcements 25 min _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 20:11:45 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07877 for ; Wed, 23 Feb 2005 20:11:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D47uT-0007ut-DX for manet-web-archive@ietf.org; Wed, 23 Feb 2005 20:35:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kmy-0006Ve-AZ; Tue, 22 Feb 2005 19:54:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Vc5-0008Pl-Av for manet@megatron.ietf.org; Tue, 22 Feb 2005 03:41:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27029 for ; Tue, 22 Feb 2005 03:41:42 -0500 (EST) Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3VyS-0003rn-56 for manet@ietf.org; Tue, 22 Feb 2005 04:04:56 -0500 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.12.10/8.12.10) with ESMTP id j1M8feTL015598; Tue, 22 Feb 2005 09:41:40 +0100 Message-ID: <421AF054.3020105@unibas.ch> Date: Tue, 22 Feb 2005 09:41:56 +0100 From: Christophe Jelger Organization: University of Basel User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manetautoconf@ml.free.fr Subject: Re: [MANET-AUTOCONF] Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> <421A4903.4040001@iprg.nokia.com> In-Reply-To: <421A4903.4040001@iprg.nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.1.8 X-SMTP-Vilter-Virus-Backend: savse X-SMTP-Vilter-Status: clean X-SMTP-Vilter-savse-Virus-Status: clean X-SMTP-Vilter-Unwanted-Backend: attachment X-SMTP-Vilter-attachment-Unwanted-Status: clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Content-Transfer-Encoding: 7bit Hello Charlie, See my comments inline. Regards Christophe Charles E. Perkins wrote: > Hello Christophe, > > Here are some comments on your topics. > > ext Christophe Jelger wrote: > > >>But as Ryuji states in Section 2.1, can we see a MANET as a unique layer >>2 segment ? I know this is not the WG consensus, but it's a very viable >>assumption. In particular, usual IPv6 operations can be re-used without >>modifications since we emulate a broadcast link. Autoconf, neighbor >>discovery, DAD, everything can be used straightforward. An example is >>the LUNAR protocol (see http://core.it.uu.se/adhoc), which sits below IP >>and fools the IP layer by emulating the behavior of a LAN. >> >> > > Surely it's possible, but then it seems to me that you are hiding > some multi-hop operations underneath layer 3. For instance, you > used the word "fools". I think this strategy goes along the path > towards restricting IP to run on top of things that resemble LANs. > So, perhaps the argument should be settled according to whatever > people think is the appropriate model for a network-layer protocol > that purports to route between links. Well you're right : such a solution hides the multihop nature of a MANET to IP. However, in many cases one may want a MANET to resemble a LAN ... and actually it is not so far from what is done in an infrastructure 802.11 network : the physical topology is a star, nodes cannot communicate directly, but still IP "is fooled" and sees a "broadcast-like" LAN. It can happen that 2 nodes are radio isolated as they communicate via the access point : so it's a clear two-hops communication, but no IP routing is involved. I just think that the LAN analogy is very useful in many cases, it's a pity that it has not been considered more by the WG. > > >> ....... how do >>we define the boundaries of a MANET ? I think this issue should >>seriously be considered, especially if we want to do global address >>autoconfiguration with multiple gateways and prefixes. >> >> > > Yes, I agree it needs serious consideration. I wonder if it has to > be solved before we engineer an autoconfiguration protocol for > a single MANET. I hope it doesn't, honestly. Probably we don't need to solve this before we have a first autoconfiguration protocol, but I think we should always keep this in mind so that if we want logical organizations in a MANET we can easily add such an extension. > > >>Of course ;-) I still advocate the use of prefix continuity, as a mean >>to create logical sub-networks inside a MANET. I will hopefully update >>my draft this week. >> >> > > Do you insist that a router advertising a prefix should offer > connectivity to every host addressable by way of that prefix? I'm sorry I'm not sure I fully understand what you mean by that. Prefix continuity was just the idea that we can create contiguous (connected) logical sub-networks inside a MANET. Can you please clarify your point ? As I said in a previous email, I will submit a updated version of my draft later this week : I removed some non-vital stuff, and try to have a short proposal. > > Regards, > Charlie P. > > > MANET Autoconf mailing-list > To unsubscribe: mailto:manetautoconf-request@ml.free.fr?subject=unsubscribe > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 20:19:10 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10184 for ; Wed, 23 Feb 2005 20:19:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D481e-0000FZ-HK for manet-web-archive@ietf.org; Wed, 23 Feb 2005 20:42:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D47MG-0004xn-IC; Wed, 23 Feb 2005 20:00:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D47MD-0004wL-PY for manet@megatron.ietf.org; Wed, 23 Feb 2005 19:59:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03582 for ; Wed, 23 Feb 2005 19:59:53 -0500 (EST) Received: from web21004.mail.yahoo.com ([216.136.227.58]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D47iy-0006dK-Ei for manet@ietf.org; Wed, 23 Feb 2005 20:23:31 -0500 Received: (qmail 29878 invoked by uid 60001); 24 Feb 2005 00:59:50 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=QWSGrbRo0jkxggn+tWEpKIv+8obUsTbbYJUGPbsysYu139/orkl9u3YODK8EhZ3Gqo7hW8Fxqsbh22RKUWwv8SBh5Js3vzIM6DWErkzTfcN/Clx0oNnZjSVwcIiWBo7qhy0d8/rqD0vCOL6YxeGAV4fzEbsHowJ8ENn28Iz0dKM= ; Message-ID: <20050224005950.29876.qmail@web21004.mail.yahoo.com> Received: from [141.225.9.235] by web21004.mail.yahoo.com via HTTP; Wed, 23 Feb 2005 16:59:50 PST Date: Wed, 23 Feb 2005 16:59:50 -0800 (PST) From: Yang Xiao To: manet@ietf.org In-Reply-To: <421D258B.7050303@stfx.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.6 (/) X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb Subject: [manet] ICWN-05 CFP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3971661e40967acfc35f708dd5f33760 -------------------------------------------------------------------------------- CALL FOR PAPER The 2005 International Conference on Wireless Networks (ICWN-05) Monte Carlo Resort, Las Vegas, Nevada, USA, June 27-30, 2005 http://juliet.stfx.ca/~lyang/icwn-05/ -------------------------------------------------------------------------------- Scope and Interests: The International Multi-conference in Computer Science and Computer Engineering is a major annual international research event. The last Multi-conference attracted over 1,650 computer science and Engineering researchers from 78 countries. It is anticipated that the 2005 International Multi-conference will attract about 2000 participants. The ICWN-05 is one of the major 18 planned events. Topics of interest include, but are not limited to: Mobile wireless QoS, radio resource management Mobile wireless Internet, IPv6 Heterogeneous wireless networks, radio access networks OFDM W-CDMA, cdma2000, TD-SCDMA, ... MIMO, adaptive antenna Software-defined radio, reconfigurable radio networks Wireless security Wireless applications, mobile e-commerce, multimedia Satellite-based systems Broadcast networks High altitude platform GPS, location-based service Mobile agents Wireless & mobile applications Multiple access Routing, multicasting, ... Resource management, wireless QoS Mobile Internet Transport-layer issues Wireless security Wireless network architectures Mobile computing Modeling, simulation, ... Ad hoc networks, sensor networks, ... 4G, 3.5G, 3G, ... wireless systems Personal area networks, body wireless networks, Bluetooth Wireless sensor networks Coding & modulation Multi-user detection Power management & control, low-power protocols Wireless IP networks, interworking Wireless multimedia, QoS adaptation WAP, mobile e-commerce Location-based service, GPS Distributed algorithms for wireless networks SUBMISSION INFORMATION ---------------------- Prospective authors are invited to submit their draft papers in PS or PDF format to conference program chairs via electronic mail. Papers must not have been previously published or currently submitted for publication elsewhere. The first page of the draft paper should include: title of the paper, name, affiliation, postal address, E-mail address, telephone number, & Fax number for each author. The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Contributions will be reviewed by at least three reviewers from both Program Committee and external reviewers for originality, significance, clarity, soundness, relevance and technical contents on basis of papers. The length of the Camera-Ready papers (if accepted) will be limited to 7 (IEEE style) pages. The conference proceedings will be published by CSREA Press (ISBN) in hardcopy/book. The proceedings will be available at the conference. In addition to the hardcopy, it is also planned to publish the papers on a CD. All conference proceedings published by CSREA Press are considered for inclusion in major database indexes that are designed to provide easy access to the current literature of the sciences (database examples: ISI Thomson Scientific, IEE INSPEC, ...). The program committee will select one winner for the Best Paper Award (all regular papers are eligible) and one winner for the Best Student Paper Award (only the regular papers whose first author is a full-time student are eligible). Each winner will be presented at the conference with a certificate and cash. A special issue of best selected papers at International Journal of Wireless and Mobile Computing (IJWMC) has been scheduled. IMPORTANT DATES --------------- Paper submission Due March 14, 2005 Notification of Acceptance April 11, 2005 Final camera-ready paper + registration April 20, 2005 CONFERENCE CHAIRS ----------------- Prof. Laurence T. Yang (General Co-Chair) St. Francis Xavier University, Canada Email: lyang@stfx.ca Prof. Chi-Hsiang Yeh (General Co-Chair) Queen's University, Canada Email: chi-hsiang.yeh@ece.queensu.ca Prof. Mirela S Moretti Annoni Notare (Program Co-Chair) Barddal University, Brazil Email: mirela@barddal.br Dr. Li-Chun Wang (Program Co-Chair) National Chiao-Tung University, Taiwan Email: lichun@cc.nctu.edu.tw Dr. Geyong Min (Program Vice-Chair) University of Bradford, U.K Email: g.min@brad.ac.uk Dr. Yang Xiao (Program Vice-Chair) University of Memphis, USA Email: yangxiao@memphis.edu Dr. Jingyuan(Alex) Zhang (Program Vice-Chair) University of Alabama, USA Email: zhang@cs.ua.edu Dr. Xiaobao Zhou (Program Vice-Chair) University of Colorado, USA Email: zbo@rabbit.uccs.edu STEERING COMMITTEE ------------------ Hamid R. Arabnia (chair), University of Georgia, USA Laurence T. Yang, St. Francis Xavier University, Canada TECHNICAL/PROGRAM COMMITTEE ---------------------------- To be added -----------------ENDS--------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 21:17:28 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00459 for ; Wed, 23 Feb 2005 21:17:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D48w4-0006SC-3Y for manet-web-archive@ietf.org; Wed, 23 Feb 2005 21:41:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ooA-0004uv-2W; Wed, 23 Feb 2005 00:11:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3oo3-0004sz-1g for manet@megatron.ietf.org; Wed, 23 Feb 2005 00:11:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08743 for ; Wed, 23 Feb 2005 00:11:14 -0500 (EST) Received: from sitemail3.everyone.net ([216.200.145.37] helo=omta06.mta.everyone.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3pAV-0001h3-Db for manet@ietf.org; Wed, 23 Feb 2005 00:34:40 -0500 Received: from sitemail.everyone.net (bigiplb-dsnat [172.16.0.19]) by omta06.mta.everyone.net (Postfix) with ESMTP id 69DDF41162; Tue, 22 Feb 2005 21:11:12 -0800 (PST) Received: by sitemail.everyone.net (Postfix, from userid 99) id 184493948; Tue, 22 Feb 2005 21:11:12 -0800 (PST) Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Date: Tue, 22 Feb 2005 21:11:11 -0800 (PST) From: venkata sivannarayana muppalla To: manet@ietf.org X-Originating-Ip: [210.212.228.8] X-Eon-Sig: AQH7p09CHBBwAACt9AEAAAAC,c26f3806325c5737935c2617ac9a356c Message-Id: <20050223051112.184493948@sitemail.everyone.net> X-Spam-Score: 0.9 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Cc: ns-users@isi.edu Subject: [manet] how to specify radius for mobilenode X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: muppalla999@ragalahari.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Hi all i want to specify the transmission range of a mobilenode to be 50. where and how should i write the code for that. Thanks in advance Thanks & Regards M.V.Sivannarayana Be great in act, as you are in thought _____________________________________________________________ Listen to Non Stop Music @ http://www.ragalahari.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 22:35:49 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29859 for ; Wed, 23 Feb 2005 22:35:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4A9r-0006YK-Ui for manet-web-archive@ietf.org; Wed, 23 Feb 2005 22:59:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3yMU-0006tI-9f; Wed, 23 Feb 2005 10:23:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3yMS-0006sV-T0 for manet@megatron.ietf.org; Wed, 23 Feb 2005 10:23:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26607 for ; Wed, 23 Feb 2005 10:23:28 -0500 (EST) Received: from web51601.mail.yahoo.com ([206.190.38.206]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D3yj4-0004xM-AB for manet@ietf.org; Wed, 23 Feb 2005 10:47:00 -0500 Received: (qmail 27465 invoked by uid 60001); 23 Feb 2005 15:23:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=hO4YKmMpKaXO3/ZvsI2fR11rhHbGkgx6viGRq42K6Jq3/q7kfUOz3/5T8H1iAHfZEy2Mpw+MxMMq2TqkhnwOJkqPkA3poW9xYLFAWAYQuVEAaxO+z2zmqsDGb1pEf0B3bhnCuJ6r10eNJIBVn+f8koenOG4k3NyyYOeguVGJADs= ; Message-ID: <20050223152316.27461.qmail@web51601.mail.yahoo.com> Received: from [161.246.1.33] by web51601.mail.yahoo.com via HTTP; Wed, 23 Feb 2005 07:23:15 PST Date: Wed, 23 Feb 2005 07:23:15 -0800 (PST) From: TAING Nguon To: ns-users@ISI.EDU, manet@ietf.org In-Reply-To: <20050223094239.96946.qmail@web51602.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.9 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Subject: [manet] Unable to extract shortest path in DSR X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Dear all, I used sample program wireless1.tcl of the tutoral. I havent changed any thing including connection pattern and scenario file, excepts adding some portion of code to that tcl file. The added code is as below: -------- Agent/DSRAgent instproc handlePktWithoutSR {length} { puts "length $length" } ----------- MobiCache instproc findRoute {Rlength} { puts "Route Length $Rlength" } ------------ 1. The first block, I tried to get a path from dsragent.cc. In DSRAgent::handlePktWithoutSR, before RETURN statement of the block IF (ROUTE_CACHE->findRoute(p.dest, p.route, 1)), I added some code as below: ------------ char out[100] ; // Prepare the output to the Tcl interpreter. sprintf(out, "%s handlePktWithoutSR %d",name(), p.route.length() ); Tcl& tcl = Tcl::instance(); tcl.eval(out); ------------- 2. The second block, I tried to get shortest path from mobicache.cc file. In MobiCache::findRoute, before RETURN TRUE in the IF ( MIN_CACHE) block, I added some code as below: --------------- char Rlength[100]; sprintf(Rlength, "%s findRoute %d",name(), min_length ); Tcl& tcl = Tcl::instance(); tcl.eval(Rlength); -------------- 3. after that i used command - make clean - make - ns wireless1.tcl when I run simulation(ns wireless1.tcl), I got nothing even from dsragent.cc or mobicache.cc. I would like to know the adding code is incorrect or I placed my adding code to an inccorect place. Please help me. Thanks very much for your times. Looking forward to hearing from you. Regards, Nguon __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 23:21:14 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16596 for ; Wed, 23 Feb 2005 23:21:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Ars-0002wu-23 for manet-web-archive@ietf.org; Wed, 23 Feb 2005 23:44:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3knI-0006el-59; Tue, 22 Feb 2005 19:54:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3WIp-00075L-ON for manet@megatron.ietf.org; Tue, 22 Feb 2005 04:26:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04886 for ; Tue, 22 Feb 2005 04:25:54 -0500 (EST) Received: from isis.lip6.fr ([132.227.60.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3WfE-0005nL-KS for manet@ietf.org; Tue, 22 Feb 2005 04:49:09 -0500 Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) by isis.lip6.fr (8.13.1/jtpda-5.4+victor) with ESMTP id j1M9PNJP006210 ; Tue, 22 Feb 2005 10:25:23 +0100 X-pt: isis.lip6.fr Received: from [132.227.61.11] (ariane [132.227.61.11]) by tibre.lip6.fr (8.11.6p3/8.11.6) with ESMTP id j1M9PNp20154; Tue, 22 Feb 2005 10:25:23 +0100 (CET) In-Reply-To: <421A1B0D.1040005@unibas.ch> References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <35411357dc6782b9024498609f82060f@insa-lyon.fr> Content-Transfer-Encoding: 7bit From: Guillaume Chelius Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt Date: Tue, 22 Feb 2005 10:23:53 +0100 To: Christophe Jelger X-Mailer: Apple Mail (2.619.2) X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.5.10 (isis.lip6.fr [132.227.60.2]); Tue, 22 Feb 2005 10:25:24 +0100 (CET) X-Scanned-By: isis.lip6.fr X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, Ryuji Wakikawa , manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Hi all, > But as Ryuji states in Section 2.1, can we see a MANET as a unique > layer 2 segment ? I know this is not the WG consensus, but it's a very > viable assumption. In particular, usual IPv6 operations can be re-used > without modifications since we emulate a broadcast link. Autoconf, > neighbor discovery, DAD, everything can be used straightforward. An > example is the LUNAR protocol (see http://core.it.uu.se/adhoc), which > sits below IP and fools the IP layer by emulating the behavior of a > LAN. This is also the philosophy of the Ananas (http://sourceforge.net/projects/ananas) protocol which emulates a broadcast medium on top of a multiple-interface MANet. However, it is quite clear that implementing MANet at level 2 is not the WG philosophy. > --- Hot topic 2 : > > Now I also remember talking on the autoconf mailing list with some > people about different things which lead us to the definition of a > MANET ... and I was particularly puzzled by statements such as : two > inter-connected MANETs. Which leads to the immediate question : how do > we define the boundaries of a MANET ? I think this issue should > seriously be considered, especially if we want to do global address > autoconfiguration with multiple gateways and prefixes. Christophe, I agree with you on the fact that the definnition of a MANet boundary should be seriously considered. As you said in your previous mail, this issue is also bound to the flooding problem. When performing a flooding on the all-manet-multicast address, we do not want the packet to go to the Internet through Internet-connected gateway interfaces. We must have some way to differentiate interfaces connected to a MANet from interfaces that are not. This is one thing we proposed in an earlier draft: draft-chelius-adhoc-ipv6-00.txt Best regards, Guillaume Chelius. ---------------------------- ARES Project, INRIA web: http://ares.insa-lyon.fr/~gchelius mail: guillaume.chelius@insa-lyon.fr phone: (+33) 472 436 182 fax: (+33) 472 436 227 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Feb 23 23:53:38 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27715 for ; Wed, 23 Feb 2005 23:53:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4BND-0006KP-2r for manet-web-archive@ietf.org; Thu, 24 Feb 2005 00:17:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kno-0006sS-Jc; Tue, 22 Feb 2005 19:54:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ZlU-0004BS-CY for manet@megatron.ietf.org; Tue, 22 Feb 2005 08:07:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27224 for ; Tue, 22 Feb 2005 08:07:40 -0500 (EST) Received: from nemo.cce.unipr.it ([160.78.48.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3a7q-0004GS-R4 for manet@ietf.org; Tue, 22 Feb 2005 08:30:57 -0500 Received: from mammolo.tlc.unipr.it (mammolo.tlc.unipr.it [160.78.29.96]) by smtp.unipr.it (8.11.6/8.11.6) with ESMTP id j1MD6tD09320 for ; Tue, 22 Feb 2005 14:06:55 +0100 From: Marco Date: Tue, 22 Feb 2005 14:06:58 +0100 User-Agent: KMail/1.5.1 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200502221406.58493.bragalini_m@tiscali.it> X-CCE-UniPR-MailScanner: Found to be clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: quoted-printable Subject: [manet] Fwd: problem with scheduler X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: quoted-printable =2D--------- Messaggio inoltrato ---------- Subject: problem with scheduler Date: 09:59, marted=EC 22 febbraio 2005 =46rom: Marco To: ns-users@isi.edu Hy guys, I want to modify battery consumption of a tx node in C++. I have implemented the commands: Tcl& tcl =3D Tcl::instance(); tcl.evalf("$ns_ at %f \"$node_(%d) setPt %f\"",NOW,i,pt); where i is txnode and pt is the power. When I run the simulation, I obtain this error: ns: $ns_ at 69.235425 "$node_(4) setPt 0.281800": can't schedule command in past (_o5 cmd line 1) invoked from within "_o5 cmd at 69.235425 {_o90 setPt 0.281800}" invoked from within "catch "$self cmd $args" ret" invoked from within "if [catch "$self cmd $args" ret] { set cls [$self info class] global errorInfo set savedInfo $errorInfo error "error when calling class $cls: $args" $..." (procedure "_o5" line 2) (SplitObject unknown line 2) invoked from within "_o5 at 69.235425 {_o90 setPt 0.281800}" ("eval" body line 1) invoked from within "eval $scheduler_ at $args" (procedure "_o3" line 3) (Simulator at line 3) invoked from within "$ns_ at 69.235425 "$node_(4) setPt 0.281800"" I don't understand what it means... Thanks, Marco =2D------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 24 02:55:00 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13241 for ; Thu, 24 Feb 2005 02:55:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4ECl-0005gq-9i for manet-web-archive@ietf.org; Thu, 24 Feb 2005 03:18:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Doh-0000iG-2Q; Thu, 24 Feb 2005 02:53:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Dlm-0006ca-5I for manet@megatron.ietf.org; Thu, 24 Feb 2005 02:50:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12945 for ; Thu, 24 Feb 2005 02:50:44 -0500 (EST) Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4E8c-0005c2-44 for manet@ietf.org; Thu, 24 Feb 2005 03:14:23 -0500 Received: from samurai.local.sfc.wide.ad.jp (PA206078.au-net.ne.jp [61.198.206.78]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.10/8.12.0) with ESMTP id j1O7oPFj026094; Thu, 24 Feb 2005 16:50:29 +0900 Date: Thu, 24 Feb 2005 15:56:10 +0900 Message-ID: From: Ryuji Wakikawa To: guillaume.chelius@insa-lyon.fr Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt In-Reply-To: <35411357dc6782b9024498609f82060f@insa-lyon.fr> References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> <35411357dc6782b9024498609f82060f@insa-lyon.fr> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin7.2.0) MULE/5.0 (SAKAKI) Organization: Keio University/WIDE MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: multipart/mixed; boundary="Multipart_Thu_Feb_24_15:56:10_2005-1" X-Spam-Score: 0.1 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: manet@ietf.org, ryuji@sfc.wide.ad.jp, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca --Multipart_Thu_Feb_24_15:56:10_2005-1 Content-Type: text/plain; charset=US-ASCII --Multipart_Thu_Feb_24_15:56:10_2005-1 Content-Type: text/plain; charset=US-ASCII > > > --- Hot topic 2 : > > > > Now I also remember talking on the autoconf mailing list with some > > people about different things which lead us to the definition of a > > MANET ... and I was particularly puzzled by statements such as : two > > inter-connected MANETs. Which leads to the immediate question : how do > > we define the boundaries of a MANET ? I think this issue should > > seriously be considered, especially if we want to do global address > > autoconfiguration with multiple gateways and prefixes. > > Christophe, I agree with you on the fact that the definnition of a > MANet boundary should be seriously considered. As you said in your > previous mail, this issue is also bound to the flooding problem. When > performing a flooding on the all-manet-multicast address, we do not > want the packet to go to the Internet through Internet-connected > gateway interfaces. We must have some way to differentiate interfaces > connected to a MANet from interfaces that are not. This is one thing we > proposed in an earlier draft: draft-chelius-adhoc-ipv6-00.txt For isolated MANET, the boundary can be defined as a range where flooded packet are reached in terms of hoplimit,etc. For connected MANET with IGW, the boundary can be simple defined with the address configuration mechanism. I.e. all the nodes assigned a global address form a MANET. I did not notice your draft, can you send me a copy? regards, ryuji --Multipart_Thu_Feb_24_15:56:10_2005-1 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --Multipart_Thu_Feb_24_15:56:10_2005-1-- From manet-bounces@ietf.org Thu Feb 24 02:57:51 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13539 for ; Thu, 24 Feb 2005 02:57:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4EFV-0005mH-U5 for manet-web-archive@ietf.org; Thu, 24 Feb 2005 03:21:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Doe-0000f9-TP; Thu, 24 Feb 2005 02:53:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Dle-0006Yb-DZ for manet@megatron.ietf.org; Thu, 24 Feb 2005 02:50:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12936 for ; Thu, 24 Feb 2005 02:50:36 -0500 (EST) Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4E8U-0005bh-4V for manet@ietf.org; Thu, 24 Feb 2005 03:14:15 -0500 Received: from samurai.local.sfc.wide.ad.jp (PA206078.au-net.ne.jp [61.198.206.78]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.10/8.12.0) with ESMTP id j1O7oGFj026091; Thu, 24 Feb 2005 16:50:19 +0900 Date: Thu, 24 Feb 2005 15:50:22 +0900 Message-ID: From: Ryuji Wakikawa To: Christophe.Jelger@unibas.ch Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt In-Reply-To: <421A1B0D.1040005@unibas.ch> References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin7.2.0) MULE/5.0 (SAKAKI) Organization: Keio University/WIDE MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Spam-Score: 0.1 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: manet@ietf.org, ryuji@sfc.wide.ad.jp, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Hello Christophe At Mon, 21 Feb 2005 18:31:57 +0100, Christophe Jelger wrote: > > Ryuji/all, > > Well I thought I would post the hot topic issue in a separate email for > clarity. ;-) > > --- Hot topic 1 : > > I think most of the content of the draft makes sense, as soon as one > agrees about the definition of a "link" in a MANET. It's clear that the > MANET WG consensus is that a MANET is a multi-hop multi-link network, > i.e. the link-layer is composed of multiple links. Well that's one > definition which is fine and in full accordance with IETF activities > which are targeted above layer 2. > > But as Ryuji states in Section 2.1, can we see a MANET as a unique layer > 2 segment ? I know this is not the WG consensus, but it's a very viable > assumption. In particular, usual IPv6 operations can be re-used without > modifications since we emulate a broadcast link. Autoconf, neighbor > discovery, DAD, everything can be used straightforward. An example is > the LUNAR protocol (see http://core.it.uu.se/adhoc), which sits below IP > and fools the IP layer by emulating the behavior of a LAN. I prefer the fist statement. My initial concern was NDP operation in MANET, because NDP is very tight to the link definition. It's not reasonable to modify NDP a lot for manet. It causes the interoperability issues between a manet node and a v6 node. As you said, with LUNAR (hide multihop link from IP), MANET is transparent to NDP/IPv6 at all. (which is great advantage though..). > --- Hot topic 2 : > > Now I also remember talking on the autoconf mailing list with some > people about different things which lead us to the definition of a MANET > ... and I was particularly puzzled by statements such as : two > inter-connected MANETs. Which leads to the immediate question : how do > we define the boundaries of a MANET ? I think this issue should > seriously be considered, especially if we want to do global address > autoconfiguration with multiple gateways and prefixes. I agree on this. > Of course ;-) I still advocate the use of prefix continuity, as a mean > to create logical sub-networks inside a MANET. I will hopefully update > my draft this week. :-) did you submit an updated version? > Hope this will trigger some discussions on the autoconf list which is > too quiet since Christmas break. ;-) I finally recovered from holidays:-p _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 24 03:06:17 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14393 for ; Thu, 24 Feb 2005 03:06:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4ENg-0005ze-Jl for manet-web-archive@ietf.org; Thu, 24 Feb 2005 03:29:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Doj-0000lI-J0; Thu, 24 Feb 2005 02:53:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4DoR-0000TT-QX for manet@megatron.ietf.org; Thu, 24 Feb 2005 02:53:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13091 for ; Thu, 24 Feb 2005 02:53:29 -0500 (EST) Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4EBG-0005eT-Fa for manet@ietf.org; Thu, 24 Feb 2005 03:17:08 -0500 Received: from samurai.local.sfc.wide.ad.jp (PA206078.au-net.ne.jp [61.198.206.78]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.10/8.12.0) with ESMTP id j1O7nxFj026083; Thu, 24 Feb 2005 16:50:05 +0900 Date: Thu, 24 Feb 2005 15:40:12 +0900 Message-ID: From: Ryuji Wakikawa To: Christophe.Jelger@unibas.ch Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt In-Reply-To: <421A1636.6000208@unibas.ch> References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1636.6000208@unibas.ch> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin7.2.0) MULE/5.0 (SAKAKI) Organization: Keio University/WIDE MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Spam-Score: 0.1 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 Cc: manet@ietf.org, Pascal Thubert , ryuji@sfc.wide.ad.jp, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Hello Christophe Thanks for comments. At Mon, 21 Feb 2005 18:11:18 +0100, Christophe Jelger wrote: > > Hello Ryuji, > > Before I trigger another hot topic of discussion (in a separate email), > here are some comments about the draft. As a general comment, I think > most of the draft gives a reasonable view of IPv6 networking in a MANET. > > Some more detailed comments (sorry for the long email). I'm purposely a > bit "nasty" sometimes, of course don't take it personnaly, my goal is > just to trigger discussions. don't mind;-) > About the "broadcast" address : shall we use ff02::1 or ff02::2, or even > both ? I mean some messages could be sent to all nodes, and other > messages can be sent to all_nodes_that_also_do_routing. This triggers > the question : do we allow nodes in a MANET not to take part in the > routing activity ? If yes, then using ff02::1 and ff02::2 would make > sense because we could differentiate between nodes/routers from > nodes/non_routers. I tried to inherit the v4 operation. In v4, routing protocols use 255.255.255.255 as a limited broadcast, it's simple to say using ff02::1. I am not so positive to use ff02;:2 for flooding, because router in IPv6 sense and router in manet sense is slightly different. If all manet "routers" satisfy IPv6 router requirements. It will be fine, but.. In addition, I want to keep ff02::2 for Internet Gateways (IPv6 router + manet interface). The clean solution is to have a new limited broadcast address for all manet nodes/routers, but overhead to get these address must be high. > Section 2.2 : I think using unique local unicast addresses in a MANET > makes a lot of sense since they (sort of) replace site-local addresses. > However, the BIG problem is that such addresses are not automatically > generated. I think that's really annoying, because if there is no > special host to advertise such a prefix, the nodes of an autonomous > MANET would not create such an address, and would then not be able to > communicate since we don't route link-local addresses. Now if each MANET > node was allowed to generate the Global ID and subnet ID fields (56 > bits, chosen via some random method), then all the nodes could at least > have an address routeable in the MANET. Maybe a well-known > MANET_Global_ID could even be used and reserved for MANETs. Each node > could then compute its own Subnet_ID randomly. So ok all the nodes in > the MANET would not use the same prefix, but is it really important ? > (as you say in Section 3.1, a node can keep its unique local even when > merges/partitions occur). Or do we want prefix continuity ? (as defined > in my soon_updated draft ;-) Good point. I agree with you here. My first idea was a new well-known prefix for manet nodes. However, IPv6 WG is not completed the ULP spec and I tried not to bring the confusion. If we say all the nodes in a MANET use the individual ULP address, we should have a manet specific prefix range. Otherwise, it will bring another problems to ULP operation in wired. > Section 3.2 : I would avoid talking about "foreign" network, as it does > not have a clear meaning in a MANET (unless you relate it to MIP). OK. > Section 4 : from previous discussions on the autoconf mailing list with > C. Perkins and P. Engelstaad, I'm still not sure that such a strict > statement is clear/right. As you explain in Section 7.1, top of page 9, > a node should sometimes avoid using the tunnel when it uses its home > address. I fully agree with that, but is this in agreement with RFC 3484 > ? (which says use the home address, which for me means "use the tunnel" > because home address is by essence topologically not correct, despite > not written explicitely in RFC 3484). I think this is opened to > interpretation, so maybe one should be very clear about that. Right. This is not specified yet. FYI. Pascal, Greg and I setup a mail-list to discuss the integration of MANET and MIP/NEMO. please check the announce mail sent to NEMO ML. > Section 6.1 : By IP flooding, do you mean some sort of multicast routing > ? (as broadcast/multicast is the same thing with IPv6). I mean, this > forwarding entry would be setup dynamically (by some multicast routing > protocol) or would it be a static "well-known" forwarding behavior ? If > yes, then one must be careful about leaks : you don't want the flooding > to "escape" from the MANET, but that means the gateway must be aware > that some of its interfaces are not in the MANET, and as you say in > Section 5.1 that "there is no mechanism to detect whether attached > network is a MANET or a normal IPv6 network". Moreover, I would remove > the statement that the all_manet_multicast address can also be defined > for unique local scope, because these addresses have (strictly speaking) > a global scope (but are not globally routeable). I did not discuss how to stop flooding here. I tried to explain how flooding of each protocol (specified with IPv4) can be operated in IPv6. For example, MPR flooding is an example. MPR6 simply uses ff02::1 like it uses 255.255.255.255 in IPv4. The prevention of flooded packets leak should be solved by MPR and not by IPv6. > Section 7.1 : as I said earlier, I agree that the tunnel should of > course not be used to communicate with MANET nodes, but in the mean time > the home address is somehow meaningless if the tunnel cannot be used. I believe it's meaningful:-) The home address is assigned to a node (not interface). It can still use as an identifier of a node in a manet. Moreover, in an isolated manet, DNS is not expected. The use of home address is one answer to solve a destination address, if the home address is well-known or cached. In addition, if a communication is established between two home addresses, the communication can be kept active when one of node leaves the MANET. Here is an example. If two vehicles communicate by vehicle-vehicle MANET, one of node starts speedup and leaves the MANET. Then the nodes switch to GPRS and continue the communication. If the nodes use ULP address, this can not be achieved. > Especially if a unique local address can be used inside the MANET. So I > would not defend the use of the home address when global connectivity is > not available : use of some MANET-scope addresses is easier. It depends on operations and services. And this is all about source address selection. > Hope you find these comments useful. thanks! regards, ryuji > > Ryuji Wakikawa wrote: > > Hi Christophe and Ian > > > > We submitted a new draft regarding IPv6 support on MANET. > > The flooding address is discussed in the draft. > > > > http://www.ietf.org/internet-drafts/draft-wakikawa-manet-ipv6-support-00.txt > > > > Any comments are appreciated. > > > > thanks > > ryuji > > > > At Fri, 18 Feb 2005 11:57:50 +0100, > > Christophe Jelger wrote: > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Feb 24 09:42:23 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25802 for ; Thu, 24 Feb 2005 09:42:23 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4KZ3-0007TK-Ky for manet-web-archive@ietf.org; Thu, 24 Feb 2005 10:06:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4K7W-0003Gk-SV; Thu, 24 Feb 2005 09:37:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4K7T-0003GG-N2 for manet@megatron.ietf.org; Thu, 24 Feb 2005 09:37:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25254 for ; Thu, 24 Feb 2005 09:37:32 -0500 (EST) Received: from isis.lip6.fr ([132.227.60.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4KUM-0007Ky-OM for manet@ietf.org; Thu, 24 Feb 2005 10:01:15 -0500 Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) by isis.lip6.fr (8.13.1/jtpda-5.4+victor) with ESMTP id j1OEbM0f012049 ; Thu, 24 Feb 2005 15:37:23 +0100 X-pt: isis.lip6.fr Received: from [132.227.61.11] (ariane [132.227.61.11]) by tibre.lip6.fr (8.11.6p3/8.11.6) with ESMTP id j1OEbMp03769; Thu, 24 Feb 2005 15:37:22 +0100 (CET) In-Reply-To: References: <200502161524.KAA22973@ietf.org> <4215CA2E.2090209@unibas.ch> <421A1B0D.1040005@unibas.ch> <35411357dc6782b9024498609f82060f@insa-lyon.fr> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: multipart/mixed; boundary=Apple-Mail-14--47949517 Message-Id: <47dc15c2bd6c6b76d1431e51eded620c@insa-lyon.fr> From: Guillaume Chelius Subject: Re: [manet] I-D ACTION:draft-ietf-manet-dymo-00.txt Date: Thu, 24 Feb 2005 15:35:52 +0100 To: Ryuji Wakikawa X-Mailer: Apple Mail (2.619.2) X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.5.10 (isis.lip6.fr [132.227.60.2]); Thu, 24 Feb 2005 15:37:23 +0100 (CET) X-Scanned-By: isis.lip6.fr X-Spam-Score: 0.0 (/) X-Scan-Signature: 4f41a758283586c0aa45e30a4caea1da Cc: manet@ietf.org, manetautoconf@ml.free.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bf298c52ab1dc9f39fd87b679918f163 --Apple-Mail-14--47949517 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Hi Ryuji, Please see my remarks below. >> Christophe, I agree with you on the fact that the definnition of a >> MANet boundary should be seriously considered. As you said in your >> previous mail, this issue is also bound to the flooding problem. When >> performing a flooding on the all-manet-multicast address, we do not >> want the packet to go to the Internet through Internet-connected >> gateway interfaces. We must have some way to differentiate interfaces >> connected to a MANet from interfaces that are not. This is one thing >> we >> proposed in an earlier draft: draft-chelius-adhoc-ipv6-00.txt > > For isolated MANET, the boundary can be defined as a range where > flooded packet are reached in terms of hoplimit,etc. > > For connected MANET with IGW, the boundary can be simple defined with > the address configuration mechanism. I.e. all the nodes assigned a > global address form a MANET. The problem is that the Internet-connected interface of the gateway is also configured with a global address. So there is no way for the gateway to decide which of its interfaces are in a MANet and which are not. > I did not notice your draft, can you send me a copy? The draft is quite old and has expired. Please find it in attachment. An implementation of this draft is also available for FreeBSD at http://sourceforge.net/projects/anax (FreeAna6-routing and kernel). To summary, there were three main ideas in the draft: 1) to add an MANET_MODE flag associated to each interface in order for a node to know which interfaces are or are not part of a MANet. Using this flag we can define a MANet as a maximal connected set of MANet interfaces. There are no more problems of MANet boudaries. 2) creation of a a manet scope for unicast as well as multicast addresses. MANet interfaces are associated with MANET-local addresses and a MANET scope is used for multicast diffusion inside a MANet. Validity of MANet-local (unicast and multicast) addresses is limited to the MANet. For example, a packet destinated to the ALL-MANET-NODES must not be forwarded through an interface which is not in MANET_MODE. I guess this second idea is close to the one expressed by Christophe Jelger when he talks about "IPv6 MANET-local addresses" (please Christophe, correct me if I'm wrong). 3) use of a single ad hoc address to identify all MANet interfaces of a single node. This last point is more polemical and this proposition was made in order to ease the vertical handover (or interface mobility) inside a MANet. More generally, I view a MANet as a new IPv6 scope. MANet interfaces must be attributed a MANet-local addresses in order to insure addressing and routing inside an isolated MANet and to give the addressing and routing material to setup other protocols such as global address configuration protocols in Internet-connected MANets. Just as with link-local addresses. A MANet multicast scope should also be defined in order to limit the diffusion of information to the MANet or to a subset of the MANet (e.g. all MANet GWs...).The validity of theses MANet addresses must be limited to the MANet. However, in order to make this scope viable, we should solve the issue of MANet boundarie which is for example partially responsible for the deprecation of site-local addresses (problem with site boudary definition). We must introduce a clear mechanism (e.g. flag in the system interface structure) to differentiate interfaces that are and are not part of a MANet. As soon as this is made, definition of a MANet becomes clear: it is a maximal connected set of MANet interfaces. MANet-restricted packets (the one using MANet-local addresses) must not be forwarded through interfaces that are not in MANET-MODE. Best regards, Guillaume Chelius. ---------------------------- ARES Project, INRIA web: http://ares.insa-lyon.fr/~gchelius mail: guillaume.chelius@insa-lyon.fr phone: (+33) 472 436 182 fax: (+33) 472 436 227 --Apple-Mail-14--47949517 Content-Type: text/plain; x-mac-hide-extension=yes; x-unix-mode=0644; name="draft-chelius-adhoc-ipv6-00.txt" Content-Disposition: attachment; filename=draft-chelius-adhoc-ipv6-00.txt Content-Transfer-Encoding: 7bit Internet Draft G. Chelius Document: draft-chelius-adhoc-ipv6-00.txt E. Fleury Expires: March 2003 Ares, Inria September 2002 IPv6 Addressing Architecture Support for mobile ad hoc networks Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of rfc-2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract The concept of node identifier, in practical terms an IP address, is crucial in ad hoc networks. Its use allows the setup of IP routing for ad hoc connectivity and the identification of several wireless devices as part of a unique ad hoc node. In this document, a new addressable object is defined: the ad hoc connector. It virtualizes several ad hoc network interfaces into a single addressable object. To locally address ad hoc connectors, a third IPv6 local-use unicast address (adhoc-local address) and the correlated use of the subnet multicast scope are defined. Table of Contents Status of this Memo................................................1 Abstract...........................................................1 1. Introduction....................................................3 2. Terminology.....................................................3 3. Ad hoc connector................................................4 3.1 Ad hoc connector management....................................4 3.2 Interface binding..............................................5 Chelius, Fleury Expires March 2003 1 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 4. Addressing an ad hoc connector..................................5 4.1 Local addressing...............................................5 4.2 Global addressing..............................................6 5. Addressing multiple ad hoc connectors...........................6 5.1 Predefined ad hoc multicast addresses..........................6 5.2 Multicast and ad hoc sub-networks..............................7 5.3 Multicast membership...........................................8 6. Duplicated ad hoc address detection.............................8 7. Global Prefix Discovery.........................................8 8. Security Considerations.........................................8 9. Notes...........................................................9 References........................................................10 Author's Addresses................................................10 Chelius, Fleury Expires March 2003 2 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 1. Introduction The notion of ad hoc network is something particular compared to classical network architectures. It is a logical view that unifies several physical networks in a single multigraph topology. As said in [rfc2501], the concept of a "node identifier", in practical terms an IP address, is crucial in ad hoc networks. Its use allows the setup of IP routing for ad hoc connectivity as well as the identification of several wireless devices as part of a unique ad hoc node. To gather several ad hoc interfaces in a single entity, the notion of ad hoc connectors is introduced. The ad hoc connector is the basic element of ad hoc networks. It virtualizes several network interfaces into a single addressable object. A host may have several ad hoc connectors and an interface may be bound to several ad hoc connectors. The ad hoc connector defines a set of addresses which identify indistinctly all bounded interfaces. IPv6 addressing architecture proposes two local unicast addresses and their equivalent multicast scope: link-local and site-local. The use of link-local unicast and multicast addresses is unsuitable to ad hoc networks. A link-Local unicast address refers to a single interface and its validity is limited to the interface link. Since an ad hoc network may be included in a larger site or spread over different sites, a specific ad hoc use of site-local addresses is also inappropriate. In addition, a site-local address identifies a single interface whereas an ad hoc address may identify several ones. To locally address ad hoc connectors, we propose the definition of a third IPv6 local-use unicast address: adhoc-local addresses. Their validity is limited to an ad hoc network. They provide a basic identification support for ad hoc nodes that can be extended by other configuration mechanisms such as stateless global address attribution. In the IPv6 architecture scheme, an ad hoc network may be at the same time, a multi-link subnet and a multi-link multi-subnet. Considering the whole ad hoc network as a multi-link subnet is achieved by matching a particular multicast scope, the subnet scope, with the ad hoc network. To support the multi-link multi-subnet vision, the notion of logical ad hoc sub-networks, also called channels, is introduced. A channel is a connex set of ad hoc connectors sharing a common channel value. A specific range of multicast addresses is associated to each channel. It enables the restriction of multicast groups to a given channel. 2. Terminology Ad hoc connector - the basic element of an ad hoc network. It virtualizes several network interfaces in a Chelius, Fleury Expires March 2003 3 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 single addressable object. Ad hoc identifier - a 64bits value that pseudo-uniquely identifies an ad hoc connector. Ad hoc channel - a non null 16bits value associated to an ad hoc connector. This value indicates the ad hoc sub-network the ad hoc connector is connected to. Ad hoc interface - a network interface bound to an ad hoc connector. Ad hoc host - a host with at least one ad hoc interface. Ad hoc route - a network route that only transits through ad hoc interfaces. Ad hoc network - a maximal and connex set of ad hoc connectors. Ad hoc sub-network - a maximal and connex set of ad hoc connectors sharing a common channel value. Ad hoc router - an ad hoc node which may route packets between ad hoc network(s) and non ad hoc network(s). Ad hoc sub-router - an ad hoc node which may route packets between two or more ad hoc sub-networks. All ad hoc nodes must be configured as IPv6 unicast and multicast routers. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in rfc-2119 [rfc2119]. 3. Ad hoc connector As defined in [rfc2501], a MANet is the *union* of physical-layer multihop topologies, i.e. a multigraph. In this multigraph, it is inappropriate to use the network interface as the basic addressable element; network interfaces only exist in one single physical layer topology. The ad hoc connector is defined as the basic element of ad hoc networks. It is a view of mind that virtualizes several network interfaces into a single addressable object. 3.1 Ad hoc connector management Chelius, Fleury Expires March 2003 4 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 In the network, an ad hoc connector is identified by a 64bits value, the ad hoc identifier. Another 16bits non null value is associated to the connector: its ad hoc channel value. Ad hoc connectors are created and destroyed by user management. Ad hoc IDs and ad hoc channel values are provided by the user at the connector creation. The ad hoc channel may be changed during the ad hoc connector life. A host may have several ad hoc connectors. However, ad hoc connectors of a single host must have different identifiers and different channel values. For the ad hoc network to correctly behave, it is preferred for ad hoc IDs to be unique. It is the user responsibility to ensure uniqueness of its IDs. To build pseudo-unique IDs, host interface MAC addresses or cryptographic mechanisms such as the one described in [SUCV] may be used. 3.2 Interface binding Network interfaces are manually bound to and unbound from ad hoc connectors by user management. A network interface may be bound to several ad hoc connectors and several network interfaces may be bound to a same ad hoc connector. 4. Addressing an ad hoc connector An ad hoc connector is associated to a set of IPv6 addresses which identify all bounded addresses. These addresses are an adhoc-local address and eventually one or more global addresses. The local address ensures connectivity in the ad hoc network and the global ones enable Internet connectivity. 4.1 Local addressing To address an ad hoc connector inside an ad hoc network, we define a third type of local-use unicast address: adhoc-local. The adhoc- local scope is for use in a single adhoc network. It is valid in all ad hoc sub-networks of the ad hoc network. Adhoc-Local addresses have the following format: | 10 | | | | bits | 54 bits | 64 bits | +----------+-------------------------+----------------------------+ |1111111001| 0 | ad hoc connector ID | +----------+-------------------------+----------------------------+ Each ad hoc connector is associated to a single adhoc-local address constructed using its identifier. Chelius, Fleury Expires March 2003 5 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 Ad Hoc nodes must not forward any packet with adhoc-local source or destination through a non ad hoc interface. In addition to addresses given in [rfc2373], an ad hoc interface is required to recognize the following addresses as identifying itself: o adhoc-local addresses of all ad hoc connectors it is bounded to. An ad hoc interface is required to join the solicited-node multicast groups associated to the following unicast addresses: o adhoc-local addresses of all ad hoc connectors it is bounded to. 4.2 Global addressing Ad hoc connectors may be addressed using global addresses if global prefixes are available in the ad hoc network. If a given global prefix P is delivered to an ad hoc connector with identifier Id, the global address constructed by concatenation of P and Id is associated to the ad hoc connector An ad hoc interface is required to recognize the following addresses as identifying itself: o all global addresses associated to all ad hoc connectors it is bounded to. An ad hoc interface is required to join the solicited-node multicast groups associated to the following unicast addresses: o all global addresses associated to all ad hoc connectors it is bounded to. 5. Addressing multiple ad hoc connectors To address multiple ad hoc connectors and to limit the scope of a multicast group to an ad hoc network, we use the subnet multicast scope as defined in [IPV6ADDR]. 5.1 Predefined ad hoc multicast addresses In addition to the ones given in [IPV6ADDR], the following well- known ad hoc multicast addresses are predefined: "All ad hoc nodes" address: FF03:0:0:0:0:0:0:1 Chelius, Fleury Expires March 2003 6 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 The above multicast address identifies the group of all IPv6 ad hoc nodes within the ad hoc network. "All ad hoc routers" address: FF03:0:0:0:0:0:0:A The above multicast address identifies the group of all IPv6 ad hoc routers within the ad hoc network. "All ad hoc sub-routers" address: FF03:0:0:0:0:0:0:B The above multicast address identifies the group of all IPv6 ad hoc sub-routers within the ad hoc network. Ad Hoc nodes must not forward any multicast packet with subnet scope through a non ad hoc interface. 5.2 Multicast and ad hoc sub-networks To address multiple ad hoc connectors inside a single ad hoc sub- network and to limit the scope of a multicast group to an ad hoc sub-network, we define a range of multicast addresses: FF03:0:0:channel value:0:0:0:0 For a given channel value X, the following well-known ad hoc multicast addresses are predefined: Reserved Multicast Address: FF03:0:0:X:0:0:0:0 The above multicast address is reserved and shall never be assigned to any multicast group. "All ad hoc nodes of a sub-network" address: FF03:0:0:X:0:0:0:1 The above multicast address identifies the group of all IPv6 nodes within the ad hoc sub-network. "All ad hoc routers of a sub-network" address: FF03:0:0:X:0:0:0:A The above multicast address identifies the group of all IPv6 ad hoc routers within the ad hoc sub-network. "All ad hoc sub-routers of a sub-network" address: FF03:0:0:X:0:0:0:B The above multicast address identifies the group of all IPv6 ad hoc sub-routers within the ad hoc sub-network. Chelius, Fleury Expires March 2003 7 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 Ad Hoc nodes must not forward any multicast packet limited to an ad hoc sub-network with channel value X through an interface that is not connected to an ad hoc connector with channel value X. 5.3 Multicast membership Ad hoc interfaces must join the following multicast groups: o "All ad hoc nodes" o "All ad hoc nodes of a sub-network" for the channel values of the ad hoc connectors they are bounded to. In addition, ad hoc interfaces of ad hoc routers must join the following groups: o "All ad hoc routers" o "All ad hoc routers of a sub-network" for the channel values of the ad hoc connectors they are bounded to. In addition, ad hoc interfaces of ad hoc sub-routers must join the following groups: o "All ad hoc sub-routers" o "All ad hoc sub-routers of a sub-network" for the channel values of the ad hoc connectors they are bounded to. 6. Duplicated ad hoc address detection Ad hoc specific Duplicated Address Detection (DAD) may be performed once or several times, eventually periodically, on ad hoc addresses. Ad hoc specific DAD is not mandatory since it is not safe. It is an ad hoc node responsibility to ensure uniqueness of its ad hoc addresses; either using an ad hoc specific DAD, either using unique or pseudo-unique ad hoc connector identifiers. Classical DAD protocols are inappropriate in the ad hoc environment. Definition of an appropriate protocol is behind the scope of this document. An example is given in [AUTOCONF]. 7. Global Prefix Discovery Global prefixes may be manually or automatically delivered to ad hoc connectors. Definition of an ad hoc specific Prefix Discovery Protocol is behind the scope of this document. An example is given in [CONNECT]. 8. Security Considerations Chelius, Fleury Expires March 2003 8 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 IPv6 addressing documents do not have any direct impact on Internet infrastructure security. Authentication of IPv6 packets is defined in [AUTH]. This document does not modify security issues related to ad hoc networks. 9. Notes Values of the adhoc-local unicast prefix and predefined multicast addresses are given as examples and are not restrictive. Addresses and prefixes must be attributed by the IANA. Chelius, Fleury Expires March 2003 9 INTERNET-DRAFT Ad Hoc IPv6 Architecture September 2002 References [AUTH] Atkinson, R., "IP Authentication Header", RFC 1826, August 1995. [rfc2373] Hinden, R. and Deering, S., "IP Version 6 Addressing Architecture", RFC 2373, July 1998. [rfc2461] Narten, T. and Nordmark, E. and Simpson, W., "Neighbor Discovery for IP version 6 (IPv6)", RFC 2461, December 1998. [rfc2501] Corson, S. and Macker, J., "Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations", RFC 2501, January 1999. [AUTOCONF] Perkins, C. and Malinen, J. and Wakikawa, R. and Belding-Royer, E. And Sun, Y., "IP Address Autoconfiguration for Ad Hoc Networks", Internet draft, draft-ietf-manet-autoconf-01.txt. [SUCV] Montenegro, G. and Castelluccia, C., "SUCV Identifiers and Addresses", Internet draft, draft-montenegro-sucv-02.txt. [IPV6ADDR] Hinden, R. and Deering, S., "IP Version 6 Addressing Architecture", Internet draft, draft-ietf-ipngwg-addr-arch-v3- 08.txt. [CONNECT] Wakikawa, R. and Malinen, J. and Perkins, C. and Nilsson, A. and Tuominen, A., "Global connectivity for IPv6 Mobile Ad Hoc Networks", Internet draft, draft-wakikawa-manet-globalv6-01.txt. Author's Addresses Guillaume Chelius Ares, Inria Batiment Leonard de Vinci 21 avenue Jean Capelle 69621 Villeurbanne Cedex France Email: gchelius@telecom.insa-lyon.fr Eric Fleury Ares, Inria Batiment Leonard de Vinci 21 avenue Jean Capelle 69621 Villeurbanne Cedex France Email: Eric.Fleury@inria.fr Chelius, Fleury Expires March 2003 10 --Apple-Mail-14--47949517 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit --Apple-Mail-14--47949517 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --Apple-Mail-14--47949517-- From manet-bounces@ietf.org Thu Feb 24 15:50:11 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19336 for ; Thu, 24 Feb 2005 15:50:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Pw4-0003h6-P9 for manet-web-archive@ietf.org; Thu, 24 Feb 2005 15:50:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4PuN-0007uv-Gj; Thu, 24 Feb 2005 15:48:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4PuL-0007nD-5o for manet@megatron.ietf.org; Thu, 24 Feb 2005 15:48:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19105 for ; Thu, 24 Feb 2005 15:48:22 -0500 (EST) Received: from bay15-f16.bay15.hotmail.com ([65.54.185.16] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4PuJ-0003dK-3H for manet@ietf.org; Thu, 24 Feb 2005 15:48:24 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Feb 2005 12:47:01 -0800 Message-ID: Received: from 211.191.61.234 by by15fd.bay15.hotmail.msn.com with HTTP; Thu, 24 Feb 2005 20:46:46 GMT X-Originating-IP: [211.191.61.234] X-Originating-Email: [kukhee96@hotmail.com] X-Sender: kukhee96@hotmail.com From: "cho kuk-pyo" To: manet@ietf.org Date: Fri, 25 Feb 2005 05:46:46 +0900 Mime-Version: 1.0 X-OriginalArrivalTime: 24 Feb 2005 20:47:01.0216 (UTC) FILETIME=[FD5C8600:01C51AB1] X-Spam-Score: 1.7 (+) X-Scan-Signature: 08e48e05374109708c00c6208b534009 X-MIME-Autoconverted: from 8bit to base64 by ietf.org id PAA19105 Subject: [manet] i want to stop manet mailing list... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2029753890==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.8 (++) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 --===============2029753890== Content-Type: text/plain; charset=ks_c_5601-1987; format=flowed Content-Transfer-Encoding: base64 SSdtIHNvIHNvcnJ5Lg0KSSB3YW50IHRvIHN0b3AgbWFuZXQgbWFpbGluZyBsaXN0Lg0KSGF2 ZSBhIG5pY2UgZGF5Lg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Ku/PFrcfRILi4s7Kw+iC1+7bmx9EgsPi1 v8O8ILv9yLAuLi4gIMH2sd0gTVNOIMS/ucK0z8a8v6G8rSC9w8Dbx8+8vL/kISAgIA0KaHR0 cDovL2dyb3Vwcy5tc24uY29tLz9wZ21hcmtldD1rby1rciAgDQoNCg== --===============2029753890== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2029753890==-- From manet-bounces@ietf.org Thu Feb 24 21:28:47 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22169 for ; Thu, 24 Feb 2005 21:28:47 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4VDo-0003LJ-5Q for manet-web-archive@ietf.org; Thu, 24 Feb 2005 21:28:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4V6Y-0007dw-11; Thu, 24 Feb 2005 21:21:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4V6V-0007cW-Gc for manet@megatron.ietf.org; Thu, 24 Feb 2005 21:21:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21614 for ; Thu, 24 Feb 2005 21:21:17 -0500 (EST) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4V6X-0003B0-P2 for manet@ietf.org; Thu, 24 Feb 2005 21:21:22 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j1P2LI55024327 for ; Thu, 24 Feb 2005 21:21:18 -0500 (EST) Received: from gateway.ece.neu.edu ([129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005022421211706980 for ; Thu, 24 Feb 2005 21:21:17 -0500 Received: from localhost (basagni@localhost) by gateway.ece.neu.edu (8.9.3/8.9.3) with ESMTP id VAA29502 for ; Thu, 24 Feb 2005 21:21:17 -0500 (EST) X-Authentication-Warning: gateway.ece.neu.edu: basagni owned process doing -bs Date: Thu, 24 Feb 2005 21:21:17 -0500 (EST) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Subject: [manet] IEEE SECON 2005, Call for Papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 We apologize if you receive multiple copies of this CfP ************************************************************* Preliminary Announcement and Call for Papers *** IEEE SECON 2005 *** Second Annual IEEE Communications Society Conference on Sensor and Ad Hoc Communications and Networks Santa Clara, California, USA September 26-29, 2005 Paper Submission Deadline: April 6, 2005 http://www.ieee-secon.org/2005 ************************************************************ Building on the success of last year's inaugural conference, this new IEEE Communications Society conference will provide a forum to exchange ideas, techniques, and applications, discuss best practices, raise awareness and share experiences among researchers, practitioners, standard developers and policy makers in the field of sensor and ad hoc networks and systems. The conference will be organized to provide for a degree of collegiality and continuity in the discussions of the various topics among participants from the industrial, governmental and academic sectors. Original technical papers that address the communications, networking, systems and algorithmic aspects of ad hoc and sensor networks, as well as those that describe practical deployment and implementation experiences, are solicited for presentation at the conference and publication in the conference proceedings. Papers presenting novel contributions in such disciplines as communications, networking protocols and architectures, algorithms, embedded systems, middleware and information management, and novel applications are solicited. PAPERS: Full papers describing original, previously unpublished research work, experimental efforts, practical experiences, and industrial and commercial developments in sensor and ad hoc communications and networks. Papers with a deep focus on a specific discipline or stimulated by the synergistic interaction of diverse disciplines are encouraged. Particular topics of interest include, but are not limited to: * New architectures, protocols and access control to support communication, localization, time synchronization, routing and data dissemination in heterogeneous, large-scale distributed, ad hoc networks and sensor networks * Novel algorithms and theories for management, supervisory control and monitoring of distributed ad hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes * Modeling and performance evaluation of large-scale distributed and ad hoc sensor networks, practical implementations, and real-work experiences * Theories and models on fundamental information and communication aspects of wireless ad hoc and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and ad hoc networks * Integration of sensors into engineered systems, including novel techniques for sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing and efficient schemes to maximize accuracy and minimize false alarms * Chip-based systems incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware and tools for ad hoc and sensor network applications development, deployment and management * Mesh networking, mobile ad hoc peer-to-peer multipoint communications, applications and experiences TUTORIALS and PANELS: Proposals for tutorials and panels on current topics in the field of ad hoc and sensor networking and applications are solicited. Panels related to the commercial application and development of sensors and ad hoc networks are especially encouraged. DEMOS and EXPO: Demonstrations that showcases the practical implementations, industrial and commercial developments, and new applications for ad hoc and sensor networks are solicited. SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically through the EDAS system. Details regarding the paper format and the submission process will be posted at the conference web site. IMPORTANT DATES: April 6, 2005 Paper submission deadline May 1, 2005 Tutorial/Panel/Demo proposals deadline June 13, 2005 Notifications July 8, 2005 Camera-ready due date TPC Co-Chairs: Elizabeth Belding-Royer ebelding@cs.ucsb.edu Marwan Krunz krunz@ece.arizona.edu Thyaga Nandagopal thyaga@lucent.com General Chair: J.J. Garcia-Luna-Aceves jj@soe.ucsc.edu -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntington Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu *** http://www.ece.neu.edu/faculty/basagni/ *** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 25 05:03:40 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24733 for ; Fri, 25 Feb 2005 05:03:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4cK4-0004cB-PM for manet-web-archive@ietf.org; Fri, 25 Feb 2005 05:03:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4cHV-0005Vw-8L; Fri, 25 Feb 2005 05:01:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4cHS-0005VZ-LO for manet@megatron.ietf.org; Fri, 25 Feb 2005 05:01:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24482 for ; Fri, 25 Feb 2005 05:01:04 -0500 (EST) Received: from web21004.mail.yahoo.com ([216.136.227.58]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D4cHY-0004Yb-JE for manet@ietf.org; Fri, 25 Feb 2005 05:01:13 -0500 Received: (qmail 4102 invoked by uid 60001); 25 Feb 2005 10:01:03 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=HRcHA3L5nOIHS/Jbs4vEHPOsdPS2MwOVk3DKGp315P344mPMRIrineLz1FXdq5JEFIkE4n3d7Pb0J6umjVP20y1LEdfwa9uHUBTqLepeKoxSUXDET0W0jFzigXxcLa7TGet7J8jHh7e3kuLHlEHASBxiOsm+32yYGV2DoQ87RIc= ; Message-ID: <20050225100103.4100.qmail@web21004.mail.yahoo.com> Received: from [68.221.141.171] by web21004.mail.yahoo.com via HTTP; Fri, 25 Feb 2005 02:01:03 PST Date: Fri, 25 Feb 2005 02:01:03 -0800 (PST) From: Yang Xiao To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.1 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Subject: [manet] International Symposium on Wireless Local and Personal Area Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 Call For Papers International Symposium on Wireless Local and Personal Area Networks (part of WirelessCom 2005) http://www.cs.ualberta.ca/~ehab/WirelessCom2005-WLANs-WPANs/ Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA June 13-16th, 2005 Call for papers (pdf) Scope and Topics of Interest Original papers are invited on emerging architectures and technologies in the design of wireless local area networks (WLANs) and wireless personal area networks (WPANs) with emphasis on the use of such networks in diverse areas of applications such as supporting ubiquitous mobile Internet access, and the design of ad-hoc networks, and sensor networks. The symposium solicits high quality and previously unpublished work in the field. Topics of interest include, but are not limited to: Medium access techniques and protocols for WLANs/WPANs Emerging standards and testbeds for WLANs/WPANs WLANs/WPANs protocols for smart antennas Energy efficiency in protocol and systems design Resource assignment and sharing in WLANs/WPANs Self configuration in WLANs/WPANs Provisioning quality of service in WLANs/WPANs Multimedia networking architectures and protocols for WLANs/WPANs Integration and interoperability of WLANs/WPANs and 3G (and beyond) networks Interoperability issues between wireless standards/protocols and the Internet User mobility and workload modeling Security issues in WLANs/WPANs Paper Submission and Important Dates Note that all papers are limited to six pages, and must be in standard IEEE double-column format. All submissions will be handled electronically and must be in PDF format. The conference has designated best papers awards. https://msrcmt.research.microsoft.com/WirelessCom2005/CallForPapers.aspx Manuscript Submission: March 15, 2005 Acceptance Notification: April 15, 2005 Camera-Ready Papers Due: May 1, 2005 Organizing Committee Symposium Co-Chairs Ehab S. Elmallah Department of Computing Science, University of Alberta, Edmonton, Alberta Canada, T6G 2E8 ehab@cs.ualberta.ca Yang Xiao Computer Science Division The University of Memphis, 373 Dunn Hall, Memphis, TN 38152, USA yangxiao@ieee.org Publicity Co-Chairs Kui Wu Department of Computer Science University of Victoria Victoria, British Columbia Canada V8W 3P6 wkui@cs.uvic.ca Vincent Wong Department of Electrical and Computer Engineering The University of British Columbia 2356 Main Mall, Vancouver, BC, Canada, V6T 1Z4 vincentw@ece.ubc.ca Technical Program Committee Imad Aad, EPFL, Switzerland Giuseppe Bianchi, University of Roma Tor Vergata, Italy Azzedine Boukerche, SITE, University of Ottawa, Canada Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Liang Cheng, Lehigh University, USA Sunghyun Choi, Seoul National University, Korea Jing Deng, University of New Orleans, USA Christos Douligeris, University of Piraeus, Greece Xiaojiang (James) Du, North Dakota State University, USA Nelson Fonseca, State University of Campinas, Brazil Daqing Gu, MERL, USA Xingang Guo, Intel, USA Janelle Harms, University of Alberta, Canada Ekram Hossain, University of Manitoba, Canada Antonio Iera, University Mediterranea of Reggio Calabria, Italy Weijia Jia, City University of Hong Kong, Hong Kong Xiaohua Jia, City University of Hong Kong , Hong Kong Victor Leung, University of British Columbia, Canada Haizhon Li, University of Memphis, USA Ting-Yu Lin, National Chiao-Tung University, Taiwan Jiangchuan Liu, Simon Fraser University, Canada Xiang-Yang Li, Illinois Institute of Technology, USA Mike MacGregor, University of Alberta, Canada Jelena Misic, University of Manitoba, Canada Vojislav B Misic, University of Manitoba, Canada Qiang Ni, National University of Ireland, Ireland Jianping Pan, NTT MCL, USA Yi Qian, University of Puerto Rico, USA Daji Qiao, Iowa State University, USA Bo Sun, Lamar University, USA Ilenia Tinnirello, University of Palermo, Italy Dimitrios Vergados, University of the Aegean, Greece Feiyi Wang, Cisco Systems Inc, USA Lan Wang, University of Memphis, USA Li-Chun Wang, National Chiao Tung University, Taiwan Wenye Wang, North Carolina State University, USA Xudong Wang, Kiyon Inc., USA Yu Wang, University of California, Santa Cruz, USA Vincent Wong, University of British Columbia, Canada Haitao Wu, Microsoft Research, China Hongyi Wu, University of Louisiana at Lafayette, USA Jie Wu, Florida Atlantic University , USA Kui Wu, University of Victoria, Canada Surong Zeng, Motorola, USA Hao Zhu, Florida International University, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 25 09:24:11 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19562 for ; Fri, 25 Feb 2005 09:24:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4gOD-0001uu-L9 for manet-web-archive@ietf.org; Fri, 25 Feb 2005 09:24:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4gIs-0004zS-5I; Fri, 25 Feb 2005 09:18:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4gIq-0004zL-8A for manet@megatron.ietf.org; Fri, 25 Feb 2005 09:18:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18943 for ; Fri, 25 Feb 2005 09:18:46 -0500 (EST) Received: from bugs.comnets.uni-bremen.de ([134.102.186.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4gIx-0001mJ-Ms for manet@ietf.org; Fri, 25 Feb 2005 09:18:57 -0500 Received: from serpens (bugs.comnets.uni-bremen.de [134.102.155.1]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id j1PEIXq17972; Fri, 25 Feb 2005 15:18:34 +0100 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host bugs.comnets.uni-bremen.de [134.102.155.1] claimed to be serpens From: "Koojana Kuladinithi" To: "'Manel Guerrero'" , "'gabriel montenegro'" Subject: RE: [manet] Require address auto-configuration implementation orsimulation code! Date: Fri, 25 Feb 2005 15:21:27 +0100 Organization: University of Bremen Message-ID: <000001c51b45$4b8a85f0$f69c15ac@SWD> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <41FE027D.2070802@upf.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Cc: "'zhang zhi'" , manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Hi Manel & Gabriel, Sorry for the late reply to this. One of our students has implemented SAODV in JAdhoc software with considering the key management. She implemented secret challenge to manage the key. If you need more details, contact vara_fon@yahoo.com Kind regards Koojana >-----Original Message----- >From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] >On Behalf Of Manel Guerrero >Sent: Monday, January 31, 2005 11:04 AM >To: gabriel montenegro >Cc: zhang zhi; manet@ietf.org >Subject: Re: [manet] Require address auto-configuration >implementation orsimulation code! > > >Hi Gabriel :) > >Yes, I'm not aware of any implementation of SAODV Key Management. > >Regards, > > Manel > >gabriel montenegro wrote: >> Yes, I agree. We've actually discussed this before on this list, and >> at the AODV NG workshop (2002), although we did not implement it: >> >> Protecting AODV against impersonation attacks >> http://doi.acm.org/10.1145/581291.581313 >> >> There's some discussion as well in the updated "SUCV" paper at: >> >> Crypto-based identifiers (CBIDs): Concepts and applications >> http://doi.acm.org/10.1145/984334.984338 >> >> Manel, did I understand you correctly that this is not yet >part of any >> public AODV implementation? If it is implemented, could you please >> send the pointer? >> >> thanks, >> >> -gabriel >> > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Feb 25 12:39:08 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11548 for ; Fri, 25 Feb 2005 12:39:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4jQv-000729-RP for manet-web-archive@ietf.org; Fri, 25 Feb 2005 12:39:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4jLN-0000bQ-Mc; Fri, 25 Feb 2005 12:33:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4jLI-0000Oj-UW for manet@megatron.ietf.org; Fri, 25 Feb 2005 12:33:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10990 for ; Fri, 25 Feb 2005 12:33:29 -0500 (EST) Received: from carrierpigeon.cs.umd.edu ([128.8.129.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4jLR-0006ub-Nv for manet@ietf.org; Fri, 25 Feb 2005 12:33:42 -0500 Received: from MINDLAP2 (mindlap2.cs.umd.edu [172.16.0.37]) (authenticated bits=0) by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id j1PHXEn8021828 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 25 Feb 2005 12:33:17 -0500 (EST) Message-Id: <200502251733.j1PHXEn8021828@carrierpigeon.cs.umd.edu> From: "Moustafa Youssef" To: Date: Fri, 25 Feb 2005 12:28:12 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000A_01C51B36.2D502C20" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-MS-TNEF-Correlator: 0000000006F61F65A15E334E985099AB7E0DC8D3C4492200 X-Spam-Score: 0.0 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 Subject: [manet] 3rd CFP: IEEE WirelessCom Symposium on Mobile Computing, 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C51B36.2D502C20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable (Our apologies if you receive multiple copies of this CFP) ------------------------------------------------------------- Third Call for Papers Symposium on Mobile Computing http://www.csee.umbc.edu/~younis/WC_MobCom05.htm as part of=20 IEEE WirelessCom 2005 Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/05/ June 13-16, 2005 Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC Recent years have witnessed an enormous growth in the development and applications of mobile computing environments and devices. Many practitioners envision a future empowered with context and location = aware computation and communication infrastructure that allow users to access = data and receive service at any place and any time. Compared to conventional platforms, the mobility of computing nodes introduces many challenges to = the design of almost all systems components.=20 This symposium will foster a forum for discussing and presenting recent research results on mobile computer systems. Original papers are invited = in the broader area of mobile computing. Papers must report high-quality = and previously unpublished work. Topics of interest include, but are not = limited to, the following: =95 Architecture and infrastructure support=09 =95 Middleware and operating systems services =95 Development platforms and environments =95 Adaptive resource management schemes =95 Pervasive and Context-aware Computing =95 Performance metrics and studies =95 Power aware computation and communication =95 Data consistency and synchronization protocols =95 Fault-tolerant architectural and operation models =95 Wearable computing devices and systems =95 Time constrained mobile systems =95 Robust ad-hoc networking techniques =95 Efficient localization techniques =95 Wireless sensor networks =95 Mobile peer to peer systems =95 Quality of service provisioning =95 Context-conscious computing =95 Web caching and services =95 Emerging applications and systems =95 Mobile agents =95 Mobile commerce =95 Security and privacy issues Submission Guidelines --------------------- Original papers are solicited and must represent high-quality and = previously unpublished work, not currently under review by another conference or journal. Prospective authors should submit their paper electronically through https://msrcmt.research.microsoft.com/WirelessCom2005. All = papers are limited to 6 pages in standard IEEE double-column format.=20 Important Dates --------------- Paper Submission Deadline: March 15, 2005 Notification of Acceptance: April 15, 2005 Camera-Ready Papers: May 1, 2005 Symposium Co-Chairs ------------------- Mohamed Younis Department of Computer Science and Electrical Engineering University of Maryland Baltimore County, 1000 Hilltop Circle, Baltimore, MD 21250 Voice: (410) 455-3968, FAX: (410) 455-3968 E-mail: younis@csee.umbc.edu=20 Hesham El-Rewini Department of Computer Science and Engineering Southern Methodist University 3145 Dyer Street, Dallas, TX 75205 Voice: (214) 768-3278, FAX: (214) 768-3085 E-mail: rewini@engr.smu.edu Publicity Chair ---------------- Moustafa Youssef Department of Computer Science University of Maryland at College Park, College Park, MD 20742 Voice: (301) 405-0341, FAX: (301) 405-6707 E-mail: moustafa@cs.umd.edu ------=_NextPart_000_000A_01C51B36.2D502C20 Content-Type: application/ms-tnef; name="winmail.dat" Content-Disposition: attachment; filename="winmail.dat" Content-Transfer-Encoding: base64 eJ8+Ig8RAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBoCgAAEQAAAAsAAQ4BAAAAAgEKDgEAAAAYAAAAAAAAAAb2 H2WhXjNOmFCZq34NyNPCgAAAAwAUDgEAAAALAB8OAQAAAAIB+A8BAAAAEAAAAAb2H2WhXjNOmFCZ q34NyNMCAfoPAQAAABAAAAAG9h9loV4zTphQmat+DcjTAwD+DwUAAAACAQkQAQAAANkIAADVCAAA XhAAAExaRnXjznrwAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3TwqAAqQD4wIAY2gKwHPwZXQwIAcT AoAP8wBQfwRWCFUHshHFDlEDARDHMvcGAAbDEcUzBEYQyRLbEdPbCO8J9zsYvw4wNRHCDGDOYwBQ CwkBZDM2EVALpoggKE8IcCBhcBhBTmcIkAQgBpAgeQhgIAEYwGNlaXZlIG1odWx0BSBsH1AFoHBl HkJvHpB0aAQAEsBG3FApCqIKhAqALSH/Iw+3JB8ktyE0ICYvJlBUILC/CyASwAdAAyACEAXAUB3g fwSQELAl3yZQBrEd8ACQdcZtIGADoE1vYgMQH1BLCFAqEHUfoG5nKLZoQQJAcDovL3cssC4SYxEg ZS4qYGJjLjEJgHUvfh6xAwBzLxhXQ18qwSsxMDUu7SxAbSi/ME9hBCAKsQVAJyBxL08wU0lFM4Ag V90ngGUf0AQQKzEgAdAu4EkhNFNoBJBhdCqSYRx1aQfwB5AYYSwgS55hAHAd4AdANeBCZQDQjmg2 YDWyNmBIYXcLcHE3wVVTQSE0LEkfAS4mcQpQCfBzdSzgYS/KaAqwZweQL2YA0B+BoHkvc2FmOBB0 LKDTM9UFoG0vLuAvMh89dgZKLgAfUDEzLTE27zZgNIgnQQWQaAMAOnADIO5THfAAgAWwcyCwLHAz ZNxUQ0HQNmBBwFBB8QBw8SegU1NDQcAhOiE0NgC/HxACMB6gNzARECwwYR9BvQPwdD6gBBAJgEJx IAnwmwWwBGB1BCAJwG93IKB/HnADoCCgH1ABAB9AGFBw/weARHFCgh3gC1BAUR+gQMG/IGIEYCrj PIErZEYRdieAfwIgSAIEIEKCR5EN4AeQLtk1oW55MYA1UGMfoEkC7yiBSpMAkCqRYSgAK3AIcPUf UGUqEXcEkEXBRVFHAP8FoAIwDsJCghhQSOQd0DgQ/05hSgRQdUKRPIEfcEBCUIPnC4ADUDFgdHIb cE5DIKDvNWAd0CfgRtAgRoBNMjVw7R3QY0vxBCBkNWBOAEKC/x72VMFL0h3QSDJMcQtgVxL/SGJM YR+gB4BMICsyUPEnoP9VEU+BH0ACMEkRQHELUQAw/UZBczZgR1JJk0VgTHAgcf9KCEYwAQAeYQIw A2AtoEvx/x9gTFIQ4SfgCfA60VUCR1T9AJBnA6AgcQdABGBTYFRC/VaweVNgTpAEIEoCTRFLMf9M ICE6J2EEIGCgKhYD8Cfj32DBHcEoAiphKBJkBAA7MP8EEEpiQoJMkAeQWfJKcR7y/0RxZhIKwBDg ZxIfgSBRA6DvSZsTIWClTCBPBRAeMFpD/yhjHdBOYQuASsAOsCegRyX6YgNgYQSBauJOAElvK6D/ TCAoVB9hYDEYwB3wMbEgsPhnaC058DbhW9FlxUrA/UZxbExwLgArYAJgBAA1MOtPEQWwa0wgVCAR LPAgYu9dMU7hYDELgGMKQAEANmC+YitwauNGMAVANvBta2NfNXBbFAIQVGIrkTpDGyf+OTSwAZER YRDga2FTpEKCP1MdOkBIoBhhd3N23U1p/GRkH9BQ40KCIBA1Qkpi72CmVsUopXc3REepWodCc/9K qnbeVbAFMB8yZhEIYVcRfwOBOsFIAwTwNTAHgXbdUL9W0TFgHzJCgghQT6MtUNT/Kz2E6lrCAHCD MhEwBRBykf9CglNgc8AeQYfOTsJQz1Hf/wIgfg5Vwk+BAJBgwXOQcCTLYKBzkGhK4Wl6UHRMkG90 oFBQBvB9/kY1wB+QLf81cB/QNVBIInfYQHF8KWgz+wEAkd9XRLEBoEnbS7WQFf9gw3bdB2KPU1Nw C3FFwUmVH5jfd3MIAHQQYDJkLWj/UFBcwBEwcfJKYngRQDE58f19/kUBIA3gCJBEcVBCNvD/kPWe r5ZnM9VWsUDSneZ9/n8qxShwEyFVEaYTm793c1H/b9UgcVbGkWFNlIefhkePYv+gcEZySgeV/3eg OnB34WWV932Pn9UHgHJqIWWhSKqYn/+lHjrBgS8qtlIyBJAfEHbd/wZgOzAFEHAXHzAA0ExwBAF7 ohghSVNxYHTwZWEqkUf/NdCVsZrxKKUkvyWIaf95kv8G8KBha3JCgm62ZhRvb3B//3GJNmB0krbx GMACMMGjbGJ7wTIH0WLAwnSgNTFPcmb3TuGJMgWxaghhWkFuIQNg/nMocEzBheIrcJ2wRNFBEP0I YGyKEbmyBUBHUSeAanT/RhAf0EzAkLJAYcGhIKADYPZ1wDAsM3MsgVrwZ3AOoPouZyYudPAFACow IHDL4O88gjPJNIJMIEEn4WqJdNj8IDYxgV6iRyFTYEKBCxG9M2RkCGCXMauRCkBtA6D3iOPL4GHb SSoRACCTko8R/7rfJWooUwYAubh+8GxQuqKnQVB7JGdjMTU/Kk50oPcGkFKWIHFBVVEFMIki2AU+ QbehAyDY3CfAsEFhLb82AGxQTHAoVNgHTHAxPyrnNMUqBwhQLUMQ8CeA1L/fJT0qwBDwB4AnoFkt 8yE0/37wMZJIAyBxKzTWoqByV+X2RcmzQFNFK6Ca8QZxSnG+VQMAH0AREFvF2HF5C2D9QpFCB0BY kQWwhxIuADtgbTZgMTSQEVBIY6E1cHC/EsAngHOgc+HphzdxRDRwZw4hAUAhQ1ZvS+FBUCgiNOqg KSA0GwAtMxg5Njg2YD1xRkFY8+3eITRFLQDAAxBBUC3k9kAs+2HbSAeQ41Hmkd1h/3YhAKDkL+U/ 5kXnaDTFCGD/xQIqoREwnbBlEQVA6BghNPwzMe5QfuBEoNaxU3AJ4B82UY8QJ+AxYEIBWCA3rw5A NKbthuzQNO4wN+6wee6AMjfuwJKU7zP9GDBeODS18LYYwPQCQF6Bcvwucx9wLYK4j9ZgcWK+gf9M cODj4U/ii27BO6BOAOOx/UWhZvRP9V+1xugf6SRUIf8S0F5hOtAoQcKx3KUKquyTuDA3NA5Q7Tv/ MDHuMXEu4C0wM+4A7tkOBzZ+Nwzg8FxGYgWS8ZEtMWQFAUh9EtAAAAADAA00/T8DAAMADzT9PwMA AgEUNAEAAAAQAAAATklUQfm/uAEAqgA32W4AAAIBfwABAAAAMQAAADAwMDAwMDAwMDZGNjFGNjVB MTVFMzM0RTk4NTA5OUFCN0UwREM4RDNDNDQ5MjIwMAAAAAADAAYQ8PwnxwMABxD0CgAAAwAQEAAA AAADABEQAAAAAB4ACBABAAAAZQAAAChPVVJBUE9MT0dJRVNJRllPVVJFQ0VJVkVNVUxUSVBMRUNP UElFU09GVEhJU0NGUCktLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0AAAAAJKo= ------=_NextPart_000_000A_01C51B36.2D502C20 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------=_NextPart_000_000A_01C51B36.2D502C20-- From manet-bounces@ietf.org Sat Feb 26 11:33:25 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14250 for ; Sat, 26 Feb 2005 11:33:25 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D54t5-0006hg-0c for manet-web-archive@ietf.org; Sat, 26 Feb 2005 11:33:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D54qW-00064H-PQ; Sat, 26 Feb 2005 11:31:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D54qV-00064C-Af for manet@megatron.ietf.org; Sat, 26 Feb 2005 11:31:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14165 for ; Sat, 26 Feb 2005 11:31:08 -0500 (EST) Received: from cs-exs2.bu.edu ([128.197.10.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D54qs-0006ft-2o for manet@ietf.org; Sat, 26 Feb 2005 11:31:34 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Sat, 26 Feb 2005 11:31:16 -0500 Message-ID: <0511C607B17F804EBE96FFECD1FD98591E8329@cs-exs2.cs-nt.bu.edu> Thread-Topic: SenMetrics 2005 CFP Thread-Index: AcUcIIchkdciAMx/RrmAubU2BdI7Tw== From: "Ibrahim Matta" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Content-Transfer-Encoding: quoted-printable Subject: [manet] SenMetrics 2005 CFP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Content-Transfer-Encoding: quoted-printable ** Apologies if you receive multiple copies of this CFP ** CALL FOR PAPERS SenMetrics 2005 Third International Workshop on Measurement, Modeling,=20 and Performance Analysis of Wireless Sensor Networks=20 San Diego, CA, USA July 21, 2005 (in conjunction with MobiQuitous 2005) http://www.senmetrics.org/ E-mail: senmetrics@ece.osu.edu The SenMetrics workshop solicits papers on the development=20 and application of analytic, simulation, prototype testbed,=20 and measurement-based performance evaluation techniques to=20 the area of wireless sensor networks. Of particular interest=20 is work that furthers the state-of-the-art in performance=20 evaluation methods, or those that creatively apply=20 previously developed methods to understand or to gain=20 important insights into key design trade-offs in wireless=20 sensor networks.=20 Topics of interest include, but are not limited to: =20 Performance-oriented design and evaluation studies of: - wireless sensor networks - sensor node hardware and software architectures - data collection - addressing=20 - security, reliability, and robustness - operating systems - energy aware network protocols - applications - localization - fundamental limits and tradeoffs - topology management - deployment - distributed actuation and control - system development and testbed experience - benchmarks Performance methodology techniques and algorithms for:=20 - system, protocol, and algorithm modeling - analytic evaluation - system measurement and monitoring - model verification and validation - workload characterization - simulation - statistical analysis - stochastic modeling=20 - experimental design - reliability analysis - performance optimization IMPORTANT DATES: Paper Submission Deadline: April 15, 2005 Notification of Acceptance: June 1, 2005 Camera Ready Paper Due: June 15, 2005 Workshop Date: July 21, 2005 PAPERS: Authors are invited to submit for review, papers that=20 neither have been previously published nor are under review=20 by another conference or journal. Priority will be given to=20 original contributions describing recent and innovative=20 research results or developments in the scope of the workshop.=20 Papers must be written in English, using font no smaller than=20 10 points and not to exceed 10 pages. Only PDF and PostScript=20 formats will be accepted, and all submissions will be handled=20 electronically. Further details on submission procedures will=20 be soon available at http://www.senmetrics.org/ GENERAL CHAIR: Raghupathy Sivakumar, Georgia Institute of Technology PROGRAM CHAIRS: Eylem Ekici, Ohio State University Ibrahim Matta, Boston University PUBLICITY CHAIR: Seung-Jong Park, Louisiana State University TECHNICAL PROGRAM COMMITTEE: Alhussein Abouzeid (RPI) Ozgur B. Akan (Middle East Technical U, Turkey) Andrew Campbell (Columbia University)=20 Sonia Fahmy (Purdue University)=20 Paul Havinga (University of Twente, The Netherlands) Ahmed Helmy (USC) Holger Karl (University of Paderborn, Germany) Bhaskar Khrisnamachari (USC)=20 Marwan Krunz (University of Arizona) Kang-Won Lee (IBM Research) Mingyan Liu (University of Michigan) Stephan Olariu (Old Dominion University) Sergio Palazzo (University of Catania, Italy) Seung-Jong Park (Louisiana State University) Ness Shroff (Purdue University)=20 David Starobinski (Boston University)=20 Ioannis Stavrakakis (University of Athens, Greece)=20 Xin Wang (University at Buffalo) Wenye Wang (North Carolina State University)=20 Lixia Zhang (UCLA) Taieb Znati (University of Pittsburgh) _______________________________________________________ =3D=3D=3D Ibrahim Matta, Associate Professor Computer Science Department Boston University, Boston, MA 02215, USA Tel: (617) 358-1062, Fax: (617) 353-6457 matta@cs.bu.edu http://www.cs.bu.edu/~matta=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 27 12:23:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14701 for ; Sun, 27 Feb 2005 12:23:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5S9P-0001eV-Eu for manet-web-archive@ietf.org; Sun, 27 Feb 2005 12:24:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5S5z-0002kw-Cx; Sun, 27 Feb 2005 12:20:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5S5w-0002kl-K4 for manet@megatron.ietf.org; Sun, 27 Feb 2005 12:20:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14465; Sun, 27 Feb 2005 12:20:37 -0500 (EST) Received: from mail1.engr.ucsb.edu ([128.111.53.4] helo=smtp.engr.ucsb.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5S6V-0001bU-2A; Sun, 27 Feb 2005 12:21:16 -0500 Received: from ip70-185-181-15.sb.sd.cox.net ([70.185.181.15]:52873 helo=[192.168.0.11]) by smtp.engr.ucsb.edu with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1D5S5h-0004uR-Dt; Sun, 27 Feb 2005 09:20:27 -0800 Mime-Version: 1.0 (Apple Message framework v619.2) Message-Id: <32535c269a7157ee5901786ffdaea1d4@cs.ucsb.edu> From: Ian Chakeres Date: Sun, 27 Feb 2005 09:20:26 -0800 To: agenda@ietf.org, manet X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: Determined clean by smtp.engr.ucsb.edu using clamd / ClamAV version 0.80 X-SA-Exim-Connect-IP: 70.185.181.15 X-SA-Exim-Mail-From: idc@cs.ucsb.edu Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on smtp.engr.ucsb.edu X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL, BAYES_00, UPPERCASE_25_50 autolearn=no version=3.0.1 X-SA-Exim-Version: 4.1 (built Mon, 13 Dec 2004 10:51:27 -0800) X-SA-Exim-Scanned: Yes (on smtp.engr.ucsb.edu) X-Spam-Score: 0.3 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: 7bit Cc: Joe Macker Subject: [manet] IETF 62 MANET WG Draft Agenda X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 7bit Here is the draft agenda for IETF 62 Mobile Ad-hoc Networks (manet) ================================== CHAIRS: Joe Macker Ian Chakeres DRAFT AGENDA: Agenda Bashing and Status 5 min Macker WG Next Stage 20 min Macker -MANET WG Charter DYMO Plans/Discussion 20 min Chakeres -draft-ietf-manet-dymo-00.txt MPRP Plans/Discussion 20 min Clausen SMRF Plans/Discussion 20 min Perkins OSPF-MANET Update 20 min Henderson MANET-AUTOCONF BOF 10 min Clausen/Singh 2nd OLSR Interop 5 min Clausen Open Discussion, Related Work & Announcements _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Feb 27 14:32:00 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24319 for ; Sun, 27 Feb 2005 14:32:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5U9e-0003yU-GY for manet-web-archive@ietf.org; Sun, 27 Feb 2005 14:32:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5U6o-0001ge-Ls; Sun, 27 Feb 2005 14:29:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5U6m-0001gX-Qr for manet@megatron.ietf.org; Sun, 27 Feb 2005 14:29:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24247 for ; Sun, 27 Feb 2005 14:29:39 -0500 (EST) Received: from [203.199.83.248] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D5U7N-0003wl-CR for manet@irtf.org; Sun, 27 Feb 2005 14:30:18 -0500 Received: (qmail 29651 invoked by uid 510); 27 Feb 2005 19:31:06 -0000 Date: 27 Feb 2005 19:31:06 -0000 Message-ID: <20050227193106.29650.qmail@webmail36.rediffmail.com> Received: from unknown (203.208.193.197) by rediffmail.com via HTTP; 27 feb 2005 19:31:06 -0000 MIME-Version: 1.0 From: "gokina " To: manet@irtf.org X-Spam-Score: 1.8 (+) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Subject: [manet] Installation Problem in ns-2.28 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gokina List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0111920732==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da This is a multipart mime message --===============0111920732== Content-type: multipart/alternative; boundary="Next_1109532666---0-203.199.83.248-29637" This is a multipart mime message --Next_1109532666---0-203.199.83.248-29637 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =0ADear members,=0A=0A I tried to install ns2 using allinone and from in= dividual packages. Both are giving installation problems. =0A=0A In buildin= g from sources, I followed the following steps as given in the website=0A= =0Abuild OTcl, TclCL and ns =0A=0Acd into the OTcl directory =0Arun ./confi= gure =0Arun make =0Acd into the TclCL directory =0Arun ./configure =0Arun m= ake =0Acd into the ns directory =0Arun ./configure =0Arun make =0ANow I am = getting problem when I tried to cd into the ns directory and then run ./con= figure. It is giving "make failed". for ns-2.28.=0A=0APlease let me know if= there is any solution for this problem and give me some suggestions or com= ments so that I can proceed further.=0A=0ASincerely,=0A=0AGokina.=0A --Next_1109532666---0-203.199.83.248-29637 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0ADear members,
=0A
=0A  I tried to install ns= 2 using allinone and from individual packages. Both are giving installation= problems.
=0A
=0A In building from sources, I followed the followin= g steps as given in the website
=0A
=0Abuild OTcl, TclCL and ns
= =0A
=0Acd into the OTcl directory
=0Arun ./configure
=0Arun make=
=0Acd into the TclCL directory
=0Arun ./configure
=0Arun make =
=0Acd into the ns directory
=0Arun ./configure
=0Arun make
= =0ANow I am getting problem when I tried to cd into the ns directory and th= en run ./configure. It is giving "make failed". for ns-2.28.
= =0A
=0APlease let me know if there is any solution for this problem and = give me some suggestions or comments so that I can proceed further.
=0A<= BR>=0ASincerely,
=0A
=0AGokina.
=0A=0A

=0A

=0A=0A --Next_1109532666---0-203.199.83.248-29637-- --===============0111920732== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0111920732==-- From manet-bounces@ietf.org Mon Feb 28 11:01:01 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03839 for ; Mon, 28 Feb 2005 11:01:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5nLC-0001mX-Ah for manet-web-archive@ietf.org; Mon, 28 Feb 2005 11:01:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5nHv-0007bh-9B; Mon, 28 Feb 2005 10:58:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5nHt-0007ba-OX for manet@megatron.ietf.org; Mon, 28 Feb 2005 10:58:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03463 for ; Mon, 28 Feb 2005 10:58:22 -0500 (EST) Received: from poros.telenet-ops.be ([195.130.132.44]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5nId-0001fF-TG for manet@ietf.org; Mon, 28 Feb 2005 10:59:13 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by poros.telenet-ops.be (Postfix) with SMTP id 914513BC0CC for ; Mon, 28 Feb 2005 16:58:19 +0100 (MET) Received: from [192.168.2.102] (d54C2A0ED.access.telenet.be [84.194.160.237]) by poros.telenet-ops.be (Postfix) with ESMTP id 67CB83BC199 for ; Mon, 28 Feb 2005 16:58:19 +0100 (MET) Message-ID: <42233F97.5010000@ugent.be> Date: Mon, 28 Feb 2005 16:58:15 +0100 From: Bart De Wilde User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Content-Transfer-Encoding: 7bit Subject: [manet] aodv X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Does anybody know about any aodv implementations for nodes with multiple radio interfaces ? (or related work) tnx bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Feb 28 12:41:56 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14370 for ; Mon, 28 Feb 2005 12:41:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5out-0004D6-Gl for manet-web-archive@ietf.org; Mon, 28 Feb 2005 12:42:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5oqr-0006if-DX; Mon, 28 Feb 2005 12:38:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5oqp-0006iR-Br for manet@megatron.ietf.org; Mon, 28 Feb 2005 12:38:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14035 for ; Mon, 28 Feb 2005 12:38:29 -0500 (EST) Received: from [203.193.147.238] (helo=iitg.ernet.in) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5orX-00048Y-0l for manet@ietf.org; Mon, 28 Feb 2005 12:39:20 -0500 Received: from loktak.iitg.ernet.in (loktak.iitg.ernet.in [202.141.80.32]) by iitg.ernet.in (8.12.8/8.12.0) with ESMTP id j1SHeBCi031669 for ; Mon, 28 Feb 2005 23:10:11 +0530 Received: from loktak.iitg.ernet.in (localhost.localdomain [127.0.0.1]) by loktak.iitg.ernet.in (8.12.10/8.12.10) with ESMTP id j1SHbfoZ023117 for ; Mon, 28 Feb 2005 23:07:41 +0530 Received: from localhost (kvinod@localhost) by loktak.iitg.ernet.in (8.12.10/8.12.10/Submit) with ESMTP id j1SHbfpC023113 for ; Mon, 28 Feb 2005 23:07:41 +0530 X-Authentication-Warning: loktak.iitg.ernet.in: kvinod owned process doing -bs Date: Mon, 28 Feb 2005 23:07:41 +0530 (IST) From: Vinod To: manet@ietf.org In-Reply-To: <200502281711.j1SHBHoB021691@luit.iitg.ernet.in> Message-ID: References: <200502281711.j1SHBHoB021691@luit.iitg.ernet.in> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Subject: [manet] Re: Installation Problem in ns-2.28 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 Hi, If ur installing on fc3 then u better use the patch available in the net.. i installed ns allinone (patched) n its working fine.. get bak to me if u still have problems ---------------------- Vinod Kone, Btech,Computer Science, VI sem, Room 179,Kapili, IIT Guwahati. mail me @: kvinod@iitg.ernet.in vinodkone@yahoo.com Mobile: 9864036875 On Mon, 28 Feb 2005 manet-request@ietf.org wrote: > Send manet mailing list submissions to > manet@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www1.ietf.org/mailman/listinfo/manet > or, via email, send a message with subject or body 'help' to > manet-request@ietf.org > > You can reach the person managing the list at > manet-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of manet digest..." > > > Today's Topics: > > 1. IETF 62 MANET WG Draft Agenda (Ian Chakeres) > 2. Installation Problem in ns-2.28 (gokina ) > 3. aodv (Bart De Wilde) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 27 Feb 2005 09:20:26 -0800 > From: Ian Chakeres > Subject: [manet] IETF 62 MANET WG Draft Agenda > To: agenda@ietf.org, manet > Cc: Joe Macker > Message-ID: <32535c269a7157ee5901786ffdaea1d4@cs.ucsb.edu> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Here is the draft agenda for IETF 62 > > Mobile Ad-hoc Networks (manet) > ================================== > > CHAIRS: Joe Macker > Ian Chakeres > > DRAFT AGENDA: > > Agenda Bashing and Status 5 min Macker > > WG Next Stage 20 min Macker > -MANET WG Charter > > DYMO Plans/Discussion 20 min Chakeres > -draft-ietf-manet-dymo-00.txt > > MPRP Plans/Discussion 20 min Clausen > > SMRF Plans/Discussion 20 min Perkins > > OSPF-MANET Update 20 min Henderson > > MANET-AUTOCONF BOF 10 min Clausen/Singh > > 2nd OLSR Interop 5 min Clausen > > Open Discussion, Related Work > & Announcements > > > > > ------------------------------ > > Message: 2 > Date: 27 Feb 2005 19:31:06 -0000 > From: "gokina " > Subject: [manet] Installation Problem in ns-2.28 > To: manet@irtf.org > Message-ID: <20050227193106.29650.qmail@webmail36.rediffmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > > Dear members, > > I tried to install ns2 using allinone and from individual packages. Both are giving installation problems. > > In building from sources, I followed the following steps as given in the website > > build OTcl, TclCL and ns > > cd into the OTcl directory > run ./configure > run make > cd into the TclCL directory > run ./configure > run make > cd into the ns directory > run ./configure > run make > Now I am getting problem when I tried to cd into the ns directory and then run ./configure. It is giving "make failed". for ns-2.28. > > Please let me know if there is any solution for this problem and give me some suggestions or comments so that I can proceed further. > > Sincerely, > > Gokina. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://www1.ietf.org/pipermail/manet/attachments/20050227/2542c0f3/attachment.htm > > ------------------------------ > > Message: 3 > Date: Mon, 28 Feb 2005 16:58:15 +0100 > From: Bart De Wilde > Subject: [manet] aodv > To: manet@ietf.org > Message-ID: <42233F97.5010000@ugent.be> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Does anybody know about any aodv implementations for nodes with multiple > radio interfaces ? (or related work) > > tnx > > bart > > > > ------------------------------ > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > End of manet Digest, Vol 10, Issue 29 > ************************************* > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet