From mailnull@www1.ietf.org Sat Feb 1 03:24:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01003 for ; Sat, 1 Feb 2003 03:24:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h118Sgx27473 for manet-archive@odin.ietf.org; Sat, 1 Feb 2003 03:28:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h118SfJ27470 for ; Sat, 1 Feb 2003 03:28:41 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00989 for ; Sat, 1 Feb 2003 03:24:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h118K8J27222; Sat, 1 Feb 2003 03:20:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h118FUJ27147 for ; Sat, 1 Feb 2003 03:15:30 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00824 for ; Sat, 1 Feb 2003 03:11:05 -0500 (EST) Received: (qmail 32058 invoked by uid 417); 1 Feb 2003 08:14:39 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 1 Feb 2003 08:14:39 -0000 Received: from ankur ([203.94.199.34]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Sat, 01 Feb 2003 01:14:18 -0700 Message-ID: <007601c2c9ca$48e5ed40$43c75ecb@ankur> From: "Ankur Jain" To: gupta@cpsc.ucalgary.ca, "manet" References: <3E3B0ABD.6050602@cpsc.ucalgary.ca> Subject: Re: [manet] APE test bed Date: Sat, 1 Feb 2003 13:41:15 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Abhinav, I think you are getting the error because you haven't copied the contents of linux kernel in ~/ape-sources-0.4/kernel/linux. I will suggest that you download the kernel from ftp.kernel.org and just don't copy the kernel from /usr/src/linux on your computer. Also download the pcmcia package and copy in the same directory. Download the kernel for which patches are available in the source code of APE. After that , you have to set all symobolic links as specified in the manual. Hope this helps Regards Ankur -------------------------------------------- Ankur Jain ankurjain@softhome.net http://www.geocities.com/ankurjain009/ -------------------------------------------- ----- Original Message ----- From: Abhinav Gupta To: manet Sent: Saturday, February 01, 2003 5:16 AM Subject: [manet] APE test bed > Hi, > > I have downloaded the APE (Ad hoc performance evaluation) testbed and am > trying to install it. When I try to make the package I get following error: > /home/grads/gupta/ape-sources-0.4/kernel/linux/Makefile: No such file or > directory > > Am I supposed to copy the contents of linux kernal under /usr/src/linux > 2.4.x to ~/ape-sources-0.4/kernel/linux? > > Also if somebody has used this package, can they let me know of its > performance? > > > Abhinav. > > _______________________________________________ > 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 mailnull@www1.ietf.org Sat Feb 1 20:15:00 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18440 for ; Sat, 1 Feb 2003 20:15:00 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h121JFU16842 for manet-archive@odin.ietf.org; Sat, 1 Feb 2003 20:19:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h121JFJ16839 for ; Sat, 1 Feb 2003 20:19:15 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18429 for ; Sat, 1 Feb 2003 20:14:29 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1218LJ16572; Sat, 1 Feb 2003 20:08:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1213NJ15819 for ; Sat, 1 Feb 2003 20:03:23 -0500 Received: from exstudent9.city.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18283 for ; Sat, 1 Feb 2003 19:58:36 -0500 (EST) Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59) id ; Sun, 2 Feb 2003 11:30:40 +1030 Message-ID: From: "Liaw, Yong Shyang - LIAYS001" To: "'calafate@disca.upv.es'" , Alvin Valera Cc: manet@ietf.org Subject: RE: [manet] Error simulating with AODV, DSR and TORA Date: Sun, 2 Feb 2003 11:33:07 +1030 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1213NJ15820 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, From my own experience with DSR model in opnet, it is possible that DSR reports Route_Error even in a single flow scenario, which I think it is likely due to contention in the MAC (as suggested by Alvin). But I am surprised at the large detection time of 10-20 seconds. Is this detection time for the source or for a node with a broken link? If it is for the source, one possible reasons is that ROUTE_ERROR message is lost on its way back to the source. > -----Original Message----- > From: calafate@disca.upv.es [mailto:calafate@disca.upv.es] > Sent: Saturday, 1 February 2003 1:39 > To: Alvin Valera > Cc: manet@ietf.org > Subject: Re: [manet] Error simulating with AODV, DSR and TORA > > > Hi Alvin, > > Thank you for your comments on this subject. > > My opinion is that, since I created a very simple scenario > with just 6 ones and > 1 traffic flow, we can't blame collisions for the behaviour > observed. Also, it's > true that the sender retries several times (I think 4 times), > but I guess that > 10 or 20 seconds to detect a broken link is too much, don't > you? If link-level > aware protocols were supposed to behave that bad, we would > conform to just > sending "Hellos"! > > It's curious to notice that the problems are not the same for > all: the worst > performance can be seen with DSR but TORA suddenly stops > sending packets and > everything is still! > > Please comment the "ns-random 0" line and you'll see exactly > what I see. > > Best regards, > > Carlos > > > > Mensaje citado por: Alvin Valera : > > > Hi Carlos Miguel, > > > > I performed many simulations in ns-2.1b8 specifically > > on the reaction of routing protocols to link failures. > > I haven't encountered your problem, though. > > > > Could it be that the delay in detecting a link failure > > is due to link layer retransmissions? In 802.11, as > > far as ns-2.1b8 is concerned, a sender retries several > > times (I could not remember the exact value) before > > informing the routing protocol that a data packet is > > undeliverable? > > > > Another possible reason is congestion. In my studies, > > I encountered many instances where 802.11 reports a > > link layer failure even though the receiver is within > > range. This is due to the fact that in highly > > congested environment, the MAC of the sender may fail > > to acquire the channel or complete the > > RTS-CTS-DATA-ACK. > > > > > > Best regards, > > Alvin > > > > > _________________________________________________ > Carlos Miguel Tavares de Araújo Cesariny Calafate > Becário de la Universidad Politécnica de Valencia > e-mail: calafate@disca.upv.es > http://reptar.grc.upv.es/~calafate/ > Tel: +34 963879703 ext. 77977 > _________________________________________________ > \\\\\\\"In an open world without walls and fences who needs > Windows and > Gates?\\\\\\\" > _______________________________________________ > 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 mailnull@www1.ietf.org Sun Feb 2 10:37:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07241 for ; Sun, 2 Feb 2003 10:37:21 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12Ffqx06328 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 10:41:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12FfqJ06325 for ; Sun, 2 Feb 2003 10:41:52 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07236 for ; Sun, 2 Feb 2003 10:36:49 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12FQdJ04936; Sun, 2 Feb 2003 10:26:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12FJoJ04684 for ; Sun, 2 Feb 2003 10:19:50 -0500 Received: from dire.bris.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06906 for ; Sun, 2 Feb 2003 10:14:46 -0500 (EST) Received: from golf.een.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Sun, 2 Feb 2003 15:18:05 +0000 Received: from EEN9097.een.bris.ac.uk (een9097.een.bris.ac.uk [137.222.189.97]) by golf.een.bris.ac.uk (8.9.3/8.9.3) with ESMTP id PAA21977 for ; Sun, 2 Feb 2003 15:13:21 GMT From: "D Kothris, Electrical & Electronic Engineering" Date: Sun, 2 Feb 2003 15:13:22 +0000 To: manet@ietf.org Message-ID: Priority: NORMAL X-Mailer: Execmail for Win32 Version 5.0.1 Build (55) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Subject: [manet] Wireless testbed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, My group is currently interested in 'assembling' a wireless testbed of ad hoc nature (dynamic in nature, but typically of very limited mobility associated with the nodes). We wish to develop routing protocols and applications suited for such environments and use this tesbed to evaluate them. Would anyone like to suggest some possible solutions? For example I have been thinking of laptops installed with linux (((modifying the kernel to accommodate for the protocols, but we have limited knowledge of linux nevertheless))) or with 802.11 wireless adaptors. In the second case though I am not sure if true ad hoc functionality can be obtained. Any suggestions would be welcomed Regards Dimos _________________________________________________________________ ***************************************************************** Dimosthenis Kothris Centre for Communications Research, University of Bristol, Network & Protocols group Address: Contact numbers: _________________________________________________________________ Network & Protocols Center for Communcations research Merchant Venturers Building Tel : +44 117 903 1104 Woodland Road Fax : +44 117 954 5206 Bristol BS8 1UB Mobile: +44 7779 40 48 42 United Kingdom Email : d.kothris@bristol.ac.uk ***************************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 2 11:46:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08322 for ; Sun, 2 Feb 2003 11:46:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12GpQr09764 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 11:51:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12GpQJ09761 for ; Sun, 2 Feb 2003 11:51:26 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08316 for ; Sun, 2 Feb 2003 11:46:22 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12GgLJ09448; Sun, 2 Feb 2003 11:42:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12GZ7J08606 for ; Sun, 2 Feb 2003 11:35:07 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08119 for ; Sun, 2 Feb 2003 11:30:03 -0500 (EST) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h12GXbG390788; Sun, 2 Feb 2003 11:33:37 -0500 (EST) Received: from tom ([198.70.228.2]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id AYY68201 (AUTH talin); Sun, 2 Feb 2003 11:33:35 -0500 (EST) Message-ID: <002301c2cad8$8298e4c0$643f640a@tom> From: "Tao Lin" To: "D Kothris, Electrical & Electronic Engineering" , References: Subject: Re: [manet] Wireless testbed Date: Sun, 2 Feb 2003 11:31:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit There are many ad hoc protocols implemented in Linux already (without touching the kernel). Examples include AODV, DSR, OLSR, and TBRPF. You may also design and implement one by yourself. You can setup a real wireless test bed using laptops with 802.11 NICs. You can also setup a wired testbed to emulate wireless ad hoc networks with a dynamic switch we developed for this purpose (Refer to io.irean.vt.edu/~tlin for the free software and the related paper). This dynamic switch is transparent to all end hosts, does not require any modification at the end hosts, and can control the topology dynamically during the emulations. Best, Tao Lin ECE Dept. Virginia Tech. ----- Original Message ----- From: "D Kothris, Electrical & Electronic Engineering" To: Sent: Sunday, February 02, 2003 10:13 AM Subject: [manet] Wireless testbed > Hi, > > My group is currently interested in 'assembling' a wireless testbed of > ad hoc nature (dynamic in nature, but typically of very limited > mobility associated with the nodes). We wish to develop routing > protocols and applications suited for such environments and use this > tesbed to evaluate them. > > Would anyone like to suggest some possible solutions? > > For example I have been thinking of laptops installed with linux > (((modifying the kernel to accommodate for the protocols, but we have > limited knowledge of linux nevertheless))) or with 802.11 wireless > adaptors. In the second case though I am not sure if true ad hoc > functionality can be obtained. > > Any suggestions would be welcomed > > Regards > > Dimos > _________________________________________________________________ > ***************************************************************** > Dimosthenis Kothris Centre for Communications Research, > University of Bristol, > Network & Protocols group > > Address: Contact numbers: > _________________________________________________________________ > Network & Protocols > Center for Communcations research > Merchant Venturers Building Tel : +44 117 903 1104 > Woodland Road Fax : +44 117 954 5206 > Bristol BS8 1UB Mobile: +44 7779 40 48 42 > United Kingdom Email : d.kothris@bristol.ac.uk > ***************************************************************** > > _______________________________________________ > 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 mailnull@www1.ietf.org Sun Feb 2 12:32:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09267 for ; Sun, 2 Feb 2003 12:32:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12Hb8612295 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 12:37:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12Hb7J12285 for ; Sun, 2 Feb 2003 12:37:08 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09263 for ; Sun, 2 Feb 2003 12:32:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HTQJ11746; Sun, 2 Feb 2003 12:29:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HNCJ11599 for ; Sun, 2 Feb 2003 12:23:12 -0500 Received: from maild.telia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08990 for ; Sun, 2 Feb 2003 12:18:06 -0500 (EST) Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by maild.telia.com (8.12.5/8.12.5) with ESMTP id h12HLchp024165; Sun, 2 Feb 2003 18:21:38 +0100 (CET) X-Original-Recipient: manet@ietf.org Received: from h60n2fls35o1121.telia.com (h60n2fls35o1121.telia.com [217.211.83.60]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h12HLcB08796; Sun, 2 Feb 2003 18:21:38 +0100 (CET) Subject: Re: [manet] Wireless testbed From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: "D Kothris, Electrical & "Electronic Engineering Cc: manet@ietf.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1044206495.3114.7.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 02 Feb 2003 18:21:35 +0100 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit If you want to avoid duplication of efforts, take a look at: http://apetestbed.sourceforge.net/ Erik On Sun, 2003-02-02 at 16:13, D Kothris, Electrical & Electronic Engineering wrote: > Hi, > > My group is currently interested in 'assembling' a wireless testbed of > ad hoc nature (dynamic in nature, but typically of very limited > mobility associated with the nodes). We wish to develop routing > protocols and applications suited for such environments and use this > tesbed to evaluate them. > > Would anyone like to suggest some possible solutions? > > For example I have been thinking of laptops installed with linux > (((modifying the kernel to accommodate for the protocols, but we have > limited knowledge of linux nevertheless))) or with 802.11 wireless > adaptors. In the second case though I am not sure if true ad hoc > functionality can be obtained. > > Any suggestions would be welcomed > > Regards > > Dimos > _________________________________________________________________ > ***************************************************************** > Dimosthenis Kothris Centre for Communications Research, > University of Bristol, > Network & Protocols group > > Address: Contact numbers: > _________________________________________________________________ > Network & Protocols > Center for Communcations research > Merchant Venturers Building Tel : +44 117 903 1104 > Woodland Road Fax : +44 117 954 5206 > Bristol BS8 1UB Mobile: +44 7779 40 48 42 > United Kingdom Email : d.kothris@bristol.ac.uk > ***************************************************************** > > _______________________________________________ > 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 mailnull@www1.ietf.org Sun Feb 2 12:38:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09363 for ; Sun, 2 Feb 2003 12:38:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12HhR313000 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 12:43:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HhRJ12997 for ; Sun, 2 Feb 2003 12:43:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09360 for ; Sun, 2 Feb 2003 12:38:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HZPJ11978; Sun, 2 Feb 2003 12:35:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HYeJ11903 for ; Sun, 2 Feb 2003 12:34:40 -0500 Received: from farley1.Colorado.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09191 for ; Sun, 2 Feb 2003 12:29:34 -0500 (EST) Received: (from nobody@localhost) by farley1.Colorado.EDU (8.11.2/8.11.2/ITS-5.0/webmail) id h12HX2m18250; Sun, 2 Feb 2003 10:33:02 -0700 (MST) From: Shweta.Bhandare@colorado.edu Received: from 0-1pool15-78.nas6.thornton1.co.us.da.qwest.net (0-1pool15-78.nas6.thornton1.co.us.da.qwest.net [67.4.15.78]) by webmail.colorado.edu (IMP) with HTTP for ; Sun, 2 Feb 2003 10:33:02 -0700 Message-ID: <1044207182.3e3d564e74aba@webmail.colorado.edu> Date: Sun, 2 Feb 2003 10:33:02 -0700 To: "D Kothris, Electrical & Electronic Engineering" Cc: manet@ietf.org Subject: Re: [manet] Wireless testbed References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Our group at the University of Colorado at Boulder have developed an wireless test-bed - please contact: sanghani@colorado.edu for questions. I have attached the paper that will appear in the WCNC conference. Regards, Shweta. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 2 12:39:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09390 for ; Sun, 2 Feb 2003 12:39:36 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12HiAE13037 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 12:44:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HiAJ13034 for ; Sun, 2 Feb 2003 12:44:10 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09377 for ; Sun, 2 Feb 2003 12:39:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12Ha5J12024; Sun, 2 Feb 2003 12:36:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12HZ1J11923 for ; Sun, 2 Feb 2003 12:35:01 -0500 Received: from farley1.Colorado.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09204 for ; Sun, 2 Feb 2003 12:29:56 -0500 (EST) Received: (from nobody@localhost) by farley1.Colorado.EDU (8.11.2/8.11.2/ITS-5.0/webmail) id h12HXSU18263; Sun, 2 Feb 2003 10:33:28 -0700 (MST) From: Shweta.Bhandare@colorado.edu Received: from 0-1pool15-78.nas6.thornton1.co.us.da.qwest.net (0-1pool15-78.nas6.thornton1.co.us.da.qwest.net [67.4.15.78]) by webmail.colorado.edu (IMP) with HTTP for ; Sun, 2 Feb 2003 10:33:28 -0700 Message-ID: <1044207208.3e3d5668261e4@webmail.colorado.edu> Date: Sun, 2 Feb 2003 10:33:28 -0700 To: "D Kothris, Electrical & Electronic Engineering" Cc: manet@ietf.org Subject: Re: [manet] Wireless testbed References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Our group at the University of Colorado at Boulder have developed an wireless test-bed - please contact: sanghani@colorado.edu for questions. I have attached the paper that will appear in the WCNC conference. Regards, Shweta. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 2 15:11:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11300 for ; Sun, 2 Feb 2003 15:11:12 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12KFoL20427 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 15:15:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12KFoJ20424 for ; Sun, 2 Feb 2003 15:15:50 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11286 for ; Sun, 2 Feb 2003 15:10:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12K2BJ19466; Sun, 2 Feb 2003 15:02:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12JxAJ19344 for ; Sun, 2 Feb 2003 14:59:10 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11126 for ; Sun, 2 Feb 2003 14:54:01 -0500 (EST) Received: (qmail 32503 invoked by uid 417); 2 Feb 2003 19:57:37 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 2 Feb 2003 19:57:37 -0000 Received: from ankur ([203.94.241.63]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Sun, 02 Feb 2003 12:57:32 -0700 Message-ID: <009501c2caf5$666fdac0$3ff15ecb@ankur> From: "Ankur Jain" To: "D Kothris, Electrical & Electronic Engineering" Cc: manet@ietf.org References: Subject: Re: [manet] Wireless testbed Date: Mon, 3 Feb 2003 01:17:25 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Dimos I will suggest to use either APE (http://apetestbed.sourceforge.net/ ) or Mobiemu (http://mobiemu.sourceforge.net/ ). I have used both implementation on my testbed and I would say both implementation are excellent for testing various routing protocols for ad hoc networks on the actual testbed for ad hoc networks. But if you want to make it "very real", use APE. Another solution is use the tool as suggested by Tao Lin from io.irean.vt.edu/~tlin. Although I didn't implement it on my testbed, I read the paper and found it good. If you have enough funds (and persons), you can make your testbed implementation similar to the researchers of Monarch group at CMU / Rice (monarch.cs.cmu.edu). Hope this helps. Regards Ankur ----- Original Message ----- From: D Kothris, Electrical & Electronic Engineering To: Sent: Sunday, February 02, 2003 8:43 PM Subject: [manet] Wireless testbed > Hi, > > My group is currently interested in 'assembling' a wireless testbed of > ad hoc nature (dynamic in nature, but typically of very limited > mobility associated with the nodes). We wish to develop routing > protocols and applications suited for such environments and use this > tesbed to evaluate them. > > Would anyone like to suggest some possible solutions? > > For example I have been thinking of laptops installed with linux > (((modifying the kernel to accommodate for the protocols, but we have > limited knowledge of linux nevertheless))) or with 802.11 wireless > adaptors. In the second case though I am not sure if true ad hoc > functionality can be obtained. > > Any suggestions would be welcomed > > Regards > > Dimos > _________________________________________________________________ > ***************************************************************** > Dimosthenis Kothris Centre for Communications Research, > University of Bristol, > Network & Protocols group > > Address: Contact numbers: > _________________________________________________________________ > Network & Protocols > Center for Communcations research > Merchant Venturers Building Tel : +44 117 903 1104 > Woodland Road Fax : +44 117 954 5206 > Bristol BS8 1UB Mobile: +44 7779 40 48 42 > United Kingdom Email : d.kothris@bristol.ac.uk > ***************************************************************** > > _______________________________________________ > 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 mailnull@www1.ietf.org Sun Feb 2 20:50:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14935 for ; Sun, 2 Feb 2003 20:50:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h131tLg03921 for manet-archive@odin.ietf.org; Sun, 2 Feb 2003 20:55:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h131tKJ03918 for ; Sun, 2 Feb 2003 20:55:20 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14931 for ; Sun, 2 Feb 2003 20:50:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h131bhJ03419; Sun, 2 Feb 2003 20:37:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h131S9J02493 for ; Sun, 2 Feb 2003 20:28:09 -0500 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14545 for ; Sun, 2 Feb 2003 20:22:53 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 2 Feb 2003 17:26:27 -0800 Received: from 68.49.198.196 by pv1fd.pav1.hotmail.msn.com with HTTP; Mon, 03 Feb 2003 01:26:27 GMT X-Originating-IP: [68.49.198.196] From: "m c" To: manet@ietf.org Date: Sun, 02 Feb 2003 20:26:27 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Feb 2003 01:26:27.0837 (UTC) FILETIME=[45FE1AD0:01C2CB23] Subject: [manet] Multicast routing algorithm and implemented router Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello all, Just wanted to inform everyone that a new multicast routing algorithm has been developed and implemented at Virginia Tech. This multicast routing algorithm has been titled Extensions to Multicast for Mobile Ad-hoc Networks (XMMAN) and attempts to reduce redundent data rebroadcasts. It seems that most of the existing multicast algorithms attempt to reduce routing overhead, but pretty much ignore the problem of data overhead. That is, multicast routers do not try to aggregate the data flows to reduce unneccessary data rebroadcasts. This algorithm was first presented in a masters thesis (http://scholar.lib.vt.edu/theses/available/etd-08142002-131727/). A REAL implementation can be found at http://www.irean.vt.edu/navciiti/ (click on "Resources"). This was written in C under the Linux 2.4 operating system, but should work in pretty much any Linux environment. Chapter 4: Protocol of the thesis reads like an internet draft, and should be easy to read. Have fun! Mike _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 3 06:01:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02599 for ; Mon, 3 Feb 2003 06:01:27 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13B6M011188 for manet-archive@odin.ietf.org; Mon, 3 Feb 2003 06:06:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13B6MJ11185 for ; Mon, 3 Feb 2003 06:06:22 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02580 for ; Mon, 3 Feb 2003 06:00:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13AlhJ10403; Mon, 3 Feb 2003 05:47:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13AjBJ10297 for ; Mon, 3 Feb 2003 05:45:11 -0500 Received: from marfik.upv.es (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02272 for ; Mon, 3 Feb 2003 05:39:44 -0500 (EST) From: calafate@disca.upv.es Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h13AhUk03829; Mon, 3 Feb 2003 11:43:30 +0100 Received: from smtp2.upv.es (smtp.cc.upv.es [158.42.250.10]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h13AhXL25521; Mon, 3 Feb 2003 11:43:33 +0100 (MET) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by smtp2.upv.es (8.11.4/8.11.4) with ESMTP id h13BNnD16587; Mon, 3 Feb 2003 12:23:49 +0100 Received: by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0, from userid 30) id 865FF1FE8E; Mon, 3 Feb 2003 11:41:38 +0100 (CET) To: "Liaw, Yong Shyang - LIAYS001" Subject: RE: [manet] Error simulating with AODV, DSR and TORA Message-ID: <1044268898.3e3e4762800dc@nao.disca.upv.es> Date: Mon, 03 Feb 2003 11:41:38 +0100 (CET) Cc: manet@ietf.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 158.42.180.53 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Yes, collisions are possible even in a single flow scenario, but the problem is that upper layer protocols (such as DSR) do not detect the broken link at all, even after a long time and a lot of packets lost. In my scenario, nodes are positioned like this: B C A D E F And the flow initially goes A-B-C-D. Suddenly, I make node C go away and node B is not able to detect that the link to C is broken, and so the flow does not change to the route A-E-F-D! (Sometimes it does, but after a long time.) Mensaje citado por: "Liaw, Yong Shyang - LIAYS001" : > Hi, > > From my own experience with DSR model in opnet, it is possible that DSR > reports > Route_Error even in a single flow scenario, which I think it is likely > due to > contention in the MAC (as suggested by Alvin). But I am surprised at the > large > detection time of 10-20 seconds. Is this detection time for the source > or for a > node with a broken link? If it is for the source, one possible reasons > is that > ROUTE_ERROR message is lost on its way back to the source. > > > -----Original Message----- > > From: calafate@disca.upv.es [mailto:calafate@disca.upv.es] > > Sent: Saturday, 1 February 2003 1:39 > > To: Alvin Valera > > Cc: manet@ietf.org > > Subject: Re: [manet] Error simulating with AODV, DSR and TORA > > > > > > Hi Alvin, > > > > Thank you for your comments on this subject. > > > > My opinion is that, since I created a very simple scenario > > with just 6 ones and > > 1 traffic flow, we can't blame collisions for the behaviour > > observed. Also, it's > > true that the sender retries several times (I think 4 times), > > but I guess that > > 10 or 20 seconds to detect a broken link is too much, don't > > you? If link-level > > aware protocols were supposed to behave that bad, we would > > conform to just > > sending "Hellos"! > > > > It's curious to notice that the problems are not the same for > > all: the worst > > performance can be seen with DSR but TORA suddenly stops > > sending packets and > > everything is still! > > > > Please comment the "ns-random 0" line and you'll see exactly > > what I see. > > > > Best regards, > > > > Carlos > > > > > > > > Mensaje citado por: Alvin Valera : > > > > > Hi Carlos Miguel, > > > > > > I performed many simulations in ns-2.1b8 specifically > > > on the reaction of routing protocols to link failures. > > > I haven't encountered your problem, though. > > > > > > Could it be that the delay in detecting a link failure > > > is due to link layer retransmissions? In 802.11, as > > > far as ns-2.1b8 is concerned, a sender retries several > > > times (I could not remember the exact value) before > > > informing the routing protocol that a data packet is > > > undeliverable? > > > > > > Another possible reason is congestion. In my studies, > > > I encountered many instances where 802.11 reports a > > > link layer failure even though the receiver is within > > > range. This is due to the fact that in highly > > > congested environment, the MAC of the sender may fail > > > to acquire the channel or complete the > > > RTS-CTS-DATA-ACK. > > > > > > > > > Best regards, > > > Alvin > > > > > > > > > _________________________________________________ > > Carlos Miguel Tavares de Araújo Cesariny Calafate > > Becário de la Universidad Politécnica de Valencia > > e-mail: calafate@disca.upv.es > > http://reptar.grc.upv.es/~calafate/ > > Tel: +34 963879703 ext. 77977 > > _________________________________________________ > > \\\\\\\"In an open world without walls and fences who needs > > Windows and > > Gates?\\\\\\\" > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > _________________________________________________ Carlos Miguel Tavares de Araújo Cesariny Calafate Becário de la Universidad Politécnica de Valencia e-mail: calafate@disca.upv.es http://reptar.grc.upv.es/~calafate/ Tel: +34 963879703 ext. 77977 _________________________________________________ \\\\\\\"In an open world without walls and fences who needs Windows and Gates?\\\\\\\" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 3 06:42:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03247 for ; Mon, 3 Feb 2003 06:42:06 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13Bl2a14123 for manet-archive@odin.ietf.org; Mon, 3 Feb 2003 06:47:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13Bl2J14120 for ; Mon, 3 Feb 2003 06:47:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03244 for ; Mon, 3 Feb 2003 06:41:34 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13BWsJ12814; Mon, 3 Feb 2003 06:32:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13BVYJ12783 for ; Mon, 3 Feb 2003 06:31:34 -0500 Received: from rasheen.osdp.is.tsukuba.ac.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02948 for ; Mon, 3 Feb 2003 06:26:05 -0500 (EST) Received: from John (bill.is.tsukuba.ac.jp [130.158.81.66]) by rasheen.osdp.is.tsukuba.ac.jp (8.12.6/8.12.6) with SMTP id h13BTbOP021010; Mon, 3 Feb 2003 20:29:37 +0900 (JST) (envelope-from lijie@is.tsukuba.ac.jp) Message-ID: <019301c2cb77$56c19870$42519e82@John> From: "Jie Li" To: Cc: "Professor Mohammad S. Obaidat" , "Yuguang Fang" Date: Mon, 3 Feb 2003 20:28:13 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] CFP -- SPECTS'2003 deadline is extended to February 28 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Colleagues We apologize if you receive multiple copies of this message. We know you have too many deadlines already, due to numerous requests, the committee of SCS SPECTS'2003 decides to extend the paper submission deadline to Feburay 28 for your convience. We do treasure your contribution to this conference held in Montreal, Canada in July 2003. Thank you for your attention. Sincerely, --- Dr. Jie Li Institute of Infomation Sciences & Electronics University of Tsukuba Tsukuba Science City, Ibaraki 305-8573 Japan %%%% CFP 2003 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS 2003) July 20-24, 2003 Montreal, Canada http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm Submission Deadlines Submission of Papers: February 28, 2003. Notification of Acceptance - April 25, 2003 Final Camera-Ready Submission - May 23, 2003 This annual international conference is a forum for professionals involved in performance evaluation of computer and telecommunication systems. Evaluation of computer systems and networks is needed at every stage in the life cycle of the product including design, manufacturing, sales/purchase, use, upgrade, tuning, etc. The discipline of performance evaluation has progressed rapidly in the past decade, and it has now begun to approach maturity. Significant progress has been made in analytic modeling, simulation, and measurement approaches for performance evaluation of computer and telecommunication systems. Topics of interest include, but are not limited to: Networking and Telecommunication Systems - Internet Technology - Quality of Service (QoS) - DiffServ/IntServ - MPLS - TCP - World Wide Web (WWW) Technology - Networking Techniques - Unicast and Multicast Routing - Congestion Control - Switching Techniques - Teletraffic - Network Protocols - Network Management and Control - Network Capacity Planning - Network Architecture Evaluation - Service and QoS Pricing - Security and Authentication -Broadband Networks - High-Speed Networking - ATM - Optical Networks - Wireless Systems and Networks - Satellite Systems - UMTS - Mobile Networks/Computing - Ad-hoc networks - Multimedia Communications Computer Systems - Distributed Architectures - Client/Server - Distributed Systems and Agents - Parallel and Distributed Computing - Massively Parallel Systems - Cluster Computing - Grid Computing - Interconnection Networks - Computer Architectures - Microprocessors/Microcomputers - Memory Systems - High Performance I/O - Real-time Systems - Scheduling Schemes -Software - Software Performance, Evaluation and Testing - Parallel Algorithms and Languages - Hardware and Software Monitors - High-Performance Computing - Workload and Traffic Characterization - Scientific Computing Algorithms - Reconfigurable Computing - Electronic Commerce Tools, Methodologies and Applications - Parallel and Distributed Simulation - Verification and Validation - Performance Tools and Methodologies - Neural Networks and Fuzzy Logic Applications to High Performance Computing/Networking - Performance Optimization - Queueing Systems and Networks - Scalability Studies - Integrated Modeling and Measurement - On-Line Performance Adaptation and Tuning - Process Algebra-Based Models - Performance Bounds - Integrated Design and Performance - New Performance Models - Mathematical Aspects of Performance - New Performability Schemes and Models - Case Studies General Chair Mohammad S. Obaidat Dept. of Computer Science, Monmouth University W. Long Branch, NJ 07764, USA Tel +1-732-571-4482 Fax +1-732-263-5202 E-mail: obaidat@monmouth.edu Senior Program Chair Franco Davoli DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy Tel +39-010-353-2732 Fax +39-010-353-2154 E-Mail: franco@dist.unige.it Program Co-Chairs Ibrahim Onyuksel Dept. of Computer Sciences, N. Illinois Univ., USA E-mail: onyuksel@cs.niu.edu Erina Ferro ISTI, Institute of National Research Council (C.N.R.) C.N.R. Pisa Research Area, Building B, Room 73 Via G. Moruzzi, 1 56124 Pisa, Italy E-mail: erina.ferro@cnuce.cnr.it Vice Program Chair and Tutorial Chair Raffaele Bolla DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy E-mail: lelus@dist.unige.it Vice Program Chair and Web Master Imad Mahgoub Department of Computer Science and Engineering Florida Atlantic University Boca Raton, FL 33431 E-mail: imad@cse.fau.edu Industrial Track and Special Sessions Chair J. Fox, Motorola Inc., UK E-mail: fox.ijcs@btinternet.com Technical Program Committee Ian Akyildiz, Georgia Tech., USA Mohammed Atiquzzaman, University of Oklahoma, USA Louis G. Birta, University of Ottawa, Canada Abdullah Abonamah, Zayed University, UAE Noureddine Boudriga, University of Tunis, Tunisia Hasan Cam, Arizona State University, USA Andrew Campbell, Columbia University, USA Nedo Celandroni, ISTI-CNR, Italy Haitham Cruickshank, University of Surrey, UK Hassan B. Diab, American University of Beirut, Lebanon Gabor Fodor, Ericsson Radio Systems, Sweden Geoffrey Fox, Indiana University, USA Luigi Fratta, Politecnico di Milano, Italy Aura Ganz, University of Massachusetts, USA Erol Gelenbe, University of Central Florida, USA Mario Gerla, UCLA, USA Sami Habib, Kuwait University, Kuwait Omar Hammami, ENSTA, France Jarmo Harju, Tampere University of Technology, Finland Herman Hughes, Michigan State University, USA Andrzej Jajszczyk, University of Mining and Metallurgy, Poland Abbas Jamalipour, University of Sydney, Australia Ingemar Kaj, Uppsala University, Sweden Krishna Kant, Intel, USA Helen Karatza, Aristotle University of Thessalonica, Greece Demetrios Kazakos, University of Louisiana, USA Ulrich Killat, Tech Univ. of Hamburg, Germany Tag Gon Kim, KAIST, Korea Kevin Kwiat, Air Force Research Laboratory, USA Veronica Lagrange M. Reis, Compaq Computers Corp., USA Axel Lehmann, Universitat der Bundeswehr Munchen, Germany Daniel C. Lee, USC, USA Mike T. Liu, Ohio State University, USA Erich Lutz, DLR, Germany Sam Makki, Queensland University of Technology, Australia Krzysztof Malinowski, Warsaw Technical University, Poland Mario Marchese, University of Genoa, Italy Jose L. Marzo, Universitat de Girona, Spain Xiannong Meng, Bucknell University, USA Hussein Mouftah, Queen's University, Canada Mohamed Ould-Khaoua, University of Glasgow, UK Sergio Palazzo, Universita di Catania, Italy Georgios I. Papadimitriou, Aristotle University, Greece Achille Pattavina, Politecnico di Milano, Italy Krzysztof Pawlikowski, University of Canterbury, New Zealand Gregory D. Peterson, University of Tennessee Steven Pink, University of Arizona, USA George Polyzos, AUEB, Greece Ramon Puigjaner, Universitat de les Illes Balears, Spain Kaliappa Ravindran, CUNY, USA Gian Paolo Rossi, Universita di Milano, Italy Izhak Rubin, UCLA, USA Vicente Santonja, Technical University of Valencia, Spain Donald Schilling, CUNY, USA Jens B. Schmitt, TU Darmstadt, Germany Harald Skinnemoen, Nera, Norway Tatsuya Suda, UCI, USA Iwao Toda, Fujutsu Laboratories Ltd., Japan Phuoc Tran-Gia, University of Wuerzburg, Germany Kishor Trivedi, Duke University, USA Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA Manuel Villen-Altamirano, Telefonica, Spain Bernd E. Wolfinger, Hamburg University, Germany Michele Zorzi, Universita di Ferrara, Italy Publicity Chair: Yuguang (Michael) Fang, University of Florida, USA, E-mail: fang@ece.ufl.edu Publicity Vice Chair: Jie Li University of Tsukuba, Japan Publicity Committee: Chiara Petrioli, Universita` di Roma "La Sapienza", Italy Chuck Song, Chinese Academy of Sciences, China Ahmed Nuseirat, Al-Isra University, Jordan International Liaisons B. Sadoun, Al-Balqa' Applied University, Jordan Bsadoun@go.com.jo M. Sawan, Montreal Poly, Canada Sawan@vlsi.polymtl.ca N. Tchamov, Tampere Univ. of Technology, Finland Nikolay@cs.tut.fi Paper Submission Submit your complete papers electronically to: http://scs.proceedingscentral.com/ All required instructions will be posted on this web site. Submissions should not exceed 25 double-spaced, 8.5x11 inch pages (including figures, tables, and references) in 10-12 point font. Include five to ten keywords, complete postal and e-mail addresses, and fax and phone numbers of corresponding author. If you have difficulty in electronic submission, contact the Web Master, Program Chairs or the Conference Coordinator, Mr. Steve Branch, The Society for Modeling and Simulation International, 4838 Ronson Court, Suite L, San Diego, CA 92111, USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org Extended versions of selected accepted papers in SPECTS 2003 will be considered for possible publication in scholarly journals. Proposals for tutorials should be sent to the Conference Vice Program Chair, Raffaele Bolla. Proposals for special sessions and panel sessions should be submitted to the special Sessions Chair. For more information regarding presentations or exhibitions at SPECTS 2002 contact: Mr. Steve Branch at the address shown above. Sponsored by The Society for Modeling and Simulation International. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 3 11:46:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12852 for ; Mon, 3 Feb 2003 11:46:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13GpDG03411 for manet-archive@odin.ietf.org; Mon, 3 Feb 2003 11:51:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13GpDJ03408 for ; Mon, 3 Feb 2003 11:51:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12836 for ; Mon, 3 Feb 2003 11:45:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13GamJ01935; Mon, 3 Feb 2003 11:36:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13GWXJ01701 for ; Mon, 3 Feb 2003 11:32:33 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12214 for ; Mon, 3 Feb 2003 11:26:58 -0500 (EST) Received: (cpmta 22005 invoked from network); 3 Feb 2003 08:30:29 -0800 Received: from 12.221.64.123 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.66) with SMTP; 3 Feb 2003 08:30:29 -0800 X-Sent: 3 Feb 2003 16:30:29 GMT Message-ID: <3E3E9082.7060608@cs.uiuc.edu> Date: Mon, 03 Feb 2003 09:53:38 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: calafate@disca.upv.es CC: manet@ietf.org, ns-users@isi.edu Subject: Re: [manet] Error simulating with AODV, DSR and TORA References: <1044009368.3e3a519878bad@nao.disca.upv.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Analysis of the trace file (with mac trace on) reveals that this problem is due to a bug in the 802.11 mac implementation. 802.11 tries to send an RTS several times (7 times in ns2) before reporting failure. In the ns2 mac, the retry counter is reset when the mac successsfully sends or _receives_ a packet. As long as node 1 in your scenario keeps receiving packets from node 0, before it can reach seven retries, it will not report failure. My trace file shows that node 1 retries this particular RTS about 650 times between 25 and 33.13 seconds. The particular culprit is in void MAC802_11::recvDATA(Packet*); the conditional branch that cleans up CTS packets after successful reception resets ssrc_, the RTS retry counter. Anybody know why? Commenting out the line that reads ssrc_ = 0; forces the proper behavior. calafate@disca.upv.es wrote: >Hi, > >I have sent a possible bug report to the NS mailing list, but since no one was >able to give me a reply, perhaps someone in this mailing list is interested. > >Results of dozens of simulations using AODV, DSR and TORA in ns2.1b9a (2.1b8 >too) show that these protocols do not behave correctly when there are 802.11 >broken links. > >When looking at the overall results of simulations with many nodes, the effect I >describe is not evident. It is necessary to look at a single flow to see that >nodes fail to quickly detect broken links, making the re-routing process last >too long. This effect does not exist when using other protocols like OLSR or >Hello-driven AODV since they do not use link-layer info. > >The files I attach show this problem clearly in a very simple scenario > >Please help! > >Best regards, > >_________________________________________________ >Carlos Miguel Tavares de Araújo Cesariny Calafate >Polytechnic University of Valencia >e-mail: calafate@disca.upv.es >http://reptar.grc.upv.es/~calafate/ >Tel: +34 963879703 ext. 77977 >_________________________________________________ > > -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 3 12:35:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14321 for ; Mon, 3 Feb 2003 12:35:05 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13He8a08181 for manet-archive@odin.ietf.org; Mon, 3 Feb 2003 12:40:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13He8J08178 for ; Mon, 3 Feb 2003 12:40:08 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14311 for ; Mon, 3 Feb 2003 12:34:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13HNqJ06302; Mon, 3 Feb 2003 12:23:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13HL3J06166 for ; Mon, 3 Feb 2003 12:21:03 -0500 Received: from marfik.upv.es (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13712 for ; Mon, 3 Feb 2003 12:15:21 -0500 (EST) From: calafate@disca.upv.es Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h13HItk08912; Mon, 3 Feb 2003 18:18:55 +0100 Received: from smtp2.upv.es (smtp.cc.upv.es [158.42.250.10]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h13HIwg00553; Mon, 3 Feb 2003 18:18:59 +0100 (MET) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by smtp2.upv.es (8.11.4/8.11.4) with ESMTP id h13HxBD18571; Mon, 3 Feb 2003 18:59:12 +0100 Received: by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0, from userid 30) id F1D1A1FE8E; Mon, 3 Feb 2003 18:16:57 +0100 (CET) To: Casey Carter Subject: Re: [manet] Error simulating with AODV, DSR and TORA Message-ID: <1044292617.3e3ea409eb79e@nao.disca.upv.es> Date: Mon, 03 Feb 2003 18:16:57 +0100 (CET) Cc: manet@ietf.org References: <1044009368.3e3a519878bad@nao.disca.upv.es> <3E3E9082.7060608@cs.uiuc.edu> In-Reply-To: <3E3E9082.7060608@cs.uiuc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 158.42.180.53 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Casey, I am happy someone really looked into the BUG I described. I wanted to congratulate you for your efforts since I have tested your solution and it seems to actually solve the problem for all three protocols (DSR, AODV and TORA). Even though it might look a small bug, it is not! This bug makes the results achieved with these Link Level Aware protocols innacurate, since a carefull examination of what's going on in each flow shows that what's happening is not what is expected to happend. If you have more information on how to correct this bug, please e-mail me. Best regards, Carlos Calafate UPV Spain Mensaje citado por: Casey Carter : > Analysis of the trace file (with mac trace on) reveals that this problem > > is due to a bug in the 802.11 mac implementation. 802.11 tries to send > > an RTS several times (7 times in ns2) before reporting failure. In the > ns2 mac, the retry counter is reset when the mac successsfully sends or > > _receives_ a packet. As long as node 1 in your scenario keeps receiving > > packets from node 0, before it can reach seven retries, it will not > report failure. My trace file shows that node 1 retries this particular > > RTS about 650 times between 25 and 33.13 seconds. > > The particular culprit is in void MAC802_11::recvDATA(Packet*); the > conditional branch that cleans up CTS packets after successful reception > > resets ssrc_, the RTS retry counter. Anybody know why? Commenting out > the line that reads > > ssrc_ = 0; > > forces the proper behavior. > > calafate@disca.upv.es wrote: > > >Hi, > > > >I have sent a possible bug report to the NS mailing list, but since no > one was > >able to give me a reply, perhaps someone in this mailing list is > interested. > > > >Results of dozens of simulations using AODV, DSR and TORA in ns2.1b9a > (2.1b8 > >too) show that these protocols do not behave correctly when there are > 802.11 > >broken links. > > > >When looking at the overall results of simulations with many nodes, the > effect I > >describe is not evident. It is necessary to look at a single flow to > see that > >nodes fail to quickly detect broken links, making the re-routing > process last > >too long. This effect does not exist when using other protocols like > OLSR or > >Hello-driven AODV since they do not use link-layer info. > > > >The files I attach show this problem clearly in a very simple scenario > > > >Please help! > > > >Best regards, > > > >_________________________________________________ > >Carlos Miguel Tavares de Araújo Cesariny Calafate > >Polytechnic University of Valencia > >e-mail: calafate@disca.upv.es > >http://reptar.grc.upv.es/~calafate/ > >Tel: +34 963879703 ext. 77977 > >_________________________________________________ > > > > > > > -- > Casey Carter > Casey@Carter.net > ccarter@uiuc.edu > AIM: cartec69 > > > > _________________________________________________ Carlos Miguel Tavares de Araújo Cesariny Calafate Becário de la Universidad Politécnica de Valencia e-mail: calafate@disca.upv.es http://reptar.grc.upv.es/~calafate/ Tel: +34 963879703 ext. 77977 _________________________________________________ \\\\\\\"In an open world without walls and fences who needs Windows and Gates?\\\\\\\" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 3 21:29:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27512 for ; Mon, 3 Feb 2003 21:29:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h142YwG10602 for manet-archive@odin.ietf.org; Mon, 3 Feb 2003 21:34:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h142YwJ10599 for ; Mon, 3 Feb 2003 21:34:58 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27508 for ; Mon, 3 Feb 2003 21:29:11 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h142JFJ10126; Mon, 3 Feb 2003 21:19:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h142EwJ10033 for ; Mon, 3 Feb 2003 21:14:58 -0500 Received: from web40802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA27332 for ; Mon, 3 Feb 2003 21:09:12 -0500 (EST) Message-ID: <20030204021248.37560.qmail@web40802.mail.yahoo.com> Received: from [137.132.3.11] by web40802.mail.yahoo.com via HTTP; Mon, 03 Feb 2003 18:12:48 PST Date: Mon, 3 Feb 2003 18:12:48 -0800 (PST) From: Alvin Valera Subject: Re: [manet] Error simulating with AODV, DSR and TORA To: Casey Carter , calafate@disca.upv.es Cc: manet@ietf.org, ns-users@isi.edu In-Reply-To: <3E3E9082.7060608@cs.uiuc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Casey & Carlos Miguel, I tried Carlos Miguel's test scenarios but didn't encounter the problem of long link layer detection delay. When I received this e-mail, it became apparent that in my version of ns-2 (ns-2.1b8 June 6, 2001 release), the line ssrc_ = 0; is _NOT_ commented! That's why I couldn't duplicate Carlos Miguel's results! I find this odd. Who commented out that line in the succeeding versions and for what reason? Best regards, Alvin --- Casey Carter wrote: > Analysis of the trace file (with mac trace on) > reveals that this problem > is due to a bug in the 802.11 mac implementation. > 802.11 tries to send > an RTS several times (7 times in ns2) before > reporting failure. In the > ns2 mac, the retry counter is reset when the mac > successsfully sends or > _receives_ a packet. As long as node 1 in your > scenario keeps receiving > packets from node 0, before it can reach seven > retries, it will not > report failure. My trace file shows that node 1 > retries this particular > RTS about 650 times between 25 and 33.13 seconds. > > The particular culprit is in void > MAC802_11::recvDATA(Packet*); the > conditional branch that cleans up CTS packets after > successful reception > resets ssrc_, the RTS retry counter. Anybody know > why? Commenting out > the line that reads > > ssrc_ = 0; > > forces the proper behavior. > > calafate@disca.upv.es wrote: > > >Hi, > > > >I have sent a possible bug report to the NS mailing > list, but since no one was > >able to give me a reply, perhaps someone in this > mailing list is interested. > > > >Results of dozens of simulations using AODV, DSR > and TORA in ns2.1b9a (2.1b8 > >too) show that these protocols do not behave > correctly when there are 802.11 > >broken links. > > > >When looking at the overall results of simulations > with many nodes, the effect I > >describe is not evident. It is necessary to look at > a single flow to see that > >nodes fail to quickly detect broken links, making > the re-routing process last > >too long. This effect does not exist when using > other protocols like OLSR or > >Hello-driven AODV since they do not use link-layer > info. > > > >The files I attach show this problem clearly in a > very simple scenario > > > >Please help! > > > >Best regards, > > > >_________________________________________________ > >Carlos Miguel Tavares de Araújo Cesariny Calafate > >Polytechnic University of Valencia > >e-mail: calafate@disca.upv.es > >http://reptar.grc.upv.es/~calafate/ > >Tel: +34 963879703 ext. 77977 > >_________________________________________________ > > > > > > > -- > Casey Carter > Casey@Carter.net > ccarter@uiuc.edu > AIM: cartec69 > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 00:20:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00710 for ; Tue, 4 Feb 2003 00:20:54 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h145QD819373 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 00:26:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h145QDJ19370 for ; Tue, 4 Feb 2003 00:26:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00671 for ; Tue, 4 Feb 2003 00:20:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1457vJ18588; Tue, 4 Feb 2003 00:07:57 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1455IJ17891 for ; Tue, 4 Feb 2003 00:05:18 -0500 Received: from exstudent9.city.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00113 for ; Mon, 3 Feb 2003 23:59:27 -0500 (EST) Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59) id ; Tue, 4 Feb 2003 15:31:32 +1030 Message-ID: From: "Liaw, Yong Shyang - LIAYS001" To: manet@ietf.org Subject: [manet] delay in sending the next packet in DSR Date: Tue, 4 Feb 2003 15:34:02 +1030 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I have a question regarding DSR & would appreciate if any one can help. In DSR, when sending data packet from the send queue, shall you wait for (delay*no_hop) before sending the next data packet? where delay is the time you wait for a reply from 1 hop away (i.e. 30ms), no_hop is the number of hops I find the Opnet's DSR model implements the above, but I could not find in the DSR Internet-draft that said this for data packet (though there is some random delay for sending reply packets). In this a bug? I would appreciate if you can help me. Thank you. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 02:58:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13388 for ; Tue, 4 Feb 2003 02:58:31 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1483rE06120 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 03:03:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1483rJ06117 for ; Tue, 4 Feb 2003 03:03:53 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13360 for ; Tue, 4 Feb 2003 02:57:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h147lUJ05461; Tue, 4 Feb 2003 02:47:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h147iKJ05342 for ; Tue, 4 Feb 2003 02:44:20 -0500 Received: from mail.vnmails.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA13094 for ; Tue, 4 Feb 2003 02:38:25 -0500 (EST) Message-Id: <200302040738.CAA13094@ietf.org> Received: from localhost ([127.0.0.1]) by mail.vnmails.com (Merak 5.5.7) with SMTP id HRA73987 for ; Tue, 04 Feb 2003 02:42:01 -0500 Date: Tue, 04 Feb 2003 02:42:01 -0500 From: Imran Alvi To: "manet@ietf.org" X-Mailer: IceWarp Web Mail 3.5.1 X-Originating-IP: 203.170.74.177 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Re: manet digest, Vol 1 #325 - 8 msgs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I have joined group recently I was studying about protocols which have less overhead and better QoS performance over wireless LAN, can ATM (on MAC Layer) fullfill the requiremnts of QoS in MANETS?. Regards Imran Alvi > 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-admin@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of manet digest..." > > > Today's Topics: > > 1. RE: my doubts about QoS in ad hoc networks (Scott Corson) > 2. RE: my doubts about QoS in ad hoc networks (Shaiful) > 3. RE: my doubts about QoS in ad hoc networks (Xiaoning He) > 4. RE: my doubts about QoS in ad hoc networks (Xiaoning He) > 5. Buffer size in Wireless LAN (Liaw, Yong Shyang - LIAYS001) > 6. Error simulating with AODV, DSR and TORA (calafate@disca.upv.es) > 7. Re: Error simulating with AODV, DSR and TORA (Alvin Valera) > 8. Re: Error simulating with AODV, DSR and TORA (calafate@disca.upv.es> ) > > --__--__-- > > Message: 1 > From: Scott Corson > To: "'Manish Karir'" , > "'Liaw, Yong Shyang - LIAYS001'" > > Cc: "'manet@ietf.org'" > Subject: RE: [manet] my doubts about QoS in ad hoc networks > Date: Thu, 30 Jan 2003 14:50:38 -0500 > > > > > If some one has good ideas on how to do this study or has done this > > study, please enlighten the rest of us. > > I have some ideas... See below. > > > Perhaps one of the tasks for the irtf might be to publish a > > common set > > of metrics that should be presented for every new protocol. > > It is not > > sufficient to simply present a protocol and describe how it works. > > There should be a checklist that evey proposer of a new > > protocol should > > have to fulfill before submitting their work. > > One of the near-term goals of the IRTF group will be to specify just what> it > is we are looking for in a protocol, and how its performance should be > quantified. > > > > > I know there is some work on common metrics, for example > > control packet > > overhead seems to have emerged as a "must have" metric in any study. > > This is probably a good metric, but once again, total meaningless, > > unless put in the perspective of mobility. the actual metric > > should be: > > "control overhead given that our scenario is xxxxx on the > > mobility scale" > > To study a protocol, a set of protocol-independent "black box" criteria a> re > necessary. For example, I don't care what the protocol is, but I do care > how my data traffic is delivered (xput, latency, possibly other metrics). > At this level of analysis, you don't care *how* a protocol does what it > does. You only measure *what* is does; i.e. the effectiveness of data > routing based on some set of criteria. These need to be defined, along w> ith > test cases, etc. > > Beyond that, one can delve into various levels of "white box" testing on > a > protocol class or individual protocol basis. For example, certain > performance criteria may be valid for "proactive" protocols (e.g. HELLO > protocol overhead), but not for reactive and vice versa. Other criteria > may > only apply to a given protocol. > > I think control packet overhead as a metric in isolation is relatively > useless. It says little about the effectiveness of routing (the ultimate > black box measure). It is meaningful only upon close inspection of what > is > happening with a given protocol, to understand its inner workings, to > improve it, etc. > > Once we nail down the set of this year's mtg dates, I'll post the IRTF > webpage, the mailing list and a lot of this kind of discussion is welcome > there. > > -Scott > > --__--__-- > > Message: 2 > Date: Thu, 30 Jan 2003 16:29:30 -0800 (PST) > From: Shaiful > To: manet@ietf.org > Cc: xiaoning@docomolabs-usa.com > Subject: [manet] RE: my doubts about QoS in ad hoc networks > > Hi, > > Forgive me for my ignorance of 802.16. But do you > have any support for your statement that 802.16 works > much better than 802.11 for point-to-point connection? > This is just like saying PPP is better than ethernet > over cross-cable. Or TCP/IP is worst than specialised > protocol for intranet communication. It just doesn't > make sense to me. Can you enlighten us about this > matter. > > Thanks, > > Regards, > Shaiful > > xiaoning wrote: > > For me, ad-hoc is only a term used to emphasize > infrastructureless network. It is independent of > moving speed. To one extreme, if all nodes are fixed, > I > didn't see why QoS can not be provided. 802 WLAN may > not work, but point-to-point wireless such as 802.16 > may work very well. To another extreme, if all nodes > are moving as fast as they want, that requires further > study and I think that's the case implied in this > mailing list and in your question. Even in your > scenario, how you place the nodes, what kind of > interference exists around you will definitely affect > your result. Furthermore, besides the military usage > and emergence usage, there are still > many other scenarios which ad-hoc network can be used. > Under those scenarios, 802.11 WLAN is not the best > choice. > > In short, I think QoS for ad-hoc network is something > important in the future. But it heavily depends on the > assumptions and scenarios. > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > --__--__-- > > Message: 3 > From: "Xiaoning He" > To: "'Shaiful'" , > Date: Thu, 30 Jan 2003 16:32:30 -0800 > Subject: [manet] RE: my doubts about QoS in ad hoc networks > > I am sorry I didn't make my comment clear enough. My point is that the > test results are technology and network setup specific. > > In general, I believe the QoS is something we have to do for the ad-hoc. > > Xiaoning He, Ph.D > Research Engineer > > NTT-DoCoMo USA Labs > 181 Metro Drive, Suite 300 > San Jose, CA 95110 > > Email: xiaoning@docomolabs-usa.com > Phone: +1 (408) 451-4737 > Fax: +1 (408) 573-1090 > > > -----Original Message----- > From: Shaiful [mailto:shaifuljahari@yahoo.com] > Sent: Thursday, January 30, 2003 4:30 PM > To: manet@ietf.org > Cc: xiaoning@docomolabs-usa.com > Subject: RE: my doubts about QoS in ad hoc networks > > Hi, > > Forgive me for my ignorance of 802.16. But do you > have any support for your statement that 802.16 works > much better than 802.11 for point-to-point connection? > This is just like saying PPP is better than ethernet > over cross-cable. Or TCP/IP is worst than specialised > protocol for intranet communication. It just doesn't > make sense to me. Can you enlighten us about this > matter. > > Thanks, > > Regards, > Shaiful > > xiaoning wrote: > > For me, ad-hoc is only a term used to emphasize > infrastructureless network. It is independent of > moving speed. To one extreme, if all nodes are fixed, > I > didn't see why QoS can not be provided. 802 WLAN may > not work, but point-to-point wireless such as 802.16 > may work very well. To another extreme, if all nodes > are moving as fast as they want, that requires further > study and I think that's the case implied in this > mailing list and in your question. Even in your > scenario, how you place the nodes, what kind of > interference exists around you will definitely affect > your result. Furthermore, besides the military usage > and emergence usage, there are still > many other scenarios which ad-hoc network can be used. > Under those scenarios, 802.11 WLAN is not the best > choice. > > In short, I think QoS for ad-hoc network is something > important in the future. But it heavily depends on the > assumptions and scenarios. > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > > > > --__--__-- > > Message: 4 > From: "Xiaoning He" > To: "'Shaiful'" , > Date: Thu, 30 Jan 2003 16:33:42 -0800 > Subject: [manet] RE: my doubts about QoS in ad hoc networks > > That's also the why I use "May" in my previous email. > > Xiaoning He, Ph.D > Research Engineer > > NTT-DoCoMo USA Labs > 181 Metro Drive, Suite 300 > San Jose, CA 95110 > > Email: xiaoning@docomolabs-usa.com > Phone: +1 (408) 451-4737 > Fax: +1 (408) 573-1090 > > > -----Original Message----- > From: Shaiful [mailto:shaifuljahari@yahoo.com] > Sent: Thursday, January 30, 2003 4:30 PM > To: manet@ietf.org > Cc: xiaoning@docomolabs-usa.com > Subject: RE: my doubts about QoS in ad hoc networks > > Hi, > > Forgive me for my ignorance of 802.16. But do you > have any support for your statement that 802.16 works > much better than 802.11 for point-to-point connection? > This is just like saying PPP is better than ethernet > over cross-cable. Or TCP/IP is worst than specialised > protocol for intranet communication. It just doesn't > make sense to me. Can you enlighten us about this > matter. > > Thanks, > > Regards, > Shaiful > > xiaoning wrote: > > For me, ad-hoc is only a term used to emphasize > infrastructureless network. It is independent of > moving speed. To one extreme, if all nodes are fixed, > I > didn't see why QoS can not be provided. 802 WLAN may > not work, but point-to-point wireless such as 802.16 > may work very well. To another extreme, if all nodes > are moving as fast as they want, that requires further > study and I think that's the case implied in this > mailing list and in your question. Even in your > scenario, how you place the nodes, what kind of > interference exists around you will definitely affect > your result. Furthermore, besides the military usage > and emergence usage, there are still > many other scenarios which ad-hoc network can be used. > Under those scenarios, 802.11 WLAN is not the best > choice. > > In short, I think QoS for ad-hoc network is something > important in the future. But it heavily depends on the > assumptions and scenarios. > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > > > > --__--__-- > > Message: 5 > From: "Liaw, Yong Shyang - LIAYS001" > To: manet@ietf.org > Subject: [manet] Buffer size in Wireless LAN > Date: Fri, 31 Jan 2003 17:08:46 +1030 > > Hi, > > What shall be the buffer size for wireless LAN (802.11) Mac layer? I have> seen > that it has been set to 4MByte in the DSR model in Opnet. Is this a reaso> nable > value (in WLAN network card)? > > Thank in advance. > > --__--__-- > > Message: 6 > From: calafate@disca.upv.es > To: manet@ietf.org > Date: Fri, 31 Jan 2003 11:36:08 +0100 (CET) > Subject: [manet] Error simulating with AODV, DSR and TORA > > This message is in MIME format. > > ---MOQ1044009368649427ca7e46218a0bc9bff12af99112 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 8bit > > Hi, > > I have sent a possible bug report to the NS mailing list, but since no on> e was > able to give me a reply, perhaps someone in this mailing list is interest> ed. > > Results of dozens of simulations using AODV, DSR and TORA in ns2.1b9a (2.> 1b8 > too) show that these protocols do not behave correctly when there are 802> .11 > broken links. > > When looking at the overall results of simulations with many nodes, the e> ffect I > describe is not evident. It is necessary to look at a single flow to see > that > nodes fail to quickly detect broken links, making the re-routing process > last > too long. This effect does not exist when using other protocols like OLSR> or > Hello-driven AODV since they do not use link-layer info. > > The files I attach show this problem clearly in a very simple scenario > > Please help! > > Best regards, > > _________________________________________________ > Carlos Miguel Tavares de Araújo Cesariny Calafate > Polytechnic University of Valencia > e-mail: calafate@disca.upv.es > http://reptar.grc.upv.es/~calafate/ > Tel: +34 963879703 ext. 77977 > _________________________________________________ > > ---MOQ1044009368649427ca7e46218a0bc9bff12af99112 > Content-Type: application/x-tcl; name="testlimit.tcl"; name="testlimi> t.tcl" > Content-Disposition: inline; filename="testlimit.tcl" > Content-Transfer-Encoding: base64 > > > CgojID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09P > T09PT09PT09PT09PT09PT09PT0KIyBEZWZpbmUgb3B0aW9ucwojID09PT09PT09PT09PT09PT > 09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0 > KCnNldCB2YWwoY2hhbikgICAgICAgQ2hhbm5lbC9XaXJlbGVzc0NoYW5uZWwKc2V0IHZhbChw > cm9wKSAgICAgICBQcm9wYWdhdGlvbi9Ud29SYXlHcm91bmQKc2V0IHZhbChuZXRpZikgICAgI > CBQaHkvV2lyZWxlc3NQaHkKc2V0IHZhbChtYWMpICAgICAgICBNYWMvODAyXzExCnNldCB2YW > woaWZxKSAgICAgICAgUXVldWUvRHJvcFRhaWwvUHJpUXVldWUKc2V0IHZhbChsbCkgICAgICA > gICBMTApzZXQgdmFsKGFudCkgICAgICAgIEFudGVubmEvT21uaUFudGVubmEKc2V0IHZhbCh4 > KSAgICAgICAgICAgICAgMTUwMCAgICAgICAgICAgIDsjIFggZGltZW5zaW9uIG9mIHRoZSB0b > 3BvZ3JhcGh5CnNldCB2YWwoeSkgICAgICAgICAgICAgIDE1MDAgICAgICAgICAgICA7IyBZIG > RpbWVuc2lvbiBvZiB0aGUgdG9wb2dyYXBoeQpzZXQgdmFsKGlmcWxlbikgICAgICAgICA1MCA > gICAgICAgICAgICA7IyBtYXggcGFja2V0IGluIGlmcQpzZXQgdmFsKHNlZWQpICAgICAgICAg > ICAxLjAKc2V0IHZhbChhZGhvY1JvdXRpbmcpICAgQU9EVgpzZXQgdmFsKG5uKSAgICAgICAgI > CAgICA2ICAgICAgICAgICAgIDsjIGhvdyBtYW55IG5vZGVzIGFyZSBzaW11bGF0ZWQgCnNldC > B2YWwoY3ApICAgICAgICAgICAgICJjYnItbjQ4LXMxLW00OC1yNS4wIiAgICAgIDsjcGFkcm9 > uIGRlIGNvbmV4aW9uZXMKc2V0IHZhbChzYykgICAgICAgICAgICAgInNjZW4tbGltaXQyIiAg > ICAgOyAjZXNjZW5hcmlvIGRlIHRyYWZpY28gCnNldCB2YWwoc3RvcCkgICAgICAgICAgIDUwL > jAgICAgICAgICAgICAgOyMgc2ltdWxhdGlvbiB0aW1lCnNldCB2YWwodHJmaWxlKSAgICAgIC > AgIG91dC50cgpzZXQgdmFsKG5hbWZpbGUpICAgICAgICBvdXQubmFtCnNldCB2YWwocmFuZG9 > tX21vYmlsaXR5KSAgIEZBTFNFCgojID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 > PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQojIE1haW4gUHJvZ3JhbQojI > D09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT > 09PT09PT09PT09PT09PT0KCiMKIyBJbml0aWFsaXplIEdsb2JhbCBWYXJpYWJsZXMKIwoKIyB > zZXQgcmFuZG9tIG51bWJlciBnZW5lcmF0b3IgCm5zLXJhbmRvbSAwCgojdXNpbmc6IE1hYyBz > ZXQgYmFuZHdpZHRoXyAxMU1iCgojIGNyZWF0ZSBzaW11bGF0b3IgaW5zdGFuY2UKCnNldCBuc > 18JCVtuZXcgU2ltdWxhdG9yXQoKI3RyYWNlIGZpbGUgZm9ybWF0CgokbnNfIHVzZS1uZXd0cm > FjZQoKCiMgc2V0dXAgdG9wb2dyYXBoeSBvYmplY3QKCnNldCB0b3BvCVtuZXcgVG9wb2dyYXB > oeV0KCiMgY3JlYXRlIHRyYWNlIG9iamVjdCBmb3IgbnMgYW5kIG5hbQoKc2V0IHRyYWNlZmQJ > W29wZW4gJHZhbCh0cmZpbGUpIHddCnNldCBuYW10cmFjZSAgICBbb3BlbiAkdmFsKG5hbWZpb > GUpIHddCgokbnNfIHRyYWNlLWFsbCAkdHJhY2VmZAokbnNfIG5hbXRyYWNlLWFsbC13aXJlbG > VzcyAkbmFtdHJhY2UgJHZhbCh4KSAkdmFsKHkpCgojIGRlZmluZSB0b3BvbG9neQokdG9wbyB > sb2FkX2ZsYXRncmlkICR2YWwoeCkgJHZhbCh5KQoKCiMKIyBDcmVhdGUgR29kCiMKc2V0IGdv > ZF8gW2NyZWF0ZS1nb2QgJHZhbChubildCgojCiMgZGVmaW5lIGhvdyBub2RlIHNob3VsZCBiZ > SBjcmVhdGVkCiMKCiNnbG9iYWwgbm9kZSBzZXR0aW5nCgokbnNfIG5vZGUtY29uZmlnIC1hZG > hvY1JvdXRpbmcgJHZhbChhZGhvY1JvdXRpbmcpIFwKICAgICAgICAgICAgICAgICAtbGxUeXB > lICR2YWwobGwpIFwKICAgICAgICAgICAgICAgICAtbWFjVHlwZSAkdmFsKG1hYykgXAogICAg > ICAgICAgICAgICAgIC1pZnFUeXBlICR2YWwoaWZxKSBcCiAgICAgICAgICAgICAgICAgLWlmc > UxlbiAkdmFsKGlmcWxlbikgXAogICAgICAgICAgICAgICAgIC1hbnRUeXBlICR2YWwoYW50KS > BcCiAgICAgICAgICAgICAgICAgLXByb3BUeXBlICR2YWwocHJvcCkgXAogICAgICAgICAgICA > gICAgIC1waHlUeXBlICR2YWwobmV0aWYpIFwKICAgICAgICAgICAgICAgICAtY2hhbm5lbFR5 > cGUgJHZhbChjaGFuKSBcCgkJIC10b3BvSW5zdGFuY2UgJHRvcG8gXAoJCSAtYWdlbnRUcmFjZ > SBPTiBcCiAgICAgICAgICAgICAgICAgLXJvdXRlclRyYWNlIE9OIFwKICAgICAgICAgICAgIC > AgICAtbWFjVHJhY2UgT0ZGIFwKICAgICAgICAgICAgICAgICAtbW92ZW1lbnRUcmFjZSAgT0Z > GCgoKIwojICBDcmVhdGUgdGhlIHNwZWNpZmllZCBudW1iZXIgb2Ygbm9kZXMgWyR2YWwobm4p > XSBhbmQgImF0dGFjaCIgdGhlbQojICB0byB0aGUgY2hhbm5lbC4gCgpmb3Ige3NldCBpIDB9I > HskaSA8ICR2YWwobm4pIH0ge2luY3IgaX0gewoJc2V0IG5vZGVfKCRpKSBbJG5zXyBub2RlXQ > p9CgojCiMgRGVmaW5lIGFnZW50IGNvbm5lY3Rpdml0eQojCgpwdXRzICJMb2FkaW5nIGNvbm5 > lY3Rpb24gcGF0dGVybi4uLiIKI3NvdXJjZSAkdmFsKGNwKQoKIyBEZWZpbmUgdGVzdCBjb25u > ZWN0aW9ucwoKCnNldCB1ZHBfKDApIFtuZXcgQWdlbnQvVURQXQokbnNfIGF0dGFjaC1hZ2Vud > CAkbm9kZV8oMCkgJHVkcF8oMCkKc2V0IG51bGxfKDApIFtuZXcgQWdlbnQvTnVsbF0KJG5zXy > BhdHRhY2gtYWdlbnQgJG5vZGVfKDMpICRudWxsXygwKQpzZXQgY2JyXygwKSBbbmV3IEFwcGx > pY2F0aW9uL1RyYWZmaWMvQ0JSXQokY2JyXygwKSBzZXQgcGFja2V0U2l6ZV8gMTI4CiRjYnJf > KDApIHNldCBpbnRlcnZhbF8gMC4wMQokY2JyXygwKSBzZXQgcmFuZG9tXyAwCiRjYnJfKDApI > GF0dGFjaC1hZ2VudCAkdWRwXygwKQokbnNfIGNvbm5lY3QgJHVkcF8oMCkgJG51bGxfKDApCi > Ruc18gYXQgMjAuMCAiJGNicl8oMCkgc3RhcnQiCgoKCiMgCiMgRGVmaW5lIG5vZGUgbW92ZW1 > lbnQgbW9kZWwKIwoKaWYgeyR2YWwocmFuZG9tX21vYmlsaXR5KX0gewogICAgcHV0cyAiUmFu > ZG9tIG1vYmlsaXR5IG9uIgogICAgCiAgICAjU3RhcnQgUmFuZG9tIG1vdGlvbgogICAgZm9yI > HtzZXQgaSAwfSB7JGkgPCAkdmFsKG5uKSB9IHtpbmNyIGl9IHsKCSRub2RlXygkaSkgcmFuZG > 9tLW1vdGlvbiAxCQk7IyBlbmFibGUgcmFuZG9tIG1vdGlvbgoJJG5vZGVfKCRpKSBzdGFydAo > gICAgfQoKfSBlbHNlIHsKICAgICMgCiAgICAjIERlZmluZSB0cmFmZmljIG1vZGVsCiAgICAj > CiAgICBwdXRzICJSYW5kb20gbW9iaWxpdHkgb2ZmOiBMb2FkaW5nIHNjZW5hcmlvIGZpbGUuL > i4iCiAgICBzb3VyY2UgJHZhbChzYykKfQoKCgoKIyBEZWZpbmUgbm9kZSBpbml0aWFsIHBvc2 > l0aW9uIGluIG5hbQoKZm9yIHtzZXQgaSAwfSB7JGkgPCAkdmFsKG5uKX0ge2luY3IgaX0gewo > KICAgICMgMjAgZGVmaW5lcyB0aGUgbm9kZSBzaXplIGluIG5hbSwgbXVzdCBhZGp1c3QgaXQg > YWNjb3JkaW5nIHRvIHlvdXIgc2NlbmFyaW8KICAgICMgVGhlIGZ1bmN0aW9uIG11c3QgYmUgY > 2FsbGVkIGFmdGVyIG1vYmlsaXR5IG1vZGVsIGlzIGRlZmluZWQKICAgIAogICAgJG5zXyBpbm > l0aWFsX25vZGVfcG9zICRub2RlXygkaSkgMjAKfQoKCiMKIyBUZWxsIG5vZGVzIHdoZW4gdGh > lIHNpbXVsYXRpb24gZW5kcwojCmZvciB7c2V0IGkgMH0geyRpIDwgJHZhbChubikgfSB7aW5j > ciBpfSB7CiAgICAkbnNfIGF0ICR2YWwoc3RvcCkuMCAiJG5vZGVfKCRpKSByZXNldCI7Cn0KC > iRuc18gYXQgICR2YWwoc3RvcCkuMDAwMiAicHV0cyBcIk5TIEVYSVRJTkcuLi5cIiA7ICRuc1 > 8gaGFsdCIKCiNwdXRzICR0cmFjZWZkICJNIDAuMCBubiAkdmFsKG5uKSB4ICR2YWwoeCkgeSA > kdmFsKHkpIHJwICR2YWwoYWRob2NSb3V0aW5nKSIKI3B1dHMgJHRyYWNlZmQgIk0gMC4wIHNj > ICR2YWwoc2MpIGNwICR2YWwoY3ApIHNlZWQgJHZhbChzZWVkKSIKI3B1dHMgJHRyYWNlZmQgI > k0gMC4wIHByb3AgJHZhbChwcm9wKSBhbnQgJHZhbChhbnQpIgoKcHV0cyAiU3RhcnRpbmcgU2 > ltdWxhdGlvbi4uLiIKJG5zXyBydW4KCgoKCgo= > > > ---MOQ1044009368649427ca7e46218a0bc9bff12af99112 > Content-Type: application/octet-stream; name="scen-limit2"; name="sce> n-limit2" > Content-Disposition: inline; filename="scen-limit2" > Content-Transfer-Encoding: base64 > > > CiRub2RlXygwKSBzZXQgWF8gMTAwLjAKJG5vZGVfKDApIHNldCBZXyAyNTAuMAokbm9kZV8oM> Ckg > c2V0IFpfIDAuMDAwMDAwMDAwMDAwCiRub2RlXygxKSBzZXQgWF8gMjUwLjAKJG5vZGVfKDEpI> HNl > dCBZXyA0NTAuMAokbm9kZV8oMSkgc2V0IFpfIDAuMDAwMDAwMDAwMDAwCiRub2RlXygyKSBzZ> XQg > WF8gNTAwLjAKJG5vZGVfKDIpIHNldCBZXyA0NTAuMAokbm9kZV8oMikgc2V0IFpfIDAuMDAwM> DAw > MDAwMDAwCiRub2RlXygzKSBzZXQgWF8gNjUwLjAKJG5vZGVfKDMpIHNldCBZXyAyNTAuMAokb> m9k > ZV8oMykgc2V0IFpfIDAuMDAwMDAwMDAwMDAwCiRub2RlXyg0KSBzZXQgWF8gMjQ5LjAKJG5vZ> GVf > KDQpIHNldCBZXyA0NS4wCiRub2RlXyg0KSBzZXQgWl8gMC4wMDAwMDAwMDAwMDAKJG5vZGVfK> DUp > IHNldCBYXyA1MDAuMAokbm9kZV8oNSkgc2V0IFlfIDUwLjAKJG5vZGVfKDUpIHNldCBaXyAwL> jAw > MDAwMDAwMDAwMAoKCiMkbnNfIGF0IDI0LjUwMDAwMDAwMDAwMCAiJG5vZGVfKDIpIHNldGRlc> 3Qg > MjUwLjAgNTAuMCAxMDAuMCIKIyRuc18gYXQgMjUuMDAwMDAwMDAwMDAwICIkbm9kZV8oMSkgc> 2V0 > ZGVzdCAyNDkuMCAxNDk5LjAgMTAwLjAiCgokbnNfIGF0IDI0LjAwMDAwMDAwMDAwMCAiJG5vZ> GVf > KDQpIHNldGRlc3QgMjUwLjAgNTAuMCAxMDAwLjAiCiRuc18gYXQgMjUuMDAwMDAwMDAwMDAwI> CIk > bm9kZV8oMikgc2V0ZGVzdCAxNDk5LjAgMTQ5OS4wIDEwMDAuMCIK > > > ---MOQ1044009368649427ca7e46218a0bc9bff12af99112-- > > > --__--__-- > > Message: 7 > Date: Fri, 31 Jan 2003 04:39:40 -0800 (PST) > From: Alvin Valera > Subject: Re: [manet] Error simulating with AODV, DSR and TORA > To: calafate@disca.upv.es, manet@ietf.org > > Hi Carlos Miguel, > > I performed many simulations in ns-2.1b8 specifically > on the reaction of routing protocols to link failures. > I haven't encountered your problem, though. > > Could it be that the delay in detecting a link failure > is due to link layer retransmissions? In 802.11, as > far as ns-2.1b8 is concerned, a sender retries several > times (I could not remember the exact value) before > informing the routing protocol that a data packet is > undeliverable? > > Another possible reason is congestion. In my studies, > I encountered many instances where 802.11 reports a > link layer failure even though the receiver is within > range. This is due to the fact that in highly > congested environment, the MAC of the sender may fail > to acquire the channel or complete the > RTS-CTS-DATA-ACK. > > > Best regards, > Alvin > > --- calafate@disca.upv.es wrote: > > Hi, > > > > I have sent a possible bug report to the NS mailing > > list, but since no one was > > able to give me a reply, perhaps someone in this > > mailing list is interested. > > > > Results of dozens of simulations using AODV, DSR and > > TORA in ns2.1b9a (2.1b8 > > too) show that these protocols do not behave > > correctly when there are 802.11 > > broken links. > > > > When looking at the overall results of simulations > > with many nodes, the effect I > > describe is not evident. It is necessary to look at > > a single flow to see that > > nodes fail to quickly detect broken links, making > > the re-routing process last > > too long. This effect does not exist when using > > other protocols like OLSR or > > Hello-driven AODV since they do not use link-layer > > info. > > > > The files I attach show this problem clearly in a > > very simple scenario > > > > Please help! > > > > Best regards, > > > > _________________________________________________ > > Carlos Miguel Tavares de Araújo Cesariny Calafate > > Polytechnic University of Valencia > > e-mail: calafate@disca.upv.es > > http://reptar.grc.upv.es/~calafate/ > > Tel: +34 963879703 ext. 77977 > > _________________________________________________ > > > > > ATTACHMENT part 2 application/x-tcl > name=testlimit.tcl; name=testlimit.tcl > > > > ATTACHMENT part 3 application/octet-stream > name=scen-limit2; name=scen-limit2 > > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > --__--__-- > > Message: 8 > From: calafate@disca.upv.es > To: Alvin Valera > Subject: Re: [manet] Error simulating with AODV, DSR and TORA > Date: Fri, 31 Jan 2003 16:08:54 +0100 (CET) > Cc: manet@ietf.org > > Hi Alvin, > > Thank you for your comments on this subject. > > My opinion is that, since I created a very simple scenario with just 6 on> es and > 1 traffic flow, we can't blame collisions for the behaviour observed. Als> o, it's > true that the sender retries several times (I think 4 times), but I guess> that > 10 or 20 seconds to detect a broken link is too much, don't you? If link-> level > aware protocols were supposed to behave that bad, we would conform to jus> t > sending "Hellos"! > > It's curious to notice that the problems are not the same for all: the wo> rst > performance can be seen with DSR but TORA suddenly stops sending packets > and > everything is still! > > Please comment the "ns-random 0" line and you'll see exactly what I see. > > Best regards, > > Carlos > > > > Mensaje citado por: Alvin Valera : > > > Hi Carlos Miguel, > > > > I performed many simulations in ns-2.1b8 specifically > > on the reaction of routing protocols to link failures. > > I haven't encountered your problem, though. > > > > Could it be that the delay in detecting a link failure > > is due to link layer retransmissions? In 802.11, as > > far as ns-2.1b8 is concerned, a sender retries several > > times (I could not remember the exact value) before > > informing the routing protocol that a data packet is > > undeliverable? > > > > Another possible reason is congestion. In my studies, > > I encountered many instances where 802.11 reports a > > link layer failure even though the receiver is within > > range. This is due to the fact that in highly > > congested environment, the MAC of the sender may fail > > to acquire the channel or complete the > > RTS-CTS-DATA-ACK. > > > > > > Best regards, > > Alvin > > > > > _________________________________________________ > Carlos Miguel Tavares de Araújo Cesariny Calafate > Becário de la Universidad Politécnica de Valencia > e-mail: calafate@disca.upv.es > http://reptar.grc.upv.es/~calafate/ > Tel: +34 963879703 ext. 77977 > _________________________________________________ > \\\\\\\"In an open world without walls and fences who needs Windows and > Gates?\\\\\\\" > > > --__--__-- > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > End of manet Digest _______________________________________________________ Buy phone cards and save at http://www.vnphonecards.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 06:22:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16200 for ; Tue, 4 Feb 2003 06:22:25 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14BRqi17571 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 06:27:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BRqJ17568 for ; Tue, 4 Feb 2003 06:27:52 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16167 for ; Tue, 4 Feb 2003 06:21:53 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14B9NJ16772; Tue, 4 Feb 2003 06:09:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14B2mJ15969 for ; Tue, 4 Feb 2003 06:02:48 -0500 Received: from anyida.tts.lth.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15699 for ; Tue, 4 Feb 2003 05:56:49 -0500 (EST) Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id MAA03033; Tue, 4 Feb 2003 12:00:34 +0100 (MET) Message-ID: <3E3F9C97.4050301@telecom.lth.se> Date: Tue, 04 Feb 2003 11:57:27 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Alvin Valera CC: Casey Carter , calafate@disca.upv.es, manet@ietf.org, ns-users@isi.edu Subject: Re: [manet] Error simulating with AODV, DSR and TORA References: <20030204021248.37560.qmail@web40802.mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------040808070309090501010106" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------040808070309090501010106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi, Just wanted to conform what Alvin says: in my version of ns-2 (ns-2.1b9a) the line ssrc_ = 0; is NOT commented - i.e. the same as Alvin says. And that's why I told Carlos that the AODV code in ns-2.1b9a should be able to detect link breaks pretty fast. Regards Ali Alvin Valera wrote: >Hi Casey & Carlos Miguel, > >I tried Carlos Miguel's test scenarios but didn't >encounter the problem of long link layer detection >delay. When I received this e-mail, it became apparent >that in my version of ns-2 (ns-2.1b8 June 6, 2001 >release), the line > > ssrc_ = 0; > >is _NOT_ commented! That's why I couldn't duplicate >Carlos Miguel's results! > >I find this odd. Who commented out that line in the >succeeding versions and for what reason? > >Best regards, >Alvin > >--- Casey Carter wrote: > >>Analysis of the trace file (with mac trace on) >>reveals that this problem >>is due to a bug in the 802.11 mac implementation. >>802.11 tries to send >>an RTS several times (7 times in ns2) before >>reporting failure. In the >>ns2 mac, the retry counter is reset when the mac >>successsfully sends or >>_receives_ a packet. As long as node 1 in your >>scenario keeps receiving >>packets from node 0, before it can reach seven >>retries, it will not >>report failure. My trace file shows that node 1 >>retries this particular >>RTS about 650 times between 25 and 33.13 seconds. >> >>The particular culprit is in void >>MAC802_11::recvDATA(Packet*); the >>conditional branch that cleans up CTS packets after >>successful reception >>resets ssrc_, the RTS retry counter. Anybody know >>why? Commenting out >>the line that reads >> >> ssrc_ = 0; >> >>forces the proper behavior. >> >>calafate@disca.upv.es wrote: >> >>>Hi, >>> >>>I have sent a possible bug report to the NS mailing >>> >>list, but since no one was >> >>>able to give me a reply, perhaps someone in this >>> >>mailing list is interested. >> >>>Results of dozens of simulations using AODV, DSR >>> >>and TORA in ns2.1b9a (2.1b8 >> >>>too) show that these protocols do not behave >>> >>correctly when there are 802.11 >> >>>broken links. >>> >>>When looking at the overall results of simulations >>> >>with many nodes, the effect I >> >>>describe is not evident. It is necessary to look at >>> >>a single flow to see that >> >>>nodes fail to quickly detect broken links, making >>> >>the re-routing process last >> >>>too long. This effect does not exist when using >>> >>other protocols like OLSR or >> >>>Hello-driven AODV since they do not use link-layer >>> >>info. >> >>>The files I attach show this problem clearly in a >>> >>very simple scenario >> >>>Please help! >>> >>>Best regards, >>> >>>_________________________________________________ >>>Carlos Miguel Tavares de Araújo Cesariny Calafate >>>Polytechnic University of Valencia >>>e-mail: calafate@disca.upv.es >>>http://reptar.grc.upv.es/~calafate/ >>>Tel: +34 963879703 ext. 77977 >>>_________________________________________________ >>> >>> >> >>-- >>Casey Carter >>Casey@Carter.net >>ccarter@uiuc.edu >>AIM: cartec69 >> >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> > > >__________________________________________________ >Do you Yahoo!? >Yahoo! Mail Plus - Powerful. Affordable. Sign up now. >http://mailplus.yahoo.com >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > --------------040808070309090501010106 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

Just wanted to conform what Alvin says: in my version of ns-2 (ns-2.1b9a) the line

    ssrc_ = 0;

is NOT commented - i.e. the same as Alvin says. And that's why I told Carlos that the AODV code in ns-2.1b9a should be able to detect link breaks pretty fast.

Regards
Ali


Alvin Valera wrote:
Hi Casey & Carlos Miguel,

I tried Carlos Miguel's test scenarios but didn't
encounter the problem of long link layer detection
delay. When I received this e-mail, it became apparent
that in my version of ns-2 (ns-2.1b8 June 6, 2001
release), the line 

    ssrc_ = 0;

is _NOT_ commented! That's why I couldn't duplicate
Carlos Miguel's results!

I find this odd. Who commented out that line in the
succeeding versions and for what reason? 

Best regards,
Alvin 

--- Casey Carter <ccarter@cs.uiuc.edu> wrote:
Analysis of the trace file (with mac trace on)
reveals that this problem 
is due to a bug in the 802.11 mac implementation. 
802.11 tries to send 
an RTS several times (7 times in ns2) before
reporting failure. In the 
ns2 mac, the retry counter is reset when the mac
successsfully sends or 
_receives_ a packet.  As long as node 1 in your
scenario keeps receiving 
packets from node 0, before it can reach seven
retries, it will not 
report failure.  My trace file shows that node 1
retries this particular 
RTS about 650 times between 25 and 33.13 seconds.

The particular culprit is in void
MAC802_11::recvDATA(Packet*); the 
conditional branch that cleans up CTS packets after
successful reception 
resets ssrc_, the RTS retry counter.  Anybody know
why? Commenting out 
the line that reads

  ssrc_ = 0;

forces the proper behavior.

calafate@disca.upv.es wrote:

Hi,

I have sent a possible bug report to the NS mailing
list, but since no one was
able to give me a reply, perhaps someone in this
mailing list is interested.
Results of dozens of simulations using AODV, DSR
and TORA in ns2.1b9a (2.1b8
too) show that these protocols do not behave
correctly when there are 802.11
broken links.

When looking at the overall results of simulations
with many nodes, the effect I
describe is not evident. It is necessary to look at
a single flow to see that  
nodes fail to quickly detect broken links, making
the re-routing process last
too long. This effect does not exist when using
other protocols like OLSR or
Hello-driven AODV since they do not use link-layer
info.
The files I attach show this problem clearly in a
very simple scenario
Please help!

Best regards, 

_________________________________________________
Carlos Miguel Tavares de Araújo Cesariny Calafate
Polytechnic University of Valencia
e-mail: calafate@disca.upv.es
http://reptar.grc.upv.es/~calafate/
Tel: +34 963879703 ext. 77977
_________________________________________________
 


-- 
Casey Carter
Casey@Carter.net
ccarter@uiuc.edu
AIM: cartec69



_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


--------------040808070309090501010106-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 06:49:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17673 for ; Tue, 4 Feb 2003 06:49:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14BtDN20023 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 06:55:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BtDJ20019 for ; Tue, 4 Feb 2003 06:55:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17646 for ; Tue, 4 Feb 2003 06:49:16 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BbdJ18724; Tue, 4 Feb 2003 06:37:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BVoJ17780 for ; Tue, 4 Feb 2003 06:31:50 -0500 Received: from diver.doc.ic.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16388 for ; Tue, 4 Feb 2003 06:25:52 -0500 (EST) Received: from kiwi.doc.ic.ac.uk ([146.169.2.59] ident=slk) by diver.doc.ic.ac.uk with esmtp (Exim 3.16 #7) id 18g1Gc-0001vh-00 for manet@ietf.org; Tue, 04 Feb 2003 11:29:30 +0000 Date: Tue, 4 Feb 2003 11:29:29 +0000 (GMT) From: Sye Loong Keoh To: manet@ietf.org In-Reply-To: <20030204074502.5360.89745.Mailman@www1.ietf.org> Message-ID: References: <20030204074502.5360.89745.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Java API for Wireless LAN 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I would like to know whether is there any Java API available to interface with the Wireless LAN 802.11 card? How about the generic connection framework (GCF) in J2ME? Can we use it to interface with the wireless LAN? Thank you. ___________________________________________________ Sye Loong Keoh Department of Computing, Imperial College London, Huxley Building, 180, Queen's Gate, London SW7 2BZ, U.K. Telephone: +44 (0) 20759 48449 Homepage: http://www.doc.ic.ac.uk/~slk "Whatever you think is right, go ahead and do it" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 10:52:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25929 for ; Tue, 4 Feb 2003 10:52:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14Fw7D03388 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 10:58:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14Fw7J03385 for ; Tue, 4 Feb 2003 10:58:07 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25896 for ; Tue, 4 Feb 2003 10:52:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14FhOJ02565; Tue, 4 Feb 2003 10:43:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14FacJ01670 for ; Tue, 4 Feb 2003 10:36:38 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25315 for ; Tue, 4 Feb 2003 10:30:35 -0500 (EST) Received: (cpmta 24720 invoked from network); 4 Feb 2003 07:34:11 -0800 Received: from 12.221.64.123 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.65) with SMTP; 4 Feb 2003 07:34:11 -0800 X-Sent: 4 Feb 2003 15:34:11 GMT Message-ID: <3E3FD48A.9020202@cs.uiuc.edu> Date: Tue, 04 Feb 2003 08:56:10 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ali Hamidian CC: Alvin Valera , calafate@disca.upv.es, manet@ietf.org, ns-users@isi.edu Subject: Re: [manet] Error simulating with AODV, DSR and TORA References: <20030204021248.37560.qmail@web40802.mail.yahoo.com> <3E3F9C97.4050301@telecom.lth.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit To clarify: I know that the line is not commented -- that is the problem. To correct the problem, the line must be removed. Consider a hypothetical example: A <====> B C A and B are within range, C is far away. B sends RTS to C, sets ssrc_ to 0. C doesn't receive. Loop: B retries RTS to C, sets ssrc_ to 1. C doesn't receive. B retries RTS to C, sets ssrc_ to 2. C doesn't receive. A sends RTS to B, sets ssrc_ to 0. B receives RTS, sends CTS to A. A receives CTS, sets ssrc_ to 0, sends DATA. // Gerrit says this is a bug also: but it's not the one I refer to. B receives DATA, sends ACK to A, sets ssrc_ to 0. // THIS is the bug: B's ssrc_ is for the B-C exchange, it is unrelated to the A-B exchange. goto Loop In this way, B can continue retransmitting RTS for the exact same packet indefinitely. That's the bug I'm talking about. Ali Hamidian wrote: > Hi, > > Just wanted to conform what Alvin says: in my version of ns-2 > (ns-2.1b9a) the line > > ssrc_ = 0; > > is NOT commented - i.e. the same as Alvin says. And that's why I told > Carlos that the AODV code in ns-2.1b9a should be able to detect link > breaks pretty fast. > > Regards > Ali > > > Alvin Valera wrote: > >>Hi Casey & Carlos Miguel, >> >>I tried Carlos Miguel's test scenarios but didn't >>encounter the problem of long link layer detection >>delay. When I received this e-mail, it became apparent >>that in my version of ns-2 (ns-2.1b8 June 6, 2001 >>release), the line >> >> ssrc_ = 0; >> >>is _NOT_ commented! That's why I couldn't duplicate >>Carlos Miguel's results! >> >>I find this odd. Who commented out that line in the >>succeeding versions and for what reason? >> >>Best regards, >>Alvin >> >>--- Casey Carter wrote: >> >> >>>Analysis of the trace file (with mac trace on) >>>reveals that this problem >>>is due to a bug in the 802.11 mac implementation. >>>802.11 tries to send >>>an RTS several times (7 times in ns2) before >>>reporting failure. In the >>>ns2 mac, the retry counter is reset when the mac >>>successsfully sends or >>>_receives_ a packet. As long as node 1 in your >>>scenario keeps receiving >>>packets from node 0, before it can reach seven >>>retries, it will not >>>report failure. My trace file shows that node 1 >>>retries this particular >>>RTS about 650 times between 25 and 33.13 seconds. >>> >>>The particular culprit is in void >>>MAC802_11::recvDATA(Packet*); the >>>conditional branch that cleans up CTS packets after >>>successful reception >>>resets ssrc_, the RTS retry counter. Anybody know >>>why? Commenting out >>>the line that reads >>> >>> ssrc_ = 0; >>> >>>forces the proper behavior. >>> >>>calafate@disca.upv.es wrote: >>> >>> >>> >>>>Hi, >>>> >>>>I have sent a possible bug report to the NS mailing >>>> >>>> >>>list, but since no one was >>> >>> >>>>able to give me a reply, perhaps someone in this >>>> >>>> >>>mailing list is interested. >>> >>> >>>>Results of dozens of simulations using AODV, DSR >>>> >>>> >>>and TORA in ns2.1b9a (2.1b8 >>> >>> >>>>too) show that these protocols do not behave >>>> >>>> >>>correctly when there are 802.11 >>> >>> >>>>broken links. >>>> >>>>When looking at the overall results of simulations >>>> >>>> >>>with many nodes, the effect I >>> >>> >>>>describe is not evident. It is necessary to look at >>>> >>>> >>>a single flow to see that >>> >>> >>>>nodes fail to quickly detect broken links, making >>>> >>>> >>>the re-routing process last >>> >>> >>>>too long. This effect does not exist when using >>>> >>>> >>>other protocols like OLSR or >>> >>> >>>>Hello-driven AODV since they do not use link-layer >>>> >>>> >>>info. >>> >>> >>>>The files I attach show this problem clearly in a >>>> >>>> >>>very simple scenario >>> >>> >>>>Please help! >>>> >>>>Best regards, >>>> >>>>_________________________________________________ >>>> >>>> >>>> -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 16:46:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05334 for ; Tue, 4 Feb 2003 16:46:45 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14LqOn26321 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 16:52:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14LqOJ26318 for ; Tue, 4 Feb 2003 16:52:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05324 for ; Tue, 4 Feb 2003 16:46:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14LXKJ24660; Tue, 4 Feb 2003 16:33:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14LOfJ24361 for ; Tue, 4 Feb 2003 16:24:41 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04629 for ; Tue, 4 Feb 2003 16:18:31 -0500 (EST) Received: (cpmta 24580 invoked from network); 4 Feb 2003 13:22:08 -0800 Received: from 12.221.64.123 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.64) with SMTP; 4 Feb 2003 13:22:08 -0800 X-Sent: 4 Feb 2003 21:22:08 GMT Message-ID: <3E4025F7.40005@cs.uiuc.edu> Date: Tue, 04 Feb 2003 14:43:35 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Liaw, Yong Shyang - LIAYS001" CC: manet@ietf.org Subject: Re: [manet] delay in sending the next packet in DSR References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit This is a standard hack for ad hoc routing simulations that avoids interaction with ARP. ARPs based on the BSD implementation have a single-packet buffer where they hold packets while performing address resolution. Additional packets that arrive replace the packet in the buffer. So, if you have a bunch of packets waiting for the route reply, and send them to the link layer all at once, ARP will drop all but the last if it does not already have an address mapping for the nexthop. The hack is to guess how long an ARP request/reply cycle takes, and delay sending packets by cycle_time * #hops. There is substantial discussion of this issue in my paper "ARP Considered Harmful: Manycast Transactions in Ad Hoc Networks" to appear in WCNC 2003 -- available at . We discuss how ARP does not seem to integrate properly into ad hoc networks, and present an alternative that places responsibility for address resolution in the routing protocol, where it can be done with zero cost. Liaw, Yong Shyang - LIAYS001 wrote: >Hi, > >I have a question regarding DSR & would appreciate if any one can help. > >In DSR, when sending data packet from the send queue, shall you wait for >(delay*no_hop) before sending the next data packet? >where delay is the time you wait for a reply from 1 hop away (i.e. 30ms), > no_hop is the number of hops > >I find the Opnet's DSR model implements the above, but I could not find in the >DSR Internet-draft that said this for data packet (though there is some random >delay for sending reply packets). In this a bug? I would appreciate if you can >help me. > >Thank you. > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 21:35:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11993 for ; Tue, 4 Feb 2003 21:35:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h152fLs10632 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 21:41:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h152fLJ10629 for ; Tue, 4 Feb 2003 21:41:21 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11939 for ; Tue, 4 Feb 2003 21:35:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h152R9J09585; Tue, 4 Feb 2003 21:27:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h152IcJ09421 for ; Tue, 4 Feb 2003 21:18:38 -0500 Received: from web40803.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA11225 for ; Tue, 4 Feb 2003 21:12:23 -0500 (EST) Message-ID: <20030205021600.46848.qmail@web40803.mail.yahoo.com> Received: from [165.21.83.197] by web40803.mail.yahoo.com via HTTP; Tue, 04 Feb 2003 18:16:00 PST Date: Tue, 4 Feb 2003 18:16:00 -0800 (PST) From: Alvin Valera Subject: Re: [manet] Error simulating with AODV, DSR and TORA To: calafate@disca.upv.es, manet@ietf.org In-Reply-To: <1044009368.3e3a519878bad@nao.disca.upv.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Carlos Miguel, The problem that you encountered seems to come from the 11Mb/s bandwidth that you used. One other reason why I couldn't duplicate your results was that I fixed my bandwidth to 2Mb/s somewhere in my scripts. I tried your scenarios but my simulations still used the 2Mb/s. The problem, as Casey have shown in the previous mails, is that a DATA reception clears the ssrc_. With 11Mb/s, it is possible to have an asynchronous DATA transmissions in between RTS. With 2Mb/s, this is not possible (at least it did not occur in any of my simulations). One way to solve your problem, without UNcommenting the line "ssrc_ = 0" is to adjust the inter-frame spacing values. Regards, Alvin --- calafate@disca.upv.es wrote: > Hi, > > I have sent a possible bug report to the NS mailing > list, but since no one was > able to give me a reply, perhaps someone in this > mailing list is interested. > > Results of dozens of simulations using AODV, DSR and > TORA in ns2.1b9a (2.1b8 > too) show that these protocols do not behave > correctly when there are 802.11 > broken links. > > When looking at the overall results of simulations > with many nodes, the effect I > describe is not evident. It is necessary to look at > a single flow to see that > nodes fail to quickly detect broken links, making > the re-routing process last > too long. This effect does not exist when using > other protocols like OLSR or > Hello-driven AODV since they do not use link-layer > info. > > The files I attach show this problem clearly in a > very simple scenario > > Please help! > > Best regards, > > _________________________________________________ > Carlos Miguel Tavares de Araújo Cesariny Calafate > Polytechnic University of Valencia > e-mail: calafate@disca.upv.es > http://reptar.grc.upv.es/~calafate/ > Tel: +34 963879703 ext. 77977 > _________________________________________________ > > ATTACHMENT part 2 application/x-tcl name=testlimit.tcl; name=testlimit.tcl > ATTACHMENT part 3 application/octet-stream name=scen-limit2; name=scen-limit2 __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 4 22:49:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14413 for ; Tue, 4 Feb 2003 22:49:02 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h153snD14130 for manet-archive@odin.ietf.org; Tue, 4 Feb 2003 22:54:49 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h153smJ14127 for ; Tue, 4 Feb 2003 22:54:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14401 for ; Tue, 4 Feb 2003 22:48:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h153eDJ13551; Tue, 4 Feb 2003 22:40:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h153X8J12732 for ; Tue, 4 Feb 2003 22:33:08 -0500 Received: from icu.ac.kr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13206 for ; Tue, 4 Feb 2003 22:26:50 -0500 (EST) Received: (from kebi@localhost) by icu.ac.kr (8.11.5/8.11.5) id h153Ta723654 for manet@ietf.org ; Wed, 5 Feb 2003 12:29:36 +0900 (KST) Date: Wed, 5 Feb 2003 12:29:36 +0900 (KST) Message-Id: <200302050329.h153Ta723654@icu.ac.kr> X-Authentication-Warning: mail.icu.ac.kr: kebi set sender to ekyulee@icu.ac.kr using -f From: "EunKyu Lee" User-Host: 129.254.180.233 Reply-To: ekyulee@icu.ac.kr In-Reply-To: ekyulee@icu.ac.kr To: "manet@ietf.org" X-Mailer: KEBI WWW-MAIL [version 1.0] X-Mail-Id: ekyulee.23642104441577665 X-Priority: 3 MIME-Version: 1.0 Content-type: multipart/alternative; boundary="kebi129.254.180.233.23642104441577347" Subject: [manet] ad hoc implementation on WinCE Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , 4YA_ 8^=CAv@T4O4Y. --kebi129.254.180.233.23642104441577347 Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit
 
I hope to test ad hoc network on WindowsCE.
Is there anyone who know papers, sources, web contact, laboratory, etc.
Of course about the implementation or simulation of ad hoc on WindowsCE.
 
Thanks in advance
 
Best Regards,
Ekyu
--kebi129.254.180.233.23642104441577347 Content-Type: text/html; charset=euc-kr Content-Transfer-Encoding: 8bit
 

I hope to test ad hoc network on WindowsCE.

Is there anyone who know papers, sources, web contact, laboratory, etc.

Of course about the implementation or simulation of ad hoc on WindowsCE.

 

Thanks in advance

 

Best Regards,

Ekyu
  --kebi129.254.180.233.23642104441577347-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 5 08:46:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24876 for ; Wed, 5 Feb 2003 08:46:17 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15DqFp25905 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 08:52:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15DqEJ25902 for ; Wed, 5 Feb 2003 08:52:14 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24848 for ; Wed, 5 Feb 2003 08:45:45 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15DbLJ25070; Wed, 5 Feb 2003 08:37:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15DYdJ24478 for ; Wed, 5 Feb 2003 08:34:39 -0500 Received: from waldorf.cs.uni-dortmund.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24227 for ; Wed, 5 Feb 2003 08:28:10 -0500 (EST) Received: from postamt.cs.uni-dortmund.de (postamt [129.217.4.40]) by waldorf.cs.uni-dortmund.de with ESMTP id h15DVcF20601; Wed, 5 Feb 2003 14:31:38 +0100 (MET) Received: from grant (grant [129.217.16.109]) (authenticated bits=0) by postamt.cs.uni-dortmund.de (8.12.6/8.12.5) with ESMTP id h15DVbcK018648 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Feb 2003 14:31:37 +0100 (MET) Content-Type: text/plain; charset="us-ascii" From: Oliver Waldhorst Organization: University of Dortmund To: manet@ietf.org, ns-users@isi.edu Date: Wed, 5 Feb 2003 14:31:37 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200302051431.37180.waldhorst@ls4.cs.uni-dortmund.de> Content-Transfer-Encoding: 8bit Subject: [manet] ns-2 implementations of MAODV and MDSR available Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit We would like to announce the availability of ns-2 implementations of two multicast routing protocols for mobile ad hoc networks: * Multicast Ad hoc On-Demand Distance Vector (MAODV) Routing * Simple Multicast and Broadcast Extensions to Dynamic Source Routing (MDSR) These implementations have been developed as part of our research on peer-to-peer computing in mobile ad hoc networks. A patch for ns-2.1b9a is available on the Web: http://www4.cs.uni-dortmund.de/~Lindemann Regards, Oliver Waldhorst -- ------------------------------------------------------------------------ Oliver Waldhorst, M.S. University of Dortmund Department of Computer Science Computer Systems and Performance Evaluation Phone: +49 (231) 755-4797 August-Schmidt-Str. 12 Fax: +49 (231) 755-2417 44227 Dortmund, Germany E-mail:ow@ls4.cs.uni-dortmund.de WWW: http://www4.cs.uni-dortmund.de/~Waldhorst/ ------------------------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 5 10:15:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27990 for ; Wed, 5 Feb 2003 10:15:24 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15FLNV31969 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 10:21:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15FLNJ31966 for ; Wed, 5 Feb 2003 10:21:23 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27980 for ; Wed, 5 Feb 2003 10:14:53 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15F8nJ31191; Wed, 5 Feb 2003 10:08:49 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15F6sJ30457 for ; Wed, 5 Feb 2003 10:06:54 -0500 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27404 for ; Wed, 5 Feb 2003 10:00:15 -0500 (EST) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id h15FEQQK031664 for ; Wed, 5 Feb 2003 13:14:26 -0200 Message-ID: <00bc01c2cd29$049e1f60$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Wed, 5 Feb 2003 13:12:37 -0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B9_01C2CD18.410793C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] IP address request for a node that is on sleep mode Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00B9_01C2CD18.410793C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Relating to the autoconfiguration papers I would like to know what would = be the behavior when there is a request=20 for an IP address of a node that is on sleep mode ... Thanks in advance. --------------------------------------------------- F=E1bio Mesquita Buiati Universidade de Bras=EDlia - UnB email - fabio@redes.unb.br Brazil --------------------------------------------------- ------=_NextPart_000_00B9_01C2CD18.410793C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
 
Relating to the autoconfiguration papers I would = like to=20 know what would be the behavior when there is a request =
for an IP address of a node that is on sleep = mode=20 ...
 
Thanks in advance.
---------------------------------------------------
F=E1bio = Mesquita=20 Buiati
Universidade de Bras=EDlia - UnB
email - fabio@redes.unb.br
Brazil
---------------------------------------------------
------=_NextPart_000_00B9_01C2CD18.410793C0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 5 12:43:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03322 for ; Wed, 5 Feb 2003 12:43:44 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15Hnm410211 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 12:49:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15HnmJ10208 for ; Wed, 5 Feb 2003 12:49:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03315 for ; Wed, 5 Feb 2003 12:43:13 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15HOrJ08158; Wed, 5 Feb 2003 12:24:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15HMBJ08067 for ; Wed, 5 Feb 2003 12:22:11 -0500 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02303 for ; Wed, 5 Feb 2003 12:15:37 -0500 (EST) Received: from cdpd (winlabo3.rutgers.edu [165.230.120.102]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id h15HJGPI029599 for ; Wed, 5 Feb 2003 12:19:16 -0500 (EST) Date: Wed, 5 Feb 2003 12:18:35 -0500 (EST) From: Umut Akyol X-Sender: umut@cdpd To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] RTS/CTS Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi this question is in fact about the infrastructure mode of 802.11b but I think it's relevant... Suppose two BSS operating in the same channel and close enough to cause interference and hear themselves. A station in one of these BSSs start an RTS/CTS transmission and the AP replies with a CTS. What happens when the other AP hears this CTS? Does it stop transmission and wait or what? Umut _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 5 12:58:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04192 for ; Wed, 5 Feb 2003 12:58:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15I4vo11003 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 13:04:57 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15I4uJ11000 for ; Wed, 5 Feb 2003 13:04:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04147 for ; Wed, 5 Feb 2003 12:58:22 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15HhiJ09931; Wed, 5 Feb 2003 12:43:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15HgAJ09869 for ; Wed, 5 Feb 2003 12:42:10 -0500 Received: from donkeykong.gpcc.itd.umich.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03026 for ; Wed, 5 Feb 2003 12:35:36 -0500 (EST) Received: from asteroids.gpcc.itd.umich.edu (asteroids.gpcc.itd.umich.edu [141.211.2.218]) by donkeykong.gpcc.itd.umich.edu (8.8.8/4.3-mailhub) with ESMTP id MAA20880 for ; Wed, 5 Feb 2003 12:39:14 -0500 (EST) Received: from localhost (sgoswami@localhost) by asteroids.gpcc.itd.umich.edu (8.9.1a/5.1-client) with ESMTP id MAA23455 for ; Wed, 5 Feb 2003 12:39:13 -0500 (EST) Precedence: first-class Date: Wed, 5 Feb 2003 12:39:13 -0500 (EST) From: "s. goswami" X-X-Sender: sgoswami@asteroids.gpcc.itd.umich.edu cc: manet@ietf.org Subject: Re: [manet] RTS/CTS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , the other hears CTS and differs. On Wed, 5 Feb 2003, Umut Akyol wrote: > Hi this question is in fact about the infrastructure mode of 802.11b but I > think it's relevant... > Suppose two BSS operating in the same channel and close enough to cause > interference and hear themselves. A station in one of these BSSs start an > RTS/CTS transmission and the AP replies with a CTS. What happens when the > other AP hears this CTS? Does it stop transmission and wait or what? > > Umut > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Feb 5 14:33:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07665 for ; Wed, 5 Feb 2003 14:33:22 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15JdQF17295 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 14:39:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JdQJ17292 for ; Wed, 5 Feb 2003 14:39:26 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07657 for ; Wed, 5 Feb 2003 14:32:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JNbJ15925; Wed, 5 Feb 2003 14:23:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JLhJ15808 for ; Wed, 5 Feb 2003 14:21:43 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07078 for ; Wed, 5 Feb 2003 14:15:06 -0500 (EST) Received: (qmail 29229 invoked by uid 417); 5 Feb 2003 19:18:45 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 5 Feb 2003 19:18:45 -0000 Received: from ankur ([203.94.198.43]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Wed, 05 Feb 2003 12:18:38 -0700 Message-ID: <006001c2cd4b$79df16e0$2bc65ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: "Umut Akyol" Cc: manet@ietf.org References: Subject: Re: [manet] RTS/CTS Date: Thu, 6 Feb 2003 00:39:36 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Umut, When two APs are in the interference range of each other (which shouldn't be in first place..), if one AP sends a CTS then the other AP has to stop the transmission. Otherwise, collisions can't be avoided which is the function of 'CA' in CSMA/CA. Regards, Ankur ---------------------------------------------------------------------------- Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia Space Shuttle - STS 107 " The paths from dreams to success does exist, May you have the vision to find it, the courage to get on to it, and the perseverance to follow it. Wishing you a great journey !" ---------------------------------------------------------------------------- ----- Original Message ----- From: Umut Akyol To: Sent: Wednesday, February 05, 2003 10:48 PM Subject: [manet] RTS/CTS > Hi this question is in fact about the infrastructure mode of 802.11b but I > think it's relevant... > Suppose two BSS operating in the same channel and close enough to cause > interference and hear themselves. A station in one of these BSSs start an > RTS/CTS transmission and the AP replies with a CTS. What happens when the > other AP hears this CTS? Does it stop transmission and wait or what? > > Umut > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Feb 5 15:00:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08510 for ; Wed, 5 Feb 2003 15:00:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15K6ds18744 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 15:06:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15K6cJ18741 for ; Wed, 5 Feb 2003 15:06:38 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08500 for ; Wed, 5 Feb 2003 15:00:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JqkJ18018; Wed, 5 Feb 2003 14:52:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JpmJ17919 for ; Wed, 5 Feb 2003 14:51:48 -0500 Received: from mhs99ykf.rim.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08022 for ; Wed, 5 Feb 2003 14:45:12 -0500 (EST) Received: from ngw04ykf.rim.net (ngw04ykf.rim.net [10.102.100.115]) by mhs99ykf.rim.net (Postfix) with SMTP id AFEE4B4AAA for ; Wed, 5 Feb 2003 14:48:50 -0500 (EST) Received: from pgs04ykf.rim.net ([10.102.101.130]) by ngw04ykf.rim.net (NAVGW 2.5.2.9) with SMTP id M2003020514484919494 for ; Wed, 05 Feb 2003 14:48:49 -0500 Received: from XCH21YKF.rim.net ([10.102.100.36]) by pgs04ykf.rim.net with Microsoft SMTPSVC(5.0.2195.5329); Wed, 5 Feb 2003 14:48:50 -0500 content-class: urn:content-classes:message Subject: RE: [manet] RTS/CTS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 5 Feb 2003 14:48:45 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: <763E1F980D65B74B9CF77C67473951AC02421013@xch01yow.rim.net> Thread-Topic: [manet] RTS/CTS Thread-Index: AcLNTeWA/i+E+GA3RUOTMUlNjW47IgAAFLGA From: "Haining Zhang" To: "Ankur Jain" , "Umut Akyol" Cc: X-OriginalArrivalTime: 05 Feb 2003 19:48:50.0251 (UTC) FILETIME=[9AC509B0:01C2CD4F] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h15JpmJ17920 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit That's why poeple have to do a site survey on RF use before deployment. Otherwise, it would be a mess. PCF is a better choice than DCF in a high interference environment. But PCF is optional and not supported by all devices. Cheers Haining -----Original Message----- From: Ankur Jain [mailto:ankurjain@softhome.net] Sent: Wednesday, February 05, 2003 2:10 PM To: Umut Akyol Cc: manet@ietf.org Subject: Re: [manet] RTS/CTS Hi Umut, When two APs are in the interference range of each other (which shouldn't be in first place..), if one AP sends a CTS then the other AP has to stop the transmission. Otherwise, collisions can't be avoided which is the function of 'CA' in CSMA/CA. Regards, Ankur ---------------------------------------------------------------------------- Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia Space Shuttle - STS 107 " The paths from dreams to success does exist, May you have the vision to find it, the courage to get on to it, and the perseverance to follow it. Wishing you a great journey !" ---------------------------------------------------------------------------- ----- Original Message ----- From: Umut Akyol To: Sent: Wednesday, February 05, 2003 10:48 PM Subject: [manet] RTS/CTS > Hi this question is in fact about the infrastructure mode of 802.11b but I > think it's relevant... > Suppose two BSS operating in the same channel and close enough to cause > interference and hear themselves. A station in one of these BSSs start an > RTS/CTS transmission and the AP replies with a CTS. What happens when the > other AP hears this CTS? Does it stop transmission and wait or what? > > Umut > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Feb 5 15:06:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08686 for ; Wed, 5 Feb 2003 15:06:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15KC9O19706 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 15:12:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15KC9J19703 for ; Wed, 5 Feb 2003 15:12:09 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08672 for ; Wed, 5 Feb 2003 15:05:32 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JxKJ18336; Wed, 5 Feb 2003 14:59:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15JwmJ18306 for ; Wed, 5 Feb 2003 14:58:48 -0500 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08153 for ; Wed, 5 Feb 2003 14:52:08 -0500 (EST) Received: from cdpd (winlabo3.rutgers.edu [165.230.120.102]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id h15JtdPI005656; Wed, 5 Feb 2003 14:55:39 -0500 (EST) Date: Wed, 5 Feb 2003 14:55:00 -0500 (EST) From: Umut Akyol X-Sender: umut@cdpd To: Ankur Jain cc: manet@ietf.org Subject: Re: [manet] RTS/CTS In-Reply-To: <006001c2cd4b$79df16e0$2bc65ecb@ankur> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , If the other AP stops,then all the STA's in its BSS must also stop right? I don't think that this kind of a coordination is specified in the protocol. Or is it specified? For example how will the other AP's and STA's will start transmission then? How will they schedule beaconing afterwards? Regards, Umut On Thu, 6 Feb 2003, Ankur Jain wrote: > Hi Umut, > > When two APs are in the interference range of each other (which shouldn't be > in first place..), if one AP sends a CTS then the other AP has to stop the > transmission. Otherwise, collisions can't be avoided which is the function > of 'CA' in CSMA/CA. > > Regards, > Ankur > > > > ---------------------------------------------------------------------------- > Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia > Space Shuttle - STS 107 > > " The paths from dreams to success does exist, > May you have the vision to find it, > the courage to get on to it, > and the perseverance to follow it. > Wishing you a great journey !" > ---------------------------------------------------------------------------- > > > > > > ----- Original Message ----- > From: Umut Akyol > To: > Sent: Wednesday, February 05, 2003 10:48 PM > Subject: [manet] RTS/CTS > > > > Hi this question is in fact about the infrastructure mode of 802.11b but I > > think it's relevant... > > Suppose two BSS operating in the same channel and close enough to cause > > interference and hear themselves. A station in one of these BSSs start an > > RTS/CTS transmission and the AP replies with a CTS. What happens when the > > other AP hears this CTS? Does it stop transmission and wait or what? > > > > Umut > > > > _______________________________________________ > > 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 mailnull@www1.ietf.org Wed Feb 5 17:31:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13496 for ; Wed, 5 Feb 2003 17:31:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15Mbrd03163 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 17:37:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15Mbrp03160 for ; Wed, 5 Feb 2003 17:37:53 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13479 for ; Wed, 5 Feb 2003 17:31:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15MKsp01850; Wed, 5 Feb 2003 17:20:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15MDkp01509 for ; Wed, 5 Feb 2003 17:13:46 -0500 Received: from exstudent9.city.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12822 for ; Wed, 5 Feb 2003 17:07:05 -0500 (EST) Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59) id ; Thu, 6 Feb 2003 08:39:08 +1030 Message-ID: From: "Liaw, Yong Shyang - LIAYS001" To: manet@ietf.org Subject: RE: [manet] delay in sending the next packet in DSR Date: Thu, 6 Feb 2003 08:41:35 +1030 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Forgot to CC this email to MANET list. ============= Hi Casey, Thank you for your reply. In the Opnet DSR model, the delay is not purposed to model the ARP interaction (the ARP interaction is not model at all). It is meaned to allow time for an ERROR message (i.e. Route_error) to return to the source, if any, before sending the next packet. That place a limit on how fast DSR can send!!! In my simulation, I find that for a 6-hop linear topology (static), the delay is 180ms (30ms per hop), and hence place a limit of 5.5 packets/sec it can send. When I set the delay to be very small (i.e. 1ms per hop), it gives me a much better performance of over 20 packet per second. The delay does not seem to be the correct thing to do. And as I said before, DSR Internet draft does not say anything about this (or I could not find it). > -----Original Message----- > From: Casey Carter [mailto:ccarter@cs.uiuc.edu] > Sent: Wednesday, 5 February 2003 7:14 > To: Liaw, Yong Shyang - LIAYS001 > Cc: manet@ietf.org > Subject: Re: [manet] delay in sending the next packet in DSR > > > This is a standard hack for ad hoc routing simulations that avoids > interaction with ARP. ARPs based on the BSD implementation have a > single-packet buffer where they hold packets while performing address > resolution. Additional packets that arrive replace the packet in the > buffer. So, if you have a bunch of packets waiting for the > route reply, > and send them to the link layer all at once, ARP will drop > all but the > last if it does not already have an address mapping for the nexthop. > The hack is to guess how long an ARP request/reply cycle takes, and > delay sending packets by cycle_time * #hops. > > There is substantial discussion of this issue in my paper "ARP > Considered Harmful: Manycast Transactions in Ad Hoc Networks" > to appear > in WCNC 2003 -- available at > . We discuss how > ARP does > not seem to integrate properly into ad hoc networks, and present an > alternative that places responsibility for address resolution in the > routing protocol, where it can be done with zero cost. > > Liaw, Yong Shyang - LIAYS001 wrote: > > >Hi, > > > >I have a question regarding DSR & would appreciate if any > one can help. > > > >In DSR, when sending data packet from the send queue, shall > you wait for > >(delay*no_hop) before sending the next data packet? > >where delay is the time you wait for a reply from 1 hop away > (i.e. 30ms), > > no_hop is the number of hops > > > >I find the Opnet's DSR model implements the above, but I > could not find in the > >DSR Internet-draft that said this for data packet (though > there is some random > >delay for sending reply packets). In this a bug? I would > appreciate if you can > >help me. > > > >Thank you. > > > >_______________________________________________ > >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 mailnull@www1.ietf.org Wed Feb 5 17:39:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13923 for ; Wed, 5 Feb 2003 17:39:32 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15MjgH03590 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 17:45:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15Mjfp03587 for ; Wed, 5 Feb 2003 17:45:41 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13895 for ; Wed, 5 Feb 2003 17:39:01 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15MVhp02265; Wed, 5 Feb 2003 17:31:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15MUep02205 for ; Wed, 5 Feb 2003 17:30:40 -0500 Received: from fsa.cpsc.ucalgary.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13261 for ; Wed, 5 Feb 2003 17:23:46 -0500 (EST) Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsa.cpsc.ucalgary.ca (8.12.7/8.12.7) with ESMTP id h15MQxTl013053 for ; Wed, 5 Feb 2003 15:26:59 -0700 Received: from cpsc.ucalgary.ca (ict720f [136.159.17.10]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id h15MQvMP013915 for ; Wed, 5 Feb 2003 15:26:57 -0700 Message-ID: <3E418FB1.7010902@cpsc.ucalgary.ca> Date: Wed, 05 Feb 2003 15:26:57 -0700 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.2 required=7.3 X-Spam-Level: *** Content-Transfer-Encoding: 7bit Subject: [manet] Installing APE Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I have been trying to install APE Testbed from Uppsala University. I have used the Linux kernel (2.4.18) already sitting on my laptop to build my own distribution. There are two problems that I am facing: 1. The AODV-UU implementation while compiling generates errors and fails installation. 2. When I remove the AODV-UU and compile the rest of the package, it compiles, but the when I install it and try to boot into APE, I get the message "Kernel Panic" and booting freezes. Could someone please guide me as to how to install the APE testbed on my laptop. I am using Red Hat Linux 7.3 kernel 2.4.18? Thanks, Abhinav _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 5 19:56:28 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17075 for ; Wed, 5 Feb 2003 19:56:28 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1612fI10016 for manet-archive@odin.ietf.org; Wed, 5 Feb 2003 20:02:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1612fp10013 for ; Wed, 5 Feb 2003 20:02:41 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17049 for ; Wed, 5 Feb 2003 19:55:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h160m6p09603; Wed, 5 Feb 2003 19:48:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h160jBp09539 for ; Wed, 5 Feb 2003 19:45:11 -0500 Received: from web20903.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16698 for ; Wed, 5 Feb 2003 19:38:27 -0500 (EST) Message-ID: <20030206004205.39614.qmail@web20903.mail.yahoo.com> Received: from [32.97.110.142] by web20903.mail.yahoo.com via HTTP; Wed, 05 Feb 2003 16:42:05 PST Date: Wed, 5 Feb 2003 16:42:05 -0800 (PST) From: Yan Liu To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1457442550-1044492125=:38256" Subject: [manet] Modifying DSR's Route-Discovery procedure Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --0-1457442550-1044492125=:38256 Content-Type: text/plain; charset=us-ascii Hi, The default DSR behavior for forwarding Route-Request packets is that it only forwards or answers the first Route-Request packet it receives for each unique request. Are there any works in place that explores modifying this behavior so that the source could potentially receive more routes? The reason is we are working on some behavior monitoring algorithm that depends on the source hearing more diverse routes. Thanks, Yan --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now --0-1457442550-1044492125=:38256 Content-Type: text/html; charset=us-ascii

Hi,

The default DSR behavior for forwarding Route-Request packets is that it only forwards or answers the first Route-Request packet it receives for each unique request.  Are there any works in place that explores modifying this behavior so that the source could potentially receive more routes?  The reason is we are working on some behavior monitoring algorithm that depends on the source hearing more diverse routes.

Thanks,

Yan


Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now --0-1457442550-1044492125=:38256-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 06:00:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12594 for ; Thu, 6 Feb 2003 06:00:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16B6Y522080 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 06:06:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16B6Yp22077 for ; Thu, 6 Feb 2003 06:06:34 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12568 for ; Thu, 6 Feb 2003 05:59:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Aocp21187; Thu, 6 Feb 2003 05:50:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Aihp20830 for ; Thu, 6 Feb 2003 05:44:43 -0500 Received: from postfix.informatik.uni-bonn.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11770 for ; Thu, 6 Feb 2003 05:37:48 -0500 (EST) X-IAI-Env-From: : [131.220.6.147] Received: from cs.uni-bonn.de (bratislava.informatik.uni-bonn.de [131.220.6.147]) by postfix.informatik.uni-bonn.de (Postfix) with ESMTP id D3C3070C82 for ; Thu, 6 Feb 2003 11:41:26 +0100 (MET) (envelope-from dewaal@cs.uni-bonn.de) (envelope-to manet@ietf.org) (1) (internal use: ta=0, tu=1, te=0, am=-, au=-) Message-ID: <3E423BCF.4010406@cs.uni-bonn.de> Date: Thu, 06 Feb 2003 11:41:19 +0100 From: Christian de Waal Organization: Computer Science IV, University of Bonn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] BonnMotion bugfix Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello all, since there are some people out there using the BonnMotion tool to generate mobility scenarios, I would like to inform you that there is an ugly bug in the RPGM model that may cause mobiles to move at extremely high velocities. On the BonnMotion website (address below), you can download a patch that corrects this mistake. Please accept our apologies in case you have used this model and now must re-run your simulations. Regards, Christian de Waal BonnMotion website: http://web.informatik.uni-bonn.de/IV/BonnMotion/ -- ____________________________________________________________________ Christian de Waal University of Bonn Phone: +49 228 73-4548 Institute of Computer Science IV Fax: +49 228 73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de 53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 10:30:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22158 for ; Thu, 6 Feb 2003 10:30:20 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16Faos07821 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 10:36:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Faop07818 for ; Thu, 6 Feb 2003 10:36:50 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22110 for ; Thu, 6 Feb 2003 10:29:49 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FNkp07106; Thu, 6 Feb 2003 10:23:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FLOp06954 for ; Thu, 6 Feb 2003 10:21:24 -0500 Received: from mail.zrz.tu-berlin.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20849 for ; Thu, 6 Feb 2003 10:14:24 -0500 (EST) Received: from mail.zrz.tu-berlin.de ([130.149.4.15]) by mail.zrz.tu-berlin.de with esmtp (exim-3.36) for id 18gnms-0003Zq-00; Thu, 06 Feb 2003 16:18:02 +0100 Received: from mail.zrz.TU-Berlin.DE ([130.149.4.15]) by mail.zrz.TU-Berlin.DE (MailMonitor for SMTP v1.2.0 ) ; Thu, 6 Feb 2003 16:18:02 +0100 (CET) Received: from ftmail.ee.tu-berlin.de ([130.149.49.250]) by mail.zrz.tu-berlin.de with esmtp (exim-3.36) for id 18gnms-0003Zh-00; Thu, 06 Feb 2003 16:18:02 +0100 Received: from obelix (obelix.tkn.TU-Berlin.DE [130.149.49.71]) by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id h16FI2026421 for ; Thu, 6 Feb 2003 16:18:02 +0100 From: "Christian Frank" To: Date: Thu, 6 Feb 2003 16:17:15 +0100 Message-ID: <000f01c2cdf2$d4935400$47319582@ee.tuberlin.de> 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.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20030205170005.5795.38515.Mailman@www1.ietf.org> X-Virus-Scanned: Sophos MailMonitor on mail.zrz.tu-berlin.de; Thu, 06 Feb 2003 16:18:02 +0100 Content-Transfer-Encoding: 7bit Subject: [manet] Implementation of Perkins/Koodli Service Discovery Draft? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, I am currently involved in research on service discovery in ad-hoc networks. In this context, I am interested in the Internet Draft "Service Discovery in On-Demand Ad Hoc Networks" by Koodli and Perkins: www.ietf.org/internet-drafts/draft-koodli-manet-servicediscovery-00.txt Here the questions: (1) Have you done or do you know about a prototype implementation of this draft? (2) Do you know of any additional specification regarding to which nodes hold "service bindings", specifically: At what point does a node store such a service binding (an association between a service and the IP address of the node hosting the service application)? Also, I would appreciate any other experience or comments regarding the draft. Thank you, Christian -- Christian Frank Telecommunications & Networks Group TU-Berlin E-Mail: chfrank@cs.tu-berlin.de Tel: +49 30 31423823 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 11:20:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24322 for ; Thu, 6 Feb 2003 11:20:32 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16GR3i12154 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 11:27:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16GR3p12151 for ; Thu, 6 Feb 2003 11:27:03 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24316 for ; Thu, 6 Feb 2003 11:20:01 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16GEVp11440; Thu, 6 Feb 2003 11:14:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16GD6p11394 for ; Thu, 6 Feb 2003 11:13:06 -0500 Received: from marfik.upv.es (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23776 for ; Thu, 6 Feb 2003 11:06:01 -0500 (EST) From: calafate@disca.upv.es Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h16G9p608320 for ; Thu, 6 Feb 2003 17:09:52 +0100 Received: from smtp2.upv.es (smtp2.cc.upv.es [158.42.250.31]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h16A6eU07642 for ; Thu, 6 Feb 2003 11:06:40 +0100 (MET) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by smtp2.upv.es (8.11.4/8.11.4) with ESMTP id h16AkuD26844 for ; Thu, 6 Feb 2003 11:46:57 +0100 Received: by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0, from userid 30) id ACFF81FE8E; Thu, 6 Feb 2003 11:04:16 +0100 (CET) To: manet@ietf.org Subject: Re: [manet] Error simulating with AODV, DSR and TORA Message-ID: <1044525856.3e423320a71e0@nao.disca.upv.es> Date: Thu, 06 Feb 2003 11:04:16 +0100 (CET) References: <20030204021248.37560.qmail@web40802.mail.yahoo.com> <3E3F9C97.4050301@telecom.lth.se> In-Reply-To: <3E3F9C97.4050301@telecom.lth.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 150.145.8.145 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, I think there is some confusion concerning the error I referred to. It is in NS2.1b9a, and commenting the line > ssrc_ = 0; Appears to solve it. Best regards, _________________________________________________ Carlos Miguel Tavares de Araújo Cesariny Calafate Becário de la Universidad Politécnica de Valencia e-mail: calafate@disca.upv.es http://reptar.grc.upv.es/~calafate/ Tel: +34 963879703 ext. 77977 _________________________________________________ \\\\\\\"In an open world without walls and fences who needs Windows and Gates? \\\\\\\" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 14:54:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01938 for ; Thu, 6 Feb 2003 14:54:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16K1Ye26633 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 15:01:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16K1Yp26630 for ; Thu, 6 Feb 2003 15:01:34 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01926 for ; Thu, 6 Feb 2003 14:54:27 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16JkBp25988; Thu, 6 Feb 2003 14:46:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Jh3p25800 for ; Thu, 6 Feb 2003 14:43:03 -0500 Received: from dfw-gate3.raytheon.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01472 for ; Thu, 6 Feb 2003 14:35:56 -0500 (EST) Received: from ds02e00.directory.ray.com (ds02e00.directory.ray.com [147.25.130.245]) by dfw-gate3.raytheon.com (8.12.5/8.12.5) with ESMTP id h16JdYeG020928 for ; Thu, 6 Feb 2003 13:39:34 -0600 (CST) Received: from ds02e00.directory.ray.com (localhost [127.0.0.1]) by ds02e00.directory.ray.com (8.12.6/8.12.1) with ESMTP id h16JdVVK022623 for ; Thu, 6 Feb 2003 19:39:32 GMT Received: from fcexchange.fal.us.ray.com (fcexchange.fal.us.ray.com [147.18.176.31]) by ds02e00.directory.ray.com (8.12.6/8.12.1) with ESMTP id h16JdSUJ022593 for ; Thu, 6 Feb 2003 19:39:28 GMT Received: by FCEXCHANGE with Internet Mail Service (5.5.2653.19) id <12G9Q63C>; Thu, 6 Feb 2003 14:39:30 -0500 Message-ID: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> From: "Su, William" To: manet@ietf.org Date: Thu, 6 Feb 2003 14:39:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] 802.11 Ad hoc mode? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I posted this question couple of month ago, received no response so I'll try it again... Does anyone knows where I can find good source to answer these questions? Couldn't seem to find them in the 802.11 spec (Part11:MAC-PHY Specification): 1. In ad-hoc (IBSS) mode, how do the stations find each other in multi-channel mode (if they are supported)? The spec says all stations generate beacons in random interval, but does not say if they do a full sweep scan across all the channels for beacons if they don't hear anything for a period of time. In some configuration menus for 802.11 device (e.g. D-Link cards) suggests that when turning on two ad-hoc mode stations they shouldn't be turned on together but should allow some time to pass before turning on the 2nd unit (otherwise 2 separate network could be formed). What's the reason for this? Why couldn't the station do a passive scan periodically to avoid this? 2. Does IBSS mode support probes? And are they used in the full sweep scan (if multiple channel mode is supported)? If so, how do stations coordinate who generate probe-response and who doesn't (so there is no flooding of replies)? 3. How does association work in IBSS mode? Does a station send association request to all the neighbors it hears on the beacons? Also, does 802.11 IBSS use ARP to get the neighbor's IP address? Does this process takes place in association or it is separate? Any information would be greatly appreciated, William _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 15:08:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02459 for ; Thu, 6 Feb 2003 15:08:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16KFDL27851 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 15:15:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16KFDp27848 for ; Thu, 6 Feb 2003 15:15:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02442 for ; Thu, 6 Feb 2003 15:08:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16JxNp26497; Thu, 6 Feb 2003 14:59:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Jw0p26436 for ; Thu, 6 Feb 2003 14:58:00 -0500 Received: from web21006.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01844 for ; Thu, 6 Feb 2003 14:50:52 -0500 (EST) Message-ID: <20030206195431.36646.qmail@web21006.mail.yahoo.com> Received: from [68.18.210.86] by web21006.mail.yahoo.com via HTTP; Thu, 06 Feb 2003 11:54:31 PST Date: Thu, 6 Feb 2003 11:54:31 -0800 (PST) From: Yang Xiao Reply-To: YangXiao@ieee.org Subject: Re: [manet] 802.11 Ad hoc mode? To: "Su, William" , manet@ietf.org In-Reply-To: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , William I believe that IEEE 802.11 never support "multiple channels" and has no intention to support "multiple channels" so far. Regards Yang --- "Su, William" wrote: > Hi, > > I posted this question couple of month ago, received no response so > I'll try > it again... > > Does anyone knows where I can find good source to answer these > questions? > Couldn't seem to find them in the 802.11 spec (Part11:MAC-PHY > Specification): > > 1. In ad-hoc (IBSS) mode, how do the stations find each other in > multi-channel mode (if they are supported)? The spec says all > stations > generate beacons in random interval, but does not say if they do a > full > sweep scan across all the channels for beacons if they don't hear > anything > for a period of time. In some configuration menus for 802.11 device > (e.g. > D-Link cards) suggests that when turning on two ad-hoc mode stations > they > shouldn't be turned on together but should allow some time to pass > before > turning on the 2nd unit (otherwise 2 separate network could be > formed). > What's the reason for this? Why couldn't the station do a passive > scan > periodically to avoid this? > > 2. Does IBSS mode support probes? And are they used in the full > sweep scan > (if multiple channel mode is supported)? If so, how do stations > coordinate > who generate probe-response and who doesn't (so there is no flooding > of > replies)? > > 3. How does association work in IBSS mode? Does a station send > association > request to all the neighbors it hears on the beacons? Also, does > 802.11 > IBSS use ARP to get the neighbor's IP address? Does this process > takes > place in association or it is separate? > > Any information would be greatly appreciated, > > William > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 15:36:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03325 for ; Thu, 6 Feb 2003 15:36:19 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16KgtX29794 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 15:42:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Kgtp29791 for ; Thu, 6 Feb 2003 15:42:55 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03298 for ; Thu, 6 Feb 2003 15:35:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16KOrp28244; Thu, 6 Feb 2003 15:24:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16KNCp28199 for ; Thu, 6 Feb 2003 15:23:12 -0500 Received: from web21005.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA02667 for ; Thu, 6 Feb 2003 15:16:04 -0500 (EST) Message-ID: <20030206201942.67346.qmail@web21005.mail.yahoo.com> Received: from [68.18.210.86] by web21005.mail.yahoo.com via HTTP; Thu, 06 Feb 2003 12:19:42 PST Date: Thu, 6 Feb 2003 12:19:42 -0800 (PST) From: Yang Xiao Reply-To: YangXiao@ieee.org Subject: RE: [manet] 802.11 Ad hoc mode? To: "Su, William" , YangXiao@ieee.org, manet@ietf.org In-Reply-To: <72F06A8F0165D611AD2A00508BCFF600075A874E@FCEXCHANGE> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , William Sorry for misunderstanding. Some comments. The Probe Frame 1) Transmitted by a mobile station, attempting to quickly locate a WLAN. 2) May be used to locate particular BSS (SSID) or any WLAN 3) Used in active scanning, 4) Probe Response looks like a Beacon frame, sent by AP in the BSS or by last transmitting Beacon station in the IBSS Scanning 1) Passive scanning: The station will scan all channels 2) Active scanning: a) The station will scan all channels b) It will send a Probe request to get details on the BSS, if exists in the current channel. Beacons: 1) Transmitted periodically by the AP to locate and identify its BSS 2) The AP will send a Beacon to notify the station that it has buffered frames to that station. 3) If AP exists, AP sends Beacons. Otherwise other stations will send. Association 1)Make logical connection between the AP to the station – the AP will not receive any data from a station before the association. assist the DS to know where to deliver the mobile data. 2) Reassociation ( Similar to the association ) Send repeatedly to the AP. Hope that these will help Regards Yang --- "Su, William" wrote: > Yang, > > sorry about the confusion, what I meant was : "What happens if > multiple > different IBSS are operating on 2 or more different channels at the > same > time - how do the beaconing mechanism works, association, ARP > functionality...etc". It seems like with 802.11b there can only be 3 > out of > 11 channels simultenously in use due to the requirement to prevent > interference, but with 802.11a all 12 can be used. > > please let me know if you any any information o this, > > thanks, > > William > > > -----Original Message----- > From: Yang Xiao [mailto:yangxiao_acm@yahoo.com] > Sent: Thursday, February 06, 2003 2:55 PM > To: Su, William; manet@ietf.org > Subject: Re: [manet] 802.11 Ad hoc mode? > > > William > > I believe that IEEE 802.11 never support "multiple channels" and has > no > intention to support "multiple channels" so far. > > Regards > > Yang > > --- "Su, William" wrote: > > Hi, > > > > I posted this question couple of month ago, received no response so > > I'll try > > it again... > > > > Does anyone knows where I can find good source to answer these > > questions? > > Couldn't seem to find them in the 802.11 spec (Part11:MAC-PHY > > Specification): > > > > 1. In ad-hoc (IBSS) mode, how do the stations find each other in > > multi-channel mode (if they are supported)? The spec says all > > stations > > generate beacons in random interval, but does not say if they do a > > full > > sweep scan across all the channels for beacons if they don't hear > > anything > > for a period of time. In some configuration menus for 802.11 > device > > (e.g. > > D-Link cards) suggests that when turning on two ad-hoc mode > stations > > they > > shouldn't be turned on together but should allow some time to pass > > before > > turning on the 2nd unit (otherwise 2 separate network could be > > formed). > > What's the reason for this? Why couldn't the station do a passive > > scan > > periodically to avoid this? > > > > 2. Does IBSS mode support probes? And are they used in the full > > sweep scan > > (if multiple channel mode is supported)? If so, how do stations > > coordinate > > who generate probe-response and who doesn't (so there is no > flooding > > of > > replies)? > > > > 3. How does association work in IBSS mode? Does a station send > > association > > request to all the neighbors it hears on the beacons? Also, does > > 802.11 > > IBSS use ARP to get the neighbor's IP address? Does this process > > takes > > place in association or it is separate? > > > > Any information would be greatly appreciated, > > > > William > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 15:55:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04036 for ; Thu, 6 Feb 2003 15:55:40 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16L2GD30848 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 16:02:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16L2Gp30845 for ; Thu, 6 Feb 2003 16:02:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04017 for ; Thu, 6 Feb 2003 15:55:09 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16KgMp29759; Thu, 6 Feb 2003 15:42:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Kfjp29655 for ; Thu, 6 Feb 2003 15:41:45 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03255 for ; Thu, 6 Feb 2003 15:34:38 -0500 (EST) Received: from che.onthejob.net (localhost [127.0.0.1]) by che.onthejob.net (8.12.5/8.12.5) with ESMTP id h16KcGE0001497 for ; Thu, 6 Feb 2003 14:38:16 -0600 Received: (from dyoung@localhost) by che.onthejob.net (8.12.5/8.12.5/Submit) id h16KcGTe001495 for manet@ietf.org; Thu, 6 Feb 2003 14:38:16 -0600 Date: Thu, 6 Feb 2003 14:38:16 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] 802.11 Ad hoc mode? Message-ID: <20030206203816.GF13895@che.onthejob.net> Mail-Followup-To: manet@ietf.org References: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> User-Agent: Mutt/1.4i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, Feb 06, 2003 at 02:39:30PM -0500, Su, William wrote: > Does anyone knows where I can find good source to answer these questions? > Couldn't seem to find them in the 802.11 spec (Part11:MAC-PHY > Specification): Answers below. BTW, this does not seem like a very IETFish question. Is there perhaps a better venue? Possibly I can persuade my workplace to set up a mailing list for practical discussions on 802.11 arcana. > 1. In ad-hoc (IBSS) mode, how do the stations find each other in > multi-channel mode (if they are supported)? The spec says all stations > generate beacons in random interval, but does not say if they do a full > sweep scan across all the channels for beacons if they don't hear anything > for a period of time. In some configuration menus for 802.11 device (e.g. > D-Link cards) suggests that when turning on two ad-hoc mode stations they > shouldn't be turned on together but should allow some time to pass before > turning on the 2nd unit (otherwise 2 separate network could be formed). > What's the reason for this? Why couldn't the station do a passive scan > periodically to avoid this? Last I knew, IEEE 802.11 punted on the issue of merging two IBSSs. But for WiFi certification, an IBSS STA must join the oldest IBSS with the correct SSID. (Beacons for older IBSSs have greater TSFs.) In this way an IBSS merge is accomplished. Prism radios with STA firmware 1.4.9 and greater appear to do IBSS merges. I think that Prism radios with firmware 1.3.6 do, also. Unless they are very new, your D-Link cards are Prism. > 2. Does IBSS mode support probes? And are they used in the full sweep scan > (if multiple channel mode is supported)? If so, how do stations coordinate > who generate probe-response and who doesn't (so there is no flooding of > replies)? > > 3. How does association work in IBSS mode? Does a station send association > request to all the neighbors it hears on the beacons? Also, does 802.11 > IBSS use ARP to get the neighbor's IP address? Does this process takes > place in association or it is separate? Regardless of what the standard may (or may not) say, I have never seen an IBSS STA send its neighbor an association request. I think that STAs will do pairwise authentication, however. An 802.11 IBSS is a function of layer 2, so it is not concerned with IP numbers. Dave -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 17:49:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07572 for ; Thu, 6 Feb 2003 17:49:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16MuMa05831 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 17:56:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16MuMp05828 for ; Thu, 6 Feb 2003 17:56:22 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07563 for ; Thu, 6 Feb 2003 17:49:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16MZsp04292; Thu, 6 Feb 2003 17:35:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16MQDp04015 for ; Thu, 6 Feb 2003 17:26:13 -0500 Received: from io.iol.unh.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06726 for ; Thu, 6 Feb 2003 17:19:04 -0500 (EST) Received: from iol.unh.edu (rf2.iol.unh.edu [132.177.119.12]) by io.iol.unh.edu (8.12.7/8.12.7) with ESMTP id h16MMgdH028093 for ; Thu, 6 Feb 2003 17:22:42 -0500 Message-ID: <3E42E032.20202@iol.unh.edu> Date: Thu, 06 Feb 2003 17:22:42 -0500 From: Kevin Karcz Organization: IOL User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en,pdf MIME-Version: 1.0 CC: manet@ietf.org Subject: Re: [manet] 802.11 Ad hoc mode? References: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> <20030206203816.GF13895@che.onthejob.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit More answers below. David Young wrote: > On Thu, Feb 06, 2003 at 02:39:30PM -0500, Su, William wrote: > >>Does anyone knows where I can find good source to answer these questions? >>Couldn't seem to find them in the 802.11 spec (Part11:MAC-PHY >>Specification): > > > Answers below. > > BTW, this does not seem like a very IETFish question. Is there perhaps a > better venue? Possibly I can persuade my workplace to set up a mailing > list for practical discussions on 802.11 arcana. > > >>1. In ad-hoc (IBSS) mode, how do the stations find each other in >>multi-channel mode (if they are supported)? The spec says all stations >>generate beacons in random interval, but does not say if they do a full >>sweep scan across all the channels for beacons if they don't hear anything >>for a period of time. In some configuration menus for 802.11 device (e.g. >>D-Link cards) suggests that when turning on two ad-hoc mode stations they >>shouldn't be turned on together but should allow some time to pass before >>turning on the 2nd unit (otherwise 2 separate network could be formed). >>What's the reason for this? Why couldn't the station do a passive scan >>periodically to avoid this? > > > Last I knew, IEEE 802.11 punted on the issue of merging two IBSSs. But > for WiFi certification, an IBSS STA must join the oldest IBSS with > the correct SSID. (Beacons for older IBSSs have greater TSFs.) In this > way an IBSS merge is accomplished. > Prism radios with STA firmware 1.4.9 and greater appear to do IBSS > merges. I think that Prism radios with firmware 1.3.6 do, also. > Unless they are very new, your D-Link cards are Prism. > > >>2. Does IBSS mode support probes? And are they used in the full sweep scan >>(if multiple channel mode is supported)? If so, how do stations coordinate >>who generate probe-response and who doesn't (so there is no flooding of >>replies)? IBSS mode does use probe requests and responses. In an IBSS the generation of beacon frames is distributed. Every time a beacon is to be sent out, all the stations in the IBSS pick a random number. Whichever station picked the lowest number for that target beacon transmission time (TBTT) will be the first to send their beacon. All other stations upon hearing that beacon will discard the beacon that they had queued for that TBTT. Only the station that transmitted the beacon will then be responsible for generating any Probe Responses during that Beacon Interval. >>3. How does association work in IBSS mode? Does a station send association >>request to all the neighbors it hears on the beacons? Also, does 802.11 >>IBSS use ARP to get the neighbor's IP address? Does this process takes >>place in association or it is separate? > > > Regardless of what the standard may (or may not) say, I have never > seen an IBSS STA send its neighbor an association request. I think > that STAs will do pairwise authentication, however. Association is only used in an Infrastructure BSS, it is never used in IBSS mode. It also is not required for an IBSS station to authenticate before sending data either. (Even when WEP is in use.) > An 802.11 IBSS is a function of layer 2, so it is not concerned with > IP numbers. > > Dave > Regards, Kevin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 6 20:06:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11050 for ; Thu, 6 Feb 2003 20:06:11 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h171CrL13938 for manet-archive@odin.ietf.org; Thu, 6 Feb 2003 20:12:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h171Crp13935 for ; Thu, 6 Feb 2003 20:12:53 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11044 for ; Thu, 6 Feb 2003 20:05:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h170xop12821; Thu, 6 Feb 2003 19:59:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h170tCp12701 for ; Thu, 6 Feb 2003 19:55:12 -0500 Received: from c4.si.polymtl.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10651 for ; Thu, 6 Feb 2003 19:47:59 -0500 (EST) Received: (from nobody@localhost) by c4.si.polymtl.ca (8.11.6/8.11.6) id h170pde10337 for manet@ietf.org; Thu, 6 Feb 2003 19:51:39 -0500 Received: from 132.207.67.49 ( [132.207.67.49]) as user bemac@pop3.polymtl.ca by www.imp.polymtl.ca with HTTP; Thu, 6 Feb 2003 19:51:38 -0500 Message-ID: <1044579098.3e43031ab5fd0@www.imp.polymtl.ca> Date: Thu, 6 Feb 2003 19:51:38 -0500 From: Benjamin Macabeo To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 132.207.67.49 Content-Transfer-Encoding: 8bit Subject: [manet] RDMAR and local route repair Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, I'm a Msc student at l'École Polytechnique de Montréal. I'm very interested on RDMAR protocol and local route repair. Do you know if an implementation of this protocol is available? Do you know if it is possible to add local route repair to DSR? Thank you for your help Benjamin Macabéo _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 7 13:40:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17698 for ; Fri, 7 Feb 2003 13:40:21 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h17IlOx21700 for manet-archive@odin.ietf.org; Fri, 7 Feb 2003 13:47:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17IlOp21697 for ; Fri, 7 Feb 2003 13:47:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17684 for ; Fri, 7 Feb 2003 13:39:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17IXJp20467; Fri, 7 Feb 2003 13:33:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17IOap20183 for ; Fri, 7 Feb 2003 13:24:36 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17152 for ; Fri, 7 Feb 2003 13:17:01 -0500 (EST) Received: (qmail 11878 invoked by uid 417); 7 Feb 2003 18:20:40 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 7 Feb 2003 18:20:40 -0000 Received: from ankur ([203.94.198.101]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Fri, 07 Feb 2003 11:19:40 -0700 Message-ID: <005c01c2ced5$b0a5b180$65c65ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: gupta@cpsc.ucalgary.ca, "manet" References: <3E418FB1.7010902@cpsc.ucalgary.ca> Subject: Re: [manet] Installing APE Date: Fri, 7 Feb 2003 23:47:21 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Abhinav: Installation of APE doesn't depend on the linux kernel you are using. It will compile on any kernel of any linux (redhat linux, debian, mandrake etc.). Actually, it has is own kernel which runs on loop device. I experienced the same error of "kernel panic" when I installed APE the first time. Although, I don't the exact reason of getting this strange error, but I deduce the following reason for the error as my problem got solved in this way: On my laptop (using Redhat 7.3) , the root partition was on /dev/hda1 and the boot partition on /dev/hda2. Somehow APE looks for something in /dev/hda2 and thinks that it is root partition. But, in my case, it is not. At that time, I get the kernel panic error. When I installed APE on a different laptop (running Mandrake), it ran perfectly ok. In the second laptop, the partitions were like this : root on /dev/hda2 and boot on /dev/hda1. So, I think this could be one of the solution of your problem. In short, try to change the locations of your partition. (one way is to reinstall the linux and declare partitions in the opp. way). I am sure it will work. In my case, I compiled APE very easily in which the default AODV-UU package was there. But, if you just want to play with APE first, then why don't you just run the install script. It's already provided in the zip file. You have to compile APE only when you want to make some changes in it (e.g including your own protocol). I hope it solves your problem. If it works, then please do tell me. Regards Ankur ******************************** ankurjain@softhome.net http://www.geocities.com/ankurjain009/ ******************************** ---------------------------------------------------------------------------- Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia Space Shuttle - STS 107 " The paths from dreams to success does exist, May you have the vision to find it, the courage to get on to it, and the perseverance to follow it. Wishing you a great journey !" ---------------------------------------------------------------------------- ----- Original Message ----- From: Abhinav Gupta To: manet Sent: Thursday, February 06, 2003 3:56 AM Subject: [manet] Installing APE > Hi, > > I have been trying to install APE Testbed from Uppsala University. I > have used the Linux kernel (2.4.18) already sitting on my laptop to > build my own distribution. > > There are two problems that I am facing: > 1. The AODV-UU implementation while compiling generates errors and fails > installation. > 2. When I remove the AODV-UU and compile the rest of the package, it > compiles, but the when I install it and try to boot into APE, I get the > message "Kernel Panic" and booting freezes. > > Could someone please guide me as to how to install the APE testbed on my > laptop. I am using Red Hat Linux 7.3 kernel 2.4.18? > > Thanks, > Abhinav > > _______________________________________________ > 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 mailnull@www1.ietf.org Fri Feb 7 14:00:23 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18264 for ; Fri, 7 Feb 2003 14:00:23 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h17J7Rt23357 for manet-archive@odin.ietf.org; Fri, 7 Feb 2003 14:07:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17J7Rp23354 for ; Fri, 7 Feb 2003 14:07:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18230 for ; Fri, 7 Feb 2003 13:59:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17IqBp21931; Fri, 7 Feb 2003 13:52:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17Iixp21595 for ; Fri, 7 Feb 2003 13:44:59 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17561 for ; Fri, 7 Feb 2003 13:37:25 -0500 (EST) From: haas@ece.cornell.edu Received: from plato (plato.ece.cornell.edu [128.84.81.135]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id h17If2K29067; Fri, 7 Feb 2003 13:41:02 -0500 Date: Fri, 7 Feb 2003 13:51:32 -0500 (EST) X-X-Sender: To: m c cc: , Zygmunt Haas Subject: Re: [manet] Multicast routing algorithm and implemented router Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Mike, You may want to take a look at: Z.J. Haas and S. Sajama, ``Independent-Tree Ad Hoc Multicast Routing (ITAMAR),'' 2001 Fall Vehicular Technology Conference, Atlantic City, NJ, October 7-11, 2001 The full version of this work is scheduled for MONET publication: Z.J. Haas and S. Sajama, ``Independent-Tree Ad Hoc Multicast Routing (ITAMAR),''ACM MONET journal, special issue on Ad Hoc Networks, vol. 8, no. 5, October 2003 Zygmunt Haas. ====--==-====== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Sun, 2 Feb 2003, m c wrote: > Hello all, > > Just wanted to inform everyone that a new multicast routing algorithm has > been developed and implemented at Virginia Tech. This multicast routing > algorithm has been titled Extensions to Multicast for Mobile Ad-hoc Networks > (XMMAN) and attempts to reduce redundent data rebroadcasts. It seems that > most of the existing multicast algorithms attempt to reduce routing > overhead, but pretty much ignore the problem of data overhead. That is, > multicast routers do not try to aggregate the data flows to reduce > unneccessary data rebroadcasts. This algorithm was first presented in a > masters thesis > (http://scholar.lib.vt.edu/theses/available/etd-08142002-131727/). A REAL > implementation can be found at http://www.irean.vt.edu/navciiti/ (click on > "Resources"). This was written in C under the Linux 2.4 operating system, > but should work in pretty much any Linux environment. Chapter 4: Protocol > of the thesis reads like an internet draft, and should be easy to read. > Have fun! > > Mike > > > > > > _________________________________________________________________ > MSN 8 with e-mail virus protection service: 2 months FREE* > http://join.msn.com/?page=features/virus > > _______________________________________________ > 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 mailnull@www1.ietf.org Fri Feb 7 16:39:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22212 for ; Fri, 7 Feb 2003 16:39:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h17Lkel32636 for manet-archive@odin.ietf.org; Fri, 7 Feb 2003 16:46:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17Lkep32633 for ; Fri, 7 Feb 2003 16:46:40 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22194 for ; Fri, 7 Feb 2003 16:39:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17LXEp31466; Fri, 7 Feb 2003 16:33:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h17LMEp31193 for ; Fri, 7 Feb 2003 16:22:14 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21680 for ; Fri, 7 Feb 2003 16:14:36 -0500 (EST) From: haas@ece.cornell.edu Received: from plato (plato.ece.cornell.edu [128.84.81.135]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id h17LIEK02105; Fri, 7 Feb 2003 16:18:14 -0500 Date: Fri, 7 Feb 2003 16:28:44 -0500 (EST) X-X-Sender: To: cc: Tao Lin , Subject: Re: [manet] Wireless testbed (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , ---------- Forwarded message ---------- Hi Dimosthenis, Just to add on those, we also have ZRP implemented for Linux - it runs in the user space. If you need those for research/educational purposes, we will be happy to provide you the code upon request. Sincerely, ZYgmunt Haas. ===--==-=-===== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Sun, 2 Feb 2003, Tao Lin wrote: > There are many ad hoc protocols implemented in Linux already (without > touching the kernel). Examples include AODV, DSR, OLSR, and TBRPF. You may > also design and implement one by yourself. > > You can setup a real wireless test bed using laptops with 802.11 NICs. You > can also setup a wired testbed to emulate wireless ad hoc networks with a > dynamic switch we developed for this purpose (Refer to io.irean.vt.edu/~tlin > for the free software and the related paper). This dynamic switch is > transparent to all end hosts, does not require any modification at the end > hosts, and can control the topology dynamically during the emulations. > > Best, > > Tao Lin > ECE Dept. > Virginia Tech. > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 8 12:30:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25656 for ; Sat, 8 Feb 2003 12:30:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h18HbZF32263 for manet-archive@odin.ietf.org; Sat, 8 Feb 2003 12:37:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HbZp32260 for ; Sat, 8 Feb 2003 12:37:35 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25649 for ; Sat, 8 Feb 2003 12:29:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HO9p31190; Sat, 8 Feb 2003 12:24:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HFPp31011 for ; Sat, 8 Feb 2003 12:15:25 -0500 Received: from mail.cruzio.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25202 for ; Sat, 8 Feb 2003 12:07:24 -0500 (EST) Received: from caboose.cse.ucsc.edu (dsl3-63-249-65-126.cruzio.com [63.249.65.126]) by mail.cruzio.com with ESMTP id JAA27723 for ; Sat, 8 Feb 2003 09:11:03 -0800 (PST) Message-Id: <5.1.0.14.0.20030208090239.01abb388@mail.cruzio.com> X-Sender: chane@mail.cruzio.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 08 Feb 2003 09:05:15 -0800 To: manet@ietf.org From: "Dr. Obscure" Subject: Re: [manet] 802.11 Ad hoc mode? In-Reply-To: <20030206203816.GF13895@che.onthejob.net> References: <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> <72F06A8F0165D611AD2A00508BCFF600075A8721@FCEXCHANGE> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 02:38 PM 2/6/2003 -0600, David Young wrote: > BTW, this does not seem like a very IETFish question. Is there perhaps a > better venue? Possibly I can persuade my workplace to set up a mailing > list for practical discussions on 802.11 arcana. Yes.. might I suggest the newsgroup comp.std.wireless ? (not quite as interactive, but it works :) --ttfn --chane _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 8 12:43:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26010 for ; Sat, 8 Feb 2003 12:43:31 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h18Hp2U00375 for manet-archive@odin.ietf.org; Sat, 8 Feb 2003 12:51:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18Hp2p00372 for ; Sat, 8 Feb 2003 12:51:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26003 for ; Sat, 8 Feb 2003 12:43:00 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HcMp32288; Sat, 8 Feb 2003 12:38:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HXJp31478 for ; Sat, 8 Feb 2003 12:33:19 -0500 Received: from duck.doc.ic.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25570 for ; Sat, 8 Feb 2003 12:25:17 -0500 (EST) Received: from kiwi.doc.ic.ac.uk ([146.169.2.59] ident=slk) by duck.doc.ic.ac.uk with esmtp (Exim 3.16 #7) id 18hYmf-0004R4-00 for manet@ietf.org; Sat, 08 Feb 2003 17:28:57 +0000 Date: Sat, 8 Feb 2003 17:28:57 +0000 (GMT) From: Sye Loong Keoh To: manet@ietf.org In-Reply-To: <20030208170002.29826.53830.Mailman@www1.ietf.org> Message-ID: References: <20030208170002.29826.53830.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Ad hoc Routing Implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Can anybody show me the pointer to the ad-hoc routing implementation on Linux or windows? I know that there are several implementations on AODV. How about DSR? Anybody knows about these implementations on windows platform? Thanks in advance. ------------------------------------------------ Sye Loong KEOH Distributed Software Engineering (DSE) Group Department of Computing, Imperial College London http://www.doc.ic.ac.uk/~slk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 8 12:57:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26308 for ; Sat, 8 Feb 2003 12:57:07 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h18I4ch00905 for manet-archive@odin.ietf.org; Sat, 8 Feb 2003 13:04:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18I4bp00902 for ; Sat, 8 Feb 2003 13:04:37 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26300 for ; Sat, 8 Feb 2003 12:56:35 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HoJp00322; Sat, 8 Feb 2003 12:50:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18Hjlp32668 for ; Sat, 8 Feb 2003 12:45:47 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25863 for ; Sat, 8 Feb 2003 12:37:45 -0500 (EST) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h18HfPG506195; Sat, 8 Feb 2003 12:41:25 -0500 (EST) Received: from tom ([198.70.228.47]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id AUK73631 (AUTH talin); Sat, 8 Feb 2003 12:41:24 -0500 (EST) Message-ID: <000d01c2cf98$f5cc9800$643f640a@tom> From: "Tao Lin" To: "Sye Loong Keoh" , References: <20030208170002.29826.53830.Mailman@www1.ietf.org> Subject: Re: [manet] Ad hoc Routing Implementation Date: Sat, 8 Feb 2003 12:38:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit You may search online using the key word of "implementation"+the protocol name. At least, I know that AODV, DSR, OLSR, TBRPF, and ZRP are implemented in Linux already. Tao Lin ECE Dept. Virginia Tech. USA ----- Original Message ----- From: "Sye Loong Keoh" To: Sent: Saturday, February 08, 2003 12:28 PM Subject: [manet] Ad hoc Routing Implementation > Hi, > > Can anybody show me the pointer to the ad-hoc routing implementation on > Linux or windows? > > I know that there are several implementations on AODV. How about DSR? > > Anybody knows about these implementations on windows platform? > Thanks in advance. > > > ------------------------------------------------ > Sye Loong KEOH > Distributed Software Engineering (DSE) Group > Department of Computing, Imperial College London > http://www.doc.ic.ac.uk/~slk > _______________________________________________ > 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 mailnull@www1.ietf.org Sat Feb 8 13:03:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26606 for ; Sat, 8 Feb 2003 13:03:52 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h18IBNr01915 for manet-archive@odin.ietf.org; Sat, 8 Feb 2003 13:11:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18IBNp01912 for ; Sat, 8 Feb 2003 13:11:23 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26595 for ; Sat, 8 Feb 2003 13:03:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18HuAp00495; Sat, 8 Feb 2003 12:56:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18Hpep00405 for ; Sat, 8 Feb 2003 12:51:40 -0500 Received: from dhcp.blacksburg.ntc-com.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26026 for ; Sat, 8 Feb 2003 12:43:39 -0500 (EST) Received: (qmail 5813 invoked from network); 8 Feb 2003 17:39:54 -0000 Received: from unknown (HELO Vijay) (204.212.237.190) by dhcp.blacksburg.ntc-com.net with SMTP; 8 Feb 2003 17:39:54 -0000 From: "Vijayanand Ballapuram" To: Date: Sat, 8 Feb 2003 12:49:13 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit Subject: [manet] Zero Conf (configuration with minimum intervention) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi All, I am a student going to work on Zero Configuration Protocols ( configuration with minimum intervention) for Wireless and Mobile Ad hoc Networks for my Thesis. Please let me know research that have been done so far for “Establishing Connectivity and other services” in Wireless Mobile Ahoc Networks with “minimum human intervention”. Also, please point to papers published in this area and research groups working in this specific area. I have read the Internet Draft on “Requirements for Automatic Configuration of IP Hosts “, which states that the Zero Conf protocol can be applied to only · Hosts in the same network. · Hosts in different networks connected by a single router/gateway. So I wanted to know whether Zero Conf protocols can be applied to Mobile Ad Hoc Networks(like ships in sea) where there is possibility of many gateways, as each ship/node needs a Gateway/router to connect with the neighbour nodes which are already on a network. Any suggestions/ pointers, would be greatly appreciated. Thanks in Advance, Vijay _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 8 15:04:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29559 for ; Sat, 8 Feb 2003 15:04:45 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h18KCJ607897 for manet-archive@odin.ietf.org; Sat, 8 Feb 2003 15:12:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18KCJp07894 for ; Sat, 8 Feb 2003 15:12:19 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29546 for ; Sat, 8 Feb 2003 15:04:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18JvYp06829; Sat, 8 Feb 2003 14:57:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h18Jppp06683 for ; Sat, 8 Feb 2003 14:51:51 -0500 Received: from dhcp.blacksburg.ntc-com.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29202 for ; Sat, 8 Feb 2003 14:43:46 -0500 (EST) Received: (qmail 6572 invoked from network); 8 Feb 2003 19:40:02 -0000 Received: from unknown (HELO Vijay) (204.212.237.190) by dhcp.blacksburg.ntc-com.net with SMTP; 8 Feb 2003 19:40:02 -0000 From: "Vijayanand Ballapuram" To: Date: Sat, 8 Feb 2003 14:49:21 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit Subject: [manet] DISTRIBUTED ALGORITHMS Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi All, I request members to give me information regarding “DISTRUBUTED ALGORITHMS” in MANET, which has many potential uses like: · How IP address is allocated when a new NODE joins the network, as there is no central DHCP server. · To allocate Unique Identifiers to each node · For Service Discovery, when a node wants to find which nodes offer specific service and etc. Since, I am working on “Establishing Connectivity and other services” in Wireless Networks (with a Base Station) and also Mobile Ad hoc Networks with “minimum human intervention” I need to understand concepts and functionalities offered by DISTRIBUTED ALGORITHMS. Thanks in Advance, Vijay _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 9 12:21:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02312 for ; Sun, 9 Feb 2003 12:21:30 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h19HTVK11768 for manet-archive@odin.ietf.org; Sun, 9 Feb 2003 12:29:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19HTVp11765 for ; Sun, 9 Feb 2003 12:29:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02305 for ; Sun, 9 Feb 2003 12:20:59 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19HGVp11364; Sun, 9 Feb 2003 12:16:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19H6sp10567 for ; Sun, 9 Feb 2003 12:06:54 -0500 Received: from stephens.ittc.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01837 for ; Sun, 9 Feb 2003 11:58:22 -0500 (EST) Received: from ittc.ku.edu (fiasco.ittc.ku.edu [129.237.125.27]) by stephens.ittc.ku.edu (8.12.6/8.12.6/ITTC-ANTISPAM-ANTIVIRUS-3.0) with SMTP id h19H1xXl024600; Sun, 9 Feb 2003 11:01:59 -0600 From: Pradeepkumar Mani Received: from houston.ittc.ku.edu ([129.237.125.127]) (SquirrelMail authenticated user mpradeep) by secure.ittc.ukans.edu with HTTP; Sun, 9 Feb 2003 11:01:59 -0600 (CST) Message-ID: <3054.129.237.125.127.1044810119.squirrel@secure.ittc.ukans.edu> Date: Sun, 9 Feb 2003 11:01:59 -0600 (CST) Subject: Re: [manet] Ad hoc Routing Implementation To: In-Reply-To: References: <20030208170002.29826.53830.Mailman@www1.ietf.org> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-VirusScan: Clean Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit you can find a Linux implementation of DSR at piconet.sourceforge.net Pradeep > Hi, > > Can anybody show me the pointer to the ad-hoc routing implementation on > Linux or windows? > > I know that there are several implementations on AODV. How about DSR? > > Anybody knows about these implementations on windows platform? > Thanks in advance. > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 9 14:38:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05021 for ; Sun, 9 Feb 2003 14:38:18 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h19JkLA18188 for manet-archive@odin.ietf.org; Sun, 9 Feb 2003 14:46:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19JkKp18185 for ; Sun, 9 Feb 2003 14:46:20 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05011 for ; Sun, 9 Feb 2003 14:37:47 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19JOep16777; Sun, 9 Feb 2003 14:24:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19JC9p16583 for ; Sun, 9 Feb 2003 14:12:09 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04320 for ; Sun, 9 Feb 2003 14:03:36 -0500 (EST) Received: (qmail 16191 invoked by uid 417); 9 Feb 2003 19:07:17 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 9 Feb 2003 19:07:17 -0000 Received: from ankur ([203.94.241.8]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Sun, 09 Feb 2003 12:07:01 -0700 Message-ID: <015701c2d06e$7c94c620$08f15ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: manet@ietf.org Date: Sun, 9 Feb 2003 23:55:58 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0129_01C2D096.CB102560" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Subject: [manet] Multirate Capabilities in Ad Hoc Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0129_01C2D096.CB102560 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Is anybody working on providing multirate services in ad hoc networks at = the MAC layer level? What I mean from multirate is that we can use rate = adaptation according to the channel conditions and then process our MAC = packets accordingly. Right now, in 802.11b, there are four modes = available - 1Mbps, 2 Mpbs, 5.5 Mbps (or 6 Mpbs) and 11 Mbps.=20 Everybody would like to send the data at 11 Mbps. But there could be = some scenarios where we don't need to send at such high speed e.g. = control packets, reply to signal packets while in sleep mode. Besides = saving limited bandwidth, it will be very useful in saving power. Here, = we can have two types of adpatation - either sender based or receiver = based.=20 Has anybody doing research on providing multirate capabilities together = with a good power-saving protocol.=20 Best Regards Ankur=20 ************************************************ ankurjain@softhome.net http://www.geocities.com/ankurjain009/ ************************************************ -------------------------------------------------------------------------= ----------------------------------------------------------------------- Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia = Space Shuttle - STS 107 " The paths from dreams to success does exist, May you have the vision to find it,=20 the courage to get on to it,=20 and the perseverance to follow it.=20 Wishing you a great journey !" -------------------------------------------------------------------------= ----------------------------------------------------------------------- ------=_NextPart_000_0129_01C2D096.CB102560 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
Is anybody working on providing = multirate services=20 in ad hoc networks at the MAC layer level? What I mean from multirate is = that we=20 can use rate adaptation according to the channel conditions and then = process our=20 MAC packets accordingly. Right now, in 802.11b, there are four modes = available -=20 1Mbps, 2 Mpbs, 5.5 Mbps (or 6 Mpbs) and 11 Mbps.
 
Everybody would like to send the data = at 11 Mbps.=20 But there could be some scenarios where we don't need to send at such = high speed=20 e.g. control packets, reply to signal packets while in sleep mode. = Besides=20 saving limited bandwidth, it will be very useful in saving power. = Here, we=20 can have two types of adpatation - either sender based or receiver = based.=20
 
Has anybody doing research on providing = multirate=20 capabilities together with a good power-saving protocol.
 
Best Regards
Ankur
 
 
 
************************************************
ankurjain@softhome.net
http://www.geocities.com/= ankurjain009/
 
************************************************
 
----------------------------------------------------------------= -------------------------------------------------------------------------= -------
Dr.=20 Kalpana Chawla, Indian born astronaut said in an email from Columbia = Space=20 Shuttle - STS 107
 
" The paths from dreams to success does = exist,
   May you have the vision to find it, =
   the=20 courage to get on to it,
  and the perseverance to follow it.=20
   Wishing you a great journey=20 !"
-------------------------------------------------------------------= -------------------------------------------------------------------------= ----
------=_NextPart_000_0129_01C2D096.CB102560-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Feb 9 19:57:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10513 for ; Sun, 9 Feb 2003 19:57:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1A15Z231333 for manet-archive@odin.ietf.org; Sun, 9 Feb 2003 20:05:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1A15Zp31330 for ; Sun, 9 Feb 2003 20:05:35 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10502 for ; Sun, 9 Feb 2003 19:56:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1A0hQp30867; Sun, 9 Feb 2003 19:43:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1A0Wap30031 for ; Sun, 9 Feb 2003 19:32:36 -0500 Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09973 for ; Sun, 9 Feb 2003 19:23:57 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by ece.rice.edu (Postfix) with SMTP id C127468A7B; Sun, 9 Feb 2003 18:27:37 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by ece.rice.edu (Postfix) with ESMTP id 67EEF68A78; Sun, 9 Feb 2003 18:27:37 -0600 (CST) Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74]) by ece.rice.edu (Postfix) with ESMTP id 1D4A868A5B; Sun, 9 Feb 2003 18:27:36 -0600 (CST) Received: from localhost (kanodia@localhost) by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id SAA18619; Sun, 9 Feb 2003 18:27:35 -0600 X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs Date: Sun, 9 Feb 2003 18:27:35 -0600 (CST) From: Vikram Kanodia X-Sender: kanodia@egress.ece.rice.edu To: Ankur Jain Cc: manet@ietf.org Subject: Re: [manet] Multirate Capabilities in Ad Hoc Networks In-Reply-To: <015701c2d06e$7c94c620$08f15ecb@ankur> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Check out: @InProceedings{SKSK02, author = {B. Sadeghi and V. Kanodia and A. Sabdharwal and E. Knightly}, title = {Opportunistic Media Access for Multirate Ad Hoc Networks}, booktitle = {Proceedings of {ACM} MOBICOM 2002}, year = {2002}, address = {Atlanta, Georgia}, month = {sept}, } and @Inproceedings{HVB01, author = {G. Holland and N. Vaidya and P. Bahl}, title = {A Rate-adaptive {MAC} protocol for multi-hop wireless networks}, booktitle = {Proceedings of ACM {MobiCom} 2001}, year = 2001, address = {Rome, Italy}, } -Vikram > Hello, > > Is anybody working on providing multirate services in ad hoc networks at the MAC layer level? What I mean from multirate is that we can use rate adaptation according to the channel conditions and then process our MAC packets accordingly. Right now, in 802.11b, there are four modes available - 1Mbps, 2 Mpbs, 5.5 Mbps (or 6 Mpbs) and 11 Mbps. > > Everybody would like to send the data at 11 Mbps. But there could be some scenarios where we don't need to send at such high speed e.g. control packets, reply to signal packets while in sleep mode. Besides saving limited bandwidth, it will be very useful in saving power. Here, we can have two types of adpatation - either sender based or receiver based. > > Has anybody doing research on providing multirate capabilities together with a good power-saving protocol. > > Best Regards > Ankur > > > > ************************************************ > ankurjain@softhome.net > http://www.geocities.com/ankurjain009/ > > ************************************************ > > ------------------------------------------------------------------------------------------------------------------------------------------------ > Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia Space Shuttle - STS 107 > > " The paths from dreams to success does exist, > May you have the vision to find it, > the courage to get on to it, > and the perseverance to follow it. > Wishing you a great journey !" > ------------------------------------------------------------------------------------------------------------------------------------------------ > -- Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H) WWW: http://www.ece.rice.edu/~kanodia _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 05:45:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03731 for ; Mon, 10 Feb 2003 05:45:29 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AArpK06500 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 05:53:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AArpp06497 for ; Mon, 10 Feb 2003 05:53:51 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03716 for ; Mon, 10 Feb 2003 05:44:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AAddp06002; Mon, 10 Feb 2003 05:39:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AAUxp05147 for ; Mon, 10 Feb 2003 05:30:59 -0500 Received: from tounes103.gw.tn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03295 for ; Mon, 10 Feb 2003 05:22:02 -0500 (EST) Received: from tounes-22.ati.tn (tounes-22.ati.tn [193.95.66.22]) by tounes.tngw.tn (8.8.8/8.8.8) with ESMTP id LAA04370 for ; Mon, 10 Feb 2003 11:26:39 -0100 (GMT) Received: from smtp.planet.tn ([193.95.67.167]) by tounes-22.ati.tn (8.11.6/8.11.6) with ESMTP id h1A9Ppa01167 for ; Mon, 10 Feb 2003 11:25:51 +0200 (EET) Received: from planet.tn ([193.95.96.86]) by smtp.planet.tn (8.11.6/8.11.6) with ESMTP id h1ACQwO21242 for ; Mon, 10 Feb 2003 11:26:59 -0100 (GMT) Message-ID: <3E477CF3.4ABF0197@planet.tn> Date: Mon, 10 Feb 2003 11:20:35 +0100 From: Farouk Kamoun X-Mailer: Mozilla 4.7 [fr] (Win95; U) X-Accept-Language: fr MIME-Version: 1.0 To: manet Content-Type: multipart/mixed; boundary="------------9236F009380185EBDF96E88F" Subject: [manet] Med-Hoc-Net 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Il s'agit d'un message multivolet au format MIME. --------------9236F009380185EBDF96E88F Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Would you please annouce the following Call for Papers for the 2nd Mediterranean Workshop on Ad-Hoc Networks Thank you Farouk Kamoun 2nd Mediterranean Workshop on Ad-Hoc Networks MED-HOC NET 2003 Mahdia, Tunisia, June 25-27, 2003 First Call for papers The second Med-Hoc-Net 2003 is a major annual international workshop in the Mediterrnean region. It brings together researchers, technologists and visionaries from academia, research labs, and industry, engineers and students to exchange, discuss and share their experiences, new ideas and research about theoretical and practical aspects of ad-hoc networking. The Med-Hoc-Net 2003 second edition intends to build upon the background of the previous workshop Med-Hoc-Net 2002 held in Sardegna, Italy, by presenting theoretical and practical achievements and advances in the field, current research, experience reports, ongoing prototyping efforts, case studies, and description of innovative ad hoc systems. Keynote Speaker : Leonard Kleinrock (UCLA) “Ubiquitous Computing” Topics will include (but are not limited to): · Innovative applications · Multimedia applications middleware for support in ad hoc networks and real time transports over ad hoc networks · Pilot projects, test beds, implementations · Sensor networks · Embedded systems · Resource discovery, network reconfiguration and self organization · Multimedia location services · QoS oriented multi-hop mobile network architectures, Intserv, Diffserv, MPLS etc. · QoS support in Bluetooth, HomeRF, Hiperlan, IEEE 802.11 etc. · QoS enabling ad hoc network prototypes · Call admission and traffic control policies for ad hoc networks · Congestion control · Transport protocols · Fault tolerance and error recovery · Security in ad hoc networks · Interconnection between ad hoc and wired networks · Unicast and multicast routing in ad hoc multi-hop wireless networks · Scheduling radio resource sharing and MAC protocols for multi-hop networks · Signal processing algorithms (coding, compression) for ad hoc networks · Power management and control algorithms · Performance evaluation of QoS oriented protocols, middleware and applications via measurements, analytical models or simulation · Metrology, Ad-Hoc network measurement Tools Steering Committee: Farouk Kamoun (ENSI, Tunisia) Mario Gerla (UCLA, USA) Guy Pujolle (LIP6, France) Khaldoun Al Agha (LRI, France) Giovanni Pau (UCLA, USA) Program Chair: Abdelfettah Belghith (ENSI, Tunisia) Program Co-chair: Sami Tabbane (SUPCOM, Tunisia) Program Committee: Amine Benkiran (EMI, Morocco) Anne Fladenmuller (LIP6, France) Augusto Casaca (INESC, Portugal) Bernhard Walke (Comnets, Germany) Christophe Diot (Sprint Labs, USA) Farouk Kamoun (ENSI, Tunisia) Fouad Tobagi (Stanford Univ, USA) Gerard LeLann (INRIA, France) Giovanni Pau (UCLA, USA) Guy Omidyar (CWC, Singapore) Guy Pujolle (LIP6, France) Hamid Aghvami (King’s College London, UK) Houssam Afifi (INT, France) Jan Slavik (Testcom, Czech Republic) Jean-Marie Bonnin (ENST-Bretagne, France) Khaldoun Al Agha (LRI, France) Luigi Fratta (Polimi, Italy) Mario Gerla (UCLA, USA) Michel Diaz (LAAS, France) Otto Duarte (UFRJ, Brazil) Parviz Kermani (IBM, USA) Philippe Jacquet (INRIA, France) Pierre Rolin (FTRD, France) Raouf Boutaba (Waterloo, Canada) Ramon Puigjaner (Baleares Univ, Spain) Samir Thomé (ENST, France) Serge Fdida (LIP6, France) Sergio Palazzo (Catania Univ, Italy)) Tomas Robles Valladares (ETSI, Spain) Volker Tschamer (GMD, Gernany) Walid Dabbous (INRIA, France) Authors are invited to submit electronically original contributions in the conference themes and related topics. Papers should not be longer than 12 pages. All submitted papers will be reviewed and evaluated on the basis of relevance, originality, technical quality and clarity. Accepted papers will be included in the conference proceedings. The official workshop oral and written language is English. Paper Submission Deadlines Full Paper Electronic Submission : 15 March 2003 Notification of acceptance/Rejection : 15 April 2003 Camera ready submission of full papers: 15 May 2003 Papers must be submitted by email to: Abdelfattah.belghith@ensi.rnu.tn and frk.kamoun@planet.tn . All information, news and links will be available at the address : http://www.cck.rnu.tn/medhoc2003 Workshop organized by : CRISTAL Laboratory, Ecole Nationale des Sciences de l’Informatique, University of Manouba Tunisia. With the collaboration of : LIP6 Laboratory, University of Paris VI, France. Wireless Adaptive Mobility (WAM) Laboratory, Computer Science Dpt., UCLA, USA. UTIC Laboratory , Ecole Supérieure des Communications, Tunis, Tunisia LRI Laboratory, France. Workshop sponsored by : IFIP-TC6-WG6.8 --------------9236F009380185EBDF96E88F Content-Type: text/x-vcard; charset=us-ascii; name="frk.kamoun.vcf" Content-Description: Carte pour Farouk Kamoun Content-Disposition: attachment; filename="frk.kamoun.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Kamoun;Farouk tel;cell:+216 98 32 80 83 tel;fax:+216 71 600 449 tel;home:+216 71 775 707 tel;work:+216 71 744 065 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:frk.kamoun@planet.tn fn:Farouk Kamoun end:vcard --------------9236F009380185EBDF96E88F-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 12:20:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16498 for ; Mon, 10 Feb 2003 12:20:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AHSvt29709 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 12:28:57 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AHSup29706 for ; Mon, 10 Feb 2003 12:28:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16486 for ; Mon, 10 Feb 2003 12:19:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AHFkp29041; Mon, 10 Feb 2003 12:15:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AHAGp28889 for ; Mon, 10 Feb 2003 12:10:16 -0500 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15706 for ; Mon, 10 Feb 2003 12:00:53 -0500 (EST) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id h1AHDS8x006523; Mon, 10 Feb 2003 15:13:28 -0200 Message-ID: <00c401c2d130$1f1a2e00$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Mon, 10 Feb 2003 15:13:32 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit Subject: [manet] Autoconfiguration protocols Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi all, I would like to know which Autoconfiguration protocol would have the best concept based on performance taking into account the following issues: Initialization of network New node joining a network Concurrent initiation of address allocation Departure of nodes (graceful and abrupt) Network partition and merger Message losses Broadcast storm Would it be viable to implement it on a real environment? --------------------------------------------------- Fábio Mesquita Buiati Universidade de Brasília - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 14:01:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20902 for ; Mon, 10 Feb 2003 14:01:02 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AJ9Xt04347 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 14:09:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AJ9Wp04344 for ; Mon, 10 Feb 2003 14:09:32 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20881 for ; Mon, 10 Feb 2003 14:00:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AIsqp03115; Mon, 10 Feb 2003 13:54:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AIq5p02960 for ; Mon, 10 Feb 2003 13:52:05 -0500 Received: from fsc.cpsc.ucalgary.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20249 for ; Mon, 10 Feb 2003 13:43:01 -0500 (EST) Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.7/8.12.7) with ESMTP id h1AIkgqd004664 for ; Mon, 10 Feb 2003 11:46:42 -0700 Received: from cpsc.ucalgary.ca (ict720f [136.159.17.10]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id h1AIkfMP000721 for ; Mon, 10 Feb 2003 11:46:41 -0700 Message-ID: <3E47F391.9030004@cpsc.ucalgary.ca> Date: Mon, 10 Feb 2003 11:46:41 -0700 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-1.3 required=7.5 tests=NOSPAM_INC,SPAM_PHRASE_01_02,TO_LOCALPART_EQ_REAL, USER_AGENT,USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG version=2.43 Content-Transfer-Encoding: 7bit Subject: [manet] Questions regarding APE Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am using Cisco Aironet 350 wireless cards on the laptop and I was concerned if the APE testbed would work with them or not (I know that APE supports Orinoco). Is there anyone who has used Aironet 35X cards on APE? There is another issue that is bothering me. Everytime I boot into Linux after running APE, I get the message that the filesystem was not cleanly unmounted and then Linux proceeds to check the filesystem. This not only happened with my compiled distribution of APE, but also with the zip version of APE availaible on the APE website. Is anyone else also facing a similar problem? If yes, what is the solution to this problem? Thanks. Abhinav. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 14:55:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22803 for ; Mon, 10 Feb 2003 14:55:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AK4FN07345 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 15:04:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AK4Fp07342 for ; Mon, 10 Feb 2003 15:04:15 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22779 for ; Mon, 10 Feb 2003 14:55:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AJjKp06448; Mon, 10 Feb 2003 14:45:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AJevp06275 for ; Mon, 10 Feb 2003 14:40:57 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21796 for ; Mon, 10 Feb 2003 14:31:55 -0500 (EST) Received: from photon.ece.cornell.edu (photon.ece.cornell.edu [128.84.81.138]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id h1AJZUK09496; Mon, 10 Feb 2003 14:35:30 -0500 Date: Mon, 10 Feb 2003 14:32:08 -0500 (EST) From: Edward Hua X-X-Sender: eyh5@photon.ece.cornell.edu To: Abhinav Gupta cc: manet Subject: Re: [manet] Questions regarding APE In-Reply-To: <3E47F391.9030004@cpsc.ucalgary.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I believe Aironet 350 works with APE (as well as the 340 series). I also had the unclean unmount problem as you described. I was using a previous release of APE (0.3). If I remember right, the APE documentation mentioned it was a known issue. Since APE has a newer version now, if the problem is still there, perhaps the APE folks haven't figured out a solution yet. As far as I can tell, this unclean unmount doesn't interfere with either your APE or linux performance, so you can live with that. -Ed On Mon, 10 Feb 2003, Abhinav Gupta wrote: > Hi, > > I am using Cisco Aironet 350 wireless cards on the laptop and I was > concerned if the APE testbed would work with them or not (I know that > APE supports Orinoco). Is there anyone who has used Aironet 35X cards on > APE? > > There is another issue that is bothering me. Everytime I boot into Linux > after running APE, I get the message that the filesystem was not cleanly > unmounted and then Linux proceeds to check the filesystem. This not only > happened with my compiled distribution of APE, but also with the zip > version of APE availaible on the APE website. Is anyone else also facing > a similar problem? If yes, what is the solution to this problem? > > Thanks. > > Abhinav. > > > _______________________________________________ > 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 mailnull@www1.ietf.org Mon Feb 10 17:45:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28864 for ; Mon, 10 Feb 2003 17:45:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AMsDT18776 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 17:54:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMsDp18773 for ; Mon, 10 Feb 2003 17:54:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28731 for ; Mon, 10 Feb 2003 17:44:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMcTp18149; Mon, 10 Feb 2003 17:38:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMZPp17350 for ; Mon, 10 Feb 2003 17:35:25 -0500 Received: from titania.wins.hrl.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28348 for ; Mon, 10 Feb 2003 17:26:17 -0500 (EST) Received: from static (dhcp2-227.wins.hrl.com [206.17.239.227]) by titania.wins.hrl.com (8.10.2+Sun/8.9.3) with SMTP id h1AMTm216730; Mon, 10 Feb 2003 14:29:48 -0800 (PST) Reply-To: From: "Gavin Holland" To: "Ankur Jain" , Subject: RE: [manet] Multirate Capabilities in Ad Hoc Networks Date: Mon, 10 Feb 2003 14:29:48 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <015701c2d06e$7c94c620$08f15ecb@ankur> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OlkEid: 7CE48121FBE90AFB50BDE047B58AF5AAF36504BF Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Ankur, You can get a copy of our Mobicom '01 paper from here: http://citeseer.nj.nec.com/446806.html We will also have a paper shortly on routing over multirate links. The problem we identified is that routing protocols commonly discover routes by broadcasting; which, in 802.11, must go out at one of the rates in the basic rate set. However, because of the range/rate tradeoff, routes discovered at the broadcast rate may not be optimal. For instance, a route request broadcast at a low rate may discover a one hop route that is unusable at a higher rate, forcing all traffic on that route to use the low rate. Whereas, broadcasting the same route request at a higher rate may discover a multiple hop route with higher capacity. Thus, our approach is to make route discovery rate dependent. We are evaluating two protocols, one is to broadcast multiple route requests at different rates (ensuring that each rebroadcast goes out at the initial rate), the other is to broadcast at the lowest rate and have each intermediate node annotate the route with the best rate for the preceding link. Once the rates are known, routes can be selected according to whatever desirable criterion (e.g. highest capacity, highest reliability). -Gavin -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org]On Behalf Of Ankur Jain Sent: Sunday, February 09, 2003 10:26 AM To: manet@ietf.org Subject: [manet] Multirate Capabilities in Ad Hoc Networks Hello, Is anybody working on providing multirate services in ad hoc networks at the MAC layer level? What I mean from multirate is that we can use rate adaptation according to the channel conditions and then process our MAC packets accordingly. Right now, in 802.11b, there are four modes available - 1Mbps, 2 Mpbs, 5.5 Mbps (or 6 Mpbs) and 11 Mbps. Everybody would like to send the data at 11 Mbps. But there could be some scenarios where we don't need to send at such high speed e.g. control packets, reply to signal packets while in sleep mode. Besides saving limited bandwidth, it will be very useful in saving power. Here, we can have two types of adpatation - either sender based or receiver based. Has anybody doing research on providing multirate capabilities together with a good power-saving protocol. Best Regards Ankur ************************************************ ankurjain@softhome.net http://www.geocities.com/ankurjain009/ ************************************************ ---------------------------------------------------------------------------- -------------------------------------------------------------------- Dr. Kalpana Chawla, Indian born astronaut said in an email from Columbia Space Shuttle - STS 107 " The paths from dreams to success does exist, May you have the vision to find it, the courage to get on to it, and the perseverance to follow it. Wishing you a great journey !" ---------------------------------------------------------------------------- -------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 18:01:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29498 for ; Mon, 10 Feb 2003 18:01:18 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AN9t620463 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 18:09:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AN9tp20460 for ; Mon, 10 Feb 2003 18:09:55 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29464 for ; Mon, 10 Feb 2003 18:00:47 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMoJp18618; Mon, 10 Feb 2003 17:50:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMnvp18554 for ; Mon, 10 Feb 2003 17:49:57 -0500 Received: from iron.cs.umanitoba.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28637 for ; Mon, 10 Feb 2003 17:40:49 -0500 (EST) Received: from silver.cs.umanitoba.ca (silver.cs.umanitoba.ca [130.179.28.34]) by iron.cs.umanitoba.ca (8.11.6+Sun/8.8.5) with ESMTP id h1AMiUE10987 for ; Mon, 10 Feb 2003 16:44:31 -0600 (CST) Received: from localhost (lianglei@localhost) by silver.cs.umanitoba.ca (8.11.6+Sun/8.8.5) with ESMTP id h1AMiUo17386 for ; Mon, 10 Feb 2003 16:44:30 -0600 (CST) X-Authentication-Warning: silver.cs.umanitoba.ca: lianglei owned process doing -bs Date: Mon, 10 Feb 2003 16:44:30 -0600 (CST) From: Lei Liang To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] How to apply java to NS2? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, all, I would like to implement a protocol written in Java and integrate it into NS2 for test. how to achieve this? I know java can communicate with C++ by JNI, but the program entry must be located in java program. anybody could give me suggestions? Thanks in advance. Lei _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 18:12:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29807 for ; Mon, 10 Feb 2003 18:12:12 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1ANKnt20975 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 18:20:49 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANKnp20972 for ; Mon, 10 Feb 2003 18:20:49 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29787 for ; Mon, 10 Feb 2003 18:11:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AN7Zp20384; Mon, 10 Feb 2003 18:07:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AN6gp19647 for ; Mon, 10 Feb 2003 18:06:42 -0500 Received: from smtp1.utdallas.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29347 for ; Mon, 10 Feb 2003 17:57:34 -0500 (EST) Received: from DSL08 (dsl08.utdallas.edu [129.110.94.81]) by smtp1.utdallas.edu (Postfix) with SMTP id 24D7C388D28; Mon, 10 Feb 2003 17:01:12 -0600 (CST) Message-ID: <003901c2d158$4e7c4750$515e6e81@campus.ad.utdallas.edu> From: "Mansoor Mohsin" To: =?iso-8859-1?Q?F=E1bio_Buiati?= Cc: References: <00c401c2d130$1f1a2e00$0e43a8c0@piqui> Subject: Re: [manet] Autoconfiguration protocols Date: Mon, 10 Feb 2003 17:01:12 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C2D126.03CEC480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C2D126.03CEC480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Sanket Nasergi and Ravi Prakash have a paper in INFOCOM 2002 on node = autoconfiguration in MANETs. There is another paper in MILCOM 2002 by = myself and Ravi Prakash on the same topic but with a different approach. = Both the papers give distributed algorithms for node autoconfiguration = taking into account network initialization, arrival of new node, node = departure, network partitioing and merging, and message losses, etc. The papers can be downloaded using the following links: http://www.utdallas.edu/~ravip/papers/infocom2002.pdf http://www.utdallas.edu/~mmohsin/publications/IPAssignment.pdf -------------------------------------------------------------------------= ------- Mansoor Mohsin=20 ----- Original Message -----=20 From: "F=E1bio Buiati" To: Sent: Monday, February 10, 2003 12:13 PM Subject: [manet] Autoconfiguration protocols > Hi all, >=20 > I would like to know which Autoconfiguration protocol would have the = best > concept based on performance taking into account the following issues: >=20 > Initialization of network > New node joining a network > Concurrent initiation of address allocation > Departure of nodes (graceful and abrupt) > Network partition and merger > Message losses > Broadcast storm >=20 > Would it be viable to implement it on a real environment? > --------------------------------------------------- > F=E1bio Mesquita Buiati > Universidade de Bras=EDlia - UnB - Brazil > email - fabio@redes.unb.br > --------------------------------------------------- >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > ------=_NextPart_000_0036_01C2D126.03CEC480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Sanket = Nasergi and=20 Ravi Prakash have a paper in INFOCOM 2002 on node autoconfiguration in = MANETs.=20 There is another paper in MILCOM 2002 by myself and Ravi Prakash on the = same=20 topic but with a different approach. Both the=20 papers give distributed algorithms for node autoconfiguration = taking=20 into account network initialization, arrival of new node, node = departure,=20 network partitioing and merging, and message losses, etc.
 
The = papers can be=20 downloaded using the following links:
http://www= .utdallas.edu/~ravip/papers/infocom2002.pdf
h= ttp://www.utdallas.edu/~mmohsin/publications/IPAssignment.pdf<= /DIV>

Mansoor = Mohsin=20
 
 
----- Original Message = -----=20
From: "F=E1bio Buiati" = <fabio@redes.unb.br>
To: <manet@ietf.org>
Sent: Monday, February = 10, 2003=20 12:13 PM
Subject: [manet] = Autoconfiguration=20 protocols

> Hi all,
>
> I = would like to=20 know which Autoconfiguration protocol would have the best
> = concept based=20 on performance taking into account the following issues:
> =
>=20 Initialization of network
> New node joining a network
> = Concurrent=20 initiation of address allocation
> Departure of nodes (graceful = and=20 abrupt)
> Network partition and merger
> Message = losses
>=20 Broadcast storm
>
> Would it be viable to implement it on a = real=20 environment?
> = ---------------------------------------------------
>=20 F=E1bio Mesquita Buiati
> Universidade de Bras=EDlia - UnB - = Brazil
>=20 email - fabio@redes.unb.br
>=20 ---------------------------------------------------
>
>=20 _______________________________________________
> manet mailing=20 list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> ------=_NextPart_000_0036_01C2D126.03CEC480-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 18:39:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00621 for ; Mon, 10 Feb 2003 18:39:19 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1ANlvs22791 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 18:47:57 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANlvp22788 for ; Mon, 10 Feb 2003 18:47:57 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00598 for ; Mon, 10 Feb 2003 18:38:45 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANXRp21464; Mon, 10 Feb 2003 18:33:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANW2p21396 for ; Mon, 10 Feb 2003 18:32:02 -0500 Received: from SMTP1.ECE.NEU.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00074 for ; Mon, 10 Feb 2003 18:22:52 -0500 (EST) 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 h1ANQZMh003132 for ; Mon, 10 Feb 2003 18:26:35 -0500 (EST) Received: from bibbiena.ece.neu.edu ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.0.0.44) with SMTP id M2003021018263408205 for ; Mon, 10 Feb 2003 18:26:34 -0500 Received: from localhost (basagni@localhost) by bibbiena.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id h1ANQYC07705 for ; Mon, 10 Feb 2003 18:26:34 -0500 (EST) X-Authentication-Warning: bibbiena.ece.neu.edu: basagni owned process doing -bs Date: Mon, 10 Feb 2003 18:26:34 -0500 (EST) From: Stefano Basagni X-X-Sender: basagni@bibbiena To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] IEEE PERCOM 2003, Call for Participation and Advance Program Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We apologize if you receive multiple copies of this Call for Participation. ***************************************************** CALL FOR PARTICIPATION & ADVANCE PROGRAM ***************************************************** ----------------------------------------------------- PerCom 2003 IEEE INTERNATIONAL CONFERENCE ON PERVASIVE COMPUTING AND COMMUNICATIONS http://www.PerCom.org ----------------------------------------------------- DATES : March 23-26, 2003 VENUE : RADISSON PLAZA HOTEL, FORT WORTH ADVANCE REGISTRATION DUE BY February 28, 2003 ----------------------------------------------------- Co-sponsors: IEEE Computer Society and The University of Texas at Arlington ----------------------------------------------------- PROGRAM HIGHLIGHTS ------------------ * 53 Full Papers * 11 Short Papers * 2 Keynote Addresses * 2 Panels * 3 Tutorials (Sunday, March 23) * Demonstrations TUTORIALS *********** SUNDAY, MARCH 23, 2003 ###################### 8:30 - 12:30 PM (in Parallel) ------------------------------ Tutorial 1: Spray Computers: Explorations in Self-Organization for Pervasive Computing Tutorial 3: Security Issues in Pervasive IP Networks 2 :00 - 6:00 PM ---------------- Tutorial 2: Mobile Commerce: Issues, Applications and Technologies Tutorial 4 : TBD ADVANCE TECHNICAL PROGRAM ************************* MONDAY, MARCH 24, 2003 ####################### 9:00 - 9:30 AM --------------- WELCOME ADDRESS 9:30 - 10:30 AM --------------- KEYNOTE ADDRESS I New Horizons for Mobile Computing Speaker: Roy Want, Intel Research, Santa Clara, USA 10:30-11:00 AM COFFEE BREAK 11:00 to 12:30 PM ----------------- SESSION PC-1: MIDDLEWARE SERVICES __________________________________ Portability, Extensibility and Robustness in iROS S. R. Ponnekanti, B. Johanson, E. Kiciman and A. Fox Stanford University, USA Touch-and-Connect: A Connection Request Framework for Ad-hoc Networks and the Pervasive Computing Environment Y. Iwasaki, N. Kawaguchi, and Y. Inagaki Nagoya University, JAPAN Application-Service Interoperation without Standardized Service Interfaces S. R. Ponnekanti and A. Fox Stanford University, USA SESSION PC-2: SENSOR NETWORKS ___________________________ Node-level Energy Management for Sensor Networks in the Presence of Multiple Applications A. Boulis and M. Srivastava University of California, Los Angeles, USA Energy-Optimal and Energy-Balanced Sorting in a Single-Hop Sensor Network M. Singh and V. K. Prasanna University of Southern California, USA Energy-Aware Target Localization in Wireless Sensor Networks Y. Zou and K. Chakrabarty Duke University, USA SESSION MA-1: UBIQUITOUS SERVICES __________________________________ Seamless Service Platform for Following a User's Movement in a Dynamic Network Environment K. Takasugi, M. Nakamura, S. Tanaka, and M. Kubota NTT, JAPAN WiFi Bridge: wireless mobility framework supporting session continuity A. Calvagna, G. Morabito, and A. La Corte University of Catania, ITALY Self-Routing in Pervasive Computing Environments using Smart Messages C. Borcea, C. Intanagonwiwat, A. Saxena, Rutgers University, USA and Liviu Iftode, University of Maryland, College Park, USA --------------------- 12:30 - 2:00 PM LUNCH ---------------------- 2:00 to 3:30 PM ------------------ SESSION PC-3: PERVASIVE COMPUTING ENVIRONMENTS _____________________________________________ Movement Awareness in a Sentient Environment R. Headon, University of Cambridge, GREAT BRITAIN Adaptive Offloading Inference for Delivering Applications in Pervasive Computing Environments X. Gu, K. Nahrstedt, Univ of Illinois at Urbana-Champaign, USA A. Messer, I. Greenberg, and D. Milojicic Hewlett Packard Laboratories, ARGENTINA An architecture that treats everyday objects as communicating tangible components A. Kameas, Computer Technology Institute, GREECE S. Bellis, NMRC, IRELAND I. Mavrommati, Computer Technology Institute, GREECE Kieran Delaney, NMRC, IRELAND A. Pounds-Cornish and M. Colley, Univ of Essex, GREAT BRITAIN SESSION PC-4: PERVASIVE ENVIRONMENTS ______________________________________ Using Personnel Movements For Indoor Autonomous Environment Discovery R. Harle and A. Hopper University of Cambridge, GREAT BRITAIN Providing Contextual Information to Pervasive Computing Applications G. Judd and P. Steenkiste Carnegie Mellon University, USA WLAN Location Determination via Clustering and Probability Distributions M. Youssef, A. Agrawala, and U. Shankar University of Maryland at College Park, USA SESSION MA-2: CONTEXT AWARE COMPUTING _______________________________________ Trust for Ubiquitous, Transparent Collaboration B. Shand, N. Dimmock, and J. Bacon, University of Cambridge, GREAT BRITAIN Collaborative Context Recognition for Handheld Devices J. Mantyjarvi and J. Himberg Nokia Research Center, FINLAND Dynamic Application Composition: Customizing the Behavior of an Active Space M. Roman, B. Ziebart, and R. Campbell University of Illinois at Urbana Champaign, USA 3:30-4:00 Pm COFFEE BREAK 4:00 to 5:30 PM ------------------ SESSION PC-5: Ad Hoc Networks _____________________________ On Security Study of Two Distance Vector Routing Protocols for Mobile Ad Hoc Networks W. Wang, Y. Lu, and B. Bhargava Purdue University, USA Study of Distance Vector Routing Protocols for Mobile Ad Hoc Networks Y. Lu, W. Wang, Y. Zhong, and B. Bhargava Purdue University, USA Dynamic Bandwidth Management for Single-hop Ad hoc Wireless Networks S. Shah, K. Chen, and K. Nahrstedt University of Illinois at Urbana-Champaign, USA SESSION PC-6: LOCATION-AWARE SYSTEMS ________________________________________ Location-based E-campus Web Services: From Design to Deployment S. Koo, C. Rosenberg, H. H. Chan, and Y. C. Lee Purdue University, USA A Privacy-Oriented Broadband Ultrasonic Location System M. Hazas, University of Cambridge, GREAT BRITAIN and Andy Ward, formerly of AT&T Laboratories, Cambridge, GREAT BRITAIN Indirect Routing Using Distributed Location Information A. Viana, M. Amorim, S. Fdida, and J. Rezende Universite Pierre et Marie Curie, FRANCE SESSION MA-3: RESOURCE IDENTIFICATION AND NAMING ___________________________________________________ Splendor: A Secure, Private, and Location-aware Service Discovery Protocol Supporting Mobile Services F. Zhu and M. Mutka, Michigan State University, USA L. Ni, Hong Kong University of Science & Technology, Hong Kong Context-Sensitive Resource Discovery G. Chen and D. Kotz, Dartmouth College, USA Smart Identification Frameworks for Ubiquitous Computing Applications K. Roemer, T. Schoch, F. Mattern, and T. Duebendorfer ETH Zurich, SWITZERLAND TUESDAY MARCH 25, 2003 ########################### 9:30-10:30 AM - KEYNOTE ADDRESS II, Aaron Bobick, Georgia Institute of Technology ____________________________________ 11:00 to 12:30 PM ----------------- SESSION PC-7: LOCATION-BASED SERVICES ______________________________________ PILGRIM: A Location Broker and Mobility-Aware Recommendation System M. Brunato and R. Battiti, Universita di Trento, ITALY Location-Detection Strategies in Pervasive Computing Environments S. Fischmeister, G. Menkhaus, and A. Stumpfl University of Salzburg, AUSTRIA Dealing with Continuous Location-Dependent Queries: Just-in-Time Data Refreshment S. Ilarri and E. Mena, University of Zaragoza, SPAIN A. Illarramendi, University of the Basque Country SESSION PC-8: NETWORKING ISSUEs _________________________________ Evaluation of Kalman Filtering for Network Time Keeping A. Bletsas and A. Lippman Massachusetts Institute of Technology, USA Spatial Index On Air B. Zheng, Hong Kong University of Science and Technology, Hong Kong W.-C. Lee, The Penn State University, USA D. L. Lee, Hong Kong University of Science and Technology, Hong Kong Using Peer-to-Peer Data Routing for Infrastructure-based Wireless Networks S. Kodeswaran,O. Ratsimor, A. Joshi, T. Finin, and Y. Yesha University of Maryland, Baltimore County, USA SESSION IE-1: PHILOSOPHY OF INTELLIGENT ENVIRONMENTS _______________________________________________________ Steerable Interfaces for Pervasive Computing Spaces G. Pingali, C. Pinhanez, A. Levas, R. Kjeldsen, M. Podlaseck, N. Sukaviriya IBM T.J. Watson Research Center, USA Using Semantic Networks for Knowledge Representation in an Intelligent Environment S. Peters and H. Shrob Massachussetts Institute of Technology, USA Managing Behavior of Intelligent Environments S. Yoshihama, P. Chou, D. Wong IBM Research, USA Y. Lau, IBM, USA ------------------------ 12:30 - 2:00 PM LUNCH ------------------------ 2:00 - 3:30 PM -------------- SESSION PC-9: MOBILE SERVICES _____________________________ A Performance Comparison of Scatternet Formation Protocols for Networks of Bluetooth Devices S. Basagni, Northeastern University, USA R. Bruno, CNR - IIT Institute, ITALY C. Petrioli, Universita` di Roma "La Sapienza", ITALY Sharing Presence Information and Message Notification in an Ad Hoc Network D. Zhu and M. Mutka Michigan State University, USA Mobile Link Services with MQSeries Everyplace S. Vivek, K. Tso, and D. De Roure University of Southampton, GREAT BRITAIN SESSION PC-10: DEVICES FOR PERVASIVE COMPUTING __________________________________________________ A System of Card Type Battery-less Information Terminal: CardBIT for Situated Interaction Y. Nakamura, T. Nishimura, H. Itoh, and H. Nakashima National Inst of Advanced Industrial Science and Technology, JAPAN Interaction in Pervasive Computing Settings using Bluetooth-enabled Active Tags and Passive RFID Technology together with Mobile Phones C. Floerkemeier and F. Siegemund ETH Zurich, SWITZERLAND Text Input for Public Displays using Palmtop Computers - Separating Input from Display C. Magerkurth and R. Stenzel FhG-IPSI, GERMANY SESSION IE-2: ACTIVITY RECOGNITION ________________________________________ Object Labelling from Human Action Recognition P. Peursum, S. Venkatesh, G. West, and H. Bui Curtin University, AUSTRALIA LANDMARC: Indoor Location Sensing Using Active RFID L. Ni, Hong Kong University of Science & Technology, Hong Kong Y. Liu, A Patil Michigan State University, USA Recognition of Human Activity through Hierarchical Stochastic learning S. Luhr, H. Bui, S. Venkatesh, and G. West Curtin University of Technology, AUSTRALIa 3:30-4:00 PM COFFEE BREAK 4:00-5:30 PM Panel I ---------------------- PERVASIVE COMPUTING: ILLUSION OR REALITY? Panel Organizer: Dr. Chatschik Bisdikian, IBM T.J. Watson Research Center Panelists ------------ Abdelsalsm Helal (Univ. of Florida) Hui Lei (IBM Research) Vince Stanford (NIST) Thad E. Starner (Georgia Tech) Roy Want (Intel Research) ____________________________________________________ ##################################### 6:30 - 9:30 PM - Conference Banquet # ##################################### WEDNESDAY MARCH 26, 2003 ########################### 9:00 to 10:30 AM ------------------- SESSION PC-11: Resource Management _________________________________ ReCalendar: Calendaring and Scheduling Applications with CPU and Energy Resource Guarantees for Mobile Devices W. Yuan and K. Nahrstedt University of Illinois at Urbana-Champaign, USA Adaptation of Web Contents and Services to Terminals Capabilities: the @Terminals Approach E. Di Nitto, Politecnico di Milano, ITALY G. Sassaroli and M. Zuccala, CEFRIEL, ITALY SESSION MA-4: SYSTEM LEVEL DESIGN ISSUES ___________________________________________ BASE - A Micro-kernel-based Middleware For Pervasive Computing C. Becker, G. Schiele, and H. Gubbels University of Stuttgart, GERMANY Synthesizing Distributed Controllers for the Safe Operation of Connected Spaces B. Sridharan and A. Mathur, Purdue University, USA K.-Y. Cai, Beijing Univ of Aeronautics and Astronautics, P.R. China Mobile Agent Based Evacuation System When The Battery Runs Out: Easter H. Kaneko and Y. Fukazawa, Waseda University, JAPAN F. Kumeno, Mitsubishi Research Institute Inc., JAPAN Y. Okataku, Japan Telecom Co. Ltd, JAPAN S. Honiden, National Institute of Informatics and Univ of Tokyo, JAPAN SESSION IE-3: LOCATION DETECTION ______________________________________ System Design of Smart Table P. Steurer and M. Srivastava University of California, Los Angeles, USA Location Aware Resource Management in Smart Homes A. Roy, S. Bhaumik, A. Bhattacharya, K. Basu, D. J. Cook, and S. K. Das The University of Texas at Arlington, USA Cerberus: A Context-Aware Security Scheme for Smart Spaces J. Al-Muhtadi, A. Ranganathan, R. Campbell, and D. Mickunas University of Illinois at Urbana-Champaign, USA 11:00 to 12:30 PM ----------------- SESSION PC-S: Short Papers ___________________________ Pervasive Messaging J.-M. Wams and M. van Steen Vrije Universiteit, THE NETHERLANDS MACA-P: A MAC for Concurrent Transmissions in Multi-hop Wireless Networks A. Acharya and A. Misra, IBM TJ Watson Research Center, USA S. Bansal, Stanford University, USA LABAR: Location Area Based Ad Hoc Routing for GPS Scarce Wide-Area Ad Hoc Networks G. Zaruba, A. Suleman and V. Chaluvadi The University of Texas at Arlington, USA Bio-Inspired Mobility In Environment Aware Wireless Sensor Networks S. Doumit, and D. Agrawal University of Cincinnati, USA SESSION IE-S: SHORT PAPERS ______________________ MavHome: An Agent-Based Smart Home D. J. Cook, M. Youngblood, E. Heierman, K. Gopalratnam, S. Rao, and A. Litvin The University of Texas at Arlington, USA A New In-door Location Detection Method Adopting Learning Algorithms T. Ogawa, S. Yoshino, M. Shimizu, and H. Suda NTT Network Innovation Laboratories, JAPAN Enabling Location-Aware Pervasive Computing Applications for the Elderly S. Helal and C. Lee University of Florida, USA SESSION MA-S: AGENTS SHORT PAPERS ___________________________ Self-Adaptive Leasing for Jini K. Bowers, RPI, USA K. Mills and S. Rose, NIST, USA Scalable Home Network Interaction Model Based on Mobile Agents J.-J. Yoo and D.-I. Lee Kwangju Institute of Science and Technology, KOREA Context-aware agent platform in ubiquitous environments and its verification tests M. Hattori, K. Cho, A. Ohsuga, M. Isshiki, TOSHIBA Corporation, JAPAN S. Honiden, National Institute of Informatics and Univ of Tokyo, JAPAN Making Java-enabled Mobile Phone As Ubiquitous Terminal by Lightweight FIPA Compliant Agent Platform G. Hattori, S. Nishiyama, KDDI R&D Laboratories, JAPAN C. Ono, YRP Ubiquitous Networking Laboratories, JAPAN H. Horiuchi, KDDI R&D Laboratories, JAPAN ----------------------------- 12:30 - 2:00 PM LUNCH ------------------------------ 2:00 - 3:30 PM PANEL II ___________________________________________________ ---------------------------------------------------- GENERAL CHAIR: Behrooz A. Shirazi (UTA) GENERAL VICE CHAIR: Sajal K. Das (UTA) PROGRAM COMMITTEE CHAIR: Mohan Kumar Department of Computer Science and Engineering University of Texas at Arlington Box 19015, Arlington TX 76019-0015 Phone: 817 272 3610, Fax : 817 272 3784 Email: kumar@cse.uta.edu Special Track Chairs: Diane Cook (UTA) for Intelligent Environments Anand Tripathi (Uni. Minnesota) for Mobile Agents ---------------------------------------------------- -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntigton Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 10 18:51:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01030 for ; Mon, 10 Feb 2003 18:51:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1B00WU23349 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 19:00:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1B00Vp23346 for ; Mon, 10 Feb 2003 19:00:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01009 for ; Mon, 10 Feb 2003 18:51:22 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANkop22729; Mon, 10 Feb 2003 18:46:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ANj7p22670 for ; Mon, 10 Feb 2003 18:45:07 -0500 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00533 for ; Mon, 10 Feb 2003 18:35:58 -0500 (EST) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA01498; Mon, 10 Feb 2003 15:39:40 -0800 (PST) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h1ANddH23215; Mon, 10 Feb 2003 15:39:39 -0800 X-mProtect: <200302102339> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdJcnUZS; Mon, 10 Feb 2003 15:39:38 PST Message-ID: <3E48383A.E4D2F412@iprg.nokia.com> Date: Mon, 10 Feb 2003 15:39:38 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mansoor Mohsin CC: =?iso-8859-1?Q?F=E1bio?= Buiati , manet@ietf.org Subject: Re: [manet] Autoconfiguration protocols References: <00c401c2d130$1f1a2e00$0e43a8c0@piqui> <003901c2d158$4e7c4750$515e6e81@campus.ad.utdallas.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello folks, We had a draft on address autoconfiguration, currently available at the following URL: http://people.nokia.net/charliep/txt/aodvid/autoconf.txt It was expected to be a working group item, but recently the manet group has not been adding new work. The autoconfiguration ideas have been implemented, are known to work, and have been published in various papers at technical conferences. Regards, Charlie P. > Mansoor Mohsin wrote: > > Hi, > > Sanket Nasergi and Ravi Prakash have a paper in INFOCOM 2002 on node > autoconfiguration in MANETs. There is another paper in MILCOM 2002 by myself > and Ravi Prakash on the same topic but with a different approach. Both the > papers give distributed algorithms for node autoconfiguration taking into > account network initialization, arrival of new node, node departure, network > partitioing and merging, and message losses, etc. > > The papers can be downloaded using the following links: > http://wwwutdallas.edu/~ravip/papers/infocom2002.pdf > http://www.utdallas.edu/~mmohsin/publications/IPAssignment.pdf > > ------------------------------------------------------------------------------ > Mansoor Mohsin > > > ----- Original Message ----- > From: "Fabio Buiati" > To: > Sent: Monday, February 10, 2003 12:13 PM > Subject: [manet] Autoconfiguration protocols > > > Hi all, > > > > I would like to know which Autoconfiguration protocol would have the best > > concept based on performance taking into account the following issues: > > > > Initialization of network > > New node joining a network > > Concurrent initiation of address allocation > > Departure of nodes (graceful and abrupt) > > Network partition and merger > > Message losses > > Broadcast storm > > > > Would it be viable to implement it on a real environment? > > --------------------------------------------------- > > Fabio Mesquita Buiati > > Universidade de Brasmlia - UnB - Brazil > > email - fabio@redes.unb.br > > --------------------------------------------------- > > > > _______________________________________________ > > 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 mailnull@www1.ietf.org Mon Feb 10 19:49:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02755 for ; Mon, 10 Feb 2003 19:49:22 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1B0w1N27207 for manet-archive@odin.ietf.org; Mon, 10 Feb 2003 19:58:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1B0w1p27204 for ; Mon, 10 Feb 2003 19:58:01 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02749 for ; Mon, 10 Feb 2003 19:48:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1B0esp26372; Mon, 10 Feb 2003 19:40:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1B0dFp26273 for ; Mon, 10 Feb 2003 19:39:15 -0500 Received: from pilot19.cl.msu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02254 for ; Mon, 10 Feb 2003 19:30:05 -0500 (EST) Received: from saturn (dhcp-35-8-12-225.egr.msu.edu [35.8.12.225]) by pilot19.cl.msu.edu (8.10.2/8.10.2) with SMTP id h1B0XdB35728; Mon, 10 Feb 2003 19:33:39 -0500 Message-ID: <001c01c2d165$775a1690$e10c0823@saturn> From: "Zhou, Hongbo" To: =?iso-8859-1?Q?F=E1bio_Buiati?= Cc: References: <00c401c2d130$1f1a2e00$0e43a8c0@piqui> Subject: Re: [manet] Autoconfiguration protocols Date: Mon, 10 Feb 2003 19:35:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, There is another paper in INFOMCOM'03 on autoconfiguration. We used a different idea to assign IP addresses to the nodes in the MANET. You can download it at http://www.cse.msu.edu/~zhouhon1/doc/prophetaddressalloc.pdf. Best regards, Sincerely yours, Zhou, Hongbo (Bernie) ========================================= Ph.D. student ELANS Dept. of Computer Science & Engineering Michigan State Univ. Tel: (517) 353-4633 Email: zhouhon1@msu.edu URL: http://www.cse.msu.edu/~zhouhon1 ========================================= ----- Original Message ----- From: "Fábio Buiati" To: Sent: Monday, February 10, 2003 1:13 PM Subject: [manet] Autoconfiguration protocols Hi all, I would like to know which Autoconfiguration protocol would have the best concept based on performance taking into account the following issues: Initialization of network New node joining a network Concurrent initiation of address allocation Departure of nodes (graceful and abrupt) Network partition and merger Message losses Broadcast storm Would it be viable to implement it on a real environment? --------------------------------------------------- Fábio Mesquita Buiati Universidade de Brasília - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- _______________________________________________ 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 mailnull@www1.ietf.org Tue Feb 11 07:12:23 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00143 for ; Tue, 11 Feb 2003 07:12:23 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BCLG109772 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 07:21:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BCLGp09769 for ; Tue, 11 Feb 2003 07:21:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00131 for ; Tue, 11 Feb 2003 07:11:51 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BC48p08128; Tue, 11 Feb 2003 07:04:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BBsVp07778 for ; Tue, 11 Feb 2003 06:54:31 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28451; Tue, 11 Feb 2003 06:45:08 -0500 (EST) Message-Id: <200302111145.GAA28451@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 11 Feb 2003 06:45:08 -0500 Subject: [manet] I-D ACTION:draft-engelstad-manet-name-resolution-00.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Name Resolution in on-demand MANETS and external IP Networks Author(s) : P. Engelstad, G. Egeland Filename : draft-engelstad-manet-name-resolution-00.txt Pages : 11 Date : 2003-2-10 The most common user applications for data communication (including web browsing and e-mail) lack a method for name resolution in multi- hop wireless ad-hoc networks of mobile nodes (MANETs). While the Domain Name System (DNS) works well on the fixed Internet, it represents a centralized approach to name resolution, which is not suitable for MANETs. This document specifies a straightforward solution for name resolution in on-demand MANETs, i.e. MANETs that are routed with a reactive routing protocol, such as DSR [DSR] or AODV [AODV]. Names that are resolved locally within the MANET will normally have preference. However, MANET nodes that have access to external networks may complement the local name resolution by injecting into the MANET addresses resolved by a conventional DNS server. The proposed solution applies equally well to IPv4 or IPv6. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-engelstad-manet-name-resolution-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-engelstad-manet-name-resolution-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-engelstad-manet-name-resolution-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: <2003-2-10132837.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-engelstad-manet-name-resolution-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-engelstad-manet-name-resolution-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-10132837.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 08:10:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03535 for ; Tue, 11 Feb 2003 08:10:57 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BDJqQ13802 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 08:19:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BDJqp13799 for ; Tue, 11 Feb 2003 08:19:52 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03509 for ; Tue, 11 Feb 2003 08:10:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BD6Up12440; Tue, 11 Feb 2003 08:06:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BD4pp12401 for ; Tue, 11 Feb 2003 08:04:51 -0500 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02796; Tue, 11 Feb 2003 07:55:23 -0500 (EST) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.11.6/8.11.1) with SMTP id h1BD3L316842; Tue, 11 Feb 2003 11:03:22 -0200 Message-ID: <00fe01c2d1d6$63499b50$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Cc: References: <200302111145.GAA28451@ietf.org> Subject: Re: [manet] I-D ACTION:draft-engelstad-manet-name-resolution-00.txt Date: Tue, 11 Feb 2003 11:03:43 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FB_01C2D1BD.3DE88D30" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00FB_01C2D1BD.3DE88D30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There is an error on expiration. It is February 2002. Best regards.... ----- Original Message -----=20 From: Internet-Drafts@ietf.org=20 To: IETF-Announce:=20 Cc: manet@ietf.org=20 Sent: Tuesday, February 11, 2003 8:45 AM Subject: [manet] I-D = ACTION:draft-engelstad-manet-name-resolution-00.txt A New Internet-Draft is available from the on-line Internet-Drafts = directories. Title : Name Resolution in on-demand MANETS and external IP=20 Networks Author(s) : P. Engelstad, G. Egeland Filename : draft-engelstad-manet-name-resolution-00.txt Pages : 11 Date : 2003-2-10 The most common user applications for data communication (including=20 web browsing and e-mail) lack a method for name resolution in multi- hop wireless ad-hoc networks of mobile nodes (MANETs). While the=20 Domain Name System (DNS) works well on the fixed Internet, it=20 represents a centralized approach to name resolution, which is not=20 suitable for MANETs. This document specifies a straightforward=20 solution for name resolution in on-demand MANETs, i.e. MANETs that=20 are routed with a reactive routing protocol, such as DSR [DSR] or=20 AODV [AODV]. Names that are resolved locally within the MANET will=20 normally have preference. However, MANET nodes that have access to=20 external networks may complement the local name resolution by=20 injecting into the MANET addresses resolved by a conventional DNS=20 server. The proposed solution applies equally well to IPv4 or IPv6. A URL for this Internet-Draft is: = http://www.ietf.org/internet-drafts/draft-engelstad-manet-name-resolution= -00.txt To remove yourself from the IETF Announcement list, send a message to=20 ietf-announce-request with the word unsubscribe in the body of the = message. 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-engelstad-manet-name-resolution-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 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-engelstad-manet-name-resolution-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_000_00FB_01C2D1BD.3DE88D30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
There is an error on expiration. It is = February=20 2002.
 
Best regards....
----- Original Message -----
From:=20 Internet-Drafts@ietf.org =
Sent: Tuesday, February 11, = 2003 8:45=20 AM
Subject: [manet] I-D=20 ACTION:draft-engelstad-manet-name-resolution-00.txt

A New Internet-Draft is available from the on-line=20 Internet-Drafts directories.


Title : Name Resolution in = on-demand=20 MANETS and external IP=20 =
           &nb= sp;           &nbs= p; =20 Networks
Author(s) : P. Engelstad, G. Egeland
Filename :=20 draft-engelstad-manet-name-resolution-00.txt
Pages : 11
Date :=20 2003-2-10

The most common user applications for data = communication=20 (including
web browsing and e-mail) lack a method for name = resolution in=20 multi-
hop wireless ad-hoc networks of mobile nodes (MANETs). While = the=20
Domain Name System (DNS) works well on the fixed Internet, it=20
represents a centralized approach to name resolution, which is not =
suitable for MANETs. This document specifies a straightforward=20
solution for name resolution in on-demand MANETs, i.e. MANETs that =
are=20 routed with a reactive routing protocol, such as DSR [DSR] or
AODV = [AODV].=20 Names that are resolved locally within the MANET will
normally = have=20 preference. However, MANET nodes that have access to
external = networks may=20 complement the local name resolution by
injecting into the MANET = addresses=20 resolved by a conventional DNS
server. The proposed solution = applies=20 equally well to IPv4 or IPv6.

A URL for this Internet-Draft = is:
http://www.ietf.org/internet-drafts/draft-engelstad-mane= t-name-resolution-00.txt

To=20 remove yourself from the IETF Announcement list, send a message to=20
ietf-announce-request with the word unsubscribe in the body of the = message.

Internet-Drafts are also available by anonymous FTP. = Login=20 with the username
"anonymous" and a password of your e-mail = address. After=20 logging in,
type "cd internet-drafts" and then
"get=20 draft-engelstad-manet-name-resolution-00.txt".

A list of=20 Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html<= /A>=20
or ftp://ftp.ietf.org/iet= f/1shadow-sites.txt


Internet-Drafts=20 can also be obtained by e-mail.

Send a message to:
mailserv@ietf.org.
In the = body=20 type:
"FILE=20 = /internet-drafts/draft-engelstad-manet-name-resolution-00.txt".

NO= TE:=20 The mail server at ietf.org can return the document in
MIME-encoded = form by=20 using the "mpack" utility.  To use this
feature, insert the = command=20 "ENCODING mime" before the "FILE"
command.  To decode the = response(s),=20 you will need "munpack" or
a MIME-compliant mail reader.  = Different=20 MIME-compliant mail readers
exhibit different behavior, especially = when=20 dealing with
"multipart" MIME messages (i.e. documents which have = been=20 split
up into multiple messages), so check your local documentation = on
how to manipulate these messages.


Below is the data = which=20 will enable a MIME compliant mail reader
implementation to = automatically=20 retrieve the ASCII version of=20 the
Internet-Draft.
------=_NextPart_000_00FB_01C2D1BD.3DE88D30-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 12:29:28 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12427 for ; Tue, 11 Feb 2003 12:29:28 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BHcRv31280 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 12:38:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BHcRp31277 for ; Tue, 11 Feb 2003 12:38:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12355 for ; Tue, 11 Feb 2003 12:28:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BHPFp29963; Tue, 11 Feb 2003 12:25:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BHKep29824 for ; Tue, 11 Feb 2003 12:20:40 -0500 Received: from Tempo.Update.UU.SE (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11800 for ; Tue, 11 Feb 2003 12:11:10 -0500 (EST) Received: from Tempo.Update.UU.SE (ip6-localhost [IPv6:::1]) by Tempo.Update.UU.SE (8.12.6/8.12.6/Update-Iltempogigante) with ESMTP id h1BHEoeC005679 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Feb 2003 18:14:50 +0100 Received: from localhost (davidl@localhost) by Tempo.Update.UU.SE (8.12.6/8.12.6/Update-Iltempogigante-submit) with ESMTP id h1BHEnbg005669; Tue, 11 Feb 2003 18:14:49 +0100 X-Authentication-Warning: Tempo.Update.UU.SE: davidl owned process doing -bs Date: Tue, 11 Feb 2003 18:14:48 +0100 (CET) From: David Lundberg To: Sye Loong Keoh cc: manet@ietf.org Subject: Re: [manet] Ad hoc Routing Implementation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h1BHKep29825 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit On Sat, 8 Feb 2003, Sye Loong Keoh wrote: > Hi, > > Can anybody show me the pointer to the ad-hoc routing implementation on > Linux or windows? Here's a wikipage with some implementations: http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations // David // -------------------------------------------------------------- David Lundberg Phone: Home(Uppsala) +46-18-460356 Mail: davidl@update.uu.se Home(Gävle) +46-26-146743 Http: www.update.uu.se/~davidl Cellular +46-70-3531696 ICQ: 13440550 IT-Dept. @ UU +46-18-4716231 -------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 14:24:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16010 for ; Tue, 11 Feb 2003 14:24:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BJXmc05517 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 14:33:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJXmp05514 for ; Tue, 11 Feb 2003 14:33:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15996 for ; Tue, 11 Feb 2003 14:24:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJIVp04777; Tue, 11 Feb 2003 14:18:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJGHp04698 for ; Tue, 11 Feb 2003 14:16:17 -0500 Received: from uni02du.unity.ncsu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15560 for ; Tue, 11 Feb 2003 14:06:45 -0500 (EST) Received: (from mlsichit@localhost) by uni02du.unity.ncsu.edu (8.8.4/EC02Jan97) id OAA02412; Tue, 11 Feb 2003 14:10:28 -0500 (EST) Date: Tue, 11 Feb 2003 14:10:28 -0500 (EST) From: Mihail L Sichitiu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re:Autoconfiguration protocols Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I used to briefly work at autoconfiguration problem until I came to know that "my approach" was recently published in an MS thesis on the subject (at UT. Dallas - see link below). I have nothing to do with the thesis, but I thought it's relevant. I think that the approach in the thesis (which draws on an unpolished idea of an U. of Maryland student) is significantly more scalable (O(m) messages instead of O(nm) for m new joins in an n node ad-hoc network) than existing approaches, and deserves your attention. I honestly doubt that it can be done much better than that, but I'm looking forward to see a better solution). http://www.utdallas.edu/~mansi/ If you want to get a look at the U. of Maryland initial papers see references [12] and [13] in the thesis. I was unable to find them online, but I got a copy from the library. The main idea of the thesis (and original papers) is simple: each node in the ad-hoc network acts like a DHCP server that has besides its IP address a range of IP addresses that can offer. When a new node joins an already existing node it offers an IP address and half of its IP addresses in its care. The thesis takes care of other details like network merging and partitioning, and address reclaiming. Best regards, Mihail Sichitiu _______________________________________________________ Mihail L. Sichitiu Assistant Professor, Phone: (919) 515 7348 Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 NC State University Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit _______________________________________________________ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 14:32:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16294 for ; Tue, 11 Feb 2003 14:32:25 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BJfRK06659 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 14:41:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJfRp06656 for ; Tue, 11 Feb 2003 14:41:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16285 for ; Tue, 11 Feb 2003 14:31:54 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJSUp05160; Tue, 11 Feb 2003 14:28:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJR2p05114 for ; Tue, 11 Feb 2003 14:27:02 -0500 Received: from crete.csd.uch.gr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15797 for ; Tue, 11 Feb 2003 14:17:27 -0500 (EST) Received: from wendy.csd.uch.gr (wendy.csd.uch.gr [147.52.16.27]) by crete.csd.uch.gr (8.9.3+Sun/8.9.3) with SMTP id VAA21181 Organization: Received: (from COMM9 [147.52.20.139]) by wendy.csd.uch.gr (NAVGW 2.5 bld 89) with SMTP id M2003021121205606076 ; Tue, 11 Feb 2003 21:20:56 +0200 From: "Lykourgou" To: Date: Tue, 11 Feb 2003 21:24:04 +0200 Message-ID: <000001c2d203$272adad0$09143493@csd.uoc.gr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C2D213.EAB6B810" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] IEEE 802.11 model in Opnet!!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C2D213.EAB6B810 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello!!! I encounter some problems with the following simulation and I wonder if there is anyone who could help me. There are two wlan_station_adv (mob) nodes in 800m X 800m rectangle area. The distance between them at first is 1m. During the simulation the nodes are following two different trajectories and after 10minutes the distance between them is longer than 300m. The simulation is for 30minutes and each node selects random a destination and transmits packets. I know that during the first 10 minutes the nodes can exchange messages because their distance is shorter than 300m (= range of wireless stations) but I can't understand why they continue exchanging messages and for the rest of the simulation when the distance is longer than 300m. Could any one please explain me that or tell me what am I doing wrong. Thank you in advanced , Eydokia ------=_NextPart_000_0001_01C2D213.EAB6B810 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello!!!

I encounter = some problems with the following simulation and I wonder if there is anyone who could = help me.

 
    &nbs=
p;          There are two =
wlan_station_adv (mob) nodes in 800m X 800m rectangle area. The distance =
between them at first is 1m. During the simulation the nodes are =
following two different trajectories and after 10minutes the distance =
between them is longer than 300m. The simulation is for 30minutes and =
each node selects random a destination and transmits packets. =
  
 
    &nbs=
p;          I know that =
during the first 10 minutes the nodes can exchange messages because =
their distance is shorter than 300m (=3D range of wireless stations) but =
I can’t understand why they continue exchanging messages and for =
the rest of the simulation when the distance is longer than 300m. Could =
any one please explain me that or tell me what am I doing =
wrong.
 
Thank you in advanced = ,
Eydokia
<= pre> 
------=_NextPart_000_0001_01C2D213.EAB6B810-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 14:34:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16344 for ; Tue, 11 Feb 2003 14:34:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BJhDl06759 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 14:43:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJhDp06756 for ; Tue, 11 Feb 2003 14:43:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16337 for ; Tue, 11 Feb 2003 14:33:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJU7p05287; Tue, 11 Feb 2003 14:30:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BJTdp05254 for ; Tue, 11 Feb 2003 14:29:39 -0500 Received: from ponyexpress.ee.columbia.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15832 for ; Tue, 11 Feb 2003 14:20:01 -0500 (EST) Received: from SHAMAN (dhcp-65-84.ee.columbia.edu [128.59.65.84]) by ponyexpress.ee.columbia.edu (8.12.5/8.12.1) with SMTP id h1BJVvVT003268; Tue, 11 Feb 2003 14:31:57 -0500 Message-ID: <002701c2d203$008d24a0$54413b80@SHAMAN> From: "Gahng-Seop Ahn" To: Cc: Date: Tue, 11 Feb 2003 14:23:05 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0024_01C2D1D9.178F7060" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] Re: Qos on Adhoc nets: SWAN, vs Diffserv Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0024_01C2D1D9.178F7060 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hello: Thanks for your questions on SWAN. >Is the results shown in "Supporting Service >Differentiation for Real-Time and Best Effort Traffic in >Stateless Wireless Ad Hoc Networks (SWAN)", IEEE Transactions >on Mobile Computing, September 2002---dependent on a specific >MAC layer behaviour? (The studies cite DCF 802.11 best effort >networks.) What if there is an adhoc internetwork with >multiple link layers in place including TDMA? Or is the best >effort MAC the worst case? SWAN is designed to support soft real-time QOS - even though it is agnostic to the MAC it is designed to operate over=20 (in the worst case) best effort MACs. The SWAN rate controller=20 is introduced to resolve the limitation of best effort MACs.=20 However, if nodes are equipped with QOS capable MACs (e.g.,=20 TDMA, EDCF, etc.) then SWAN would perform even better. In this case,=20 the SWAN rate controller could be disabled, still allowing the=20 SWAN admission controller to perform sender-based=20 admission control and dynamic session regulation. >SWAN is stateless, but so is diffserv. If diffserv were used >with bandwidth brokers, with appropriate heuristics by which >to do the bandwidth brokering, mightnt it be an acceptable >alternative? (the overprovisioning could be bounded by the >admission control) >Edge routers need to be identified; but layer 2 self >organization algorithms exist which do the equivalent. It >should be possible to augment IP layer autoconfiguration to >do the same- >The advantage diffserv might have would be as a >heterogeneous qos framework, which is applicable to any >underlying adhoc technology.Also more classification >categories than SWAN-- I think the DiffServ model is too (wireline) Internet centric and=20 probably not immediately mappable to MANETs. As we all know MANETs=20 are quite different from Internet. For example, there is no notion of=20 edge and core routers in ad hoc networks allowing us to easily=20 map equivalent wireline DiffServ functions too. I also think=20 that it may not be practical to have bandwidth brokers (servers)=20 in ad hoc networks. Therefore, the original wireline DiffServ model may=20 not be deployable in ad hoc networks without major changes to its design. However, this is an open question. SWAN follows the philosophy of DiffServ but is designed to fit into=20 the structure and behavior of MANETs - and is targeted to operate over (in the worst case and most likely case)=20 best-effort MACs. Best Regards, Gahng-Seop Ahn ------=_NextPart_000_0024_01C2D1D9.178F7060 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable
Hello:

Thanks for your questions on=20 SWAN.

>Is the results shown in "Supporting=20 Service
>Differentiation for Real-Time and Best Effort Traffic=20 in
>Stateless Wireless Ad Hoc Networks (SWAN)", IEEE=20 Transactions
>on Mobile Computing, September 2002---dependent on a = specific
>MAC layer behaviour? (The studies cite DCF 802.11 best=20 effort
>networks.) What if there is an adhoc internetwork=20 with
>multiple link layers in place including TDMA? Or is  = the=20 best
>effort MAC  the worst case?

SWAN is designed to = support=20 soft real-time QOS - even though
it is agnostic to the MAC it is = designed to=20 operate over
(in the worst case) best effort MACs. The SWAN rate = controller=20
is introduced to resolve the limitation of best effort MACs. =
However, if=20 nodes are equipped with QOS capable MACs (e.g.,
TDMA, EDCF, etc.) = then SWAN=20 would perform even better. In this case,
the SWAN rate controller = could be=20 disabled, still allowing the
SWAN admission controller to perform=20 sender-based
admission control and dynamic session=20 regulation.

>SWAN is stateless, but so is diffserv. If = diffserv were=20 used
>with bandwidth brokers, with appropriate heuristics by=20 which
>to do the bandwidth brokering, mightnt it be an=20 acceptable
>alternative? (the overprovisioning could be bounded by = the
>admission control)
>Edge routers need to be identified; = but=20 layer 2 self
>organization algorithms exist which do the = equivalent.=20 It
>should be  possible to augment IP layer autoconfiguration = to
>do the same-
>The advantage diffserv might have would be = as=20 a
>heterogeneous qos framework, which is applicable to=20 any
>underlying adhoc technology.Also more=20 classification
>categories than SWAN--

I think the DiffServ = model=20 is too (wireline) Internet centric and
probably not immediately = mappable to=20 MANETs. As we all know MANETs
are quite different from Internet. For = example, there is no notion of
edge and core routers in ad hoc = networks=20 allowing us to easily
map equivalent wireline DiffServ functions = too. I also=20 think
that it may not be practical to have bandwidth brokers = (servers)=20
in ad hoc networks. Therefore, the original wireline DiffServ model = may=20
not be deployable in ad hoc networks without major
changes to its = design.=20 However, this is an open question.

SWAN follows the philosophy of = DiffServ but is designed to fit into
the structure and behavior of = MANETs -=20 and is targeted
to operate over (in the worst case and most likely = case)=20
best-effort MACs.

Best Regards,
Gahng-Seop=20 Ahn
------=_NextPart_000_0024_01C2D1D9.178F7060-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 15:59:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18315 for ; Tue, 11 Feb 2003 15:59:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BL8pr12375 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 16:08:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BL8pp12372 for ; Tue, 11 Feb 2003 16:08:51 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18307 for ; Tue, 11 Feb 2003 15:59:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BKqIp11028; Tue, 11 Feb 2003 15:52:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BKn0p10921 for ; Tue, 11 Feb 2003 15:49:00 -0500 Received: from postmark.nist.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17889 for ; Tue, 11 Feb 2003 15:39:26 -0500 (EST) Received: from Gibbon (gibbon.antd.nist.gov [129.6.50.35]) by postmark.nist.gov (8.12.5/8.12.5) with SMTP id h1BKgXf1010044; Tue, 11 Feb 2003 15:42:33 -0500 (EST) Message-ID: <016601c2d20e$6e1d3c20$23320681@Gibbon> From: "Jabin Song" To: "Lykourgou" Cc: References: <000001c2d203$272adad0$09143493@csd.uoc.gr> Subject: Re: [manet] IEEE 802.11 model in Opnet!!! Date: Tue, 11 Feb 2003 15:44:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit In OPNET WLAN models, the transmission range depends on a transmission power of the packets (default 1mW), a receprion power threshold (default 7.33E-14), and a propagation model for path loss (default Free-Space model). The transmission range is about 1160 meters when these default values are used. You can change the transmission range by changing these parameters. For example, the transmission range is around 300 meters when a transmission power of packets is set to 0.000066728 (W). Best Regards, Jabin Song ----- Original Message ----- From: Lykourgou To: manet@ietf.org Sent: Tuesday, February 11, 2003 2:24 PM Subject: [manet] IEEE 802.11 model in Opnet!!! Hello!!! I encounter some problems with the following simulation and I wonder if there is anyone who could help me. There are two wlan_station_adv (mob) nodes in 800m X 800m rectangle area. The distance between them at first is 1m. During the simulation the nodes are following two different trajectories and after 10minutes the distance between them is longer than 300m. The simulation is for 30minutes and each node selects random a destination and transmits packets. I know that during the first 10 minutes the nodes can exchange messages because their distance is shorter than 300m (= range of wireless stations) but I can't understand why they continue exchanging messages and for the rest of the simulation when the distance is longer than 300m. Could any one please explain me that or tell me what am I doing wrong. Thank you in advanced , Eydokia _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 11 17:27:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20326 for ; Tue, 11 Feb 2003 17:27:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BMadH17377 for manet-archive@odin.ietf.org; Tue, 11 Feb 2003 17:36:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BMadp17374 for ; Tue, 11 Feb 2003 17:36:39 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20323 for ; Tue, 11 Feb 2003 17:27:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BMNOp16869; Tue, 11 Feb 2003 17:23:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BMLop16789 for ; Tue, 11 Feb 2003 17:21:50 -0500 Received: from pollen.cs.concordia.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20102 for ; Tue, 11 Feb 2003 17:12:15 -0500 (EST) Received: from sunset (a_patnai@sunset [132.205.45.1]) by pollen.cs.concordia.ca (8.12.2+Sun/8.12.2) with ESMTP id h1BMFwi8029445 for ; Tue, 11 Feb 2003 17:15:58 -0500 (EST) Date: Tue, 11 Feb 2003 17:15:58 -0500 (EST) From: Anup Patnaik To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] SDL specs for AODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi I was wondering if someone has developed specifications for AODV in SDL and carried out validation and verification for the same. Is this work worth doing. Can the specs help to find out loop holes (if any) or security breaches in the protocol. Regards Anup Patnaik Ph.D. student Concordia University Montreal.Quebec.Canada _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 12 03:19:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25884 for ; Wed, 12 Feb 2003 03:19:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1C8SrS28152 for manet-archive@odin.ietf.org; Wed, 12 Feb 2003 03:28:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1C8Sqp28149 for ; Wed, 12 Feb 2003 03:28:52 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25864 for ; Wed, 12 Feb 2003 03:19:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1C8Dkp27511; Wed, 12 Feb 2003 03:13:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1C8ATp27422 for ; Wed, 12 Feb 2003 03:10:29 -0500 Received: from mx2.isti.cnr.it (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25429 for ; Wed, 12 Feb 2003 03:00:37 -0500 (EST) Received: from CONVERSION.MAIL.IAT.CNR.IT by mail.isti.cnr.it (PMDF V6.2 #30641) id <01KSCFI86HSG8Y52NA@mail.isti.cnr.it> for manet@ietf.org; Wed, 12 Feb 2003 09:03:43 +0100 (MET) Received: from iit.cnr.it (imacbruno.cnuce.cnr.it [146.48.82.118]) by mail.isti.cnr.it (PMDF V6.2 #30641) with ESMTP id <01KSCFI81T7C8Y51FC@mail.isti.cnr.it> for manet@ietf.org; Wed, 12 Feb 2003 09:03:43 +0100 (MET) Date: Wed, 12 Feb 2003 09:03:43 +0100 From: Raffaele Bruno To: manet@ietf.org Message-id: <3E49FFDF.8070201@iit.cnr.it> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_buaWIQsId4kgOojoFoM3Fw)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 Subject: [manet] PWC2003 - DEADLINE EXTENSION to February 23 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --Boundary_(ID_buaWIQsId4kgOojoFoM3Fw) Content-type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit ***** Due to the numerous requests, the submission deadline has been extended to February 23 (hard deadline) ******* [Our sincere apologies if you receive multiple copies of this CFP] ========================================================= Conference Announcement and Call for Papers PWC 2003 The Eighth International Conference on Personal Wireless Communications Sponsored by the IFIP WG 6.8 - Mobile and Wireless Communications http://www.iit.cnr.it/pwc2003 September 23-25, 2003 Telecom Italia Future Centre - Venice, Italy http://www.futurecentre.telecomitalia.it/eng/ PWC is the premier international forum for discussions between researchers, practitioners and students interested in the symbiosis of mobile computing and wireless networks. PWC 2003 is the eight conference of this series and is sponsored by IFIP WG 6.8 The PWC 2003 technical program committee is soliciting papers describing original, previously unpublished, completed or on-going research, on topics. including, but not limited to, the following: - Mobile Web Access - Mobile and Wireless Applications - Pervasive computing - Mobile and Wireless Networking - IP-based Mobile Networks - Mobility Management - QoS in the Mobile and Wireless Networks - Real-time voice/video over mobile and wireless networks - Multicasting in Wireless Services - Analysis, Simulation and Measurement of wireless and mobile systems - Mobile ad hoc networks - Wireless BAN, PAN and LAN - Wi-Fi - Third and Fourth Generation Systems - 3G/WLAN internetworking - Energy-efficient Protocols and Power Management This year conference includes two special tracks to address hot topic issues: sensor networks and wireless security. PAPER SUBMISSION AND PUBLICATION ================================= Papers should neither have been published elsewhere nor currently under review by another conference or journal. For paper submission, please follow the submission instructions at: http://www.iit.cnr.it/pwc2003 All papers will be reviewed by the program committee members. Accepted papers will appear in the conference proceedings. IMPORTANT DATES =============== Full papers due: February 23, 2003 *** EXTENDED DEADLINE Notification: May 10, 2003 Camera Ready due: June 10, 2003 GENERAL Chair: Enrico Gregori, IIT - CNR, Italy GENERAL Vice-Chair: Fabrizio Davide, Telecom Italia, Italy TECHNICAL PROGRAM Chair: Marco Conti, IIT - CNR, Italy SPECIAL TRACKs PROGRAM Co-Chairs: Silvia Giordano, SUPSI, Switzerland Stephan Olariu, Old Dominion University, USA PUBLICITY Co-Chairs: Raffaele Bruno, IIT CNR, Italy Alexandros Kaloxylos, University of Athens, Greece STEERING COMMITTEE Members: Imrich Chlamtac, University of Trento, Italy (Chair) Jon Crowcroft, University of Cambridge, UK Sajal K. Das, The University of Texas at Arlington, USA Anthony Ephremides, University of Maryland, USA K. Ben Letaief, Hong Kong University (IEEE representative) Guy Omidyar, National University of Singapore (IFIP representative) Adam Wolisz, Technical University of Berlin, Germany TECHNICAL PROGRAM COMMITTEE Members: Arup Acharya, IBM T.J. Watson Research, USA Eitan Altman, INRIA, France, Andrea Baiocchi, University of Roma "La Sapienza", Roberto Battiti, University of Trento, Italy Elizabeth M. Belding-Royer, UC Santa Barbara, USA Giuseppe Bianchi, University of Palermo, Italy Azzedine Boukerche, University of North Texas, USA Andrew T. Campbell, Columbia University, USA Carla-Fabiana Chiasserini, Politecnico di Torino, Italy Raimo Kantola, Helsinki University of Technology, Finland Holger Karl, Technische Universitaet Berlin, Germany Mohan Kumar, Univ. Texas at Arlington, USA Laura M. Feeney, SICS, Sweden, Gabor Fodor, Ericsson, Sweden Luigi Fratta, Politecnico di Milano, Italy Per Gunningberg, Uppsala University, Sweden K. Ben Letaief, Hong Kong University, Hong Kong Andrey Lyakhov, Russian Academy of Sciences, Russia, Martin Mauve, University of Mannheim, Germany Franco Mazzenga, University of Roma Tor Vergata, Italy Enzo Mingozzi, University of Pisa, Italy Refik Molva, Institut EURECOM, France Hiroyuki Morikawa, University of Tokyo, Japan Sergio Palazzo, University of Catania, Italy Michael Paterakis, Technical University of Crete, Greece Niovi Pavlidou, Aristotle University of Thessaloniki, Greece Apostolis Salkintzis, Motorola, Canada Ioannis Stavrakakis, University of Athens, Greece. Ivan Stojmenovic, University of Ottawa, Canada, Samir Tohme, Ecole Nationale Superieure des Telecommunications (ENST), France Christian Tschudin, University of Basel, Switzerland Sami Uskela, Nokia Networks, Finland Andras Valko, Ericsson AB, Sweden Hidetoshi Yokota, KDDI R&D Laboratories, Japan Bernhard Walke, Aachen University of Technology, Germany -- Raffaele Bruno ======================================= Publicity co-chair PWC 2003 Italian National Research Council - IIT Institute Via G. Moruzzi,1 - 56100 Pisa, ITALY ======================================= phone: +39 050 3153078 fax: +39 050 3152593 email: raffaele.bruno@iit.cnr.it ======================================= --Boundary_(ID_buaWIQsId4kgOojoFoM3Fw) Content-type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit ***** Due to the numerous requests, the submission deadline has been extended to February 23 (hard deadline) *******


[Our sincere apologies if you receive multiple copies of this CFP]
=========================================================

Conference Announcement and Call for Papers

PWC 2003

The Eighth International Conference on Personal Wireless Communications
Sponsored by the IFIP WG 6.8 - Mobile and Wireless Communications
http://www.iit.cnr.it/pwc2003

September 23-25, 2003
Telecom Italia Future Centre - Venice, Italy
http://www.futurecentre.telecomitalia.it/eng/


PWC is the premier international forum for discussions between researchers, practitioners and students interested in the symbiosis of mobile computing and wireless networks. PWC 2003 is the eight conference of this series and is sponsored by IFIP WG 6.8

The PWC 2003 technical program committee is soliciting papers describing original, previously unpublished, completed or on-going research, on topics. including, but not limited to, the following:

- Mobile Web Access
- Mobile and Wireless Applications
- Pervasive computing
- Mobile and Wireless Networking
- IP-based Mobile Networks
- Mobility Management
- QoS in the Mobile and Wireless Networks
- Real-time voice/video over mobile and wireless networks
- Multicasting in Wireless Services
- Analysis, Simulation and Measurement of wireless and mobile systems
- Mobile ad hoc networks
- Wireless BAN, PAN and LAN
- Wi-Fi
- Third and Fourth Generation Systems
- 3G/WLAN internetworking
- Energy-efficient Protocols and Power Management

This year conference includes two special tracks to address hot topic issues: sensor networks and wireless security.
 

PAPER SUBMISSION AND PUBLICATION
=================================

Papers should neither have been published elsewhere nor currently
under review by another conference or journal. For paper submission,
please follow the submission instructions at:
http://www.iit.cnr.it/pwc2003
All papers will be reviewed by the program committee members.
Accepted papers will appear in the conference proceedings.
 

IMPORTANT DATES
===============

Full papers due: February 23, 2003 *** EXTENDED DEADLINE
Notification:   May 10, 2003
Camera Ready due: June 10, 2003
 

GENERAL Chair: Enrico Gregori, IIT - CNR, Italy

GENERAL Vice-Chair: Fabrizio Davide, Telecom Italia, Italy

TECHNICAL PROGRAM Chair: Marco Conti, IIT - CNR, Italy

SPECIAL TRACKs PROGRAM Co-Chairs: Silvia Giordano, SUPSI, Switzerland
                                                                          Stephan Olariu, Old Dominion University, USA

PUBLICITY Co-Chairs:
Raffaele Bruno, IIT CNR, Italy
Alexandros Kaloxylos, University of Athens, Greece  

STEERING COMMITTEE Members:

Imrich Chlamtac, University of Trento, Italy (Chair)
Jon Crowcroft, University of Cambridge, UK
Sajal K. Das, The University of Texas at Arlington, USA
Anthony Ephremides, University of Maryland, USA
K. Ben Letaief, Hong Kong University (IEEE representative)
Guy Omidyar, National University of Singapore (IFIP representative)
Adam Wolisz, Technical University of Berlin, Germany

 

TECHNICAL PROGRAM COMMITTEE Members: 

Arup Acharya, IBM T.J. Watson Research, USA
Eitan Altman, INRIA, France,
Andrea Baiocchi, University of Roma "La Sapienza",
Roberto Battiti, University of Trento, Italy
Elizabeth M. Belding-Royer, UC Santa Barbara, USA
Giuseppe Bianchi, University of Palermo, Italy
Azzedine Boukerche, University of North Texas, USA
Andrew T. Campbell, Columbia University, USA
Carla-Fabiana Chiasserini, Politecnico di Torino, Italy
Raimo Kantola, Helsinki University of Technology, Finland
Holger Karl, Technische Universitaet Berlin, Germany
Mohan Kumar, Univ. Texas at Arlington, USA
Laura M. Feeney, SICS, Sweden,
Gabor Fodor, Ericsson, Sweden
Luigi Fratta, Politecnico di Milano, Italy
Per Gunningberg, Uppsala University, Sweden
K. Ben Letaief, Hong Kong University, Hong Kong
Andrey Lyakhov, Russian Academy of Sciences, Russia,
Martin Mauve, University of Mannheim, Germany
Franco Mazzenga, University of Roma Tor Vergata, Italy
Enzo Mingozzi, University of Pisa, Italy
Refik Molva, Institut EURECOM, France
Hiroyuki Morikawa, University of Tokyo, Japan
Sergio Palazzo, University of Catania, Italy
Michael Paterakis, Technical University of Crete, Greece
Niovi Pavlidou, Aristotle University of Thessaloniki, Greece
Apostolis Salkintzis, Motorola, Canada
Ioannis Stavrakakis, University of Athens, Greece.
Ivan Stojmenovic, University of Ottawa, Canada,
Samir Tohme, Ecole Nationale Superieure des Telecommunications (ENST), France
Christian Tschudin, University of Basel, Switzerland
Sami Uskela, Nokia Networks, Finland
Andras Valko, Ericsson AB, Sweden
Hidetoshi Yokota, KDDI R&D Laboratories, Japan
Bernhard Walke, Aachen University of Technology, Germany

--
Raffaele Bruno
=======================================
Publicity co-chair PWC 2003

Italian National Research Council - IIT Institute
Via G. Moruzzi,1 - 56100 Pisa, ITALY
=======================================
phone: +39 050 3153078
fax:     +39 050 3152593
email: raffaele.bruno@iit.cnr.it
=======================================
 
 

--Boundary_(ID_buaWIQsId4kgOojoFoM3Fw)-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 12 04:50:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27599 for ; Wed, 12 Feb 2003 04:50:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1CA0HS01421 for manet-archive@odin.ietf.org; Wed, 12 Feb 2003 05:00:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CA0Gp01418 for ; Wed, 12 Feb 2003 05:00:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27578 for ; Wed, 12 Feb 2003 04:50:27 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1C9lSp00810; Wed, 12 Feb 2003 04:47:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1C9jgp00747 for ; Wed, 12 Feb 2003 04:45:42 -0500 Received: from helka.iif.hu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27302 for ; Wed, 12 Feb 2003 04:35:53 -0500 (EST) Received: from CONVERSION-DAEMON.helka.iif.hu by helka.iif.hu (PMDF V6.0-24 #47461) id <0HA600701W5WRH@helka.iif.hu> for manet@ietf.org; Wed, 12 Feb 2003 10:39:32 +0100 (MET) Received: from helka.iif.hu (athos.iif.hu [193.225.12.69]) by helka.iif.hu (PMDF V6.0-24 #47461) with ESMTP id <0HA6004M5W5WBK@helka.iif.hu>; Wed, 12 Feb 2003 10:39:32 +0100 (MET) Received: from localhost (svincze@localhost) by helka.iif.hu (8.9.3/8.9.3) with ESMTP id JAA10056; Wed, 12 Feb 2003 09:39:32 +0000 (GMT) Date: Wed, 12 Feb 2003 10:39:31 +0100 (MET) From: Sandor Vincze Subject: Re: [manet] PWC2003 - DEADLINE EXTENSION to February 23 In-reply-to: <3E49FFDF.8070201@iit.cnr.it> To: Raffaele Bruno Cc: manet@ietf.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear Organizer, I would like to submitt a short paper to the special track: wireless security. This is a non solved issue not only in Pentagon, USA but also in USA. Do you still have paper slots awailable for this special track? Friendly, Dr. Sandor Vincze -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 12 07:17:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00258 for ; Wed, 12 Feb 2003 07:17:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1CCQV110045 for manet-archive@odin.ietf.org; Wed, 12 Feb 2003 07:26:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CCQVp10042 for ; Wed, 12 Feb 2003 07:26:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00248 for ; Wed, 12 Feb 2003 07:16:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CCCEp09437; Wed, 12 Feb 2003 07:12:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CC9jp09334 for ; Wed, 12 Feb 2003 07:09:45 -0500 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29915 for ; Wed, 12 Feb 2003 06:59:52 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 12 Feb 2003 04:03:35 -0800 Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP; Wed, 12 Feb 2003 12:03:35 GMT X-Originating-IP: [129.217.129.134] From: "ayman ghazi" To: manet@ietf.org Date: Wed, 12 Feb 2003 12:03:35 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 12 Feb 2003 12:03:35.0843 (UTC) FILETIME=[C560A730:01C2D28E] Subject: [manet] Anycast routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: ,


Hello,

do AODV and DSR Routing protocol support a Anycast routing ?

 

thanks

 

Ayman


Help STOP SPAM with the new MSN 8 and get 2 months FREE* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 12 07:44:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01187 for ; Wed, 12 Feb 2003 07:44:40 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1CCs3212373 for manet-archive@odin.ietf.org; Wed, 12 Feb 2003 07:54:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CCs3p12370 for ; Wed, 12 Feb 2003 07:54:03 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01178 for ; Wed, 12 Feb 2003 07:44:09 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CCeQp11619; Wed, 12 Feb 2003 07:40:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1CCd3p11514 for ; Wed, 12 Feb 2003 07:39:03 -0500 Received: from web20702.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA00760 for ; Wed, 12 Feb 2003 07:29:10 -0500 (EST) Message-ID: <20030212123253.79422.qmail@web20702.mail.yahoo.com> Received: from [131.227.76.10] by web20702.mail.yahoo.com via HTTP; Wed, 12 Feb 2003 12:32:53 GMT Date: Wed, 12 Feb 2003 12:32:53 +0000 (GMT) From: =?iso-8859-1?q?l=20s?= To: manet@ietf.org Cc: quantumparadox@yahoo.co.uk In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] IP not always required? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit General MANET question, with a setup using IP, TCP and AODV routing: In Glomosim there are functions in the IP layer (in nwip.pc) that state 'The Message is sent WITHOUT an IP header', when passing from the Transport and Routing layers, through the IP, to the MAC layer beneath. How can this be and why is no IP header needed? If it has no IP header then surely a higher level packet, such as TCP or AODV cannot be put into IP packets? The way I understood it was that all packets had to be put onto IP, is this not so? If not then what are the rules for what needs to be put onto IP and what doesn't? When the receiving node gets a message and passes it up from the MAC to the IP layer, then how does it know it should pass it to the AODV routing, given that there are no instructions as there is no IP header? Please, if anyone could help. Lee -S- CCSR, University of Surrey __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 12 22:47:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23505 for ; Wed, 12 Feb 2003 22:47:18 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1D3uwJ11055 for manet-archive@odin.ietf.org; Wed, 12 Feb 2003 22:56:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1D3uvp11052 for ; Wed, 12 Feb 2003 22:56:58 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23498 for ; Wed, 12 Feb 2003 22:46:46 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1D3flp10498; Wed, 12 Feb 2003 22:41:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1D3Xrp09630 for ; Wed, 12 Feb 2003 22:33:53 -0500 Received: from dns1.ptl.com.tw (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22768 for ; Wed, 12 Feb 2003 22:22:32 -0500 (EST) Received: from clpdestktop (pc173.ptl.com.tw [203.67.126.173]) by dns1.ptl.com.tw (X.X.X/X.X.X) with SMTP id h1D3dto28586 for ; Thu, 13 Feb 2003 11:39:55 +0800 Message-ID: <006501c2d30f$a942e960$ad7e43cb@clpdestktop> From: "clp" To: Date: Thu, 13 Feb 2003 11:26:13 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0062_01C2D352.B738D7D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] Is there any session about MANET in 56th IETF meeting ? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0062_01C2D352.B738D7D0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Dear All, I just read the draft agenda of 56th IETF meeting in San Francisco, = but there is no any session about routing of ad hoc wireless networks. = Could somebody confirm this for me ? Best, Li-Ping Chou Panansonic Taiwan Lab. ------=_NextPart_000_0062_01C2D352.B738D7D0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
Dear All,
 
    I just read the draft agenda of = 56th IETF=20 meeting in San Francisco, but there is no any session = about routing of=20 ad hoc wireless networks. Could somebody confirm this for me = ?
 
Best,
 
Li-Ping Chou
Panansonic Taiwan Lab.
------=_NextPart_000_0062_01C2D352.B738D7D0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 08:35:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11956 for ; Thu, 13 Feb 2003 08:35:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DDjmR20869 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 08:45:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DDjmp20866 for ; Thu, 13 Feb 2003 08:45:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11938 for ; Thu, 13 Feb 2003 08:35:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DDUYp19584; Thu, 13 Feb 2003 08:30:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DDQGp19436 for ; Thu, 13 Feb 2003 08:26:16 -0500 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11589 for ; Thu, 13 Feb 2003 08:15:49 -0500 (EST) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.7/8.12.5) with SMTP id h1DDRU3v025505 for ; Thu, 13 Feb 2003 11:27:30 -0200 Message-ID: <00c401c2d36b$36542200$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Thu, 13 Feb 2003 11:21:34 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit Subject: [manet] Paper Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello folks, Where can I obtain the paper "Dynamic Address Allocation Protocols for Mobile Ad Hoc Networks" written by Praveena Patchipulusu? Best regards. --------------------------------------------------- Fábio Mesquita Buiati Universidade de Brasília - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 12:30:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19082 for ; Thu, 13 Feb 2003 12:30:06 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DHe4O05335 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 12:40:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DHe3p05332 for ; Thu, 13 Feb 2003 12:40:03 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19078 for ; Thu, 13 Feb 2003 12:29:35 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DHNMp03885; Thu, 13 Feb 2003 12:23:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DHJip03706 for ; Thu, 13 Feb 2003 12:19:44 -0500 Received: from mailhost.ens-lyon.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18636 for ; Thu, 13 Feb 2003 12:09:15 -0500 (EST) Received: from ashish ([140.77.128.30]) by mailhost.ens-lyon.fr with smtp (Exim 3.35 #1 (Debian)) id 18jMux-0004J5-00 for ; Thu, 13 Feb 2003 18:12:59 +0100 Message-ID: <004301c2d383$2758e930$1e804d8c@Ashish> From: "AMEENA" To: References: <20030213170003.1934.97600.Mailman@www1.ietf.org> Date: Thu, 13 Feb 2003 18:12:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit Subject: [manet] Re: manet digest, Vol 1 #341 - 2 msgs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit ----- Original Message ----- From: To: Sent: Thursday, February 13, 2003 6:00 PM Subject: manet digest, Vol 1 #341 - 2 msgs 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-admin@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of manet digest..." Today's Topics: 1. Is there any session about MANET in 56th IETF meeting ? (clp) 2. Paper (=?iso-8859-1?Q?F=E1bio_Buiati?=) --__--__-- Message: 1 From: "clp" To: Date: Thu, 13 Feb 2003 11:26:13 +0800 Subject: [manet] Is there any session about MANET in 56th IETF meeting ? This is a multi-part message in MIME format. ------=_NextPart_000_0062_01C2D352.B738D7D0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Dear All, I just read the draft agenda of 56th IETF meeting in San Francisco, = but there is no any session about routing of ad hoc wireless networks. = Could somebody confirm this for me ? Best, Li-Ping Chou Panansonic Taiwan Lab. ------=_NextPart_000_0062_01C2D352.B738D7D0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
Dear All,
 
    I just read the draft agenda of = 56th IETF=20 meeting in San Francisco, but there is no any session = about routing of=20 ad hoc wireless networks. Could somebody confirm this for me = ?
 
Best,
 
Li-Ping Chou
Panansonic Taiwan Lab.
------=_NextPart_000_0062_01C2D352.B738D7D0-- --__--__-- Message: 2 From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Thu, 13 Feb 2003 11:21:34 -0300 Subject: [manet] Paper Hello folks, Where can I obtain the paper "Dynamic Address Allocation Protocols for Mobile Ad Hoc Networks" written by Praveena Patchipulusu? Best regards. --------------------------------------------------- Fábio Mesquita Buiati Universidade de Brasília - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- --__--__-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet End of manet Digest _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 15:06:13 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24444 for ; Thu, 13 Feb 2003 15:06:13 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DK9VH16474 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 15:09:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DK9Up16471 for ; Thu, 13 Feb 2003 15:09:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24388 for ; Thu, 13 Feb 2003 15:05:41 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJuGp15028; Thu, 13 Feb 2003 14:56:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJqDp14865 for ; Thu, 13 Feb 2003 14:52:13 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23398 for ; Thu, 13 Feb 2003 14:48:24 -0500 (EST) Received: (qmail 4803 invoked by uid 417); 13 Feb 2003 19:52:09 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 13 Feb 2003 19:52:09 -0000 Received: from ankur ([203.94.198.18]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Thu, 13 Feb 2003 12:52:04 -0700 Message-ID: <002201c2d399$7f7c3a20$12c65ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: gupta@cpsc.ucalgary.ca Cc: manet@ietf.org References: <3E47F391.9030004@cpsc.ucalgary.ca> Subject: Re: [manet] Questions regarding APE Date: Thu, 13 Feb 2003 23:50:57 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Abhinav, You can use Cisco cards with APE testbed. But the patch available for spy logging is only for Orinoco cards. So, you won't be able to draw graphs which require "vM - virtual mobility" parameter with Cisco cards. Otherwise, it will work perfectly with any card. The error that "filesystem was not cleanly unmounted" is one of the known issues as mentioned in their documentation. As far as I know, they are not able to fix it by now. You will get the same error no matter you use the default APE implementation or compile your own. - Ankur ----- Original Message ----- From: Abhinav Gupta To: manet Sent: Tuesday, February 11, 2003 12:16 AM Subject: [manet] Questions regarding APE > Hi, > > I am using Cisco Aironet 350 wireless cards on the laptop and I was > concerned if the APE testbed would work with them or not (I know that > APE supports Orinoco). Is there anyone who has used Aironet 35X cards on > APE? > > There is another issue that is bothering me. Everytime I boot into Linux > after running APE, I get the message that the filesystem was not cleanly > unmounted and then Linux proceeds to check the filesystem. This not only > happened with my compiled distribution of APE, but also with the zip > version of APE availaible on the APE website. Is anyone else also facing > a similar problem? If yes, what is the solution to this problem? > > Thanks. > > Abhinav. > > > _______________________________________________ > 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 mailnull@www1.ietf.org Thu Feb 13 15:12:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25015 for ; Thu, 13 Feb 2003 15:12:07 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DKFPm16819 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 15:15:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKFOp16816 for ; Thu, 13 Feb 2003 15:15:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24963 for ; Thu, 13 Feb 2003 15:11:35 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJwXp15115; Thu, 13 Feb 2003 14:58:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJqIp14877 for ; Thu, 13 Feb 2003 14:52:18 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23401 for ; Thu, 13 Feb 2003 14:48:29 -0500 (EST) Received: (qmail 5095 invoked by uid 417); 13 Feb 2003 19:52:14 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 13 Feb 2003 19:52:14 -0000 Received: from ankur ([203.94.198.18]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Thu, 13 Feb 2003 12:52:09 -0700 Message-ID: <002301c2d399$82772aa0$12c65ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: "l s" Cc: manet@ietf.org References: <20030212123253.79422.qmail@web20702.mail.yahoo.com> Subject: Re: [manet] IP not always required? Date: Thu, 13 Feb 2003 23:57:28 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Well, if you are using AODV, DSR or any other exisiting routing protocol for ad hoc networks, then you have to include the IP header in the packet. Otherwise, they won't be routed in our present architecture. The feautre that you mentioned in Glomosim - 'The Message is sent without an IP header" - possibly it is just for testing purposes when doing experiments with header compression. Refer to ROHC group for more on header compression. Regards Ankur ----- Original Message ----- From: l s To: Cc: Sent: Wednesday, February 12, 2003 6:02 PM Subject: [manet] IP not always required? > General MANET question, with a setup using IP, TCP and > AODV routing: > > In Glomosim there are functions in the IP layer (in > nwip.pc) that state 'The Message is sent > WITHOUT an IP header', when passing from the Transport > and Routing layers, through the IP, to the MAC layer > beneath. How can this be and why is no IP header > needed? > > If it has no IP header then surely a higher level > packet, such as TCP or AODV cannot be put into IP > packets? > > The way I understood it was that all packets had to be > put onto IP, is this not so? If not then what are the > rules for what needs to be put onto IP and what > doesn't? > > > When the receiving node gets a message and passes it > up from the MAC to the IP layer, then how does it know > it should pass it to the AODV routing, given that > there are no instructions as there is no IP header? > > Please, if anyone could help. > > Lee -S- > CCSR, University of Surrey > > > __________________________________________________ > Do You Yahoo!? > Everything you'll ever need on one web page > from News and Sport to Email and Music Charts > http://uk.my.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 mailnull@www1.ietf.org Thu Feb 13 15:48:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29253 for ; Thu, 13 Feb 2003 15:48:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DKqFR19078 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 15:52:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKqFp19075 for ; Thu, 13 Feb 2003 15:52:15 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29175 for ; Thu, 13 Feb 2003 15:48:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKZIp17738; Thu, 13 Feb 2003 15:35:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKWxp17668 for ; Thu, 13 Feb 2003 15:32:59 -0500 Received: from cse.uta.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26528 for ; Thu, 13 Feb 2003 15:29:09 -0500 (EST) Received: from uta.edu (wpnh305.uta.edu [129.107.57.25]) by cse.uta.edu (8.9.0/8.9.0) with ESMTP id OAA09941 for ; Thu, 13 Feb 2003 14:36:09 -0600 (CST) Message-ID: <3E4C00F2.5020806@uta.edu> Date: Thu, 13 Feb 2003 14:32:50 -0600 From: Gergely Zaruba User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en,pdf MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1DKWxp17669 Subject: [manet] CfP: Wireless Personal Area Networks Minitrack at HICSS Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Our appologies if this is a duplicate ********************************************************************** Call for Papers Minitrack on Wireless Personal Area Networks (WPANs) Part of the Software Track at the Thirty-seventh Annual Hawaiian International Conference on System Sciences (HICSS37), Big Island of Hawaii, January 5-8, 2004 http://crystal.uta.edu/~zaruba/hicss37/ Optional but encouraged abstract submission deadline: March 31, 2003 Submission deadline: June 1, 2003 ********************************************************************** Overview: Wireless personal area networks (WPANs) are short to very short-range wireless networks that can be used to exchange information between devices in the reach of a person. WPANs can be used to replace cables between computers and their peripherals, to establish communities helping people do their everyday chores making them more productive, or to establish location aware services. It is predicted that not only will most PDAs, phones, laptops include WPAN technology but that the number of small WPAN enabled devices (e.g., pens, cameras, headsets, various sensors) will soon outnumber the computers on the Internet. The best example representing WPANs is the recent industry standard: Bluetooth, other examples include Spike (for real time gaming - proprietary technology), and in the broad sense HomeRF. The IEEE 802 committee has also realized the importance of short-range wireless networking and initiated the establishment of the IEEE 802.15 working group to standardize protocols and interfaces for wireless personal area networking. Another key issue is the inter-working of wireless technologies to create heterogeneous wireless networks. For instance, WPANs and WLANs will enable an extension of the third generation (3G) cellular networks (i.e., UMTS and cdma2000) into devices without direct cellular access thus pointing towards next generation wireless networking. Moreover, devices interconnected in a WPAN may be able to utilize a combination of 3G access and WLAN access by selecting the access that is best for the moment. In such networks 3G, WLAN and WPAN technologies do not compete against each other but enable the user to select the best connectivity for his/her purposes. Today, WPAN research covers a very broad area, starting from technical issues like automatic formation of networks or security issues and going up all the stack to the question what kind of applications will be used in WPANs. We expect that the availability of a cheap short-range wireless technology will further fuel research and development in what, where and most importantly how WPAN technologies could be used for. Minitrack chairs: Frank Kargl, University of Ulm, Germany (frank.kargl@informatik.uni-ulm.edu) Dr. Elaine Lawrence, University of Technology, Sydney (elaine@it.uts.edu.au) Prof. Gergely V. Záruba, The University of Texas at Arlington, USA (zaruba@uta.edu) Important Deadlines: March 31, 2003 Abstracts submitted for guidance and indication of appropriate content. June 1, 2003 Full papers submitted to Minitrack Chairs through the Minitrack's Website. August 31, 2003 Notice of accepted papers sent to Authors. October 1, 2003 Accepted manuscripts sent electronically to the publisher. Authors must be registered for the conference by this date. Submission Guidelines: Abstracts need to be submitted via email to Gergely Zaruba at: zaruba@uta.edu in pdf format only. For full paper submission instructions please read and follow the online submission instructions at the minitrack's web-site: http://crystal.uta.edu/~zaruba/hicss37/ (The final paper must be no longer than 10 pages, double-column, single spaced.) Scope: The minitrack will concentrate on completed or ongoing research in the area of wireless local area networking and wireless personal area networking (excluding manufacturing). Areas of interest include but are not limited to research in: - Protocols tailored to WPANs - QoS provisioning in WPANs - WPAN applications - Performance evaluation - TCP performance of WPANs - Bluetooth for ad hoc networks (scatternets) - Bluetooth performance evaluation - Routing in Bluetooth scatternets - Security issues of WPANs - IP over Bluetooth - Mobility management and seamless integration of WPANs - Interoperability, interference and co-existence of WPANs, WLANs and 3G networks - WPANs vs. WLANs - Caching in WPANs - Service discovery in WPANs - Integration and heterogeneous wireless infrastructures employing WPANs - WPAN specific applications -- ********************************************************* Gergely V. Zaruba Ph.D. C.S. zaruba@ieee.org Assistant Professor Office: 305 Nedderman Hall Computer Science and Engineering Department (CSE@UTA) Center for Research in Wireless Mobility and Networking The University of Texas at Arlington phone:(817) 272 3602 fax:(817) 272 3784 ********************************************************* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 17:29:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13867 for ; Thu, 13 Feb 2003 17:29:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DMXHQ25890 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 17:33:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMXGp25887 for ; Thu, 13 Feb 2003 17:33:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13827 for ; Thu, 13 Feb 2003 17:29:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMIVp25117; Thu, 13 Feb 2003 17:18:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DM9Xp24729 for ; Thu, 13 Feb 2003 17:09:33 -0500 Received: from eposta.kablonet.com.tr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11382 for ; Thu, 13 Feb 2003 17:05:39 -0500 (EST) Received: (qmail 97338 invoked by uid 0); 13 Feb 2003 22:14:55 -0000 Received: from unknown (HELO ev) (aliergin@kablonet.com.tr@195.174.9.144) by 0 with SMTP; 13 Feb 2003 22:14:55 -0000 Message-ID: <006e01c2d3ac$411e84f0$0200a8c0@ev> From: "Mesut Ali Ergin" To: References: <20030212123253.79422.qmail@web20702.mail.yahoo.com> <002301c2d399$82772aa0$12c65ecb@ankur> Subject: Re: [manet] IP not always required? Date: Fri, 14 Feb 2003 00:07:08 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear All Those Interested, The mentioned nwip.pc homes the IP layer code in GloMoSim and the 'The Message is sent without an IP header" comment belongs to "NetworkIpSendRawGlomoMessage" function (and its delayed variant). IP header-less packet exists just for a short time and those mentioned functions immediately add IP headers to the packets. (In short, no data packet is actually sent out from nwip.pc to MAC without an IP header) The simple snippet is given below. Hope it helps. void NetworkIpSendRawGlomoMessage( GlomoNode* node, Message* rawMessage, NODE_ADDR destinationAddress, NetworkQueueingPriorityType priority, unsigned char protocol, unsigned int ttl) { AddIpHeader(node, rawMessage, destinationAddress, priority, protocol, ttl); RoutePacketAndSendToMac(node, rawMessage); } -- Mesut Ali Ergin ergin@ics.yeditepe.edu.tr Department of Computer Engineering, Yeditepe University, Kayisdagi, 81120, Istanbul, Turkey Tel: +90 216 578 0429 +90 216 578 0420 Fax: +90 216 578 0400 ----- Original Message ----- From: "Ankur Jain" To: "l s" Cc: Sent: Thursday, February 13, 2003 8:27 PM Subject: Re: [manet] IP not always required? > Well, if you are using AODV, DSR or any other exisiting routing protocol for > ad hoc networks, then you have to include the IP header in the packet. > Otherwise, they won't be routed in our present architecture. > > The feautre that you mentioned in Glomosim - 'The Message is sent without an > IP header" - possibly it is just for testing purposes when doing experiments > with header compression. Refer to ROHC group for more on header compression. > > Regards > Ankur > > > > > > > > ----- Original Message ----- > From: l s > To: > Cc: > Sent: Wednesday, February 12, 2003 6:02 PM > Subject: [manet] IP not always required? > > > > General MANET question, with a setup using IP, TCP and > > AODV routing: > > > > In Glomosim there are functions in the IP layer (in > > nwip.pc) that state 'The Message is sent > > WITHOUT an IP header', when passing from the Transport > > and Routing layers, through the IP, to the MAC layer > > beneath. How can this be and why is no IP header > > needed? > > > > If it has no IP header then surely a higher level > > packet, such as TCP or AODV cannot be put into IP > > packets? > > > > The way I understood it was that all packets had to be > > put onto IP, is this not so? If not then what are the > > rules for what needs to be put onto IP and what > > doesn't? > > > > > > When the receiving node gets a message and passes it > > up from the MAC to the IP layer, then how does it know > > it should pass it to the AODV routing, given that > > there are no instructions as there is no IP header? > > > > Please, if anyone could help. > > > > Lee -S- > > CCSR, University of Surrey > > > > > > __________________________________________________ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.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 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 20:57:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25900 for ; Thu, 13 Feb 2003 20:57:54 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1E21Jb05653 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 21:01:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E21Jp05650 for ; Thu, 13 Feb 2003 21:01:19 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25888 for ; Thu, 13 Feb 2003 20:57:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E1iYp04836; Thu, 13 Feb 2003 20:44:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E1dJp04654 for ; Thu, 13 Feb 2003 20:39:19 -0500 Received: from sunlight.wichita.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25407 for ; Thu, 13 Feb 2003 20:35:24 -0500 (EST) Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.1 #30593) id <0HA900H01Z99VK@sunlight.wichita.edu> for manet@ietf.org; Thu, 13 Feb 2003 19:39:09 -0600 (CST) Received: from webmail.wichita.edu (BIERSTADT.UC.TWSU.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.1 #30593) with ESMTP id <0HA900HC9Z98KQ@sunlight.wichita.edu> for manet@ietf.org; Thu, 13 Feb 2003 19:39:08 -0600 (CST) Date: Thu, 13 Feb 2003 19:39:08 -0600 From: lxsaripalli To: manet@ietf.org Message-id: <3E4BA298@webmail.wichita.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.62 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-WebMail-UserID: lxsaripalli@wichita.edu X-EXP32-SerialNo: 00003023 Content-Transfer-Encoding: 7bit Subject: [manet] Regarding the load balancing property Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit hi , i'am new to the mailing list .... i want to get started pf project involving adhoc networks..... i would like to evaluate the load balancing property of AODMV... can some one help regarding this thanks Regards Lavanya Saripalli Graduate Research Assitant Department of Psychology National Institute of Aviation and Research Wichita State University. Ph.316.978.5776 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 13 23:09:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29219 for ; Thu, 13 Feb 2003 23:09:36 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1E4D5g13181 for manet-archive@odin.ietf.org; Thu, 13 Feb 2003 23:13:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E4D4p13178 for ; Thu, 13 Feb 2003 23:13:04 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29210 for ; Thu, 13 Feb 2003 23:09:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E3xXp11784; Thu, 13 Feb 2003 22:59:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1E3osp11581 for ; Thu, 13 Feb 2003 22:50:54 -0500 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28726 for ; Thu, 13 Feb 2003 22:46:50 -0500 (EST) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329); Fri, 14 Feb 2003 11:50:33 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: [manet] Regarding the load balancing property Date: Fri, 14 Feb 2003 11:50:32 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E03635041@MBXSRV26.stu.nus.edu.sg> Thread-Topic: [manet] Regarding the load balancing property Thread-Index: AcLTy0yX9HlTo37PQom8MsYNC5qDbgAEINdg From: "Marwaha Shivanajay" To: Cc: X-OriginalArrivalTime: 14 Feb 2003 03:50:33.0050 (UTC) FILETIME=[397C2BA0:01C2D3DC] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1E3osp11582 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, This is one way to balance the load: http://www.nmsl.cs.ucsb.edu/~ksarac/icnp/2001/papers/2001-2.pdf Is there any other also?? Regards, Shivanajay "Obstacles are something you see, when you take your eyes off the goal" -----Original Message----- From: lxsaripalli [mailto:lxsaripalli@wichita.edu] Sent: Friday, February 14, 2003 9:39 AM To: manet@ietf.org Subject: [manet] Regarding the load balancing property hi , i'am new to the mailing list .... i want to get started pf project involving adhoc networks..... i would like to evaluate the load balancing property of AODMV... can some one help regarding this thanks Regards Lavanya Saripalli Graduate Research Assitant Department of Psychology National Institute of Aviation and Research Wichita State University. Ph.316.978.5776 _______________________________________________ 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 mailnull@www1.ietf.org Fri Feb 14 10:42:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25155 for ; Fri, 14 Feb 2003 10:42:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1EFkZI02238 for manet-archive@odin.ietf.org; Fri, 14 Feb 2003 10:46:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EFkZp02235 for ; Fri, 14 Feb 2003 10:46:35 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25111 for ; Fri, 14 Feb 2003 10:42:22 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EFMZp00500; Fri, 14 Feb 2003 10:22:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EFD7p32727 for ; Fri, 14 Feb 2003 10:13:07 -0500 Received: from zrtps06s.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24313 for ; Fri, 14 Feb 2003 10:08:55 -0500 (EST) Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h1EFCdU16806 for ; Fri, 14 Feb 2003 10:12:39 -0500 (EST) Received: from zrtpd0j9.us.nortel.com ([47.140.203.27]) by zrtpd0jn.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1L3PQL4D; Fri, 14 Feb 2003 10:12:39 -0500 Received: from americasm01.nt.com (wnc1h04q.us.nortel.com [47.142.211.72]) by zrtpd0j9.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1V5F8L7K; Fri, 14 Feb 2003 10:12:39 -0500 Message-ID: <3E4D0766.576ADF19@americasm01.nt.com> Date: Fri, 14 Feb 2003 10:12:38 -0500 From: "He Huang" Organization: Nortel Networks X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] multiple channel operation in wireless networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, All, I'm interested in multiple channel operation in wireless networks. Could anyone point out the papers or other resources? Thanks, He Huang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 14 11:58:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27129 for ; Fri, 14 Feb 2003 11:58:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1EH2bi07031 for manet-archive@odin.ietf.org; Fri, 14 Feb 2003 12:02:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EH2bp07028 for ; Fri, 14 Feb 2003 12:02:37 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27088 for ; Fri, 14 Feb 2003 11:58:07 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EGhRp05881; Fri, 14 Feb 2003 11:43:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EGYcp04890 for ; Fri, 14 Feb 2003 11:34:38 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26304 for ; Fri, 14 Feb 2003 11:30:24 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id LAA17064 for ; Fri, 14 Feb 2003 11:34:09 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.1.45) with SMTP id M2003021411340916239 for ; Fri, 14 Feb 2003 11:34:09 -0500 Message-Id: <5.1.1.5.2.20030214113120.02edb6e8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 14 Feb 2003 11:33:28 -0500 To: manet@ietf.org From: Joe Macker Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [manet] Scheduled meeting in San Fran Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All: While I had requested it in Jan, it took awhile for the meeting schedule for manet to show up in the Draft Agenda. At last look it was Thursday afternoon, March 20 1300-1500. Please remember the agenda is not final yet and can shift. -Joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 14 17:48:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08277 for ; Fri, 14 Feb 2003 17:48:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1EMqdU00504 for manet-archive@odin.ietf.org; Fri, 14 Feb 2003 17:52:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EMqdp00501 for ; Fri, 14 Feb 2003 17:52:39 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08273 for ; Fri, 14 Feb 2003 17:48:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EMaLp31243; Fri, 14 Feb 2003 17:36:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EMRTp30897 for ; Fri, 14 Feb 2003 17:27:29 -0500 Received: from web13310.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07499 for ; Fri, 14 Feb 2003 17:23:07 -0500 (EST) Message-ID: <20030214222653.17373.qmail@web13310.mail.yahoo.com> Received: from [152.15.22.78] by web13310.mail.yahoo.com via HTTP; Fri, 14 Feb 2003 14:26:53 PST Date: Fri, 14 Feb 2003 14:26:53 -0800 (PST) From: Xin Yan To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-786512309-1045261613=:16616" Subject: [manet] Suvivable Ad Hoc Network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --0-786512309-1045261613=:16616 Content-Type: text/plain; charset=us-ascii hi, Could anyone help to tell me any research links for "survivable ad hoc network"? Seems it is a NORMAL state for the "frequent failures of links and nodes" in Ad Hoc network, so are there any sepcial considerations when designing Ad Hoc protocols for this purpose? Appreciate your help! YXin --------------------------------- Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day --0-786512309-1045261613=:16616 Content-Type: text/html; charset=us-ascii

hi, Could anyone help to tell me any research links for "survivable ad hoc network"? Seems it is a NORMAL state for the "frequent failures of links and nodes" in Ad Hoc network, so are there any sepcial considerations when designing Ad Hoc protocols for this purpose?

Appreciate your help!

YXin


Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day --0-786512309-1045261613=:16616-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 14 18:11:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08857 for ; Fri, 14 Feb 2003 18:11:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1ENEuQ02380 for manet-archive@odin.ietf.org; Fri, 14 Feb 2003 18:14:56 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ENEup02377 for ; Fri, 14 Feb 2003 18:14:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08825 for ; Fri, 14 Feb 2003 18:10:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EMwgp00757; Fri, 14 Feb 2003 17:58:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EMrXp00526 for ; Fri, 14 Feb 2003 17:53:33 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08295 for ; Fri, 14 Feb 2003 17:49:11 -0500 (EST) Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1EMqvW168679 for ; Fri, 14 Feb 2003 17:52:57 -0500 (EST) Received: from zathras (zathras.cc.vt.edu [198.82.162.117]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BBG71877; Fri, 14 Feb 2003 17:52:57 -0500 (EST) X-WebMail-UserID: bsvijay Date: Fri, 14 Feb 2003 17:52:57 -0500 From: Vijayanand Ballapuram To: manet@ietf.org X-EXP32-SerialNo: 00002964 Message-ID: <3E4F3D29@zathras> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-Transfer-Encoding: 7bit Subject: [manet] Service Discovery Protocols Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Everyone, I need information required service discovery protocols in Wirless Networks(Base station) and MANETs. I would greatly appreciate if anyone let's me to know reserach that has been done so far in SERVICE DISCOVERY PROTOCOLS, papers, Drafts and/or any other technical documents which would give me RELATED INFORMATION. Thanks in Advance, Vijay _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 14 22:29:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13658 for ; Fri, 14 Feb 2003 22:29:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1F3Xg716934 for manet-archive@odin.ietf.org; Fri, 14 Feb 2003 22:33:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F3Xgp16931 for ; Fri, 14 Feb 2003 22:33:42 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13641 for ; Fri, 14 Feb 2003 22:29:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F3Jop16378; Fri, 14 Feb 2003 22:19:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F3F5p16277 for ; Fri, 14 Feb 2003 22:15:05 -0500 Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13352 for ; Fri, 14 Feb 2003 22:10:38 -0500 (EST) Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for manet@ietf.org; Fri, 14 Feb 2003 22:13:27 -0500 Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003021422141723478 ; Fri, 14 Feb 2003 22:14:17 -0500 Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19) id <1XS6ZCTM>; Fri, 14 Feb 2003 22:14:00 -0500 Message-Id: <881CC7991757D51196CF00508BCFE5910E8A6399@mcl-its-exs03.mail.saic.com> From: "Krishnaswamy, Padma" To: "Charles E. Perkins" Cc: manet@ietf.org Subject: RE: [manet] Autoconfiguration protocols Date: Fri, 14 Feb 2003 22:14:17 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1F3F5p16278 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, On reading the ID in the url below, I had a few questions. The relevant text from the ID is in quotes- 1. " In this document, a mechanism by which a node in an ad hoc network may autoconfigure an IP address which is unique throughout the connected portion of the ad hoc network is specified. " --does this mean the 169.254/16 space could be used separately in 2 separate disjoint adhoc nets resulting in a possible collision? Was this prefix selected instead of a block from RFC 1918 so that zeroconf criteria of coexistence with 'administered' nets is satisfied? 2. "When a node in an ad hoc network wishes to obtain an IP address, it may be difficult or impossible to contact any address allocation agency in the network. In such cases, according to the specifications given in this document, the node attempts to select a random address (on network 169.254/16 in case of IPv4, or on prefix MANET_INITIAL_PREFIX in case of IPv6). This is analogous to the way that Autonet allocations are done, and as is proposed in the zeroconf working group [3]." --what is the analogy being referred to , with what the zeroconf group proposes? 3.How is DAD done- by repeat AREQ/AREP? rgds and thanks, Padma Krishnaswamy > -----Original Message----- > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > Sent: Monday, February 10, 2003 6:40 PM > To: Mansoor Mohsin > Cc: Fábio Buiati; manet@ietf.org > Subject: Re: [manet] Autoconfiguration protocols > > > > Hello folks, > > We had a draft on address autoconfiguration, > currently available at the following URL: > http://people.nokia.net/charliep/txt/aodvid/autoconf.txt > It was expected to be a working group item, but recently > the manet group has not been adding new work. > > The autoconfiguration ideas have been implemented, > are known to work, and have been published in various > papers at technical conferences. > > Regards, > Charlie P. > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 15 04:47:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29430 for ; Sat, 15 Feb 2003 04:47:15 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1F9pJ313345 for manet-archive@odin.ietf.org; Sat, 15 Feb 2003 04:51:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F9pIp13342 for ; Sat, 15 Feb 2003 04:51:18 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29424 for ; Sat, 15 Feb 2003 04:46:43 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F9cIp12957; Sat, 15 Feb 2003 04:38:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F9XMp12148 for ; Sat, 15 Feb 2003 04:33:22 -0500 Received: from web40404.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA29236 for ; Sat, 15 Feb 2003 04:28:48 -0500 (EST) Message-ID: <20030215093230.62725.qmail@web40404.mail.yahoo.com> Received: from [193.95.79.252] by web40404.mail.yahoo.com via HTTP; Sat, 15 Feb 2003 10:32:30 CET Date: Sat, 15 Feb 2003 10:32:30 +0100 (CET) From: =?iso-8859-1?q?real=20no=20dream?= To: manet@ietf.org In-Reply-To: <20030213170003.1934.97600.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] consensus and failure detectors Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hello Is there any interesent papers which deal with groupmenbersihp and consensus , failure detectors for mobile ad hoc networks thank in advance ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 17 00:06:26 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04904 for ; Mon, 17 Feb 2003 00:06:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1H5BMH19570 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 00:11:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1H5BMp19567 for ; Mon, 17 Feb 2003 00:11:22 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04893 for ; Mon, 17 Feb 2003 00:05:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1H4l7p18092; Sun, 16 Feb 2003 23:47:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1H4bnp17906 for ; Sun, 16 Feb 2003 23:37:49 -0500 Received: from mailgw2.atr.co.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04400 for ; Sun, 16 Feb 2003 23:32:21 -0500 (EST) Received: from vcms.atr.co.jp (epsilon.atr.co.jp [133.186.254.10]) by mailgw2.atr.co.jp (Postfix) with ESMTP id B0BD018B12 for ; Mon, 17 Feb 2003 13:36:07 +0900 (JST) Received: from acr.acr.atr.co.jp (localhost [127.0.0.1]) by vcms.atr.co.jp (Postfix) with ESMTP id E9920397E5; Mon, 17 Feb 2003 13:36:05 +0900 (JST) Received: from [133.186.57.59] (rpc41 [133.186.57.59]) by acr.acr.atr.co.jp (Postfix) with ESMTP id 10CBB3D40B0; Mon, 17 Feb 2003 13:36:24 +0900 (JST) Date: Mon, 17 Feb 2003 13:37:04 +0900 From: Shingo HORISAWA To: manet@ietf.org Cc: masayama@atr.co.jp, kosuga@atr.co.jp Message-Id: <20030217131215.4F07.HORISAWA@atr.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.06 Content-Transfer-Encoding: 7bit Subject: [manet] GSR/FSR for Linux v0.3.3 released. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, all. GSR/FSR implementation for Linux version 0.3.3 is now available. You can download it form here: http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html The changes from version 0.3.3 are as follows: - introduce statistics And from version 0.3.2, ipkg package for ARM is available. You can experience GSR/FSR routing on iPAQ(familiar)/LinuxZaurus if you can use it. Please feel free to contact me if you have any questions or demands. Thanks. ********************************************************** Shingo Horisawa Researcher Department 1 ATR Adaptive Communications Research Laboratories 2-2-2 Hikaridai, Seika-cho, Soraku-gun, Kyoto 619-0288, Japan TEL +81-774-95-2720 FAX +81-774-95-1509 E-MAIL horisawa@atr.co.jp URL : http://www.acr.atr.co.jp/acr/ ********************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 17 05:35:13 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19339 for ; Mon, 17 Feb 2003 05:35:13 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HAeGu16811 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 05:40:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HAeGp16808 for ; Mon, 17 Feb 2003 05:40:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19328 for ; Mon, 17 Feb 2003 05:34:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HAR6p15488; Mon, 17 Feb 2003 05:27:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HAK9p15242 for ; Mon, 17 Feb 2003 05:20:09 -0500 Received: from iramx2.ira.uni-karlsruhe.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19059 for ; Mon, 17 Feb 2003 05:14:35 -0500 (EST) Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 18kiLr-0003c7-00; Mon, 17 Feb 2003 11:18:19 +0100 Received: from i40pc216.ipd.uni-karlsruhe.de ([141.3.48.216] helo=Piacenza) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian)) id 18kiLp-0000uk-00; Mon, 17 Feb 2003 11:18:17 +0100 From: "Michael Klein" To: Vijayanand Ballapuram CC: "manet@ietf.org" Subject: Re: [manet] Service Discovery Protocols Organization: IPD - Universitaet Karlsruhe X-mailer: Foxmail 4.2 [eg] Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Date: Mon, 17 Feb 2003 11:18:19 +0100 Message-Id: Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello Vijay, in the context of manets, we had some work done in the domain of service discovery. You can find some of our ideas in one of our papers, e.g. http://citeseer.nj.nec.com/klein02multilayer.html. Best wishes, Michael Klein -------- Original Message -------- Subject: [manet] Service Discovery Protocols Date: 2003-02-14, 17:52:00 From: Vijayanand Ballapuram To: manet >Hi Everyone, > >I need information required service discovery protocols in Wirless >Networks(Base station) and MANETs. I would greatly appreciate if anyone let's >me to know reserach that has been done so far in SERVICE DISCOVERY PROTOCOLS, >papers, Drafts and/or any other technical documents which would give me >RELATED INFORMATION. > >Thanks in Advance, > >Vijay > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet ---------------------------------- __________________________________________________________________ Michael Klein kleinm@ipd.uni-karlsruhe.de IPD, Raum 340 Universität Karlsruhe Tel: 0721 / 608-7336 Am Fasanengarten 5 76128 Karlsruhe http://wwwipd.ira.uka.de/~kleinm __________________________________________________________________ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 17 12:06:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26195 for ; Mon, 17 Feb 2003 12:06:27 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HHBcX07984 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 12:11:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HHBcp07981 for ; Mon, 17 Feb 2003 12:11:38 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26187 for ; Mon, 17 Feb 2003 12:05:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HGvOp06262; Mon, 17 Feb 2003 11:57:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HGq9p06088 for ; Mon, 17 Feb 2003 11:52:09 -0500 Received: from Linus.UCIS.Dal.Ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25551 for ; Mon, 17 Feb 2003 11:46:27 -0500 (EST) Received: from webmail.ucis.dal.ca (WebMail.UCIS.Dal.Ca [129.173.1.95]) by Linus.UCIS.Dal.Ca (8.12.6/8.12.6) with ESMTP id h1HGoDJH019540 for ; Mon, 17 Feb 2003 12:50:14 -0400 (AST) X-WebMail-UserID: zhen@mail.cs.dal.ca Date: Mon, 17 Feb 2003 12:50:26 -0400 From: zhen To: manet@ietf.org X-EXP32-SerialNo: 00002905 Subject: Re: [manet] Questions regarding APE Message-ID: <3E6A1081@webmail.ucis.dal.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.61.07 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit How about D-link Air DWL-650 802.11b PCMCIA NIC version 1.24? thanks Zhen >Message: 2 >Reply-To: "Ankur Jain" >From: "Ankur Jain" >To: gupta@cpsc.ucalgary.ca >Cc: manet@ietf.org >Subject: Re: [manet] Questions regarding APE >Date: Thu, 13 Feb 2003 23:50:57 +0530 > >Hi Abhinav, > >You can use Cisco cards with APE testbed. But the patch available for spy >logging is only for Orinoco cards. So, you won't be able to draw graphs >which require "vM - virtual mobility" parameter with Cisco cards. Otherwise, >it will work perfectly with any card. > >The error that "filesystem was not cleanly unmounted" is one of the known >issues as mentioned in their documentation. As far as I know, they are not >able to fix it by now. You will get the same error no matter you use the >default APE implementation or compile your own. > >- Ankur > > > > >----- Original Message ----- >From: Abhinav Gupta >To: manet >Sent: Tuesday, February 11, 2003 12:16 AM >Subject: [manet] Questions regarding APE > > >> Hi, >> >> I am using Cisco Aironet 350 wireless cards on the laptop and I was >> concerned if the APE testbed would work with them or not (I know that >> APE supports Orinoco). Is there anyone who has used Aironet 35X cards on >> APE? >> >> There is another issue that is bothering me. Everytime I boot into Linux >> after running APE, I get the message that the filesystem was not cleanly >> unmounted and then Linux proceeds to check the filesystem. This not only >> happened with my compiled distribution of APE, but also with the zip >> version of APE availaible on the APE website. Is anyone else also facing >> a similar problem? If yes, what is the solution to this problem? >> >> Thanks. >> >> Abhinav. >> >> >> _______________________________________________ >> 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 mailnull@www1.ietf.org Mon Feb 17 13:14:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27663 for ; Mon, 17 Feb 2003 13:14:57 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HIKA712193 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 13:20:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HIKAp12190 for ; Mon, 17 Feb 2003 13:20:10 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27660 for ; Mon, 17 Feb 2003 13:14:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HI5wp10814; Mon, 17 Feb 2003 13:05:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HI1Fp10692 for ; Mon, 17 Feb 2003 13:01:15 -0500 Received: from mailcity.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27260 for ; Mon, 17 Feb 2003 12:55:32 -0500 (EST) Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Mon, 17 Feb 2003 17:58:55 -0000 To: "manet@ietf.org" Date: Mon, 17 Feb 2003 12:58:55 -0500 From: "Yasser A. Lotfy" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off Reply-To: yasser.lotfy@lycos.com X-Mailer: MailCity Service X-Priority: 3 X-Sender-Ip: 66.185.84.207 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Gateway Discovery Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Good day everyone, Has there been any work on ad-hoc gateway discovery mechanisms. Can you please point me to any papers on this area? Regards, Yasser Carleton U _____________________________________________________________ Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year. http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 17 14:03:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28515 for ; Mon, 17 Feb 2003 14:03:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HJ8Oe15411 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 14:08:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HJ8Op15408 for ; Mon, 17 Feb 2003 14:08:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28486 for ; Mon, 17 Feb 2003 14:02:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HIsAp14077; Mon, 17 Feb 2003 13:54:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HIoVp13971 for ; Mon, 17 Feb 2003 13:50:31 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28072 for ; Mon, 17 Feb 2003 13:44:46 -0500 (EST) Received: (qmail 23184 invoked by uid 417); 17 Feb 2003 18:48:34 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 17 Feb 2003 18:48:34 -0000 Received: from ankur ([203.94.199.85]) (AUTH: LOGIN ankurjain@softhome.net) by softhome.net with esmtp; Mon, 17 Feb 2003 11:48:05 -0700 Message-ID: <024c01c2d6b5$3ee64c20$55c75ecb@ankur> Reply-To: "Ankur Jain" From: "Ankur Jain" To: "zhen" , manet@ietf.org References: <3E6A1081@webmail.ucis.dal.ca> Subject: Re: [manet] Questions regarding APE Date: Mon, 17 Feb 2003 23:45:32 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Zhen As I said before, you can use any wireless card for using APE. But for using the spylogging feature, you have to use Lucent's Orinoco card only. In the current version , the patches are available only for Orinoco cards. - Ankur ----- Original Message ----- From: zhen To: Sent: Monday, February 17, 2003 10:20 PM Subject: Re: [manet] Questions regarding APE > How about D-link Air DWL-650 802.11b PCMCIA NIC version 1.24? > > thanks > > Zhen > > >Message: 2 > >Reply-To: "Ankur Jain" > >From: "Ankur Jain" > >To: gupta@cpsc.ucalgary.ca > >Cc: manet@ietf.org > >Subject: Re: [manet] Questions regarding APE > >Date: Thu, 13 Feb 2003 23:50:57 +0530 > > > >Hi Abhinav, > > > >You can use Cisco cards with APE testbed. But the patch available for spy > >logging is only for Orinoco cards. So, you won't be able to draw graphs > >which require "vM - virtual mobility" parameter with Cisco cards. Otherwise, > >it will work perfectly with any card. > > > >The error that "filesystem was not cleanly unmounted" is one of the known > >issues as mentioned in their documentation. As far as I know, they are not > >able to fix it by now. You will get the same error no matter you use the > >default APE implementation or compile your own. > > > >- Ankur > > > > > > > > > >----- Original Message ----- > >From: Abhinav Gupta > >To: manet > >Sent: Tuesday, February 11, 2003 12:16 AM > >Subject: [manet] Questions regarding APE > > > > > >> Hi, > >> > >> I am using Cisco Aironet 350 wireless cards on the laptop and I was > >> concerned if the APE testbed would work with them or not (I know that > >> APE supports Orinoco). Is there anyone who has used Aironet 35X cards on > >> APE? > >> > >> There is another issue that is bothering me. Everytime I boot into Linux > >> after running APE, I get the message that the filesystem was not cleanly > >> unmounted and then Linux proceeds to check the filesystem. This not only > >> happened with my compiled distribution of APE, but also with the zip > >> version of APE availaible on the APE website. Is anyone else also facing > >> a similar problem? If yes, what is the solution to this problem? > >> > >> Thanks. > >> > >> Abhinav. > >> > >> > >> _______________________________________________ > >> 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 mailnull@www1.ietf.org Mon Feb 17 14:30:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29350 for ; Mon, 17 Feb 2003 14:30:40 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HJZtf16842 for manet-archive@odin.ietf.org; Mon, 17 Feb 2003 14:35:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HJZtp16839 for ; Mon, 17 Feb 2003 14:35:55 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29337 for ; Mon, 17 Feb 2003 14:30:09 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HJLrp16204; Mon, 17 Feb 2003 14:21:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HJHUp16080 for ; Mon, 17 Feb 2003 14:17:30 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28860 for ; Mon, 17 Feb 2003 14:11:45 -0500 (EST) Received: from photon.ece.cornell.edu (photon.ece.cornell.edu [128.84.81.138]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id h1HJFXK23937 for ; Mon, 17 Feb 2003 14:15:33 -0500 Date: Mon, 17 Feb 2003 14:11:30 -0500 (EST) From: Edward Hua X-X-Sender: eyh5@photon.ece.cornell.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] (disjoint) multipath routing in MANET Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I'm wondering if anybody has done any research in multipath routing in MANET that aims to achieve good end-to-end delay (bounded by some QoS delay parameter) for real-time traffic. Specifically, the multipath routing is a set of disjoint paths. I'm trying to get some idea of the degree of research in this particular area. Thanks in advance. -Ed _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 18 04:57:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23772 for ; Tue, 18 Feb 2003 04:57:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1IA2fY13609 for manet-archive@odin.ietf.org; Tue, 18 Feb 2003 05:02:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IA2fp13606 for ; Tue, 18 Feb 2003 05:02:41 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23752 for ; Tue, 18 Feb 2003 04:56:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1I9nVp13049; Tue, 18 Feb 2003 04:49:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1I9ebp12828 for ; Tue, 18 Feb 2003 04:40:37 -0500 Received: from agorate1.iserver.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23453 for ; Tue, 18 Feb 2003 04:34:34 -0500 (EST) Received: from anakin ([155.54.210.90]) by agorate1.iserver.net (8.12.6) id h1I9cGeG031163; Tue, 18 Feb 2003 02:38:18 -0700 (MST) From: "Pedro M. Ruiz" To: , Subject: RE: [manet] Gateway Discovery Date: Tue, 18 Feb 2003 10:36:34 +0100 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Yasser, We proposed a protocol called MMARP for multicast routing in MANETs which includes opperatons to deal with the interworking with fixed infrastructures. Ad hoc nodes become MIGs (Multicast Internet Gateways) whenever they detect that they are one hop away from the fixed access router. We are still improving the mechanism, but currently the discovery of the MIGs by the rest of ad hoc nodes is done by periodic and constrained advertisement using MMARP_Dfl_Route messages. The constraint is basically that announcements from many MIGs attached to the same access router are detected as duplictes, avoiding unnecessary retransmissions. Finally the decission on which MIG to select is done by each ad hoc node and may depend on many factors (# of hops, delay (selecting the first to come advertisement, etc.). For further details you may look at some material here: http://ants.dif.um.es/staff/pedrom/publications.html Hope it helps, Pedro > -----Mensaje original----- > De: manet-admin@ietf.org [mailto:manet-admin@ietf.org]En nombre de > Yasser A. Lotfy > Enviado el: lunes, 17 de febrero de 2003 18:59 > Para: manet@ietf.org > Asunto: [manet] Gateway Discovery > > > Good day everyone, > > Has there been any work on ad-hoc gateway discovery mechanisms. > Can you please point me to any papers on this area? > > Regards, > > Yasser > Carleton U > > > > _____________________________________________________________ > Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year. > http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus > _______________________________________________ > 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 mailnull@www1.ietf.org Tue Feb 18 05:53:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24905 for ; Tue, 18 Feb 2003 05:53:15 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1IAwmv17258 for manet-archive@odin.ietf.org; Tue, 18 Feb 2003 05:58:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IAwmp17255 for ; Tue, 18 Feb 2003 05:58:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24898 for ; Tue, 18 Feb 2003 05:52:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IAfJp16437; Tue, 18 Feb 2003 05:41:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IAYSp15444 for ; Tue, 18 Feb 2003 05:34:28 -0500 Received: from mailhost.iitb.ac.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24251 for ; Tue, 18 Feb 2003 05:28:24 -0500 (EST) Received: (qmail 1049 invoked from network); 18 Feb 2003 10:18:59 -0000 Received: from newsmtp.iitb.ac.in (144.16.108.201) by mailhost.iitb.ac.in with SMTP; 18 Feb 2003 10:18:59 -0000 Received: (qmail 15201 invoked from network); 18 Feb 2003 10:32:06 -0000 Received: from omkar.it.iitb.ac.in (HELO it.iitb.ac.in) ([10.129.32.22]) (envelope-sender ) by smtp.iitb.ac.in (qmail-ldap-1.03) with SMTP for ; 18 Feb 2003 10:32:05 -0000 Message-ID: <3E520A0C.70103@it.iitb.ac.in> Date: Tue, 18 Feb 2003 15:55:16 +0530 From: Ashish Krishnadeo Shinde User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org X-Scanned: By Symantec Carrier Scan Server Subject: [manet] IP Addressing in Ad hoc networks Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am new to the manet mailing list. I am currently working on enhancing QoS support in Wireless Networks. I would like to know the IP address allocation mechanism for AdHoc networks (These networks may additionally have Internet Connectivity through some Access Point). Regards - Ashish _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 18 08:25:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27693 for ; Tue, 18 Feb 2003 08:25:41 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1IDVHk26844 for manet-archive@odin.ietf.org; Tue, 18 Feb 2003 08:31:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IDVHp26841 for ; Tue, 18 Feb 2003 08:31:17 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27682 for ; Tue, 18 Feb 2003 08:25:09 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IDHxp25874; Tue, 18 Feb 2003 08:17:59 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IDBop25644 for ; Tue, 18 Feb 2003 08:11:50 -0500 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27225 for ; Tue, 18 Feb 2003 08:05:43 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 18 Feb 2003 05:09:31 -0800 Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP; Tue, 18 Feb 2003 13:09:31 GMT X-Originating-IP: [212.4.33.133] From: "Berner Vegge" To: manet@ietf.org Date: Tue, 18 Feb 2003 14:09:31 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Feb 2003 13:09:31.0698 (UTC) FILETIME=[F9BAB920:01C2D74E] Subject: [manet] Convergence time for MANET protocols versus traditional routing protocols Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello all! In Norway we have made some measurements of convergence time for OLSR and AODV. When a relay-node is suddenly turned off it takes about 12 seconds for OLSR and 3 seconds for AODV until traffic is moved to an other relay node (located close to the node that was turned off). I find these values as being rather high and wonder how long time traditional routing protocols would have used in a similar situation... Anyone who has any idea on how long time RIP or OSPF would have used to move the traffic when traffic is sent from node A to node D via node B and node B suddenly is turned off, so that traffic must be re-routed via node C instead? Thanks! Best Regards Berner _________________________________________________________________ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 18 12:17:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02294 for ; Tue, 18 Feb 2003 12:17:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1IHNa310561 for manet-archive@odin.ietf.org; Tue, 18 Feb 2003 12:23:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IHNap10558 for ; Tue, 18 Feb 2003 12:23:36 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02281 for ; Tue, 18 Feb 2003 12:17:25 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IH8Up09813; Tue, 18 Feb 2003 12:08:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IH2Zp08623 for ; Tue, 18 Feb 2003 12:02:35 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01802 for ; Tue, 18 Feb 2003 11:56:23 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id MAA15593; Tue, 18 Feb 2003 12:00:09 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.1.45) with SMTP id M2003021812000825639 ; Tue, 18 Feb 2003 12:00:08 -0500 Message-Id: <5.1.1.5.2.20030218113223.03030588@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Tue, 18 Feb 2003 11:59:49 -0500 To: "Berner Vegge" , manet@ietf.org From: Joe Macker Subject: Re: [manet] Convergence time for MANET protocols versus traditional routing protocols In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 02:09 PM 2/18/2003 +0100, Berner Vegge wrote: >Hello all! >In Norway we have made some measurements of convergence >time for OLSR and AODV. When a relay-node is >suddenly turned off it takes about 12 seconds >for OLSR and 3 seconds for AODV until traffic >is moved to an other relay node (located close >to the node that was turned off). > >I find these values as being rather high and wonder >how long time traditional routing protocols would have >used in a similar situation... I think the question you asked may be dominated by link status detection methods and protocol timers and not necessarily the routing algorithms used. Thus, some of these issues might be seen as protocol agnostic. In OSPF,etc, much of this would be dominated by the hello interval, LSA transmission intervales, router dead intervals, etc. Eg.., a router dead interval for OSPF may be around 40 seconds (the time it takes to decide a neighbor is down after a HELLO is sent). The point is this can be changed. BUT if you took off-the-shelf values as you did here, it would be quite long. (1) What was the link status detection methods used for the experiment. - HELLOs are slow and non-robust (without additional processing e.g., hysteresis) but they are the most heterogeneous of approaches. - 802.11 lack of unicast ACKs methods can be problematic, but often envisioned for decreasing detection delay - Don't forget time-varying wireless channels are common (if you may too quick a decision on quality you might be wrong), but link S/N with some smoothing would probably be the best approach (if ONLY there were standard interface mechanisms).. These aren't wired links with only 2 states (on/off). - also older OLSR implementations (v3 code) has been improved in terms of repair time and has been reported at various meetings (e.g., MPR switiching) - alot of issues here that may be implementation dependent. 2) Timers - there is usually a tradeoff between timers (increasing overhead vs. decreasing delay). - faster intervals == faster detection/faster reaction.. - with better link sensing mechanisms one has less reliance on hello intervals,etc for detection this is true for both reactive and proactive protocol. >Anyone who has any idea on how long time RIP or OSPF >would have used to move the traffic when traffic is sent >from node A to node D via node B and node B suddenly is >turned off, so that traffic must be re-routed via node C >instead? > >Thanks! >Best Regards Berner > >_________________________________________________________________ >MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner > >_______________________________________________ >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 mailnull@www1.ietf.org Wed Feb 19 03:54:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16291 for ; Wed, 19 Feb 2003 03:54:54 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1J90tW19868 for manet-archive@odin.ietf.org; Wed, 19 Feb 2003 04:00:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1J90sp19865 for ; Wed, 19 Feb 2003 04:00:54 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16284 for ; Wed, 19 Feb 2003 03:54:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1J8fcp18892; Wed, 19 Feb 2003 03:41:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1J8b5p18052 for ; Wed, 19 Feb 2003 03:37:05 -0500 Received: from zaz.kom.auc.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15990 for ; Wed, 19 Feb 2003 03:30:34 -0500 (EST) Received: from winglab.kom.auc.dk ([192.168.110.83] helo=EEFIE) by zaz.kom.auc.dk with smtp (Exim 2.05 #3) id 18lPgK-0004RW-00; Wed, 19 Feb 2003 09:34:20 +0100 Message-ID: <003d01c2d7f1$a900d750$4909a8c0@kom.auc.dk> From: "Efrayim Metin" To: "Berner Vegge" , References: Subject: Re: [manet] Convergence time for MANET protocols versus traditional routing protocols Date: Wed, 19 Feb 2003 09:34:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Berner, In your scenario the time required for Router A to convergence is the detection + holddown time + update time. The default values are: In RIP IGRP detection time 30s 30s route update 30s 90s hold-down time 180s 280s Efrayim ----- Original Message ----- From: "Berner Vegge" To: Sent: Tuesday, February 18, 2003 2:09 PM Subject: [manet] Convergence time for MANET protocols versus traditional routing protocols > Hello all! > In Norway we have made some measurements of convergence > time for OLSR and AODV. When a relay-node is > suddenly turned off it takes about 12 seconds > for OLSR and 3 seconds for AODV until traffic > is moved to an other relay node (located close > to the node that was turned off). > > I find these values as being rather high and wonder > how long time traditional routing protocols would have > used in a similar situation... > > Anyone who has any idea on how long time RIP or OSPF > would have used to move the traffic when traffic is sent > from node A to node D via node B and node B suddenly is > turned off, so that traffic must be re-routed via node C > instead? > > Thanks! > Best Regards Berner > > _________________________________________________________________ > MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og > dine venner > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Feb 19 23:00:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18466 for ; Wed, 19 Feb 2003 23:00:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K476k00574 for manet-archive@odin.ietf.org; Wed, 19 Feb 2003 23:07:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K476p00571 for ; Wed, 19 Feb 2003 23:07:06 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18462 for ; Wed, 19 Feb 2003 23:00:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K3glp31899; Wed, 19 Feb 2003 22:42:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K3Ymp30998 for ; Wed, 19 Feb 2003 22:34:48 -0500 Received: from scutsv39.scut.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17108 for ; Wed, 19 Feb 2003 22:27:53 -0500 (EST) Received: from smtp.scut.edu.cn (smtp.scut.edu.cn [202.38.193.66]) by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id LAA18236 for ; Thu, 20 Feb 2003 11:29:25 +0800 (CST) Received: from jinglun ([202.112.18.113]) (authenticated bits=0) by smtp.scut.edu.cn (8.12.3/8.12.3) with ESMTP id h1K3ZYB3006678 for ; Thu, 20 Feb 2003 11:35:40 +0800 (CST) Message-Id: <200302200335.h1K3ZYB3006678@smtp.scut.edu.cn> Date: Thu, 20 Feb 2003 11:30:3 +0800 From: "Jinglun Shi" To: "manet@ietf.org" Organization: South China University of Technology X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====002_Dragon371627167114_=====" Subject: [manet] need your help about the analytic models for mobile agents Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --=====002_Dragon371627167114_===== Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Hello all! Does anyone could provide some related papers the analytic= models for mobile agents used for Ad hoc networks, Thank you for your help in advance. Best regards, Shi Jinglun=A1=A1 =A1=A1 =3D=3D=3D=3D=3D=3D=3D=3D Shi Jinglun Network Center of SCUT, South China University of Technology, Guangzhou, China P.C.: 510640 Mobile: 13802806656 Tel: 0086-20-85294696, jlshi@scut.edu.cn =3D=3D=3D=3D=3D=3D=3D=3D=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1 --=====002_Dragon371627167114_===== Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable

Hello all!

   Does anyone could provide some related papers the= analytic models for mobile agents used for  Ad hoc networks,=

Thank you for your help in advance.

  Best regards,
 
  Shi Jinglun=A1=A1

=A1=A1
=3D=3D=3D=3D=3D=3D=3D=3D
Shi Jinglun
Network Center of= SCUT,
South China University of Technology,
Guangzhou, China 
P.C.:= 510640
Mobile: 13802806656 Tel: 0086-20-85294696, 
jlshi@scut.edu.cn
=3D=3D=3D=3D=3D=3D=3D=3D= =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1

--=====002_Dragon371627167114_=====-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 19 23:06:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18555 for ; Wed, 19 Feb 2003 23:06:13 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K4Cb101258 for manet-archive@odin.ietf.org; Wed, 19 Feb 2003 23:12:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K4Cbp01248 for ; Wed, 19 Feb 2003 23:12:37 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18541 for ; Wed, 19 Feb 2003 23:05:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K3kWp32094; Wed, 19 Feb 2003 22:46:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K3inp31969 for ; Wed, 19 Feb 2003 22:44:49 -0500 Received: from scutsv39.scut.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17536 for ; Wed, 19 Feb 2003 22:37:54 -0500 (EST) Received: from smtp.scut.edu.cn (smtp.scut.edu.cn [202.38.193.66]) by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id LAA18532 for ; Thu, 20 Feb 2003 11:39:26 +0800 (CST) Received: from jinglun ([202.112.18.113]) (authenticated bits=0) by smtp.scut.edu.cn (8.12.3/8.12.3) with ESMTP id h1K3jaB3008374 for ; Thu, 20 Feb 2003 11:45:42 +0800 (CST) Message-Id: <200302200345.h1K3jaB3008374@smtp.scut.edu.cn> Date: Thu, 20 Feb 2003 11:40:4 +0800 From: "Jinglun Shi" To: "manet@ietf.org" Organization: South China University of Technology X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1K3inp31970 Subject: [manet] need the help about the analytic models for mobile agents Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello all! Does anyone could provide some related papers the analytic models for mobile agents used for Ad hoc networks, Thank you for your help in advance. ¡¡Best regards, Shi Jinglun¡¡¡¡ 2003-02-20 ======== Shi Jinglun Network Center of SCUT, South China University of Technology, Guangzhou, China P.C.: 510640 Mobile: 13802806656 Tel: 0086-20-85294696, jlshi@scut.edu.cn ========¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 01:10:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20737 for ; Thu, 20 Feb 2003 01:10:18 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K6Gh907592 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 01:16:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6Ghp07589 for ; Thu, 20 Feb 2003 01:16:43 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20715 for ; Thu, 20 Feb 2003 01:09:47 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K5sTp06090; Thu, 20 Feb 2003 00:54:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K5pLp06029 for ; Thu, 20 Feb 2003 00:51:21 -0500 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20063 for ; Thu, 20 Feb 2003 00:44:20 -0500 (EST) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329); Thu, 20 Feb 2003 13:47:53 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Subject: RE: [manet] need the help about the analytic models for mobile agents Date: Thu, 20 Feb 2003 13:47:51 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E02E07574@MBXSRV26.stu.nus.edu.sg> Thread-Topic: [manet] need the help about the analytic models for mobile agents Thread-Index: AcLYkvHf62FxlvaYQgm+YZdLzlupVwADpXpw From: "Marwaha Shivanajay" To: Cc: X-OriginalArrivalTime: 20 Feb 2003 05:47:53.0460 (UTC) FILETIME=[9C5FFB40:01C2D8A3] Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Few papers which might be of use to you on mobile agents and its application in MANETs for routing purpose. S. Marwaha, C-K Tham and D. Srinivasan, "Mobile Agents based Routing Protocol for Mobile Ad Hoc Networks", IEEE Globecom 2002. http://www.ece.nus.edu.sg/stfpage/eletck/papers/ShivaGlobeCom_sawn-06-3.pdf K.H. Kramer, N. Minar, and P. Maes, "Tutorial: Mobile Software Agents for Dynamic Routing" http://xenia.media.mit.edu/~nelson/research/routes-sigmobile/ H. Matsuo and K. Mori, $B!H(JAccelerated Ants Routing in Dynamic Networks,$B!I(J in Proc. Intl. Conf. On Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing, pp.333-339, Aug. 2001. http://mars.elcom.nitech.ac.jp/~matsuo/SNPD01-2.pdf "Evaluating the Performance of Mobile Agent-Based Message Communication among Mobile Hosts in Large Ad Hoc Wireless Network", S. Bandyopadhyay and Krishna Paul http://portal.acm.org/citation.cfm?id=313251&coll=portal&dl=ACM&ret=1#Fulltext Regards, Shivanajay Marwaha **************************************** Research Scholar, Electrical & Computer Engineering Dept. National University of Singapore. **************************************** -----Original Message----- From: Jinglun Shi [mailto:jlshi@scut.edu.cn] Sent: Thursday, February 20, 2003 1:00 AM To: manet@ietf.org Subject: [manet] need the help about the analytic models for mobile agents Hello all! Does anyone could provide some related papers the analytic models for mobile agents used for Ad hoc networks, Thank you for your help in advance. $B!!(JBest regards, Shi Jinglun$B!!!!(J 2003-02-20 ======== Shi Jinglun Network Center of SCUT, South China University of Technology, Guangzhou, China P.C.: 510640 Mobile: 13802806656 Tel: 0086-20-85294696, jlshi@scut.edu.cn ========$B!!!!!!!!!!!!!!!!(J _______________________________________________ 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 mailnull@www1.ietf.org Thu Feb 20 01:54:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21836 for ; Thu, 20 Feb 2003 01:54:25 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K70qF10271 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 02:00:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K70pp10268 for ; Thu, 20 Feb 2003 02:00:51 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21830 for ; Thu, 20 Feb 2003 01:53:54 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6fWp09097; Thu, 20 Feb 2003 01:41:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6dWp09017 for ; Thu, 20 Feb 2003 01:39:32 -0500 Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21120 for ; Thu, 20 Feb 2003 01:32:35 -0500 (EST) Received: from ci0026exch001u.wins.lucent.com (h135-252-18-18.lucent.com [135.252.18.18]) by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1K6aMF28436 for ; Thu, 20 Feb 2003 01:36:23 -0500 (EST) Received: by CI0026EXCH001U with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Feb 2003 14:36:20 +0800 Message-ID: <31C0F08B0D18D511ACC800508BAE7B4704BE3F05@CI0026EXCH001U> From: "Wang, Lei (Raymond)" To: "'Marwaha Shivanajay'" , manet@ietf.org Cc: jlshi@scut.edu.cn Subject: RE: [manet] need the help about the analytic models for mobile ag ents Date: Thu, 20 Feb 2003 14:34:49 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-2022-jp" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , The following paper might help too: Christian Tschudin, Henrik Lundgren and Henrik Gulbrandsen, Active Routing for Ad Hoc Networks, IEEE communications magazine, Apr, 2000. - Ray Wang, Lei (Raymond) Member of Technical Staff Bell Labs Research China, Beijing. Tel: +86-10-68748088 ext. 8733 Fax: +86-10-68748360 Email: raywang@bell-labs.com, lei.wang@ieee.org > -----Original Message----- > From: Marwaha Shivanajay [mailto:engp1609@nus.edu.sg] > Sent: Thursday, February 20, 2003 1:48 PM > To: manet@ietf.org > Cc: jlshi@scut.edu.cn > Subject: RE: [manet] need the help about the analytic models > for mobile agents > > > Hi, > Few papers which might be of use to you on mobile agents and > its application in MANETs for routing purpose. > > S. Marwaha, C-K Tham and D. Srinivasan, "Mobile Agents based > Routing Protocol for Mobile Ad Hoc Networks", IEEE Globecom 2002. > http://www.ece.nus.edu.sg/stfpage/eletck/papers/ShivaGlobeCom_ > sawn-06-3.pdf > > K.H. Kramer, N. Minar, and P. Maes, "Tutorial: Mobile > Software Agents for Dynamic Routing" > http://xenia.media.mit.edu/~nelson/research/routes-sigmobile/ > > H. Matsuo and K. Mori, $B!H(JAccelerated Ants Routing in Dynamic > Networks,$B!I(J in Proc. Intl. Conf. On Software Engineering, > Artificial Intelligence, Networking and Parallel/Distributed > Computing, pp.333-339, Aug. 2001. > http://mars.elcom.nitech.ac.jp/~matsuo/SNPD01-2.pdf > > "Evaluating the Performance of Mobile Agent-Based Message > Communication among Mobile Hosts in Large Ad Hoc Wireless > Network", S. Bandyopadhyay and Krishna Paul > http://portal.acm.org/citation.cfm?id=313251&coll=portal&dl=AC > M&ret=1#Fulltext > > Regards, > Shivanajay Marwaha > **************************************** > Research Scholar, > Electrical & Computer Engineering Dept. > National University of Singapore. > **************************************** > > > -----Original Message----- > From: Jinglun Shi [mailto:jlshi@scut.edu.cn] > Sent: Thursday, February 20, 2003 1:00 AM > To: manet@ietf.org > Subject: [manet] need the help about the analytic models for > mobile agents > > > Hello all! > > Does anyone could provide some related papers the analytic > models for mobile agents used for Ad hoc networks, > Thank you for your help in advance. > > $B!!(JBest regards, > > Shi Jinglun$B!!!!(J > > 2003-02-20 > > ======== > Shi Jinglun > Network Center of SCUT, > South China University of Technology, > Guangzhou, China > P.C.: 510640 > Mobile: 13802806656 Tel: 0086-20-85294696, > jlshi@scut.edu.cn > ========$B!!!!!!!!!!!!!!!!(J > > > > > _______________________________________________ > 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 mailnull@www1.ietf.org Thu Feb 20 02:00:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22784 for ; Thu, 20 Feb 2003 02:00:36 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K772L14214 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 02:07:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K772p14203 for ; Thu, 20 Feb 2003 02:07:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22043 for ; Thu, 20 Feb 2003 02:00:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6h5p09203; Thu, 20 Feb 2003 01:43:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6fhp09109 for ; Thu, 20 Feb 2003 01:41:43 -0500 Received: from hugin.diku.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA21156 for ; Thu, 20 Feb 2003 01:34:46 -0500 (EST) Received: (qmail 27804 invoked from network); 20 Feb 2003 06:38:34 -0000 Received: from tyr.diku.dk (madsdyd@130.225.96.226) by hugin.diku.dk with QMQP; 20 Feb 2003 06:38:34 -0000 Date: Thu, 20 Feb 2003 07:38:34 +0100 (MET) From: Mads Bondo Dydensborg To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Bluetooth and MANET routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Does anyone have references to papers etc, that treat MANETs build with Bluetooth technology? I am specifically looking for resources on how to arrange piconets to cover the nodes, and how to route when you have no scatternet support. Papers that take energy consumption into account and documents actual implementations as well as simulations would be most welcome. Thanks, Mads -- +----------------------------------------------------------------------+ | Mads Bondo Dydensborg. http://www.diku.dk/users/madsdyd | | +45 35 32 14 18 | +----------------------------------------------------------------------+ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 02:54:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03319 for ; Thu, 20 Feb 2003 02:54:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K81Re24408 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 03:01:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K81Qp24405 for ; Thu, 20 Feb 2003 03:01:26 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03310 for ; Thu, 20 Feb 2003 02:54:27 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K7gZp23692; Thu, 20 Feb 2003 02:42:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K7dup23572 for ; Thu, 20 Feb 2003 02:39:56 -0500 Received: from orca.informatik.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02962 for ; Thu, 20 Feb 2003 02:32:57 -0500 (EST) Received: by orca.informatik.uni-ulm.de (Postfix, from userid 508) id 95C7A10108; Thu, 20 Feb 2003 08:37:14 +0100 (CET) Date: Thu, 20 Feb 2003 08:37:14 +0100 From: Stefan Schlott To: Mads Bondo Dydensborg Cc: manet@ietf.org, Frank Kargl Subject: Re: [manet] Bluetooth and MANET routing Message-ID: <20030220073714.GB1583@orca.informatik.uni-ulm.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, > Does anyone have references to papers etc, that treat MANETs build with > Bluetooth technology? Some research in this area was done in our department. The resulting paper has been presented on the HICSS conference this year. You'll find the paper "Bluetooth-based Ad-Hoc Networks for Voice Transmission" on our web server: http://medien.informatik.uni-ulm.de/~frank/research/hicss36.pdf Hope it helps, Stefan. -- *--- please cut here... -------------------------------------- thanks! ---* |-> E-Mail: stefan.schlott@informatik.uni-ulm.de PGP-Key: 0x2F36F4FE <-| | "I heard if you play the NT-4.0-CD backwards, you get a satanic | | message." | | "That's nothing, if you play it forward, it installs NT-4.0" | *-------------------------------------------------------------------------* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 06:08:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07241 for ; Thu, 20 Feb 2003 06:08:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KBFUI03865 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 06:15:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KBFUp03862 for ; Thu, 20 Feb 2003 06:15:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07229 for ; Thu, 20 Feb 2003 06:08:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KB2Kp02525; Thu, 20 Feb 2003 06:02:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KAxnp02418 for ; Thu, 20 Feb 2003 05:59:49 -0500 Received: from dirf.bris.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06919 for ; Thu, 20 Feb 2003 05:52:45 -0500 (EST) Received: from cs.bris.ac.uk (actually host lunaleka.cs.bris.ac.uk) by dirf.bris.ac.uk with SMTP-PRIV with ESMTP; Thu, 20 Feb 2003 10:56:15 +0000 Received: from abwyd (abwyd [137.222.103.137]) by cs.bris.ac.uk (8.9.3/8.9.3) with SMTP id KAA00433 for ; Thu, 20 Feb 2003 10:55:05 GMT Message-ID: <007a01c2d8ce$96ac6be0$8967de89@abwyd> From: Grzegorz Jablonski To: manet Date: Thu, 20 Feb 2003 10:55:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] formal verification of ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I'm doing research on formal verification of algorithms for ad-hoc networks. I'm trying to apply transition systems (process algebras etc.) in modelling and verification of the reactive algorithms running in ad-hoc environment. Does anyone do research in this area? Cheers Greg _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 08:34:26 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13249 for ; Thu, 20 Feb 2003 08:34:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KDf0i13252 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 08:41:00 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KDf0p13249 for ; Thu, 20 Feb 2003 08:41:00 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13204 for ; Thu, 20 Feb 2003 08:33:54 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KDQJp11893; Thu, 20 Feb 2003 08:26:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KDNRp11791 for ; Thu, 20 Feb 2003 08:23:27 -0500 Received: from iproxy2.ericsson.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12093 for ; Thu, 20 Feb 2003 08:16:22 -0500 (EST) Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246]) by iproxy2.ericsson.dk (8.12.2/8.12.2) with ESMTP id h1KDHvg9004658; Thu, 20 Feb 2003 14:17:57 +0100 (CET) Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38]) by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id h1KDK4x16972; Thu, 20 Feb 2003 14:20:04 +0100 (MET) From: Gerben Kuijpers To: manet@ietf.org, "aodvimpl-public@lists.sourceforge.net" Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 20 Feb 2003 14:20:04 +0100 Message-Id: <1045747204.15499.179.camel@geku> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [manet] AODV - difference between route update rules when receiving RREQ or RREP Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Does anyone know why there is a difference in the route entry update rules of AODV, in case a RREQ is received when compared to the update rules in case a RREP is received. For a RREQ, the rules for updating the route to the Originator of a RREQ are described in section 5.2: "The route is only updated if the new sequence number is either (i) higher than the destination sequence number in the route table, or (ii) the sequence numbers are equal, but the hop count (of the new information) plus one, is smaller than the existing hop count in the routing table, or (iii) the sequence number is unknown." The update rules for the route to the Destination of a RREQ/RREP when a RREP is received are given in section 5.7, similar to the rules in 5.2, but one additional rule: "(iii) the sequence numbers are the same, but the route is no longer active," Why is there a difference in these updating rules? IMO the extra rule should also be used when updating the route to the Originator, when a RREQ is received. Otherwise the following can happen (and happened in some of my simulations): [1] Node s sends a RREQ for node d seq nr for s: 1 network: (s) --- (1) --- (2) ..(several nodes in between).. (d) [2] RREQ reaches node d, sends RREP seq nr for s: 1 1 1 1 network: (s) --- (1) --- (2) ..(several nodes in between).. (d) [3] RREP forwarded using reverse routes, but from node 2 to node 1, the RREP can not be delivered (either temporarily out of range, or due to congestion/collision) -> node 2 sets route to node s to invalid and increase sequence number of route entry seq nr for s: 1 1 2 1 network: (s) --- (1) -X- (2) ..(several nodes in between).. (d) [4] After RREQ timeout (no RREP was received), node s sends another RREQ, with increased seq nr, but node 2 does not update the route entry for node s (seq nr in RREQ == seq nr route entry, same number of hops): seq nr for s: 2 2 2 2 network: (s) --- (1) -X- (2) ..(several nodes in between).. (d) [5] When new RREP travels back to node s, node 2 will drop the RREP, because the route to s is invalid (sometimes even completely removed, when more than DELETE_PERIOD has passed between the two times the RREP is received by node 2). Adding the extra rule when updating the route to the Originator of a RREQ seems to fix this problem or am I missing something here? regards, /Gerben Kuijpers _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 09:10:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14996 for ; Thu, 20 Feb 2003 09:10:42 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KEHHR15563 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 09:17:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KEHHp15560 for ; Thu, 20 Feb 2003 09:17:17 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14954 for ; Thu, 20 Feb 2003 09:10:10 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KE3jp14267; Thu, 20 Feb 2003 09:03:45 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KDxFp14051 for ; Thu, 20 Feb 2003 08:59:15 -0500 Received: from mephisto.inf.tu-dresden.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14258 for ; Thu, 20 Feb 2003 08:52:09 -0500 (EST) Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id OAA16268; Thu, 20 Feb 2003 14:55:55 +0100 (MET) Message-Id: <5.1.0.14.0.20030220144232.00b61008@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 20 Feb 2003 14:57:16 +0100 To: ns-users@ISI.EDU From: gikaru Cc: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] diverting huge trace files to another location Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I am during simulation of ad-hoc routing protocols and have been generating very huge files leading to shortage of space on the hard-disk. I am wondering how possible it is to store these files on a different location (different server that has enough space). I tried initiating in the protocols tcl script with the line: set val(out_file) "http://server-name/folder" then i set the tracefile name as: set val(tracefile) "$val(out_file)/outputfl.tr" and created the object set tracefd [open $val(tracefile) w] .... i received an error message: couldn't open "http://server-name/filder/outputfl.tr" How do i go about solving this? Any suggestion especially from those good in otcl language will be highly appreciated. Thank you in advance.... Gikaru TU-Dresden, Department of Computer Science _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 09:13:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15099 for ; Thu, 20 Feb 2003 09:13:03 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KEJcm15674 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 09:19:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KEJcp15671 for ; Thu, 20 Feb 2003 09:19:38 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15084 for ; Thu, 20 Feb 2003 09:12:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KE55p14334; Thu, 20 Feb 2003 09:05:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KE1vp14155 for ; Thu, 20 Feb 2003 09:01:57 -0500 Received: from aragorn.bbn.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14445 for ; Thu, 20 Feb 2003 08:54:51 -0500 (EST) Received: from 78-RC321.bbn.com (dhcp069-090.bbn.com [128.89.69.90]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h1KDqjpp029983; Thu, 20 Feb 2003 08:52:45 -0500 (EST) Message-Id: <5.1.0.14.2.20030220085421.027220a0@po2.bbn.com> X-Sender: celliott@po2.bbn.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 20 Feb 2003 08:57:04 -0500 To: Grzegorz Jablonski , manet From: Chip Elliott Subject: Re: [manet] formal verification of ad hoc networks In-Reply-To: <007a01c2d8ce$96ac6be0$8967de89@abwyd> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear Greg, I have seen some excellent work from Irfan Zakkiudin at Qinetiq, teamed with an Oxford formal verification group. Last I knew, though, he was analyzing pro-active forms of ad hoc routing. Zak can be reached at: Irfan Zakiuddin Cheers, -- Chip Chip Elliott Principal Engineer, BBN At 05:55 AM 2/20/2003, Grzegorz Jablonski wrote: >Hi, > >I'm doing research on formal verification of algorithms for ad-hoc networks. >I'm trying to apply transition systems (process algebras etc.) in modelling >and verification of the reactive algorithms running in ad-hoc environment. > > Does anyone do research in this area? > > Cheers >Greg > > >_______________________________________________ >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 mailnull@www1.ietf.org Thu Feb 20 09:58:26 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16494 for ; Thu, 20 Feb 2003 09:58:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KF53v18555 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 10:05:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KF53p18552 for ; Thu, 20 Feb 2003 10:05:03 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16455 for ; Thu, 20 Feb 2003 09:57:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KEprp17854; Thu, 20 Feb 2003 09:51:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KEnap17761 for ; Thu, 20 Feb 2003 09:49:36 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16043 for ; Thu, 20 Feb 2003 09:42:28 -0500 (EST) Received: (cpmta 21832 invoked from network); 20 Feb 2003 06:46:17 -0800 Received: from 12.221.64.123 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.65) with SMTP; 20 Feb 2003 06:46:17 -0800 X-Sent: 20 Feb 2003 14:46:17 GMT Message-ID: <3E54E985.8080107@cs.uiuc.edu> Date: Thu, 20 Feb 2003 08:43:17 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gikaru CC: ns-users@ISI.EDU, manet@ietf.org References: <5.1.0.14.0.20030220144232.00b61008@harmless.inf.tu-dresden.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Re: [ns] diverting huge trace files to another location Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit You can transparently pipe your tracefile into another command by starting the filename with "|". My favorite is set tracefd [open "| gzip --best > $val(tracefile).gz"] to compress traces. If you have a program that can send its stdin to another host, like ncftpput from ncftp, then you are in good shape. gikaru wrote: > > I am during simulation of ad-hoc routing protocols and have been > generating very huge files leading to shortage of space on the > hard-disk. I am wondering how possible it is to store these files on a > different location (different server that has enough space). I tried > initiating in the protocols tcl script with the line: > set val(out_file) "http://server-name/folder" > then i set the tracefile name as: > set val(tracefile) "$val(out_file)/outputfl.tr" > and created the object > set tracefd [open $val(tracefile) w] > .... i received an error message: couldn't open > "http://server-name/filder/outputfl.tr" > How do i go about solving this? > Any suggestion especially from those good in otcl language will be > highly appreciated. > Thank you in advance.... > > > Gikaru > TU-Dresden, Department of Computer Science -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 20 10:35:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18140 for ; Thu, 20 Feb 2003 10:35:44 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KFgLf21993 for manet-archive@odin.ietf.org; Thu, 20 Feb 2003 10:42:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KFgLp21990 for ; Thu, 20 Feb 2003 10:42:21 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18115 for ; Thu, 20 Feb 2003 10:35:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KFSsp20447; Thu, 20 Feb 2003 10:28:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KFQop20316 for ; Thu, 20 Feb 2003 10:26:50 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17240 for ; Thu, 20 Feb 2003 10:19:42 -0500 (EST) Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1KFNXi312688; Thu, 20 Feb 2003 10:23:33 -0500 (EST) Received: from tom ([198.70.228.51]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BBV02161 (AUTH talin); Thu, 20 Feb 2003 10:23:28 -0500 (EST) Message-ID: <003701c2d8f3$aa450de0$643f640a@tom> From: "Tao Lin" To: "Chip Elliott" , "Grzegorz Jablonski" , "manet" References: <5.1.0.14.2.20030220085421.027220a0@po2.bbn.com> Subject: Re: [manet] formal verification of ad hoc networks Date: Thu, 20 Feb 2003 10:20:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit FYI. "K. Bhargavan, C. Gunter, M. Kim, I. Lee, D. Obradovic,O. Sokolsky, and M. Viswanathan. Verisim: Formal analysis of network simulations. In Int. Symposium on Software Testing and Analysis, pages 2-13, 2000. " They have other papers on the similar topic published in IEEE transaction on software engineering 2002 and in ACM journal. Basically, their work focuses on DSDV and AODV. Tao Lin Ph. D. ECE Dept. Virginia Tech. USA ----- Original Message ----- From: "Chip Elliott" To: "Grzegorz Jablonski" ; "manet" Sent: Thursday, February 20, 2003 8:57 AM Subject: Re: [manet] formal verification of ad hoc networks > > Dear Greg, > > I have seen some excellent work from Irfan Zakkiudin > at Qinetiq, teamed with an Oxford formal verification group. > Last I knew, though, he was analyzing pro-active forms > of ad hoc routing. > > Zak can be reached at: > > Irfan Zakiuddin > > Cheers, > > -- Chip > > Chip Elliott > Principal Engineer, BBN > > > At 05:55 AM 2/20/2003, Grzegorz Jablonski wrote: > >Hi, > > > >I'm doing research on formal verification of algorithms for ad-hoc networks. > >I'm trying to apply transition systems (process algebras etc.) in modelling > >and verification of the reactive algorithms running in ad-hoc environment. > > > > Does anyone do research in this area? > > > > Cheers > >Greg > > > > > >_______________________________________________ > >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 mailnull@www1.ietf.org Fri Feb 21 04:00:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23620 for ; Fri, 21 Feb 2003 04:00:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1L97W105809 for manet-archive@odin.ietf.org; Fri, 21 Feb 2003 04:07:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1L97Wp05806 for ; Fri, 21 Feb 2003 04:07:32 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23607 for ; Fri, 21 Feb 2003 04:00:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1L8lhp03932; Fri, 21 Feb 2003 03:47:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1L8b4p02931 for ; Fri, 21 Feb 2003 03:37:04 -0500 Received: from iproxy2.ericsson.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22829 for ; Fri, 21 Feb 2003 03:29:34 -0500 (EST) Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246]) by iproxy2.ericsson.dk (8.12.2/8.12.2) with ESMTP id h1L8UVg9006058; Fri, 21 Feb 2003 09:30:31 +0100 (CET) Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38]) by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id h1L8Wcx00315; Fri, 21 Feb 2003 09:32:39 +0100 (MET) Subject: RE: [manet] AODV - difference between route update rules when receiving RREQ or RREP From: Gerben Kuijpers To: "Samir R. Das" Cc: manet@ietf.org, "aodvimpl-public@lists.sourceforge.net" In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 21 Feb 2003 09:32:38 +0100 Message-Id: <1045816359.15499.221.camel@geku> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Thanks for your response. You are right in case the link really is broken and both node 1 and node 2 discover this, thus sending a RERR to resp. the source s and destination d. However, if the RREP is dropped due to congestion, only node 2 will discover (think there is) a link break and only one RERR is sent: to the destination d. In that case the problem I pointed out remains. regards, /Gerben Kuijpers On Thu, 2003-02-20 at 16:28, Samir R. Das wrote: > Hi, > > In your scenario, the RERR will carry back the incremented seq no. (2) to > the source. The source s will increment its seq no (to 3) before the new > route discovery. This takes care of the problem you have pointed out. > > Samir > > > >-----Original Message----- > >From: manet-admin@ietf.org [mailto:manet-admin@ietf.org]On Behalf Of > >Gerben Kuijpers > >Sent: Thursday, February 20, 2003 8:20 AM > >To: manet@ietf.org; aodvimpl-public@lists.sourceforge.net > >Subject: [manet] AODV - difference between route update rules when > >receiving RREQ or RREP > > > > > > > > > >Hi, > > > >Does anyone know why there is a difference in the route entry update > >rules of AODV, in case a RREQ is received when compared to the update > >rules in case a RREP is received. For a RREQ, the rules for updating the > >route to the Originator of a RREQ are described in section 5.2: > > > >"The route is only updated if > > the new sequence number is either > > > > (i) higher than the destination sequence number in the route > > table, or > > > > (ii) the sequence numbers are equal, but the hop count (of > > the new information) plus one, is smaller than the > > existing hop count in the routing table, or > > > > (iii) the sequence number is unknown." > > > >The update rules for the route to the Destination of a RREQ/RREP when a > >RREP is received are given in section 5.7, similar to the rules in 5.2, > >but one additional rule: > > > >"(iii) the sequence numbers are the same, but the route is no > > longer active," > > > >Why is there a difference in these updating rules? IMO the extra rule > >should also be used when updating the route to the Originator, when a > >RREQ is received. Otherwise the following can happen (and happened in > >some of my simulations): > > > >[1] Node s sends a RREQ for node d > > > >seq nr for s: 1 > >network: (s) --- (1) --- (2) ..(several nodes in between).. (d) > > > >[2] RREQ reaches node d, sends RREP > > > >seq nr for s: 1 1 1 1 > >network: (s) --- (1) --- (2) ..(several nodes in between).. (d) > > > > > >[3] RREP forwarded using reverse routes, but from node 2 to node 1, the > >RREP can not be delivered (either temporarily out of range, or due to > >congestion/collision) -> node 2 sets route to node s to invalid and > >increase sequence number of route entry > > > >seq nr for s: 1 1 2 1 > >network: (s) --- (1) -X- (2) ..(several nodes in between).. (d) > > > > > >[4] After RREQ timeout (no RREP was received), node s sends another > >RREQ, with increased seq nr, but node 2 does not update the route entry > >for node s (seq nr in RREQ == seq nr route entry, same number of hops): > > > >seq nr for s: 2 2 2 2 > >network: (s) --- (1) -X- (2) ..(several nodes in between).. (d) > > > >[5] When new RREP travels back to node s, node 2 will drop the RREP, > >because the route to s is invalid (sometimes even completely removed, > >when more than DELETE_PERIOD has passed between the two times the RREP > >is received by node 2). > > > >Adding the extra rule when updating the route to the Originator of a > >RREQ seems to fix this problem or am I missing something here? > > > >regards, > > > >/Gerben Kuijpers > > > >_______________________________________________ > >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 mailnull@www1.ietf.org Fri Feb 21 06:16:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26008 for ; Fri, 21 Feb 2003 06:16:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LBNws14124 for manet-archive@odin.ietf.org; Fri, 21 Feb 2003 06:23:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LBNwp14121 for ; Fri, 21 Feb 2003 06:23:58 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26005 for ; Fri, 21 Feb 2003 06:16:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LB9Yp13434; Fri, 21 Feb 2003 06:09:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LB4Kp12541 for ; Fri, 21 Feb 2003 06:04:20 -0500 Received: from chamomile.mlab.t.u-tokyo.ac.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25628 for ; Fri, 21 Feb 2003 05:56:42 -0500 (EST) Received: (qmail 20187 invoked from network); 21 Feb 2003 11:00:32 -0000 Received: from unknown (HELO sunflower.mlab.t.u-tokyo.ac.jp) (192.168.1.1) by 133.11.236.1 with SMTP; 21 Feb 2003 11:00:32 -0000 Received: (qmail 5213 invoked from network); 21 Feb 2003 11:00:30 -0000 Received: from sunflower.mlab.t.u-tokyo.ac.jp (HELO MORI-T30.mlab.t.u-tokyo.ac.jp) (192.168.1.1) by sunflower.mlab.t.u-tokyo.ac.jp with SMTP; 21 Feb 2003 11:00:30 -0000 Message-Id: <5.0.2.7.2.20030221200028.040f18c8@localhost> X-Sender: mori@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-Jr2 Date: Fri, 21 Feb 2003 20:00:29 +0900 To: manet@ietf.org From: Hiroyuki Morikawa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [manet] CFP: MobiCom 2003 -- Paper registration due March 5, 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , CALL FOR PAPERS MobiCom 2003 The Ninth Annual International Conference on Mobile Computing and Networking September 14-19, 2003 San Diego, California, USA http://www.sigmobile.org/mobicom/2003/ Sponsored by ACM SIGMOBILE ACM MobiCom 2003, the Ninth Annual International Conference on Mobile Computing and Networking, is the ninth in a series of annual conferences sponsored by ACM SIGMOBILE dedicated to addressing the challenges in the areas of mobile computing and wireless and mobile networking. The MobiCom conference series serves as the premier international forum addressing networks, systems, algorithms, and applications that support the symbiosis of mobile computers and wireless networks. MobiCom is a highly selective, single-track conference focusing on all issues in mobile computing and wireless and mobile networking at the link layer and above. MobiCom 2003 will be held September 14-19, 2003, at the Westin Horton Plaza Hotel in beautiful, sunny San Diego, California. PAPERS: Authors are invited to submit full papers presenting new research related to the theory or practice of mobile computing and networking. All submissions must describe original research, not published or currently under review for another conference or journal. Areas of interest include, but are not limited to: - Applications and computing services supporting mobile users - Architectures, protocols, and algorithms to cope with mobility, limited bandwidth, or intermittent connectivity - Database and data management issues in mobile computing - Operating system and middleware support for mobile computing and networking - Distributed systems aspects of mobile computing - New mobile and wireless applications - Integration and interworking of wired and wireless networks - Performance of mobile and wireless networks and systems - Location-dependent applications and protocols - Security and privacy of mobile/wireless systems - Mobile ad hoc and sensor networks - Wireless multimedia systems - Algorithms and protocols for power management and control - Service creation and management environments for mobile/wireless systems The program committee will referee all papers, and accepted papers will be published in the conference proceedings. Papers of particular merit will be proposed for publication in the ACM/Kluwer Wireless Networks (WINET) and Mobile Networks and Applications (MONET) journals. CHALLENGES PAPERS: The conference also solicits short papers (maximum of 8 pages) that challenge the mobile computing community with revolutionary new technologies or visionary applications. Such papers should provide stimulating ideas or grand visions that may open up exciting avenues of far-reaching future research; descriptions of new products or simple evolution of existing work are not appropriate as Challenges Papers. Challenges Papers will be reviewed and should be submitted using the normal submission procedure but must be clearly identified as intended as Challenges Papers. SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically. Authors should prepare a Portable Document Format (PDF) or PostScript version of their full paper. Papers must be no longer than 15 pages (8 pages for Challenges submissions), in font size no smaller than 10 points, and must fit properly on US "Letter"-sized paper (8.5x11 inches) with reasonable margins. Detailed instructions on the paper submission procedure and format are available on the conference web pages. All papers being submitted must be registered by March 12, 2003. The paper submission deadline is then March 12, 2003. All submitted papers will be judged based on their quality through double-blind reviewing, where the identities of the authors are withheld from the reviewers. Authors' names must not appear in the paper or in the PostScript or PDF file. Submitted papers (or substantially similar papers) must not be currently under review for any other publication. Please direct any questions about the paper submission process to the Program Co-Chairs at mobicom_pcchairs@acm.org. TUTORIALS: Proposals for tutorials are solicited. Evaluation of tutorial proposals will be based on the expertise and experience of the instructors, and on the relevance of the subject matter. Potential instructors are requested to submit a tutorial proposal of at most 5 pages, including a biographical sketch, to the Tutorial Co-Chairs by April 7, 2003. PANELS: Panels are solicited that examine innovative, controversial, or otherwise provocative issues of interest. Panel proposals should not exceed 3 pages, including biographical sketches of the panelists. Potential panel organizers should contact the Panel Co-Chairs by April 21, 2003. RESEARCH DEMOS AND EXHIBITS: Proposals for research demos are solicited. Proposals should not exceed 3 pages and should include a description of the demo and equipment to be used. Send proposals to the Research Demo Chair by July 26, 2003. We are also planning an Expo featuring exhibits of the latest mobile computing products and services. BEST STUDENT PAPER AWARD: Papers with a student as a primary author will be considered for the Best Student Paper award, with a cash award of $1000 USD. Students must indicate with their submission that they would like to be considered for this award. IMPORTANT DATES: Paper registration deadline: March 5, 2003 Paper submission deadline: March 12, 2003 Notification of acceptance: June 16, 2003 Camera-ready version due: July 18, 2003 All papers being submitted to MobiCom 2003 must be registered by 11:59 PM PST (US Pacific timezone) March 5, 2003. The deadline for actually then submitting all registered papers is 11:59 PM PST (US Pacific timezone) March 12, 2003. These are firm deadlines. GENERAL CHAIR: David B. Johnson Rice University dbj@cs.rice.edu PROGRAM CO-CHAIRS: Anthony D. Joseph University of California, Berkeley adj@eecs.berkeley.edu Nitin H. Vaidya University of Illinois at Urbana-Champaign nhv@uiuc.edu For a complete list of Organizing and Program Committee members, please refer to the web pages at http://www.sigmobile.org/mobicom/2003/. FOR MORE INFORMATION: Please contact the General Chair or Program Co-Chairs for more information. For information on ACM SIGMOBILE and the MobiCom series of conferences, see http://www.sigmobile.org/ or contact mobicom_info@acm.org. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 21 10:29:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03459 for ; Fri, 21 Feb 2003 10:29:17 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LFaOv30735 for manet-archive@odin.ietf.org; Fri, 21 Feb 2003 10:36:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LFaOp30732 for ; Fri, 21 Feb 2003 10:36:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03453 for ; Fri, 21 Feb 2003 10:28:46 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LFNRp29984; Fri, 21 Feb 2003 10:23:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LFIFp29785 for ; Fri, 21 Feb 2003 10:18:15 -0500 Received: from anyida.tts.lth.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02799 for ; Fri, 21 Feb 2003 10:10:37 -0500 (EST) Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id PAA05997; Fri, 21 Feb 2003 15:57:29 +0100 (MET) Message-ID: <3E563E27.1010402@telecom.lth.se> Date: Fri, 21 Feb 2003 15:56:39 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: yasser.lotfy@lycos.com CC: "manet@ietf.org" Subject: Re: [manet] Gateway Discovery References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Yasser, In my master's thesis I've extended AODV such that mobile nodes can use it for routing not only within a MANET, but also between a MANET and a fixed network. To be able to do that, the mobile nodes must discover a gateway. I discuss three approaches for gateway discovery in a MANET: reactive, proactive and hybrid. You can find the thesis here if you're interested: http://www.telecom.lth.se/Personal/alexh/ Regards Ali Yasser A. Lotfy wrote: >Good day everyone, > >Has there been any work on ad-hoc gateway discovery mechanisms. Can you please point me to any papers on this area? > >Regards, > >Yasser >Carleton U > > > >_____________________________________________________________ >Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year. >http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus >_______________________________________________ >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 mailnull@www1.ietf.org Fri Feb 21 18:16:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17998 for ; Fri, 21 Feb 2003 18:16:11 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LNNR129611 for manet-archive@odin.ietf.org; Fri, 21 Feb 2003 18:23:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LNNRp29608 for ; Fri, 21 Feb 2003 18:23:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17994 for ; Fri, 21 Feb 2003 18:15:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LN7Qp29028; Fri, 21 Feb 2003 18:07:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LMwHp28072 for ; Fri, 21 Feb 2003 17:58:17 -0500 Received: from web40304.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA17663 for ; Fri, 21 Feb 2003 17:50:30 -0500 (EST) Message-ID: <20030221225421.65486.qmail@web40304.mail.yahoo.com> Received: from [130.126.136.80] by web40304.mail.yahoo.com via HTTP; Fri, 21 Feb 2003 14:54:21 PST Date: Fri, 21 Feb 2003 14:54:21 -0800 (PST) From: romit roychoudhury Subject: Re: [manet] List of Technical Reports To: manet@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, Following is a list of technical reports that may be relevant to the MANET research community. Comments are welcome. The reports are available at http://www.crhc.uiuc.edu/~nhv/publications.html ------------------------------------------------------ A Multi-Channel MAC Protocol for Ad Hoc Wireless Networks, J. So and N. H. Vaidya, January 2003. Impact of directional Antennas on Ad Hoc Routing, R. Roy Choudhury and Nitin Vaidya, August 2002. DSCR: A More Stable MAC Protocol for Wireless Networks, Xue Yang and Nitin Vaidya, August 2002. Pipelined Packet Scheduling in Wireless LANs, Xue Yang and Nitin Vaidya, Technical Report, March 2002 (revised August 2002). Detection and Handling of MAC Layer Misbehavior in Wireless Networks, Pradeep Kyasanur and Nitin Vaidya, August 2002. ------------------------------------------------------ Thanks in advance, romit ----------------------------------------------------------- Romit Roy Choudhury Graduate Student, UIUC, www.crhc.uiuc.edu/~croy ------------------------------------------------------- __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Feb 22 07:16:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09563 for ; Sat, 22 Feb 2003 07:16:05 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1MCNbE12288 for manet-archive@odin.ietf.org; Sat, 22 Feb 2003 07:23:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1MCNbp12285 for ; Sat, 22 Feb 2003 07:23:37 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09554 for ; Sat, 22 Feb 2003 07:15:34 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1MC8Hp11886; Sat, 22 Feb 2003 07:08:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1MBtFp10910 for ; Sat, 22 Feb 2003 06:55:15 -0500 Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09283 for ; Sat, 22 Feb 2003 06:47:12 -0500 (EST) Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329); Sat, 22 Feb 2003 05:51:04 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [manet] formal verification of ad hoc networks Date: Sat, 22 Feb 2003 05:51:03 -0600 Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02CFDD@KC-MAIL4.kc.umkc.edu> Thread-Topic: Re: [manet] formal verification of ad hoc networks Thread-Index: AcLaaKzjCmbBc9CeRs+zDpHQhxjEpg== From: "Ayyasamy, Senthilkumar (UMKC-Student)" To: , , Cc: X-OriginalArrivalTime: 22 Feb 2003 11:51:04.0431 (UTC) FILETIME=[ADA1C7F0:01C2DA68] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1MBtFp10911 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit > > "K. Bhargavan, C. Gunter, M. Kim, I. Lee, D. Obradovic,O. Sokolsky, and M. > Viswanathan. Verisim: Formal analysis of network simulations. In Int. > Symposium on Software Testing and Analysis, pages 2-13, 2000. " This work is more related to model checkers and theorem analyzers. They concentrate more on the validation part of the communication protocols. But, gerg is asking more related to process algebra. >> I'm doing research on formal verification of algorithms for ad-hoc networks. >> I'm trying to apply transition systems (process algebras etc.) in modelling >> and verification of the reactive algorithms running in ad-hoc environment I am not sure, but their are two types of process algebra, which are useful for communication protocols: - CCS (Calculus of Communication systems) and - PEPA (performance evaluation process algrbra.) You can find a lot of material on the net and books. But a word of caution: You cannot check your PA model unless you have a specification and design. So, i suggest using the techniques and reference mentioned by Tao lin. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 24 09:55:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15775 for ; Mon, 24 Feb 2003 09:55:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OF4N430413 for manet-archive@odin.ietf.org; Mon, 24 Feb 2003 10:04:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OF4Mp30410 for ; Mon, 24 Feb 2003 10:04:22 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15771 for ; Mon, 24 Feb 2003 09:55:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OEoip29616; Mon, 24 Feb 2003 09:50:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OEYQp28399 for ; Mon, 24 Feb 2003 09:34:26 -0500 Received: from mail.tagus.ist.utl.pt (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15207 for ; Mon, 24 Feb 2003 09:25:16 -0500 (EST) Received: (qmail 31251 invoked by uid 504); 24 Feb 2003 14:29:09 -0000 Received: from joao.oliveira@tagus.ist.utl.pt by ana.tagus.ist.utl.pt by uid 501 with qmail-scanner-1.13 (iscan: v3.1/v5.600-1011/465/47876. spamassassin: 2.43-cvs. Clear:. Processed in 0.144388 secs); 24 Feb 2003 14:29:09 -0000 Received: from unknown (HELO tagus.ist.utl.pt) ([172.20.200.30]) (envelope-sender ) by mail.tagus.ist.utl.pt (qmail-ldap-1.03) with SMTP for ; 24 Feb 2003 14:29:09 -0000 Message-ID: <3E5A2CF0.4080904@tagus.ist.utl.pt> Date: Mon, 24 Feb 2003 14:32:16 +0000 From: =?ISO-8859-1?Q?Jo=E3o_Pedro_Oliveira?= Organization: Instituto Superior =?ISO-8859-1?Q?T=E9cnico=2E?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 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: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] Simulating software. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi everyone. I am going to work on routing with mobile ad-hoc networks. Currently, I am looking for a good simulating software. Can anyone indicate me some simulators, advantages and cons? I would like a modular one, that would be relatively easy to implement some security/encryption algorithms on the existing one. Thanks in advance, egards, João Oliveira. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 24 14:34:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23834 for ; Mon, 24 Feb 2003 14:34:03 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OJghY18269 for manet-archive@odin.ietf.org; Mon, 24 Feb 2003 14:42:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OJggp18266 for ; Mon, 24 Feb 2003 14:42:42 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23811 for ; Mon, 24 Feb 2003 14:33:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OJSap16694; Mon, 24 Feb 2003 14:28:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OJMNp16403 for ; Mon, 24 Feb 2003 14:22:23 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23108 for ; Mon, 24 Feb 2003 14:13:11 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA19903 for ; Mon, 24 Feb 2003 14:17:04 -0500 (EST) Received: from [132.250.92.132] ([132.250.92.132]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.1.45) with SMTP id M2003022414170428259 for ; Mon, 24 Feb 2003 14:17:04 -0500 Mime-Version: 1.0 X-Sender: wieselth@pop.itd.nrl.navy.mil Message-Id: Date: Mon, 24 Feb 2003 14:15:36 -0500 To: manet@ietf.org From: Jeff Wieselthier Content-Type: multipart/alternative; boundary="============_-1166008359==_ma============" Subject: [manet] CFP: JSAC Special Issue on Wireless Ad Hoc Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --============_-1166008359==_ma============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" CALL FOR PAPERS IEEE Journal on Selected Areas in Communications WIRELESS AD HOC NETWORKS http://www.argreenhouse.com/society/J-SAC/Calls/wireless_adhoc.html Novel approaches are needed to address ad hoc networks, which are characterized by the lack of an infrastructure. For example, point-to-point and point-to-multipoint modes of communication must be supported in a multihop network that typically consists of small (often disadvantaged) users that are characterized by severely limited energy supply, signal-processing capability, antenna directivity, bandwidth, etc. Crucial applications for mobile ad hoc networks include military communications and disaster relief, although commercial applications are certainly possible as well. In applications with a large number of nodes, scalability is a major concern. The study of ad hoc networks is an interdisciplinary one, which can potentially incorporate communication and information theory, distributed networking algorithms, data structures and compression, coding, signal processing, detection, antenna characteristics, optimization methods, simulation, testbed implementations etc. Papers submitted for this special issue must directly address ad hoc networking issues. We outline here only a few of the many aspects of ad hoc network design and control that will be addressed in this special issue. First, distributed network organization algorithms (such as those for clustering) may be used to create the equivalent of an ad hoc infrastructure. Distributed algorithms are also needed for routing, channel access, and other control functions. Networking techniques for ad hoc networks must address the challenges imposed by the all-wireless environment. For example, by contrast with wired networks, the conventional layered protocol stack is not well suited to the ad hoc wireless networking environment because it does not exploit the potential improvements in performance that can be obtained by jointly designing protocols that span multiple layers. Specifically, it is expected that improved performance can be obtained by considering the properties of the physical and data link layers when designing and operating the media-access control (MAC) protocol. Similarly, there are potential benefits to be obtained by developing protocols that address jointly the routing and MAC functions. Additional benefits can be obtained by jointly addressing higher-layer functions along with routing and MAC. Energy-aware protocols (from the perspective of either energy-efficient or energy-constrained operation) are of critical importance in many ad hoc scenarios. Such energy-aware operation can span multiple layers, e.g., by addressing trade-offs between energy used for RF transmission and for signal processing. It is the goal of this special issue to reflect the latest in the state of the art in ad hoc networks by examining all aspects of ad hoc network design and control, including the dependencies between various network functions and the potential benefits that can be gained by cross-layer design. We are interested in papers on fundamental performance limits, but more importantly on algorithm design and performance, system implementations, etc. We are seeking papers that describe original and unpublished contributions addressing various aspects of ad hoc networking. Possible topics of interest include, but are not limited to: * Physical layer issues in ad hoc networks * Media Access Control (MAC) techniques * Self-organizing architectures and protocols * Routing protocols * Cross-layer protocol design * Mobility management * Protocols for mobile applications * Transport-layer issues * Signal-processing issues in ad hoc networks * Integration with wired networks * Applications * Energy-aware protocols * Security in ad hoc networks * Capacity and scheduling * Node implementation * Effects on existing protocols * Quality of service * Broadcasting and multicasting * Multimedia and traffic integration * Experiments and testbeds * Error-control schemes * Synchronization and scheduling * Scalability * Performance analysis and simulation * Properties of antennas * Optimization methods * Fundamental limits in ad hoc networks All papers on any of the above topics must include a definite and strong connection to ad hoc networks. Please contact Jeffrey Wieselthier at wieselthier@itd.nrl.navy.mil if there are any questions about the suitability of the paper for this special issue. Prospective authors should prepare their manuscripts in accordance with the IEEE J-SAC format described in the Information for Authors at the J-SAC website. All papers should be submitted in pdf format via email to Jeffrey Wieselthier at wieselthier@itd.nrl.navy.mil according to the following timetable: Manuscript Submission: October 15, 2003 Acceptance Notification: April 1, 2004 Final Manuscript Due: June 1, 2004 Publication: 4th Quarter 2004 Guest Editors Dr. Jeffrey E. Wieselthier, Naval Research Laboratory, Washington, DC, wieselthier@itd.nrl.navy.mil Prof. Eitan Altman, INRIA, Sophia-Antipolis, Cedex, FRANCE, Eitan.Altman@sophia.inria.fr Prof. Anthony Ephremides, University of Maryland, College Park, MD, tony@eng.umd.edu Mr. Joseph Macker, Naval Research Laboratory, Washington, DC, macker@itd.nrl.navy.mil Prof. Harlan B. Russell, Clemson University, Clemson, SC, hrussel@hubcap.clemson.edu Dr. Martha Steenstrup, Stow Research L.L.C., Flanders, NJ, steenie@rcn.com Prof. Stephen Wicker, Cornell University, Ithaca, NY, wicker@ee.cornell.edu --============_-1166008359==_ma============ Content-Type: text/html; charset="us-ascii" CFP: JSAC Special Issue on Wireless Ad Hoc Networks
                          CALL FOR PAPERS
            IEEE Journal on Selected Areas in Communications
                       WIRELESS AD HOC NETWORKS

http://www.argreenhouse.com/society/J-SAC/Calls/wireless_adhoc.html

Novel approaches are needed to address ad hoc networks, which are characterized by the lack of an infrastructure.  For example, point-to-point and point-to-multipoint modes of communication must be supported in a multihop network that typically consists of small (often disadvantaged) users that are characterized by severely limited energy supply, signal-processing capability, antenna directivity, bandwidth, etc.  Crucial applications for mobile ad hoc networks include military communications and disaster relief, although commercial applications are certainly possible as well.  In applications with a large number of nodes, scalability is a major concern.

The study of ad hoc networks is an interdisciplinary one, which can potentially incorporate communication and information theory, distributed networking algorithms, data structures and compression, coding, signal processing, detection, antenna characteristics, optimization methods, simulation, testbed implementations etc.  Papers submitted for this special issue must directly address ad hoc networking issues. 

We outline here only a few of the many aspects of ad hoc network design and control that will be addressed in this special issue.  First, distributed network organization algorithms (such as those for clustering) may be used to create the equivalent of an ad hoc infrastructure.  Distributed algorithms are also needed for routing, channel access, and other control functions.  Networking techniques for ad hoc networks must address the challenges imposed by the all-wireless environment.  For example, by contrast with wired networks, the conventional layered protocol stack is not well suited to the ad hoc wireless networking environment because it does not exploit the potential improvements in performance that can be obtained by jointly designing protocols that span multiple layers.  Specifically, it is expected that improved performance can be obtained by considering the properties of the physical and data link layers when designing and operating the media-access control (MAC) protocol.  Similarly, there are potential benefits to be obtained by developing protocols that address jointly the routing and MAC functions.  Additional benefits can be obtained by jointly addressing higher-layer functions along with routing and MAC.  Energy-aware protocols (from the perspective of either energy-efficient or energy-constrained operation) are of critical importance in many ad hoc scenarios.  Such energy-aware operation can span multiple layers, e.g., by addressing trade-offs between energy used for RF transmission and for signal processing.

It is the goal of this special issue to reflect the latest in the state of the art in ad hoc networks by examining all aspects of ad hoc network design and control, including the dependencies between various network functions and the potential benefits that can be gained by cross-layer design.  We are interested in papers on fundamental performance limits, but more importantly on algorithm design and performance, system implementations, etc.

We are seeking papers that describe original and unpublished contributions addressing various aspects of ad hoc networking.  Possible topics of interest include, but are not limited to:

     * Physical layer issues in ad hoc networks
     * Media Access Control (MAC) techniques
     * Self-organizing architectures and protocols
     * Routing protocols
     * Cross-layer protocol design
     * Mobility management
     * Protocols for mobile applications
     * Transport-layer issues
     * Signal-processing issues in ad hoc networks
     * Integration with wired networks
     * Applications
     * Energy-aware protocols
     * Security in ad hoc networks
     * Capacity and scheduling
     * Node implementation
     * Effects on existing protocols
     * Quality of service
     * Broadcasting and multicasting
     * Multimedia and traffic integration
     * Experiments and testbeds
     * Error-control schemes
     * Synchronization and scheduling
     * Scalability
     * Performance analysis and simulation
     * Properties of antennas
     * Optimization methods
     * Fundamental limits in ad hoc networks

All papers on any of the above topics must include a definite and strong connection to ad hoc networks.  Please contact Jeffrey Wieselthier at wieselthier@itd.nrl.navy.mil if there are any questions about the suitability of the paper for this special issue. 

Prospective authors should prepare their manuscripts in accordance with the IEEE J-SAC format described in the Information for Authors at the J-SAC website.  All papers should be submitted in pdf format via email to Jeffrey Wieselthier at wieselthier@itd.nrl.navy.mil according to the following timetable:

     Manuscript Submission:     October 15, 2003
     Acceptance Notification:   April 1, 2004
     Final Manuscript Due:      June 1, 2004
     Publication:               4th Quarter 2004


                       Guest Editors

Dr. Jeffrey E. Wieselthier, Naval Research Laboratory, Washington, DC, wieselthier@itd.nrl.navy.mil

Prof. Eitan Altman, INRIA, Sophia-Antipolis, Cedex, FRANCE, Eitan.Altman@sophia.inria.fr

Prof. Anthony Ephremides, University of Maryland, College Park, MD, tony@eng.umd.edu

Mr. Joseph Macker, Naval Research Laboratory, Washington, DC, macker@itd.nrl.navy.mil

Prof. Harlan B. Russell, Clemson University, Clemson, SC, hrussel@hubcap.clemson.edu

Dr. Martha Steenstrup, Stow Research L.L.C., Flanders, NJ, steenie@rcn.com

Prof. Stephen Wicker, Cornell University, Ithaca, NY, wicker@ee.cornell.edu
--============_-1166008359==_ma============-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Feb 24 15:24:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25323 for ; Mon, 24 Feb 2003 15:24:20 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OKX1u21054 for manet-archive@odin.ietf.org; Mon, 24 Feb 2003 15:33:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKX0p21051 for ; Mon, 24 Feb 2003 15:33:00 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25320 for ; Mon, 24 Feb 2003 15:23:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKHGp20293; Mon, 24 Feb 2003 15:17:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKCWp20124 for ; Mon, 24 Feb 2003 15:12:32 -0500 Received: from dire.bris.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24612 for ; Mon, 24 Feb 2003 15:03:20 -0500 (EST) Received: from cs.bris.ac.uk (actually host lunaleka.cs.bris.ac.uk) by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Mon, 24 Feb 2003 20:07:13 +0000 Received: from abwyd (abwyd [137.222.103.137]) by cs.bris.ac.uk (8.9.3/8.9.3) with SMTP id UAA22408 for ; Mon, 24 Feb 2003 20:05:45 GMT Message-ID: <005e01c2dc40$32f3c790$8967de89@abwyd> From: Grzegorz Jablonski To: manet References: <5EF7D95E17BDAD4A968C812E5ABC390B02CFDD@KC-MAIL4.kc.umkc.edu> Subject: Re: [manet] formal verification of ad hoc networks Date: Mon, 24 Feb 2003 20:06:19 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit hi, thanks, the papers on Verisim are very interesting. I wanted to go similar way, by building an abstract model in a process algebra or similar formalism and to verify it, with use of model checkers and equivalence relations. I've tried Calculus of Broadcasting Systems, it seemed the most suitable for my purposes. However, it turns out to be very difficult (at least for me!) to build a suitable formal model, which would reflect the reality of ad-hoc networks, could guide the implementation and be verifiable. Anyway, I'm still trying. Cheers Greg ----- Original Message ----- From: "Ayyasamy, Senthilkumar (UMKC-Student)" To: "celliott" ; "jablonsk" ; "manet" Cc: "taolin" Sent: Saturday, February 22, 2003 11:51 AM Subject: Re: [manet] formal verification of ad hoc networks > > > > > "K. Bhargavan, C. Gunter, M. Kim, I. Lee, D. Obradovic,O. Sokolsky, and M. > > Viswanathan. Verisim: Formal analysis of network simulations. In Int. > > Symposium on Software Testing and Analysis, pages 2-13, 2000. " > > This work is more related to model checkers and theorem analyzers. They > concentrate more on the validation part of the communication protocols. > But, gerg is asking more related to process algebra. > > >> I'm doing research on formal verification of algorithms for ad-hoc networks. > >> I'm trying to apply transition systems (process algebras etc.) in modelling > >> and verification of the reactive algorithms running in ad-hoc environment > > I am not sure, but their are two types of process algebra, which are useful > for communication protocols: > - CCS (Calculus of Communication systems) and > - PEPA (performance evaluation process algrbra.) > You can find a lot of material on the net and books. > > But a word of caution: You cannot check your PA model unless you have a specification > and design. So, i suggest using the techniques and reference mentioned by Tao lin. > > _______________________________________________ > 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 mailnull@www1.ietf.org Mon Feb 24 15:57:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26335 for ; Mon, 24 Feb 2003 15:57:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OL6Uk23612 for manet-archive@odin.ietf.org; Mon, 24 Feb 2003 16:06:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OL6Up23609 for ; Mon, 24 Feb 2003 16:06:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26329 for ; Mon, 24 Feb 2003 15:57:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKawp21160; Mon, 24 Feb 2003 15:36:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKVIp20989 for ; Mon, 24 Feb 2003 15:31:18 -0500 Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25296 for ; Mon, 24 Feb 2003 15:22:06 -0500 (EST) Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329); Mon, 24 Feb 2003 14:26:00 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [manet] formal verification of ad hoc networks Date: Mon, 24 Feb 2003 14:25:59 -0600 Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02CFE9@KC-MAIL4.kc.umkc.edu> Thread-Topic: [manet] formal verification of ad hoc networks Thread-Index: AcLcQbVtrMg2sn4MTPaAqb36wswgoAAAD1og From: "Ayyasamy, Senthilkumar (UMKC-Student)" To: "Grzegorz Jablonski" , "manet" X-OriginalArrivalTime: 24 Feb 2003 20:26:00.0436 (UTC) FILETIME=[F1E98340:01C2DC42] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1OKVIp20990 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit > I've tried Calculus of Broadcasting Systems, it seemed the > most suitable for my purposes. However, it turns out to be > very difficult (at least for me!)to build a suitable formal > model, which would reflect the reality of ad-hoc networks, > could guide the implementation and be verifiable. If you feel CBS, CCS are too theoretical, I suggest a better alternative. " Abstract State Machines" But, You should know a little of first order logic. http://www.eecs.umich.edu/gasm/ Associated ASMl software from Microsoft research. http://research.microsoft.com/foundations/ For anything, you need to know a basic specification language (be it process algebra, situation calculus, axiomatic specification or PSL) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 03:41:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20583 for ; Tue, 25 Feb 2003 03:41:22 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1P8oI409248 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 03:50:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P8oHp09245 for ; Tue, 25 Feb 2003 03:50:17 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20569 for ; Tue, 25 Feb 2003 03:40:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P8Zrp07798; Tue, 25 Feb 2003 03:35:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P8R9p07528 for ; Tue, 25 Feb 2003 03:27:09 -0500 Received: from mercury.telscom.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20018 for ; Tue, 25 Feb 2003 03:17:42 -0500 (EST) Received: from ming (193.72.156.76) by mercury.telscom.ch with MERCUR-SMTP/POP3/IMAP4-Server (v3.30.09 AS-2621446) for ; Tue, 25 Feb 2003 09:19:02 +0100 From: "Marcin Michalak" Organization: Telscom To: manet@ietf.org Date: Tue, 25 Feb 2003 09:23:26 +0100 MIME-Version: 1.0 Message-ID: <3E5B360E.6774.A275B@localhost> Priority: normal In-reply-to: X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Reply-To: marcin@telscom.ch Content-Transfer-Encoding: 7BIT Subject: [manet] Real-time transmission in ad-hoc? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Hello, I'm just starting my research in real-time transmission in ad-hoc networks and would be grateful for some documents regarding this topic. Is anyone already doing such research? Regards, Marcin Michalak ---------------------------------------------------------- Marcin Michalak Research Engineer/PhD Student Mobile: +41 79 330 83 51 Telscom AG/Bern University _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 05:08:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22372 for ; Tue, 25 Feb 2003 05:08:29 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PAHRw15088 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 05:17:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PAHQp15085 for ; Tue, 25 Feb 2003 05:17:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22314 for ; Tue, 25 Feb 2003 05:07:57 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PA2pp13468; Tue, 25 Feb 2003 05:02:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P9vsp13246 for ; Tue, 25 Feb 2003 04:57:54 -0500 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21863 for ; Tue, 25 Feb 2003 04:48:25 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 25 Feb 2003 01:52:19 -0800 X-Originating-IP: [143.117.36.153] From: "adhoc" To: References: <3E5A2CF0.4080904@tagus.ist.utl.pt> Subject: Re: [manet] Simulating software. Date: Tue, 25 Feb 2003 09:52:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 25 Feb 2003 09:52:19.0644 (UTC) FILETIME=[962ACFC0:01C2DCB3] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h1P9vsp13247 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit GLOMOSIM, NS-2, and OPNET. The first two are freeware. You can find them easily on Internet. Regards, Bosheng Zhou ----- Original Message ----- From: "João Pedro Oliveira" To: Sent: Monday, February 24, 2003 2:32 PM Subject: [manet] Simulating software. > Hi everyone. > > I am going to work on routing with mobile ad-hoc networks. > Currently, I am looking for a good simulating software. > Can anyone indicate me some simulators, advantages and cons? > I would like a modular one, that would be relatively easy to implement > some security/encryption algorithms on the existing one. > > > Thanks in advance, > > egards, > João Oliveira. > > > _______________________________________________ > 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 mailnull@www1.ietf.org Tue Feb 25 05:23:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22632 for ; Tue, 25 Feb 2003 05:23:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PAWvb15726 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 05:32:57 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PAWvp15723 for ; Tue, 25 Feb 2003 05:32:57 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22629 for ; Tue, 25 Feb 2003 05:23:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PAD4p14733; Tue, 25 Feb 2003 05:13:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PA4kp13645 for ; Tue, 25 Feb 2003 05:04:46 -0500 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21986 for ; Tue, 25 Feb 2003 04:55:17 -0500 (EST) Received: from cit.ie (mail.cit.ie [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Tue, 25 Feb 2003 09:46:46 +0000 Message-ID: <291880-22003222594646524@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Tue, 25 Feb 2003 09:46:46 -00 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] Network address translation (NAT) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I sent this message to the ns2 mailing list but got no reply so I said I would try here I want to look at NAT in an ad hoc network but I dont know how I can go simulating NAT in ns2, any suggestions? John Paul O Grady -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 10:38:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03694 for ; Tue, 25 Feb 2003 10:38:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PFldL06407 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 10:47:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFlcp06404 for ; Tue, 25 Feb 2003 10:47:39 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03689 for ; Tue, 25 Feb 2003 10:38:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFWCp04456; Tue, 25 Feb 2003 10:32:12 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFPIp04196 for ; Tue, 25 Feb 2003 10:25:18 -0500 Received: from mx2out.umbc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02891 for ; Tue, 25 Feb 2003 10:15:44 -0500 (EST) Received: from webmail.umbc.edu (webmail.umbc.edu [130.85.29.11]) by mx2out.umbc.edu (8.12.1/8.12.0/UMBC-Central 1.11 mxout 1.2.2.3 $) with ESMTP id h1PFJcGs027002 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 25 Feb 2003 10:19:39 -0500 (EST) X-WebMail-UserID: ajohn1 Date: Tue, 25 Feb 2003 10:17:10 -0500 From: alex attumalil To: manet@ietf.org X-EXP32-SerialNo: 00002897 Message-ID: <3E608554@webmail.umbc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.62 Content-Transfer-Encoding: 7bit Subject: [manet] IPv6 and Multicasting Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Does anyone out there have documentation on their experience with IPv6 Multicasting ? I am interested in knowing what protocols were used and what kind of a network it was implemented on. Also, if there is any solid data on control overheads with the various Protocols impelemented. I am aware of M6Bone and 6Net Thanks -alex _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 10:40:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03778 for ; Tue, 25 Feb 2003 10:40:41 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PFnkN06545 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 10:49:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFnkp06542 for ; Tue, 25 Feb 2003 10:49:46 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03752 for ; Tue, 25 Feb 2003 10:40:10 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFYtp04539; Tue, 25 Feb 2003 10:34:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFPcp04227 for ; Tue, 25 Feb 2003 10:25:38 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02902 for ; Tue, 25 Feb 2003 10:16:03 -0500 (EST) Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1PFJv6358136; Tue, 25 Feb 2003 10:19:57 -0500 (EST) Received: from ari424h ([208.17.194.135]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with SMTP id BCH99887; Tue, 25 Feb 2003 10:19:55 -0500 (EST) From: "Kaustubh Phanse" To: "adhoc" , Subject: RE: [manet] Simulating software. Date: Tue, 25 Feb 2003 10:27:20 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-reply-to: Importance: Normal Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit QualNet (a commercial extension of Glomosim) is another network simulation software: http://www.scalable-networks.com I think it is useful especially for ad hoc network simulations. regards Kaustubh -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org]On Behalf Of adhoc Sent: Tuesday, February 25, 2003 4:52 AM To: manet@ietf.org Subject: Re: [manet] Simulating software. GLOMOSIM, NS-2, and OPNET. The first two are freeware. You can find them easily on Internet. Regards, Bosheng Zhou ----- Original Message ----- From: "João Pedro Oliveira" To: Sent: Monday, February 24, 2003 2:32 PM Subject: [manet] Simulating software. > Hi everyone. > > I am going to work on routing with mobile ad-hoc networks. > Currently, I am looking for a good simulating software. > Can anyone indicate me some simulators, advantages and cons? > I would like a modular one, that would be relatively easy to implement > some security/encryption algorithms on the existing one. > > > Thanks in advance, > > egards, > João Oliveira. > > > _______________________________________________ > 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 mailnull@www1.ietf.org Tue Feb 25 12:29:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07511 for ; Tue, 25 Feb 2003 12:29:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PHc9l15638 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 12:38:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHc8p15633 for ; Tue, 25 Feb 2003 12:38:08 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07488 for ; Tue, 25 Feb 2003 12:28:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHIBp13417; Tue, 25 Feb 2003 12:18:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHDsp13241 for ; Tue, 25 Feb 2003 12:13:54 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06541 for ; Tue, 25 Feb 2003 12:04:16 -0500 (EST) Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1PH8C6426257; Tue, 25 Feb 2003 12:08:12 -0500 (EST) Received: from LAPTOPPC (h80ad372c.dhcp.vt.edu [128.173.55.44]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BCI23472; Tue, 25 Feb 2003 12:08:10 -0500 (EST) Message-ID: <001101c2dcf0$7515a610$2c37ad80@LAPTOPPC> From: "Tao Lin" To: Cc: Subject: Re: [manet] Real-time transmission in ad-hoc? Date: Tue, 25 Feb 2003 12:08:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, Marcin, A MS student in the Real-Time lab at Virginia Tehc, USA did some work on real-time transmission in switched Ethernet. "Jinggang Wang, "Soft Real-Time Switched Ethernet: Best-Effort Packet Scheduling Algorithm, Implementation, and Feasibility Analysis", Master´s Thesis, September 2002." If your intetrested work needs to handle message buffering and queuing due to contention, the algorithms in his thesis may share some similiarity. The PDF version of his thesis is listed at http://nile.ece.vt.edu/thesis/thesis.htm. Best, Tao Lin Ph. D. Candidate ECE Department Virginia Tech. USA >----- Original Message ----- >From: "Marcin Michalak" >To: >Sent: Tuesday, February 25, 2003 3:23 AM >Subject: [manet] Real-time transmission in ad-hoc? > > >> Hello, >> I'm just starting my research in real-time transmission in ad-hoc >> networks and would be grateful for some documents regarding this >> topic. Is anyone already doing such research? >> Regards, >> Marcin Michalak >> ---------------------------------------------------------- >> Marcin Michalak Research Engineer/PhD Student >> Mobile: +41 79 330 83 51 Telscom AG/Bern University >> >> _______________________________________________ >> 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 mailnull@www1.ietf.org Tue Feb 25 12:33:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07784 for ; Tue, 25 Feb 2003 12:33:32 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PHgeF16160 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 12:42:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHgep16157 for ; Tue, 25 Feb 2003 12:42:40 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07741 for ; Tue, 25 Feb 2003 12:33:01 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHPHp13738; Tue, 25 Feb 2003 12:25:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PHMop13640 for ; Tue, 25 Feb 2003 12:22:50 -0500 Received: from gawab.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06773 for ; Tue, 25 Feb 2003 12:13:12 -0500 (EST) Received: (qmail 28331 invoked by uid 1004); 25 Feb 2003 17:19:58 -0000 Received: from unknown (HELO amrfbkf7vt1gwf) (comm@gawab.com@62.139.29.195) by gawab.com with SMTP; 25 Feb 2003 17:19:55 -0000 Message-ID: <004801c2dcf1$e554bc80$c31d8b3e@sfux.com> Reply-To: "Amr Ezzat" From: "Amr Ezzat" To: Date: Tue, 25 Feb 2003 19:18:13 +0200 Organization: communications MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01C2DD02.A4467830" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] Qos Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0045_01C2DD02.A4467830 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable hi every body I need any sites about Qos simulations and I want to ask=20 as I know that for any field in science there is an area very famous and = newly discovered can up give me this areas in qos routing protocol I really need ur help in the simulating software note if u know an algorithms in NS to use to discover about qos plz help = me yours sincerely: Amr Ezzat e-mail: comm@gawab.com =20 ------=_NextPart_000_0045_01C2DD02.A4467830 Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable
hi every body
 
I need any sites about Qos=20 simulations
and I want to ask
as I know that for any field in science there is an area very = famous and=20 newly discovered
can up give me this areas in qos routing protocol
I really need ur help in the simulating software
 
note if u know an algorithms in NS = to use to=20 discover about qos plz help me
 
yours=20 sincerely:
          = ;            =           =20 Amr=20 Ezzat
e-mail:
         = ;            =          =20 comm@gawab.com
 
 
------=_NextPart_000_0045_01C2DD02.A4467830-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 14:34:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11890 for ; Tue, 25 Feb 2003 14:34:41 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PJhos24982 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 14:43:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PJhnp24979 for ; Tue, 25 Feb 2003 14:43:49 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11886 for ; Tue, 25 Feb 2003 14:34:10 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PJRip23290; Tue, 25 Feb 2003 14:27:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PJNfp23152 for ; Tue, 25 Feb 2003 14:23:41 -0500 Received: from fsc.cpsc.ucalgary.ca (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11239 for ; Tue, 25 Feb 2003 14:14:01 -0500 (EST) Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.7/8.12.7) with ESMTP id h1PJHgqd009355 for ; Tue, 25 Feb 2003 12:17:42 -0700 Received: from cpsc.ucalgary.ca (ict720f [136.159.17.10]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id h1PJHfMP028188 for ; Tue, 25 Feb 2003 12:17:41 -0700 Message-ID: <3E5BC155.4060309@cpsc.ucalgary.ca> Date: Tue, 25 Feb 2003 12:17:41 -0700 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-1.0 required=7.5 tests=NOSPAM_INC,SPAM_PHRASE_00_01,TO_LOCALPART_EQ_REAL, USER_AGENT,USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG version=2.43 Content-Transfer-Encoding: 7bit Subject: [manet] Visualization tool for NS2 for ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Ad hockey has been giving me problems with installation (compatibility issues with new versions of Perl/Tk ). Does anyone know of any other good visualization tool that can be used with NS2 for ad hoc networks? Abhinav _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Feb 25 18:27:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22254 for ; Tue, 25 Feb 2003 18:27:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PNbD308559 for manet-archive@odin.ietf.org; Tue, 25 Feb 2003 18:37:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PNbDp08555 for ; Tue, 25 Feb 2003 18:37:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22247 for ; Tue, 25 Feb 2003 18:27:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PNNNp07546; Tue, 25 Feb 2003 18:23:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PNJUp07360 for ; Tue, 25 Feb 2003 18:19:30 -0500 Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21585 for ; Tue, 25 Feb 2003 18:09:45 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by ece.rice.edu (Postfix) with SMTP id 19BEC68A74 for ; Tue, 25 Feb 2003 17:13:40 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by ece.rice.edu (Postfix) with ESMTP id B4AA968A68 for ; Tue, 25 Feb 2003 17:13:39 -0600 (CST) Received: from egress.ece.rice.edu (unknown [128.42.4.78]) by ece.rice.edu (Postfix) with ESMTP id 03A9A68A5B for ; Tue, 25 Feb 2003 17:13:37 -0600 (CST) Received: from localhost (kanodia@localhost) by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id RAA10432 for ; Tue, 25 Feb 2003 17:13:37 -0600 X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs Date: Tue, 25 Feb 2003 17:13:36 -0600 (CST) From: Vikram Kanodia X-Sender: kanodia@egress.ece.rice.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 X-DCC--Metrics: ece.rice.edu 1067; Body=1 Fuz1=1 Fuz2=1 Subject: [manet] PSM mode of 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Apologies of posting this message on this list but I got no reply from the ns-users mailing list...so...:) Has anybody implemented the power saving mode (PSM) in ns ? I know I have read a couple of papers reporting experiments with the PSM mode ...In any case I was wondering if you have the pSM mode in ns, whether it is posisble for you to share your code with me. Thanks, -Vikram Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H) WWW: http://www.ece.rice.edu/~kanodia _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 26 05:47:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00514 for ; Wed, 26 Feb 2003 05:47:39 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QAv7p30031 for manet-archive@odin.ietf.org; Wed, 26 Feb 2003 05:57:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QAv7p30028 for ; Wed, 26 Feb 2003 05:57:07 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00508 for ; Wed, 26 Feb 2003 05:47:08 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QAbhp28981; Wed, 26 Feb 2003 05:37:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QAV5p28047 for ; Wed, 26 Feb 2003 05:31:05 -0500 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29984 for ; Wed, 26 Feb 2003 05:21:06 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 26 Feb 2003 02:25:01 -0800 Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP; Wed, 26 Feb 2003 10:25:00 GMT X-Originating-IP: [212.4.33.133] From: "Berner Vegge" To: manet@ietf.org Date: Wed, 26 Feb 2003 11:25:00 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 26 Feb 2003 10:25:01.0058 (UTC) FILETIME=[51AC9620:01C2DD81] Subject: [manet] MANET testing in realistic environment Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello all! I have made some testing on AODV, OLSR and LUNAR in a realistic environment (i.e. not simulations). The tests are performed within an office building with ORINOCO GOLD WLAN cards. I have used WLAN IEEE802.11b as physical/link layer. The testing has very often revealed problems and constraints in the WLAN technology, such as interference when several nodes are close to each other so that the throughput drops dramatically. Changes in signal/noise relation leading do links that drop out etc has also been a problem. Finally we have seen that routing messages are lost very often at high load, so that the connections are taken down for that reason (this is probably due to lack of priority on routing packets, and as these are broadcasted with no ack and resending, they are very easily lost). I know that a lot of work is ongoing within IEEE to improve WLAN, so hopefully MANET over WLAN will be possible in a year or so. My question is if anyone else has performed realistic tests by running MANET over WLAN and if anyone has any experiences, documented results etc, that they would share with me. Thanks a lot! Best Regards Berner _________________________________________________________________ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 26 09:10:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05844 for ; Wed, 26 Feb 2003 09:10:16 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QEJlf11629 for manet-archive@odin.ietf.org; Wed, 26 Feb 2003 09:19:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QEJlp11626 for ; Wed, 26 Feb 2003 09:19:47 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05823 for ; Wed, 26 Feb 2003 09:09:45 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QE4Kp09758; Wed, 26 Feb 2003 09:04:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QDwwp09543 for ; Wed, 26 Feb 2003 08:58:58 -0500 Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04205 for ; Wed, 26 Feb 2003 08:48:56 -0500 (EST) Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Wed, 26 Feb 2003 08:53:29 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Wed, 26 Feb 2003 08:53:14 -0500 From: "Pete Sholander" To: , Subject: Re: [manet] MANET testing in realistic environment Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Berner, In the open/academic literature ... David Johnson published some early "open-air" results for DSR. Maybe check his web-site at Rice? Fred Templin and the TBRPF folks have published some tests that included a few ground nodes, and a radio-controlled helicopter (see http://www.erg.sri.com/publications.html). So, real-world MANET over WLAN results are out there ... --Pete Sholander >>> "Berner Vegge" 02/26/03 05:25AM >>> Hello all! I have made some testing on AODV, OLSR and LUNAR in a realistic environment (i.e. not simulations). The tests are performed within an office building with ORINOCO GOLD WLAN cards. I have used WLAN IEEE802.11b as physical/link layer. The testing has very often revealed problems and constraints in the WLAN technology, such as interference when several nodes are close to each other so that the throughput drops dramatically. Changes in signal/noise relation leading do links that drop out etc has also been a problem. Finally we have seen that routing messages are lost very often at high load, so that the connections are taken down for that reason (this is probably due to lack of priority on routing packets, and as these are broadcasted with no ack and resending, they are very easily lost). I know that a lot of work is ongoing within IEEE to improve WLAN, so hopefully MANET over WLAN will be possible in a year or so. My question is if anyone else has performed realistic tests by running MANET over WLAN and if anyone has any experiences, documented results etc, that they would share with me. Thanks a lot! Best Regards Berner _________________________________________________________________ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner _______________________________________________ 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 mailnull@www1.ietf.org Wed Feb 26 13:19:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18805 for ; Wed, 26 Feb 2003 13:19:07 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QISj631788 for manet-archive@odin.ietf.org; Wed, 26 Feb 2003 13:28:45 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QISjp31785 for ; Wed, 26 Feb 2003 13:28:45 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18763 for ; Wed, 26 Feb 2003 13:18:36 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QI2ep29791; Wed, 26 Feb 2003 13:02:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QHtip29561 for ; Wed, 26 Feb 2003 12:55:44 -0500 Received: from mx1.isti.cnr.it (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17654 for ; Wed, 26 Feb 2003 12:45:36 -0500 (EST) Received: from CONVERSION.MAIL.IAT.CNR.IT by mx.isti.cnr.it (PMDF V6.2 #30641) id <01KSWK11EOAO9D4BI1@mx.isti.cnr.it> for manet@ietf.org; Wed, 26 Feb 2003 18:48:29 +0100 (MET) Received: from iitpa6v64oitt1 (leli1.iit.cnr.it [146.48.98.2]) by mx.isti.cnr.it (PMDF V6.2 #30641) with SMTP id <01KSWK115MNG9ED9V4@mx.isti.cnr.it> for manet@ietf.org; Wed, 26 Feb 2003 18:48:29 +0100 (MET) Date: Wed, 26 Feb 2003 18:45:08 +0100 From: Eleonora Borgia To: manet@ietf.org Message-id: <008d01c2ddbe$cd93dea0$02623092@iitpa6v64oitt1> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Mailer: Microsoft Outlook Express 5.00.2919.6700 Content-type: multipart/alternative; boundary="Boundary_(ID_bxRcO4NdCaSsIy4SSR5iyQ)" X-Priority: 3 X-MSMail-priority: Normal Subject: [manet] ieee 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --Boundary_(ID_bxRcO4NdCaSsIy4SSR5iyQ) Content-type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I recently did some experimental studies of the behavior of the IEEE = 802.11b Protocol. I measured the IEEE 802.11b transmission ranges in a = real environment, composed by 2/4 nodes communicating in ad hoc mode. Does somebody know if there exists a free tool for carrier sensing and = interference range measurement for the same technology? Regards, Eleonora --Boundary_(ID_bxRcO4NdCaSsIy4SSR5iyQ) Content-type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
 
I recently did some experimental = studies of the=20 behavior of the IEEE 802.11b Protocol. I measured =20 the IEEE 802.11b transmission ranges in a real environment, composed by = 2/4=20 nodes communicating in ad hoc mode.
 Does somebody know if there = exists a free=20 tool for carrier sensing and interference range measurement for the same = technology?
 
Regards,
Eleonora
--Boundary_(ID_bxRcO4NdCaSsIy4SSR5iyQ)-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Feb 26 14:24:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20680 for ; Wed, 26 Feb 2003 14:24:48 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QJYPt03483 for manet-archive@odin.ietf.org; Wed, 26 Feb 2003 14:34:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QJYPp03480 for ; Wed, 26 Feb 2003 14:34:25 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20635 for ; Wed, 26 Feb 2003 14:24:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QJHVp02651; Wed, 26 Feb 2003 14:17:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QJB9p02450 for ; Wed, 26 Feb 2003 14:11:09 -0500 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19988 for ; Wed, 26 Feb 2003 14:01:01 -0500 (EST) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id h1QJ4lT27091; Wed, 26 Feb 2003 20:04:47 +0100 (MET) Message-ID: <004401c2ddce$036753e0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Berner Vegge" , References: Subject: Re: [manet] MANET testing in realistic environment Date: Wed, 26 Feb 2003 20:33:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit We have run many realistic testing with IEEE 802.11 in the past. We experienced several link instabilities due to frequent variation in link quality from remote nodes. Similar effects were also reported in NRL. This is the reason why advanced neighbor sensing has been introduced in OLSR. This kind of effect were never detected in ns-2 simulations. Philippe ----- Original Message ----- From: Berner Vegge To: Sent: Wednesday, February 26, 2003 11:25 AM Subject: [manet] MANET testing in realistic environment > Hello all! > I have made some testing on AODV, OLSR and LUNAR in a realistic > environment (i.e. not simulations). The tests are performed > within an office building with ORINOCO GOLD WLAN cards. I have > used WLAN IEEE802.11b as physical/link layer. The testing has > very often revealed problems and constraints in the WLAN > technology, such as interference when several nodes are close > to each other so that the throughput drops dramatically. > Changes in signal/noise relation leading do links that drop out > etc has also been a problem. Finally we have seen that > routing messages are lost very often at high load, so that > the connections are taken down for that reason (this is probably > due to lack of priority on routing packets, and as these are > broadcasted with no ack and resending, they are very easily lost). > I know that a lot of work is ongoing within IEEE to improve WLAN, > so hopefully MANET over WLAN will be possible in a year or so. > > My question is if anyone else has performed realistic tests by > running MANET over WLAN and if anyone has any experiences, > documented results etc, that they would share with me. > > Thanks a lot! > Best Regards Berner > > > > > > _________________________________________________________________ > MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og > dine venner > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Feb 26 16:42:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27262 for ; Wed, 26 Feb 2003 16:42:21 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QLq2b13855 for manet-archive@odin.ietf.org; Wed, 26 Feb 2003 16:52:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QLq2p13852 for ; Wed, 26 Feb 2003 16:52:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27157 for ; Wed, 26 Feb 2003 16:39:41 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QLW7p12044; Wed, 26 Feb 2003 16:32:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QLQip11889 for ; Wed, 26 Feb 2003 16:26:44 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26019 for ; Wed, 26 Feb 2003 16:16:32 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id QAA20787; Wed, 26 Feb 2003 16:20:22 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.1.45) with SMTP id M2003022616202218645 ; Wed, 26 Feb 2003 16:20:22 -0500 Message-Id: <5.1.1.5.2.20030226154659.01e01690@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 26 Feb 2003 16:20:13 -0500 To: "Philippe Jacquet" , "Berner Vegge" , From: Joe Macker Subject: Re: [manet] MANET testing in realistic environment In-Reply-To: <004401c2ddce$036753e0$1f175d80@inria.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1QLQip11890 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Berner you raise salient engineering points that are reasonably protocol agnostic. We have done significant realistic test outdoors and indoors (and with an emulation environment using 802.11) with working systems and have achieved significant imrpovements with some minor modifications.. We modified older INRIA OLSR code to add a link sensing hysteresis algorithm to improve robustness and it works reasonably well for us in many trials to date including highly congested ones (better link layer sensing info --lower layer triggers, etc-- would be a further plus for any neighbor management algorithm). We are dealing with naturally time-varying channels and highly unpredictable anomalies in many wireless scenarios not wired behavior and we should be cognizant of that fact. Also, related to your noticing routing message being lost, for Linux (RH dists) we quickly added ToS packet markings that improved the priority under network congestion for routing control packets (we tested! that this actually did improve things for the OS and queueing engine we were using). This code is available at http://pf.itd.nrl.navy.mil under the project INRIA OLSR with NRL mods. Packet jittering for distributed control events,etc may also be important this was also added and parameterized in the above experimental prototype code (very important in a simulation)..We also have newer code developments that should be released in the near future that we feel further improve the link sensing process,etc. -Joe At 08:33 PM 2/26/2003 +0100, Philippe Jacquet wrote: >We have run many realistic testing with IEEE 802.11 in the past. We >experienced several link instabilities due to frequent variation in link >quality from remote nodes. Similar effects were also reported in NRL. This >is the reason why advanced neighbor sensing has been introduced in OLSR. >This kind of effect were never detected in ns-2 simulations. > >Philippe >----- Original Message ----- >From: Berner Vegge >To: >Sent: Wednesday, February 26, 2003 11:25 AM >Subject: [manet] MANET testing in realistic environment > > >> Hello all! >> I have made some testing on AODV, OLSR and LUNAR in a realistic >> environment (i.e. not simulations). The tests are performed >> within an office building with ORINOCO GOLD WLAN cards. I have >> used WLAN IEEE802.11b as physical/link layer. The testing has >> very often revealed problems and constraints in the WLAN >> technology, such as interference when several nodes are close >> to each other so that the throughput drops dramatically. >> Changes in signal/noise relation leading do links that drop out >> etc has also been a problem. Finally we have seen that >> routing messages are lost very often at high load, so that >> the connections are taken down for that reason (this is probably >> due to lack of priority on routing packets, and as these are >> broadcasted with no ack and resending, they are very easily lost). >> I know that a lot of work is ongoing within IEEE to improve WLAN, >> so hopefully MANET over WLAN will be possible in a year or so. >> >> My question is if anyone else has performed realistic tests by >> running MANET over WLAN and if anyone has any experiences, >> documented results etc, that they would share with me. >> >> Thanks a lot! >> Best Regards Berner >> >> >> >> >> >> _________________________________________________________________ >> MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg >og >> dine venner >> >> _______________________________________________ >> 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 mailnull@www1.ietf.org Thu Feb 27 06:08:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25155 for ; Thu, 27 Feb 2003 06:08:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RBIl008369 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 06:18:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RBIkp08366 for ; Thu, 27 Feb 2003 06:18:46 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25152 for ; Thu, 27 Feb 2003 06:08:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RB0wp06918; Thu, 27 Feb 2003 06:00:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RAtap06771 for ; Thu, 27 Feb 2003 05:55:36 -0500 Received: from jive.SoftHome.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24805 for ; Thu, 27 Feb 2003 05:45:08 -0500 (EST) From: ankurjain@softhome.net Received: (qmail 20646 invoked by uid 417); 27 Feb 2003 10:49:04 -0000 Received: from slide-.softhome.net (HELO softhome.net) (172.16.2.21) by shunt-smtp-out-0 with SMTP; 27 Feb 2003 10:49:04 -0000 Received: from localhost (localhost [127.0.0.1]) (uid 417) by softhome.net with local; Thu, 27 Feb 2003 03:49:04 -0700 References: <008d01c2ddbe$cd93dea0$02623092@iitpa6v64oitt1> In-Reply-To: <008d01c2ddbe$cd93dea0$02623092@iitpa6v64oitt1> To: Eleonora Borgia Cc: manet@ietf.org Date: Thu, 27 Feb 2003 03:49:04 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sender: ankurjain@softhome.net X-Originating-IP: [203.145.171.34] Message-ID: Content-Transfer-Encoding: 7bit Subject: [manet] Re: ieee 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Eleonora, For carrier sensing, you can use the wireless manager from your card vendor or use NetStumbler. Available from www.netstumbler.org. I have used NetStumbler with Windows only. For Unix/Linux, I think you can use Kismet (www.kismetwireless.net) or dstumbler. If you are using WinCE, then you will need ministumbler. Hope it helps. Regards, Ankur Eleonora Borgia writes: > Hi all, > > I recently did some experimental studies of the behavior of the IEEE 802.11b Protocol. I measured the IEEE 802.11b transmission ranges in a real environment, composed by 2/4 nodes communicating in ad hoc mode. > Does somebody know if there exists a free tool for carrier sensing and interference range measurement for the same technology? > > Regards, > Eleonora _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 08:40:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02022 for ; Thu, 27 Feb 2003 08:40:24 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RDoNr19941 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 08:50:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RDoNp19938 for ; Thu, 27 Feb 2003 08:50:23 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02009 for ; Thu, 27 Feb 2003 08:39:52 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RDZfp18162; Thu, 27 Feb 2003 08:35:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RDVgp17841 for ; Thu, 27 Feb 2003 08:31:42 -0500 Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00638 for ; Thu, 27 Feb 2003 08:21:09 -0500 (EST) Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Thu, 27 Feb 2003 08:25:45 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Thu, 27 Feb 2003 08:25:33 -0500 From: "Pete Sholander" To: , , , Subject: Re: [manet] MANET testing in realistic environment Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ns-2 is known to have inexact wireless models, as Phillipe notes below. Have folks had better results (e.g., better agreement between simulation, emulation and "open-air" experiments) with GloMoSim, OPNET, or QualNet? --Pete Sholander >>> Joe Macker 02/26/03 04:20PM >>> Berner you raise salient engineering points that are reasonably protocol agnostic. We have done significant realistic test outdoors and indoors (and with an emulation environment using 802.11) with working systems and have achieved significant imrpovements with some minor modifications.. We modified older INRIA OLSR code to add a link sensing hysteresis algorithm to improve robustness and it works reasonably well for us in many trials to date including highly congested ones (better link layer sensing info --lower layer triggers, etc-- would be a further plus for any neighbor management algorithm). We are dealing with naturally time-varying channels and highly unpredictable anomalies in many wireless scenarios not wired behavior and we should be cognizant of that fact. Also, related to your noticing routing message being lost, for Linux (RH dists) we quickly added ToS packet markings that improved the priority under network congestion for routing control packets (we tested! that this actually did improve things for the OS and queueing engine we were using). This code is available at http://pf.itd.nrl.navy.mil under the project INRIA OLSR with NRL mods. Packet jittering for distributed control events,etc may also be important this was also added and parameterized in the above experimental prototype code (very important in a simulation)..We also have newer code developments that should be released in the near future that we feel further improve the link sensing process,etc. -Joe At 08:33 PM 2/26/2003 +0100, Philippe Jacquet wrote: >We have run many realistic testing with IEEE 802.11 in the past. We >experienced several link instabilities due to frequent variation in link >quality from remote nodes. Similar effects were also reported in NRL. This >is the reason why advanced neighbor sensing has been introduced in OLSR. >This kind of effect were never detected in ns-2 simulations. > >Philippe >----- Original Message ----- >From: Berner Vegge >To: >Sent: Wednesday, February 26, 2003 11:25 AM >Subject: [manet] MANET testing in realistic environment > > >> Hello all! >> I have made some testing on AODV, OLSR and LUNAR in a realistic >> environment (i.e. not simulations). The tests are performed >> within an office building with ORINOCO GOLD WLAN cards. I have >> used WLAN IEEE802.11b as physical/link layer. The testing has >> very often revealed problems and constraints in the WLAN >> technology, such as interference when several nodes are close >> to each other so that the throughput drops dramatically. >> Changes in signal/noise relation leading do links that drop out >> etc has also been a problem. Finally we have seen that >> routing messages are lost very often at high load, so that >> the connections are taken down for that reason (this is probably >> due to lack of priority on routing packets, and as these are >> broadcasted with no ack and resending, they are very easily lost). >> I know that a lot of work is ongoing within IEEE to improve WLAN, >> so hopefully MANET over WLAN will be possible in a year or so. >> >> My question is if anyone else has performed realistic tests by >> running MANET over WLAN and if anyone has any experiences, >> documented results etc, that they would share with me. >> >> Thanks a lot! >> Best Regards Berner >> >> >> >> >> >> _________________________________________________________________ >> MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg >og >> dine venner >> >> _______________________________________________ >> 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 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 09:34:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05350 for ; Thu, 27 Feb 2003 09:34:29 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1REiUr24356 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 09:44:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1REiUp24353 for ; Thu, 27 Feb 2003 09:44:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05327 for ; Thu, 27 Feb 2003 09:33:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1REVZp22912; Thu, 27 Feb 2003 09:31:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RESmp22801 for ; Thu, 27 Feb 2003 09:28:48 -0500 Received: from mephisto.inf.tu-dresden.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04351 for ; Thu, 27 Feb 2003 09:18:16 -0500 (EST) Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id PAA03580 for ; Thu, 27 Feb 2003 15:22:11 +0100 (MET) Message-Id: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Feb 2003 15:23:31 +0100 To: manet@ietf.org From: gikaru Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1122205281==_.ALT" Subject: [manet] generating trace files .... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1122205281==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed hello MANET researchers, I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e. s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - 1.255 -It IMEP -Il 48 -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - -Pl 0x0000 ] i expected something like...... s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48 -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] where do i need to change so as to get the expected. I am running on ns-2.1b9 If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea.. Thanks in advance Gikaru TU-Dresden, Department of Computer Science --=====================_1122205281==_.ALT Content-Type: text/html; charset="us-ascii"
hello MANET researchers,
I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e.
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -    1.255 -It IMEP -Il 48  -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - -Pl 0x0000 ]
i expected something like......
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48
  -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ]
where do i need to change so as to get the expected.
I am running on ns-2.1b9
If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea..

Thanks in advance

 Gikaru
TU-Dresden, Department of Computer Science --=====================_1122205281==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 11:12:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09798 for ; Thu, 27 Feb 2003 11:12:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RGMeo31482 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 11:22:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGMep31479 for ; Thu, 27 Feb 2003 11:22:40 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09754 for ; Thu, 27 Feb 2003 11:12:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RG7Ep30375; Thu, 27 Feb 2003 11:07:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RG3Up29872 for ; Thu, 27 Feb 2003 11:03:30 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08967 for ; Thu, 27 Feb 2003 10:52:56 -0500 (EST) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1RFup6156700; Thu, 27 Feb 2003 10:56:51 -0500 (EST) Received: from tom ([198.70.228.54]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id AWH99067 (AUTH talin); Thu, 27 Feb 2003 10:56:46 -0500 (EST) Message-ID: <001101c2de78$79066820$643f640a@tom> From: "Tao Lin" To: "gikaru" , References: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> Subject: Re: [manet] generating trace files .... Date: Thu, 27 Feb 2003 10:54:08 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C2DE4E.8D9283C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C2DE4E.8D9283C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Did you register your own packet type in packet.cc? You can check whether all files that contain your own packet type match = those for AODV. In other words, you can grep all files that contain = AODV in ns directory (not in aodv directory). For the files that contain = the AODV packet type definition, add your own packet type there. Hope this helps, =20 Tao Lin Ph.D. Candidate ECE Dept. Virginia Tech. USA ----- Original Message -----=20 From: gikaru=20 To: manet@ietf.org=20 Sent: Thursday, February 27, 2003 9:23 AM Subject: [manet] generating trace files .... hello MANET researchers, I am trying to run a modified aodv protocol on ns2. My problem is that = the trace files generated are not baring the name of my protocol = "modif_aodv"....Instead it is having IMEP... i.e.=20 s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne = -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - = 1.255 -It IMEP -Il 48 -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - -Pl = 0x0000 ]=20 i expected something like...... s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne = -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 = -It MODIF_AODV -Il 48 -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ]=20 where do i need to change so as to get the expected.=20 I am running on ns-2.1b9 If someone can spot the mistake, please guide me through....i am not = very experienced in ns....:)...I sent this to the ns users and no-one = seems to have an idea.. Thanks in advance Gikaru TU-Dresden, Department of Computer Science ------=_NextPart_000_000E_01C2DE4E.8D9283C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Did you register your own packet type = in=20 packet.cc?
 
You can check whether all files that = contain your=20 own packet type match those for AODV.  In=20 other words, you can grep all files that contain AODV in ns directory = (not=20 in aodv directory). For the files that contain the AODV = packet=20 type definition, add your own packet type there.
 
Hope this helps,
 
 Tao Lin
 Ph.D. Candidate
 ECE Dept.
 Virginia Tech.
 USA
 
 
----- Original Message -----
From:=20 gikaru
Sent: Thursday, February 27, = 2003 9:23=20 AM
Subject: [manet] generating = trace files=20 ....


hello MANET researchers,
I am = trying to run=20 a modified aodv protocol on ns2. My problem is that the trace files = generated=20 are not baring the name of my protocol "modif_aodv"....Instead it is = having=20 IMEP... i.e.
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny = 58.84 -Nz=20 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is = 1.255 -Id=20 -    1.255 -It IMEP -Il 48  -If 0 -Ii 0 -Iv = 30 -P=20 imep -Pa - -Ph - -Po - -Pl 0x0000 ]
i expected something=20 like......
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 = -Nz=20 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is = 1.255 -Id=20 -1.255 -It MODIF_AODV -Il 48
  -If 0 -Ii 0 -Iv 30 -P = mofif_aodv -Pa -=20 -Ph - -Po - -Pl 0x0000 ]
where do i need to change so as to get = the=20 expected.
I am running on ns-2.1b9
If someone can spot the = mistake,=20 please guide me through....i am not very experienced in ns....:)...I = sent this=20 to the ns users and no-one seems to have an idea..

Thanks in=20 advance

 Gikaru
TU-Dresden, Department of Computer = Science=20 ------=_NextPart_000_000E_01C2DE4E.8D9283C0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 11:38:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10677 for ; Thu, 27 Feb 2003 11:38:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RGmDU01154 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 11:48:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGmDp01151 for ; Thu, 27 Feb 2003 11:48:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10673 for ; Thu, 27 Feb 2003 11:37:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGWSp31884; Thu, 27 Feb 2003 11:32:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGTCp31753 for ; Thu, 27 Feb 2003 11:29:12 -0500 Received: from core.inf.ethz.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10036 for ; Thu, 27 Feb 2003 11:18:37 -0500 (EST) Received: from lillian-ics.inf.ethz.ch (root@lillian-ics.inf.ethz.ch [129.132.134.2]) by core.inf.ethz.ch (8.9.3/8.9.3) with ESMTP id RAA26992; Thu, 27 Feb 2003 17:22:32 +0100 (MET) Received: from inf.ethz.ch (bandos.inf.ethz.ch [129.132.134.103]) by lillian-ics.inf.ethz.ch (8.9.3/8.9.3) with ESMTP id RAA20713; Thu, 27 Feb 2003 17:22:31 +0100 (MET) Message-ID: <3E5E3B47.6060302@inf.ethz.ch> Date: Thu, 27 Feb 2003 17:22:31 +0100 From: Val Naoumov Reply-To: naoumov@inf.ethz.ch Organization: ETH Zentrum User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en, de-CH, ru MIME-Version: 1.0 To: gikaru CC: manet@ietf.org Subject: Re: [manet] generating trace files .... References: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> In-Reply-To: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Gikaru, Check the following: 1) in /common/packet.h - add your packet type (MODIF_AODV) in enum packet_t; - add `name_[PT_MODIF_AODV]="modif_aodv"` in p_info::p_info() 2) in /tcl/lib/ns_packet.tcl - insert `MODIF_AODV` in the loop "foreach prot { ... }" 3) in /trace/cmu_trace.cc - insert `case MODIF_AODV: ...` in CMUTrace::format(Packet* p, const char *why) Best wishes, Val -- Valeri Naoumov e-mail: Computer Systems Institute naoumov@inf.ethz.ch Swiss Federal Institute of Technology Zurich web: Switzerland http://www.inf.ethz.ch/~naoumov gikaru wrote: > > hello MANET researchers, > I am trying to run a modified aodv protocol on ns2. My problem is that > the trace files generated are not baring the name of my protocol > "modif_aodv"....Instead it is having IMEP... i.e. > s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne > -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - > 1.255 -It _IMEP_ -Il 48 -If 0 -Ii 0 -Iv 30 -P _imep_ -Pa - -Ph - -Po - > -Pl 0x0000 ] > i expected something like...... > s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne > -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 > -It MODIF_AODV -Il 48 > -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] > where do i need to change so as to get the expected. > I am running on ns-2.1b9 > If someone can spot the mistake, please guide me through....i am not > very experienced in ns....:)...I sent this to the ns users and no-one > seems to have an idea.. > > Thanks in advance > > Gikaru > TU-Dresden, Department of Computer Science _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 12:01:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11584 for ; Thu, 27 Feb 2003 12:01:44 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RHBnq03788 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 12:11:49 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHBmp03785 for ; Thu, 27 Feb 2003 12:11:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11554 for ; Thu, 27 Feb 2003 12:01:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGvOp01603; Thu, 27 Feb 2003 11:57:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGsop01472 for ; Thu, 27 Feb 2003 11:54:50 -0500 Received: from mephisto.inf.tu-dresden.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10880 for ; Thu, 27 Feb 2003 11:44:14 -0500 (EST) Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id RAA04575; Thu, 27 Feb 2003 17:48:09 +0100 (MET) Message-Id: <5.1.0.14.0.20030227174350.00b61008@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Feb 2003 17:49:32 +0100 To: naoumov@inf.ethz.ch From: gikaru Subject: Re: [manet] generating trace files .... Cc: manet@ietf.org In-Reply-To: <3E5E3B47.6060302@inf.ethz.ch> References: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1130965000==_.ALT" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1130965000==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Thanks Valeri for the quick responce..... I have actually added the three you mentioned. The only slight difference is that i used "PT_MODIF_AODV" in enum packet_t and in CMUTrace::format().. Any more hints?... At 05:22 PM 2/27/2003 +0100, you wrote: >Hello Gikaru, > >Check the following: > >1) in /common/packet.h > - add your packet type (MODIF_AODV) in enum packet_t; > - add `name_[PT_MODIF_AODV]="modif_aodv"` in p_info::p_info() > >2) in /tcl/lib/ns_packet.tcl > - insert `MODIF_AODV` in the loop "foreach prot { ... }" > >3) in /trace/cmu_trace.cc > - insert `case MODIF_AODV: ...` in CMUTrace::format(Packet* p, > const char *why) > > >Best wishes, >Val >-- >Valeri Naoumov e-mail: >Computer Systems Institute naoumov@inf.ethz.ch >Swiss Federal Institute of Technology Zurich web: >Switzerland >http://www.inf.ethz.ch/~naoumov > > > > >gikaru wrote: >>hello MANET researchers, >>I am trying to run a modified aodv protocol on ns2. My problem is that >>the trace files generated are not baring the name of my protocol >>"modif_aodv"....Instead it is having IMEP... i.e. >>s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >>-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - >>1.255 -It _IMEP_ -Il 48 -If 0 -Ii 0 -Iv 30 -P _imep_ -Pa - -Ph - -Po - >>-Pl 0x0000 ] >>i expected something like...... >>s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >>-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 >>-It MODIF_AODV -Il 48 >> -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] >>where do i need to change so as to get the expected. >>I am running on ns-2.1b9 >>If someone can spot the mistake, please guide me through....i am not very >>experienced in ns....:)...I sent this to the ns users and no-one seems to >>have an idea.. >>Thanks in advance >> Gikaru >>TU-Dresden, Department of Computer Science > >Gikaru >TU-Dresden, Department of Computer Science --=====================_1130965000==_.ALT Content-Type: text/html; charset="us-ascii" Thanks Valeri for the quick responce.....

I have actually added the three you mentioned. The only slight difference is that i used "PT_MODIF_AODV" in enum packet_t and in CMUTrace::format()..
Any more hints?...

At 05:22 PM 2/27/2003 +0100, you wrote:
Hello Gikaru,

Check the following:

1) in <ns>/common/packet.h
        - add your packet type (MODIF_AODV) in enum packet_t;
        - add `name_[PT_MODIF_AODV]="modif_aodv"` in p_info::p_info()

2) in <ns>/tcl/lib/ns_packet.tcl
        - insert `MODIF_AODV` in the loop "foreach prot { ... }"

3) in <ns>/trace/cmu_trace.cc
        - insert `case MODIF_AODV: ...` in CMUTrace::format(Packet* p, const char *why)


Best wishes,
Val
--
Valeri Naoumov                                  e-mail:
Computer Systems Institute                      naoumov@inf.ethz.ch
Swiss Federal Institute of Technology Zurich    web:
Switzerland                                     http://www.inf.ethz.ch/~naoumov




gikaru wrote:
hello MANET researchers,
I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e.
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -   
1.255 -It _IMEP_ -Il 48  -If 0 -Ii 0 -Iv 30 -P _imep_ -Pa - -Ph - -Po - -Pl 0x0000 ]
i expected something like......
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48
  -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ]
where do i need to change so as to get the expected.
I am running on ns-2.1b9
If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea..
Thanks in advance
 Gikaru
TU-Dresden, Department of Computer Science

Gikaru
TU-Dresden, Department of Computer Science --=====================_1130965000==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 12:07:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11829 for ; Thu, 27 Feb 2003 12:07:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RHHFd04258 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 12:17:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHHFp04255 for ; Thu, 27 Feb 2003 12:17:15 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11823 for ; Thu, 27 Feb 2003 12:06:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RH1Ap01891; Thu, 27 Feb 2003 12:01:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGwsp01745 for ; Thu, 27 Feb 2003 11:58:54 -0500 Received: from mephisto.inf.tu-dresden.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11025 for ; Thu, 27 Feb 2003 11:48:19 -0500 (EST) Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id RAA04593; Thu, 27 Feb 2003 17:52:13 +0100 (MET) Message-Id: <5.1.0.14.0.20030227175205.022e5ae0@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Feb 2003 17:53:36 +0100 To: "Tao Lin" From: gikaru Subject: Re: [manet] generating trace files .... Cc: manet@ietf.org In-Reply-To: <001101c2de78$79066820$643f640a@tom> References: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1131208593==_.ALT" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1131208593==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Thanks for the advise Tao Lin, ... I'll try that...but not a very easy task.... I'll see how it goes.... At 10:54 AM 2/27/2003 -0500, you wrote: >Did you register your own packet type in packet.cc? > >You can check whether all files that contain your own packet type match >those for AODV. In other words, you can grep all files that contain AODV >in ns directory (not in aodv directory). For the files that contain the >AODV packet type definition, add your own packet type there. > >Hope this helps, > > Tao Lin > Ph.D. Candidate > ECE Dept. > Virginia Tech. > USA > > >----- Original Message ----- >From: gikaru >To: manet@ietf.org >Sent: Thursday, February 27, 2003 9:23 AM >Subject: [manet] generating trace files .... > > > >hello MANET researchers, >I am trying to run a modified aodv protocol on ns2. My problem is that the >trace files generated are not baring the name of my protocol >"modif_aodv"....Instead it is having IMEP... i.e. >s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id >- 1.255 -It IMEP -Il 48 -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - >-Pl 0x0000 ] >i expected something like...... >s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 >-It MODIF_AODV -Il 48 > -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] >where do i need to change so as to get the expected. >I am running on ns-2.1b9 >If someone can spot the mistake, please guide me through....i am not very >experienced in ns....:)...I sent this to the ns users and no-one seems to >have an idea.. > >Thanks in advance > > Gikaru >TU-Dresden, Department of Computer Science Wilfred Githuka Gikaru TU-Dresden, Department of Computer Science Hans-Grundig Strasse 25, 01062 - Dresden tel +49-351-463-38557 fax +49-351-463-38251 --=====================_1131208593==_.ALT Content-Type: text/html; charset="us-ascii" Thanks for the advise Tao Lin,
... I'll try that...but not a very easy task....
I'll see how it goes....

At 10:54 AM 2/27/2003 -0500, you wrote:

Did you register your own packet type in packet.cc?
 
You can check whether all files that contain your own packet type match those for AODV.  In other words, you can grep all files that contain AODV in ns directory (not in aodv directory). For the files that contain the AODV packet type definition, add your own packet type there.
 
Hope this helps,
 
 Tao Lin
 Ph.D. Candidate
 ECE Dept.
 Virginia Tech.
 USA
 
 
----- Original Message -----
From: gikaru
To: manet@ietf.org
Sent: Thursday, February 27, 2003 9:23 AM
Subject: [manet] generating trace files ....



hello MANET researchers,
I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e.
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -    1.255 -It IMEP -Il 48  -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - -Pl 0x0000 ]
i expected something like......
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48
  -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ]
where do i need to change so as to get the expected.
I am running on ns-2.1b9
If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea..

Thanks in advance

 Gikaru
TU-Dresden, Department of Computer Science

Wilfred Githuka Gikaru
TU-Dresden, Department of Computer Science
Hans-Grundig Strasse 25,
01062 - Dresden
tel +49-351-463-38557
fax +49-351-463-38251 --=====================_1131208593==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 12:17:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12385 for ; Thu, 27 Feb 2003 12:17:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RHRsF05113 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 12:27:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHRsp05110 for ; Thu, 27 Feb 2003 12:27:54 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12370 for ; Thu, 27 Feb 2003 12:17:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHA5p03614; Thu, 27 Feb 2003 12:10:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RH6Ep02648 for ; Thu, 27 Feb 2003 12:06:14 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11271 for ; Thu, 27 Feb 2003 11:55:38 -0500 (EST) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id h1RGxY614829; Thu, 27 Feb 2003 11:59:34 -0500 (EST) Received: from tom ([198.70.228.54]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id AWI14532 (AUTH talin); Thu, 27 Feb 2003 11:59:33 -0500 (EST) Message-ID: <003201c2de81$3c821260$643f640a@tom> From: "Tao Lin" To: "gikaru" Cc: "manet" References: <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> <5.1.0.14.0.20030227175205.022e5ae0@harmless.inf.tu-dresden.de> Subject: Re: [manet] generating trace files .... Date: Thu, 27 Feb 2003 11:56:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit If you use "grep -r -n PT_AODV *", you won't find a lot of lines. For example, in ns 2.1b7a, only 13 lines, including some document files. Check them one by one and make sure your packet is defined as AODV does. I think it is not that difficult. :) BTW: If you tried what Valeri suggested, you may need to check your definition of your routing agent. Tao Lin Ph.D. Candidate ECE Dept. Virginia Tech. USA ----- Original Message ----- From: gikaru To: Tao Lin Cc: manet@ietf.org Sent: Thursday, February 27, 2003 11:53 AM Subject: Re: [manet] generating trace files .... Thanks for the advise Tao Lin, ... I'll try that...but not a very easy task.... I'll see how it goes.... At 10:54 AM 2/27/2003 -0500, you wrote: Did you register your own packet type in packet.cc? You can check whether all files that contain your own packet type match those for AODV. In other words, you can grep all files that contain AODV in ns directory (not in aodv directory). For the files that contain the AODV packet type definition, add your own packet type there. Hope this helps, Tao Lin Ph.D. Candidate ECE Dept. Virginia Tech. USA ----- Original Message ----- From: gikaru To: manet@ietf.org Sent: Thursday, February 27, 2003 9:23 AM Subject: [manet] generating trace files .... hello MANET researchers, I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e. s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - 1.255 -It IMEP -Il 48 -If 0 -Ii 0 -Iv 30 -P imep -Pa - -Ph - -Po - -Pl 0x0000 ] i expected something like...... s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48 -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] where do i need to change so as to get the expected. I am running on ns-2.1b9 If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea.. Thanks in advance Gikaru TU-Dresden, Department of Computer Science Wilfred Githuka Gikaru TU-Dresden, Department of Computer Science Hans-Grundig Strasse 25, 01062 - Dresden tel +49-351-463-38557 fax +49-351-463-38251 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Feb 27 12:27:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12828 for ; Thu, 27 Feb 2003 12:27:20 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RHbPv06364 for manet-archive@odin.ietf.org; Thu, 27 Feb 2003 12:37:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHbPp06361 for ; Thu, 27 Feb 2003 12:37:25 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12771 for ; Thu, 27 Feb 2003 12:26:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHMLp04562; Thu, 27 Feb 2003 12:22:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RHJqp04388 for ; Thu, 27 Feb 2003 12:19:52 -0500 Received: from mephisto.inf.tu-dresden.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11888 for ; Thu, 27 Feb 2003 12:09:16 -0500 (EST) Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id SAA04689; Thu, 27 Feb 2003 18:13:11 +0100 (MET) Message-Id: <5.1.0.14.0.20030227181248.022e5ae0@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Feb 2003 18:14:34 +0100 To: naoumov@inf.ethz.ch From: gikaru Subject: Re: [manet] generating trace files .... Cc: manet@ietf.org In-Reply-To: <3E5E4458.1030003@inf.ethz.ch> References: <5.1.0.14.0.20030227174350.00b61008@harmless.inf.tu-dresden.de> <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> <5.1.0.14.0.20030227151906.00b61008@harmless.inf.tu-dresden.de> <5.1.0.14.0.20030227174350.00b61008@harmless.inf.tu-dresden.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1132466609==_.ALT" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1132466609==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed ja... i said : set val(adhocRouting) MODIF_AODV At 06:01 PM 2/27/2003 +0100, you wrote: >Did you say > set opt(adhocRouting) MODIF_AODV >in your tcl file? > >Val > > > >gikaru wrote: >>Thanks Valeri for the quick responce..... >>I have actually added the three you mentioned. The only slight difference >>is that i used "PT_MODIF_AODV" in enum packet_t and in CMUTrace::format().. >>Any more hints?... >>At 05:22 PM 2/27/2003 +0100, you wrote: >> >>>Hello Gikaru, >>> >>>Check the following: >>> >>>1) in /common/packet.h >>> - add your packet type (MODIF_AODV) in enum packet_t; >>> - add `name_[PT_MODIF_AODV]="modif_aodv"` in p_info::p_info() >>> >>>2) in /tcl/lib/ns_packet.tcl >>> - insert `MODIF_AODV` in the loop "foreach prot { ... }" >>> >>>3) in /trace/cmu_trace.cc >>> - insert `case MODIF_AODV: ...` in CMUTrace::format(Packet* p, >>> const char *why) >>> >>> >>>Best wishes, >>>Val >>>-- >>>Valeri Naoumov e-mail: >>>Computer Systems Institute naoumov@inf.ethz.ch >>>Swiss Federal Institute of Technology Zurich web: >>>Switzerland >>>http://www.inf.ethz.ch/~naoumov >>> >>> >>> >>> >>>gikaru wrote: >>> >>>>hello MANET researchers, >>>>I am trying to run a modified aodv protocol on ns2. My problem is that >>>>the trace files generated are not baring the name of my protocol >>>>"modif_aodv"....Instead it is having IMEP... i.e. >>>>s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >>>>-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id - >>>>1.255 -It _IMEP_ -Il 48 -If 0 -Ii 0 -Iv 30 -P _imep_ -Pa - -Ph - -Po - >>>>-Pl 0x0000 ] >>>>i expected something like...... >>>>s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne >>>>-1.000000 -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 >>>>-It MODIF_AODV -Il 48 >>>> -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ] >>>>where do i need to change so as to get the expected. >>>>I am running on ns-2.1b9 >>>>If someone can spot the mistake, please guide me through....i am not >>>>very experienced in ns....:)...I sent this to the ns users and no-one >>>>seems to have an idea.. >>>>Thanks in advance >>>> Gikaru >>>>TU-Dresden, Department of Computer Science >>> >>>Gikaru >>>TU-Dresden, Department of Computer Science >>> Gikaru >> >>TU-Dresden, Department of Computer Science --=====================_1132466609==_.ALT Content-Type: text/html; charset="us-ascii" ja... i said :
      set val(adhocRouting) MODIF_AODV

At 06:01 PM 2/27/2003 +0100, you wrote:

Did you say
        set opt(adhocRouting)   MODIF_AODV
in your tcl file?

Val



gikaru wrote:
Thanks Valeri for the quick responce.....
I have actually added the three you mentioned. The only slight difference is that i used "PT_MODIF_AODV" in enum packet_t and in CMUTrace::format()..
Any more hints?...
At 05:22 PM 2/27/2003 +0100, you wrote:

Hello Gikaru,

Check the following:

1) in <ns>/common/packet.h
        - add your packet type (MODIF_AODV) in enum packet_t;
        - add `name_[PT_MODIF_AODV]="modif_aodv"` in p_info::p_info()

2) in <ns>/tcl/lib/ns_packet.tcl
        - insert `MODIF_AODV` in the loop "foreach prot { ... }"

3) in <ns>/trace/cmu_trace.cc
        - insert `case MODIF_AODV: ...` in CMUTrace::format(Packet* p, const char *why)


Best wishes,
Val
--
Valeri Naoumov                                  e-mail:
Computer Systems Institute                      naoumov@inf.ethz.ch
Swiss Federal Institute of Technology Zurich    web:
Switzerland                                    
http://www.inf.ethz.ch/~naoumov




gikaru wrote:

hello MANET researchers,
I am trying to run a modified aodv protocol on ns2. My problem is that the trace files generated are not baring the name of my protocol "modif_aodv"....Instead it is having IMEP... i.e.
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -  
1.255 -It _IMEP_ -Il 48  -If 0 -Ii 0 -Iv 30 -P _imep_ -Pa - -Ph - -Po - -Pl 0x0000 ]
i expected something like......
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 179.72 -Ny 58.84 -Nz 0.00 -Ne -1.000000  -Nl RTR -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.255 -Id -1.255 -It MODIF_AODV -Il 48
  -If 0 -Ii 0 -Iv 30 -P mofif_aodv -Pa - -Ph - -Po - -Pl 0x0000 ]
where do i need to change so as to get the expected.
I am running on ns-2.1b9
If someone can spot the mistake, please guide me through....i am not very experienced in ns....:)...I sent this to the ns users and no-one seems to have an idea..
Thanks in advance
 Gikaru
TU-Dresden, Department of Computer Science

Gikaru
TU-Dresden, Department of Computer Science



 Gikaru

TU-Dresden, Department of Computer Science
 --=====================_1132466609==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 28 07:58:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25386 for ; Fri, 28 Feb 2003 07:58:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1SD9PZ26430 for manet-archive@odin.ietf.org; Fri, 28 Feb 2003 08:09:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SD9Pp26427 for ; Fri, 28 Feb 2003 08:09:25 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25342 for ; Fri, 28 Feb 2003 07:58:25 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SCqkp24192; Fri, 28 Feb 2003 07:52:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SCbZp23120 for ; Fri, 28 Feb 2003 07:37:35 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22967; Fri, 28 Feb 2003 07:26:36 -0500 (EST) Message-Id: <200302281226.HAA22967@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 28 Feb 2003 07:26:36 -0500 Subject: [manet] I-D ACTION:draft-ietf-manet-aodv-13.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --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 : Ad Hoc On Demand Distance Vector (AODV) Routing Author(s) : C. Perkins, E. Royer, S. Das Filename : draft-ietf-manet-aodv-13.txt Pages : 35 Date : 2003-2-27 The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as 'counting to infinity') associated with classical distance vector protocols. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-aodv-13.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-aodv-13.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-aodv-13.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: <2003-2-27135906.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-aodv-13.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-aodv-13.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-27135906.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Feb 28 10:03:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00901 for ; Fri, 28 Feb 2003 10:03:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1SFDZi02795 for manet-archive@odin.ietf.org; Fri, 28 Feb 2003 10:13:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFDYp02792 for ; Fri, 28 Feb 2003 10:13:34 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00867 for ; Fri, 28 Feb 2003 10:02:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SEpKp00889; Fri, 28 Feb 2003 09:51:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SEjNp00710 for ; Fri, 28 Feb 2003 09:45:23 -0500 Received: from mx.laposte.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29798 for ; Fri, 28 Feb 2003 09:34:20 -0500 (EST) Received: from laposte.net (127.0.0.1) by mx.laposte.net (6.0.053) id 3E493E520028745D for manet@ietf.org; Fri, 28 Feb 2003 15:38:18 +0100 Date: Fri, 28 Feb 2003 15:38:18 +0100 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 From: "=?iso-8859-1?Q?ghannay.sana@laposte.net?=" To: "=?iso-8859-1?Q?manet?=" X-XaM3-API-Version: 3.2 R29 (B54 pl1) X-type: 0 X-SenderIP: 193.95.33.25 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1SEjNp00711 Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet