From exim@www1.ietf.org Sat May 1 03:25:55 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01310 for ; Sat, 1 May 2004 03:25:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJoqS-0001SX-Lg for manet-archive@odin.ietf.org; Sat, 01 May 2004 03:23:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i417NWuU005607 for manet-archive@odin.ietf.org; Sat, 1 May 2004 03:23:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJooj-000109-8j for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 03:21:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01053 for ; Sat, 1 May 2004 03:21:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJohs-0004Mm-LM for manet-web-archive@ietf.org; Sat, 01 May 2004 03:14:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJogz-0004FY-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 03:13:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJogT-00048B-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 03:13:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJoXa-0006F6-He; Sat, 01 May 2004 03:04:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJoSN-0005YX-IG for manet@optimus.ietf.org; Sat, 01 May 2004 02:58:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13551 for ; Sat, 1 May 2004 02:58:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJoSJ-0002JW-G1 for manet@ietf.org; Sat, 01 May 2004 02:58:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJoRM-0002CR-00 for manet@ietf.org; Sat, 01 May 2004 02:57:37 -0400 Received: from web8301.mail.in.yahoo.com ([203.199.122.31]) by ietf-mx with smtp (Exim 4.12) id 1BJoQT-0001z4-00 for manet@ietf.org; Sat, 01 May 2004 02:56:42 -0400 Message-ID: <20040501065611.92394.qmail@web8301.mail.in.yahoo.com> Received: from [210.212.113.4] by web8301.mail.in.yahoo.com via HTTP; Sat, 01 May 2004 07:56:11 BST Date: Sat, 1 May 2004 07:56:11 +0100 (BST) From: =?iso-8859-1?q?jyoti=20grover?= To: Subramanian Parameswaran Cc: manet@ietf.org In-Reply-To: <1083041946.408de89a6e673@webmail.msstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] Re: [ns] how to compare 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.5 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi i just want to know how to compare the parameters(speed vs throughput) & (offered traffic / throughput) of dsr & aodv protocols with tracegraph tool becoz it does not have this option of these parameters there. is there any other method? since u have used it.plz tell me. waiting for ur reply soon. i will be greatful to u. with regards jyoti --- Subramanian Parameswaran wrote: > hey jyoti, > don't get tense! i typed the link i sent u and i > got the same message. Go > ahead to google and type Tracegraph. The first > result that comes up will be of > the software. the link will be to the webpage of a > Professor from Poland, > Wroclaw Univ. There is a set of details to be filled > out and when u submit the > details it will take u to the page where the file > can be downloaded. In the > professor's webpage, u will find his email id. if u > need any help u can ask him > directly or u can mail me back. He is very prompt in > replying. So u can also > get it cleared from the best. Once u get the > software, if u play around with it > a little, u will figure out most of it and > thereafter it is just a 10 minute > job. > Hope this helps. Which univ r u from?? > Subbu > > Quoting jyoti grover : > > > hi > > the link u have sent to me is opening but the > trace > > graph is not downloaded from here.the error > message is > > like this > > > > page might have been removed or had its name > changed. > > > >e that i sent you the link to is > > > designed to read trace files of > > > size upto 100MB. All you have to do is feed the > > > trace file to it. There are > > > several comparison options based on throughput, > > > packet loss etc, which is > > > output in the form of bargraph/piechart/line > graph. > > > It is specially meant for ns2. I faced the same > > > problem too while simulating > > > adhoc networks on ns2. i could make all > comparisons > > > using tracegraph. > > > hope this helps, > > > Subbu > > > > > > > > > Quoting jyoti grover > : > > > > > > > > > > > hi > > > > i just want to know how to read that much > large > > > > trace files of these protocols,& observe some > of > > > the > > > > parameters values.& then compare with other > > > protocol > > > > observed parameters. or some other way is > there. i > > > am > > > > working on ns2 simulator. > > > > plz help me. > > > > > > > > thanking you. > > > > > > > > with regards. > > > > jyoti > > > > > > > > > > > > > > > > --- Subramanian Parameswaran > > > > > > > wrote: > Hey Jyothi, > > > > > this is Subbu. > > > > > i am sending u a link where u can download a > > > files > > > > > that reads trace files. if > > > > > u need any assitantce on how to use the > software > > > let > > > > > me know. > > > > > it's almost self-explanatory, there are > certain > > > > > parameters that are to be set > > > > > on a standard basis > > > > > mail me at sp192@msstate.edu > > > > > it's been a while since i checked this email > and > > > > > don't check it regularly. > > > > > > > > > > http://www.geocities.com/tracegraph/ > > > > > > > > > > hope this helps, > > > > > subbu > > > > > > > > > > Quoting jyoti grover > > > : > > > > > > > > > > > > > > > > > hi all > > > > > > i am comparing different manet > routing > > > > > > protocols like dsdv,aodv,dsr etc now the > trace > > > > > files > > > > > > of these protocols are very large.how to > > > compare > > > > > these > > > > > > trace files? by simply looking these much > > > large > > > > > files > > > > > > & line by line comparing them or some > other > > > way is > > > > > > there.plz help me soon. > > > > > > > > > > > > thanking you. > > > > > > > > > > > > with regards > > > > > > jyoti > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ________________________________________________________________________ > > > > > > Yahoo! India Matrimony: Find your partner > > > online. > > > > > > http://yahoo.shaadi.com/india-matrimony/ > > > > > > > > > > > > > > > > > > > > > > > > > > > *********************************************** > > > > > Subramanian (Subbu) Parameswaran > > > > > Graduate Student > > > > > Dept. of Electrical and Computer Engineering > > > > > Mississippi State University > > > > > > *********************************************** > > > > > > > > > > > > > > ________________________________________________________________________ > > > > Yahoo! India Matrimony: Find your partner > online. > > > > http://yahoo.shaadi.com/india-matrimony/ > > > > > > > > > > > > > > > > > > > **************************************************************************** > > > Sow a thought and you reap an action, sow an > action > > > and you reap a practice > > > Sow a practice and you reap a character, sow a > > > character and you reap a life. > > > Cheers !! > > > > > > ***************************************************** > > > * Subramanian (Subbu) Parameswaran > > > > * > > > * Graduate Student > > === message truncated === ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 1 05:27:08 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05435 for ; Sat, 1 May 2004 05:27:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJqgO-0003yP-VQ for manet-archive@odin.ietf.org; Sat, 01 May 2004 05:21:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i419LGCw015274 for manet-archive@odin.ietf.org; Sat, 1 May 2004 05:21:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJqf0-0003eN-6X for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 05:19:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03533 for ; Sat, 1 May 2004 04:28:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJpr3-00068e-A5 for manet-web-archive@ietf.org; Sat, 01 May 2004 04:28:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJpq5-0005uq-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 04:27:14 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BJppP-0005jt-03 for manet-web-archive@ietf.org; Sat, 01 May 2004 04:26:31 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BJpgh-0001vr-Kt for manet-web-archive@ietf.org; Sat, 01 May 2004 04:17:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJpbO-0001P4-F8; Sat, 01 May 2004 04:12:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJpZ6-0000yq-J6 for manet@optimus.ietf.org; Sat, 01 May 2004 04:09:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03047 for ; Sat, 1 May 2004 04:09:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJpZ3-0003lP-Qw for manet@ietf.org; Sat, 01 May 2004 04:09:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJpY7-0003eG-00 for manet@ietf.org; Sat, 01 May 2004 04:08:40 -0400 Received: from web8304.mail.in.yahoo.com ([203.199.122.34]) by ietf-mx with smtp (Exim 4.12) id 1BJpXe-0003XB-00 for manet@ietf.org; Sat, 01 May 2004 04:08:10 -0400 Message-ID: <20040501080740.16262.qmail@web8304.mail.in.yahoo.com> Received: from [210.212.113.4] by web8304.mail.in.yahoo.com via HTTP; Sat, 01 May 2004 09:07:40 BST Date: Sat, 1 May 2004 09:07:40 +0100 (BST) From: =?iso-8859-1?q?jyoti=20grover?= To: manet@ietf.org Cc: ns-users@isi.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] how to draw graphs from ns 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hello i am new to ns. & i want to know how to draw the relationship between different parameters from these output trace files? which tools are available for these drawing?plz tell me thanks in advance. with regards jyoti ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 1 07:04:04 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08658 for ; Sat, 1 May 2004 07:04:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJsGd-00042O-KA for manet-archive@odin.ietf.org; Sat, 01 May 2004 07:02:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i41B2lIF015511 for manet-archive@odin.ietf.org; Sat, 1 May 2004 07:02:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJsEi-0003q2-JM for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 07:00:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08580 for ; Sat, 1 May 2004 07:00:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJsEe-0003cZ-By for manet-web-archive@ietf.org; Sat, 01 May 2004 07:00:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJsDi-0003TR-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 06:59:47 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJsCv-0003LL-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 06:58:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJs97-0002c8-Sp; Sat, 01 May 2004 06:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJs56-00025F-Sj for manet@optimus.ietf.org; Sat, 01 May 2004 06:50:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08299 for ; Sat, 1 May 2004 06:50:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJs52-0002Av-Nq for manet@ietf.org; Sat, 01 May 2004 06:50:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJs42-00022y-00 for manet@ietf.org; Sat, 01 May 2004 06:49:46 -0400 Received: from [202.179.157.194] (helo=localhost.localdomain) by ietf-mx with esmtp (Exim 4.12) id 1BJs3b-0001vC-00 for manet@ietf.org; Sat, 01 May 2004 06:49:20 -0400 Received: from highway.nu.edu.pk (highway.nu.edu.pk [111.222.111.115]) by localhost.localdomain (8.12.8/8.12.5) with ESMTP id i419noU6012562 for ; Sat, 1 May 2004 15:50:07 +0600 Received: by highway with Internet Mail Service (5.5.2656.59) id ; Sat, 1 May 2004 15:50:42 +0500 Message-ID: From: 1339 <1339@nu.edu.pk> To: "'manet@ietf.org'" Date: Sat, 1 May 2004 15:50:42 +0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] Consideration of a wired link in an 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=3.6 required=5.0 tests=AWL,FROM_ALL_NUMS, FROM_ENDS_IN_NUMS,FROM_STARTS_WITH_NUMS autolearn=no version=2.60 Hi, I was just wondering if there is any routing protocol for ad-hoc that considers a link having wired network network in between. For example I have two nodes connected to each other via ethernet link. both of them also have wirless cards. They may communicate with each other using ad-hoc network as well as the wired link. If they are intermediate nodes of two other nodes (of ad-hoc), priority of routing should be given through wired link, not the ad-hoc link. Any routing protocol/scheme that does it? Regards, Shakeel Farooq Undergrad Student, National University of Computer & Emerging Sciences Lahore, Pakistan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 1 13:15:42 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03815 for ; Sat, 1 May 2004 13:15:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJy1G-000834-K5 for manet-archive@odin.ietf.org; Sat, 01 May 2004 13:11:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i41HBIR0030938 for manet-archive@odin.ietf.org; Sat, 1 May 2004 13:11:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJxme-000891-Qt for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 12:56:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01796 for ; Sat, 1 May 2004 12:56:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJxmd-0003de-4g for manet-web-archive@ietf.org; Sat, 01 May 2004 12:56:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJxl4-0002dh-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 12:54:35 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BJxjV-0000yT-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 12:52:57 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BJxjW-0004Uo-Gp for manet-web-archive@ietf.org; Sat, 01 May 2004 12:52:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJxDk-0005s1-6x; Sat, 01 May 2004 12:20:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJujz-00073l-5w for manet@optimus.ietf.org; Sat, 01 May 2004 09:41:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14324 for ; Sat, 1 May 2004 09:41:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJujx-00050n-7x for manet@ietf.org; Sat, 01 May 2004 09:41:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJujA-0004p1-00 for manet@ietf.org; Sat, 01 May 2004 09:40:24 -0400 Received: from sunlight.wichita.edu ([156.26.1.5]) by ietf-mx with esmtp (Exim 4.12) id 1BJuiT-0004Zu-00 for manet@ietf.org; Sat, 01 May 2004 09:39:41 -0400 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.2-X17 #30772) id <0HX100401F9ARD@sunlight.wichita.edu> for manet@ietf.org; Sat, 01 May 2004 08:39:10 -0500 (CDT) Received: from webmail.wichita.edu (BIERSTADT.WICHITA.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.2-X17 #30772) with ESMTP id <0HX1003O1F9AWZ@sunlight.wichita.edu> for manet@ietf.org; Sat, 01 May 2004 08:39:10 -0500 (CDT) Date: Sat, 01 May 2004 08:39:10 -0500 From: fxbaloch To: manet@ietf.org Message-id: <4093102B@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: fxbaloch@wichita.edu X-EXP32-SerialNo: 00003023, 00003770 Content-Transfer-Encoding: 7bit Subject: [manet] ns2-graphs 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello everyone, I have been working on a few simulations in ns2 and want to plot graphs of all the trace files that I have got. I know ns2 has xgraph utility but i dunno how to use it until we are using LossMonitor as a sink for traffics. I found this graphing utility on web "tracegraph". It is working ok but the problem is I want to get the graphs with respect to pause times and it doesnt have that option. Also I think there is a AD-HOCKEY Monarch extension of ns2 for graphing( i think that what it is for???) but I cant seem to make it work on ns2.27. Can anyone tell me how can I get the graphs. e.g. I want packet lost w.r.t pause times?? how will I get that...Any help will be great!!!! Thanks Fariha Baloch _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 1 13:37:42 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04786 for ; Sat, 1 May 2004 13:37:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJy1n-0000RH-NB for manet-archive@odin.ietf.org; Sat, 01 May 2004 13:11:51 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i41HBprX001683 for manet-archive@odin.ietf.org; Sat, 1 May 2004 13:11:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJxyW-0004vG-Cv for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 13:08:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02982 for ; Sat, 1 May 2004 13:08:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJxyU-0001wb-J9 for manet-web-archive@ietf.org; Sat, 01 May 2004 13:08:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJxwh-0000jL-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 13:06:35 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJxuO-00072u-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 13:04:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJxSA-0004E3-Ba; Sat, 01 May 2004 12:35:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJvkk-00005w-Qr for manet@optimus.ietf.org; Sat, 01 May 2004 10:46:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22157 for ; Sat, 1 May 2004 10:46:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJvki-0003Eh-De for manet@ietf.org; Sat, 01 May 2004 10:46:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJvju-00033J-00 for manet@ietf.org; Sat, 01 May 2004 10:45:15 -0400 Received: from stamps.cs.ucsb.edu ([128.111.41.14]) by ietf-mx with esmtp (Exim 4.12) id 1BJvjA-0002rp-00 for manet@ietf.org; Sat, 01 May 2004 10:44:28 -0400 Received: from [127.0.0.1] (csil.cs.ucsb.edu [128.111.41.12]) by stamps.cs.ucsb.edu (8.12.8/8.12.8) with ESMTP id i41EiNsD010726; Sat, 1 May 2004 07:44:23 -0700 (PDT) Subject: Re: [manet] Consideration of a wired link in an ad-hoc network From: Ian Chakeres To: 1339 <1339@nu.edu.pk> Cc: "'manet@ietf.org'" In-Reply-To: References: Content-Type: text/plain Message-Id: <1083422662.6462.243.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 01 May 2004 07:44:23 -0700 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit AODV is built to handle multiple interfaces. Since nodes only process the first RREQ they receive for particular SRC, RREQ_ID pair, if a node receives a RREQ via wired and wireless link. Since the wired link is faster, the node will likely use the wired link instead the wireless link. We have proposed an additional mechanism to further bias selected routing paths to use preferred (wired) links. Additional details can be found in our paper "Transparent Influence of Path Selection in Heterogeneous Ad hoc Networks", available at http;//moment.cs.ucsb.edu/publications. Ian Chakeres On Sat, 2004-05-01 at 03:50, 1339 wrote: > Hi, > > I was just wondering if there is any routing protocol for ad-hoc that > considers a link having wired network network in between. > > For example I have two nodes connected to each other via ethernet link. both > of them also have wirless cards. They may communicate with each other using > ad-hoc network as well as the wired link. If they are intermediate nodes of > two other nodes (of ad-hoc), priority of routing should be given through > wired link, not the ad-hoc link. Any routing protocol/scheme that does it? > > Regards, > Shakeel Farooq > Undergrad Student, > National University of Computer & Emerging Sciences > Lahore, Pakistan > > _______________________________________________ > 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 exim@www1.ietf.org Sat May 1 13:40:16 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05197 for ; Sat, 1 May 2004 13:40:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJyRC-0001FV-Au for manet-archive@odin.ietf.org; Sat, 01 May 2004 13:38:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i41Hc6GS004797 for manet-archive@odin.ietf.org; Sat, 1 May 2004 13:38:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJy2R-0000q2-3X for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 13:12:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03519 for ; Sat, 1 May 2004 13:12:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJy2P-0005a4-8o for manet-web-archive@ietf.org; Sat, 01 May 2004 13:12:29 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJy02-0003SO-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 13:10:03 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJxyR-0001us-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 13:08:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJxXx-0007Mr-Vy; Sat, 01 May 2004 12:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJw9n-00009U-60 for manet@optimus.ietf.org; Sat, 01 May 2004 11:11:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24296 for ; Sat, 1 May 2004 11:11:57 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJw9m-0000le-8U for manet@ietf.org; Sat, 01 May 2004 11:11:58 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJw8n-0000Xp-00 for manet@ietf.org; Sat, 01 May 2004 11:10:58 -0400 Received: from simon.cs.cornell.edu ([128.84.154.10]) by ietf-mx with esmtp (Exim 4.12) id 1BJw7q-0000K6-00 for manet@ietf.org; Sat, 01 May 2004 11:09:58 -0400 Received: from sundial.cs.cornell.edu (sundial.cs.cornell.edu [128.84.96.115]) by simon.cs.cornell.edu (8.11.7-20031020/8.11.7/R-3.14) with ESMTP id i41F9ux09238; Sat, 1 May 2004 11:09:56 -0400 (EDT) Received: from ringding.cs.cornell.edu (ringding.cs.cornell.edu [128.84.96.109]) by sundial.cs.cornell.edu (8.11.7-20031020/8.11.7/M-3.18) with ESMTP id i41F9tn28728; Sat, 1 May 2004 11:09:55 -0400 (EDT) Received: (from egs@localhost) by ringding.cs.cornell.edu (8.11.7-20031020/8.11.7/C-3.4) id i41F9tn26098; Sat, 1 May 2004 11:09:55 -0400 (EDT) Message-Id: <200405011509.i41F9tn26098@ringding.cs.cornell.edu> Subject: Re: [manet] Ns-2 or Glomosim To: clik4ravi@yahoo.com (Ravi kumar), manet@ietf.org Date: Sat, 1 May 2004 11:09:55 -0400 (EDT) From: "Emin Gun Sirer" In-Reply-To: from "Ravi kumar" at Apr 30, 2004 12:23:08 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Ravi, Three critical properties for network simulators are accuracy, speed, and scale. ns2 and glomosim are pretty much equivalent on all three axis. On accuracy, the core simulators, the protocol implementations, and the physical propagation and energy consumption models have been vetted by the community. On speed & scale, the two simulators are equally bad. In scenarios commonly used for evaluating ad hoc routing protocols (e.g. [1]), ns2 and glomosim perform and scale with O(N^2), where N is number of nodes, with constant factors in the same ballpark. In short, you will likely end up wasting a lot of time waiting for ns2 or glomosim to finish. The choice between ns2 and glomosim thus comes down to convenience of their respective programming environments. I would like to point out SNS, an alternative simulator whose accuracy is identical to ns2, but whose performance and scalability are significantly better. SNS is freely available for downloads here: http://www.cs.cornell.edu/people/egs/sns/ SNS is based on the same code base as ns2 - it shares the same protocol implementations, the same physical propagation model and the same energy consumption parameters. We have extensively checked its correctness against ns2 (Note that simulations typically have some amount of non-determinism, e.g. when packets are sent at precisely the same time, simulators may pick a different global order. These effects may cascade and lead to slight differences. When we force SNS and ns2 to follow the same global order, they compute bit-for-bit identical results). The main contribution in SNS is a restructuring of the internal events of the simulation engine to cache and reuse computations. SNS eliminates redundant, expensive computations both within and across simulation runs through function caching and reuse. This enables SNS to achieve performance and scale proportional to O(N) for common ad hoc networking scenarios. SNS runs accurate 10000-node simulations in under an hour. The SNS programming environment is identical to ns2 - protocol implementations written for SNS should work in ns2 without any modifications, and vice versa. Choosing a simulator is quite a difficult topic, open to religious arguments of the kind one occasionally encounters in the comparison of programming languages. I hope this message pointed out three objective, scientific metrics for choosing a suitable simulator, and suggested an alternative that improves two out of the three with no loss of accuracy. Gun. -- [1] Josh Broch, David A. Maltz, David B. Johnson, Yih-Chun Hu, and Jorjeta Jetcheva. A Performance Comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols. In Proceedings of the Fourth Annual ACM/IEEE International Conference on Mobile Computing and Networking, ACM, Dallas, TX, October 1998. [2] Kevin Walsh, Emin Gun Sirer. Staged Simulation: A General Technique for Improving Simulation Scale and Performance. To appear in ACM Transactions on Modeling and Computer Simulation (TOMACS), April 2004. [3] Kevin Walsh, Emin Gun Sirer. Staged Simulation for Improving the Scale and Performance of Wireless Network Simulations. In Procedings of the Winter Simulation Conference, New Orleans, LA, December 2003. Ravi kumar writes: > >Hi all, > > I am working on wireless security and i have >to implement an algorithm on wireless networks, ad-hoc >in particular. > > I have seen some discussion in this group on >both Ns-2 and Glomosim.I'd like to find out which one >is better in regard to functionality and ease of use. >i know that ns-2 is a generally accepted standard for >simulation in the academic community. i dont know >much about glomosim, anyway if i need a opinion i >guess this is the place to ask. > > waiting for your views. thanks in advance > >ravi > > > > >__________________________________ >Do you Yahoo!? >Win a $20,000 Career Makeover at Yahoo! HotJobs >http://hotjobs.sweepstakes.yahoo.com/careermakeover > >_______________________________________________ >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 exim@www1.ietf.org Sat May 1 20:19:28 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02485 for ; Sat, 1 May 2004 20:19:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BK4eW-00088A-0m for manet-archive@odin.ietf.org; Sat, 01 May 2004 20:16:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i420GFYk031243 for manet-archive@odin.ietf.org; Sat, 1 May 2004 20:16:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BK4Zl-0005QO-Nm for manet-web-archive@optimus.ietf.org; Sat, 01 May 2004 20:11:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02122 for ; Sat, 1 May 2004 20:11:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BK4Zj-00044e-PQ for manet-web-archive@ietf.org; Sat, 01 May 2004 20:11:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BK4Ys-0003s5-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 20:10:27 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BK4Xx-0003gB-00 for manet-web-archive@ietf.org; Sat, 01 May 2004 20:09:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BK4Np-0001dG-W1; Sat, 01 May 2004 19:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BK4HX-000779-Hk for manet@optimus.ietf.org; Sat, 01 May 2004 19:52:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01273 for ; Sat, 1 May 2004 19:52:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BK4HV-00008C-Me for manet@ietf.org; Sat, 01 May 2004 19:52:29 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BK4GV-0007io-00 for manet@ietf.org; Sat, 01 May 2004 19:51:27 -0400 Received: from smtp-mclean-x.mitre.org ([192.80.55.71] helo=smtp-mclean.mitre.org) by ietf-mx with esmtp (Exim 4.12) id 1BK4Fu-0007Wb-00 for manet@ietf.org; Sat, 01 May 2004 19:50:50 -0400 Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i41Nok124020 for ; Sat, 1 May 2004 19:50:46 -0400 Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i41Nojh24013; Sat, 1 May 2004 19:50:46 -0400 Received: from wmodempoo1-47.mitre.org (128.29.251.47) by mailhub2.mitre.org with SMTP id 2601810; Sat, 01 May 2004 19:50:42 -0400 From: "John A. Stine" To: "'1339'" <1339@nu.edu.pk>, Subject: RE: [manet] Consideration of a wired link in an ad-hoc network Date: Sat, 1 May 2004 19:50:40 -0400 Organization: The MITRE Corporation Message-ID: <000601c42fd7$1c4059f0$2ffb1d80@MITRE.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-reply-to: Importance: Normal Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable See http://www.mitre.org/work/tech_transfer/mobilemesh/ and the border discovery protocol. John -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of = 1339 Sent: Saturday, May 01, 2004 6:51 AM To: 'manet@ietf.org' Subject: [manet] Consideration of a wired link in an ad-hoc network Hi, I was just wondering if there is any routing protocol for ad-hoc that considers a link having wired network network in between. For example I have two nodes connected to each other via ethernet link. = both of them also have wirless cards. They may communicate with each other = using ad-hoc network as well as the wired link. If they are intermediate nodes = of two other nodes (of ad-hoc), priority of routing should be given through wired link, not the ad-hoc link. Any routing protocol/scheme that does = it? Regards, Shakeel Farooq Undergrad Student, National University of Computer & Emerging Sciences Lahore, Pakistan _______________________________________________ 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 exim@www1.ietf.org Sun May 2 08:41:44 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12632 for ; Sun, 2 May 2004 08:41:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKGEO-00008p-9D for manet-archive@odin.ietf.org; Sun, 02 May 2004 08:38:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i42Cc4jf000538 for manet-archive@odin.ietf.org; Sun, 2 May 2004 08:38:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKGBH-00072V-VY for manet-web-archive@optimus.ietf.org; Sun, 02 May 2004 08:34:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12509 for ; Sun, 2 May 2004 08:34:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKGBG-0005Y2-Qa for manet-web-archive@ietf.org; Sun, 02 May 2004 08:34:50 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKGAJ-0005Jf-00 for manet-web-archive@ietf.org; Sun, 02 May 2004 08:33:52 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKG9x-00055t-00 for manet-web-archive@ietf.org; Sun, 02 May 2004 08:33:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKFyt-00038X-08; Sun, 02 May 2004 08:22:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKFv7-00021k-79 for manet@optimus.ietf.org; Sun, 02 May 2004 08:18:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12024 for ; Sun, 2 May 2004 08:18:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKFv6-0001Vp-29 for manet@ietf.org; Sun, 02 May 2004 08:18:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKFu5-0001FT-00 for manet@ietf.org; Sun, 02 May 2004 08:17:06 -0400 Received: from sunlight.wichita.edu ([156.26.1.5]) by ietf-mx with esmtp (Exim 4.12) id 1BKFtG-0000oe-00 for manet@ietf.org; Sun, 02 May 2004 08:16:14 -0400 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.2-X17 #30772) id <0HX300I0161WD4@sunlight.wichita.edu> for manet@ietf.org; Sun, 02 May 2004 07:15:32 -0500 (CDT) Received: from webmail.wichita.edu (BIERSTADT.WICHITA.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.2-X17 #30772) with ESMTP id <0HX300I9K61V18@sunlight.wichita.edu> for manet@ietf.org; Sun, 02 May 2004 07:15:31 -0500 (CDT) Date: Sun, 02 May 2004 07:15:31 -0500 From: fxbaloch To: manet@ietf.org Message-id: <409371E4@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: fxbaloch@wichita.edu X-EXP32-SerialNo: 00003023, 00003770 Content-Transfer-Encoding: 7bit Subject: [manet] making ns 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello everyone, For the project I am doing in ns2 I had to do some changes in aodv.cc file. It is not a very big change, just a few if else statements. My question is... to the best of my knowledge after making chnages to file we have do "make depend" and then "make" in ns directory. I did that. The problem is that I cant seem to find changes I expect in tracefiles afterwards. Infact they are exactly the same.. i mean trace file with old aodv file and with new aodv file. It seems as if no matter what, tcl file uses old aodv code regardless. What can be the problem and how to solve it? Please help ASAP... Thanks Fariha Baloch Fariha Baloch GRA Electrical and Computer Dept., Wichita State University. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun May 2 15:29:51 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29649 for ; Sun, 2 May 2004 15:29:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKMZb-0005wI-3A for manet-archive@odin.ietf.org; Sun, 02 May 2004 15:24:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i42JON32022824 for manet-archive@odin.ietf.org; Sun, 2 May 2004 15:24:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKMTz-0002ro-Cd for manet-web-archive@optimus.ietf.org; Sun, 02 May 2004 15:18:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25277 for ; Sun, 2 May 2004 14:32:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKLl3-00074q-8e for manet-web-archive@ietf.org; Sun, 02 May 2004 14:32:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKLkB-0006pw-00 for manet-web-archive@ietf.org; Sun, 02 May 2004 14:31:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKLjb-0006ah-00 for manet-web-archive@ietf.org; Sun, 02 May 2004 14:30:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKLbG-0000BP-Np; Sun, 02 May 2004 14:22:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKLQm-00060q-Jl for manet@optimus.ietf.org; Sun, 02 May 2004 14:11:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24520 for ; Sun, 2 May 2004 14:11:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKLQk-0001wo-4i for manet@ietf.org; Sun, 02 May 2004 14:11:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKLPn-0001hq-00 for manet@ietf.org; Sun, 02 May 2004 14:10:12 -0400 Received: from web61110.mail.yahoo.com ([216.155.196.112]) by ietf-mx with smtp (Exim 4.12) id 1BKLPF-0001QZ-00 for manet@ietf.org; Sun, 02 May 2004 14:09:37 -0400 Message-ID: <20040502180908.67018.qmail@web61110.mail.yahoo.com> Received: from [141.156.71.10] by web61110.mail.yahoo.com via HTTP; Sun, 02 May 2004 11:09:08 PDT Date: Sun, 2 May 2004 11:09:08 -0700 (PDT) From: manet user To: manet@ietf.org Cc: olsr@inria.fr MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1583197423-1083521348=:66045" Subject: [manet] olsr MPR re-calculation 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 --0-1583197423-1083521348=:66045 Content-Type: text/plain; charset=us-ascii Hi, According to RFC 3626 section 8.5, MPR set is re-calculated when neighbor loss or appearance is detected, or when a change in 2-hop neighborhood is detected. 2-hop neighborhood change is detected when a 2-hop nbr tuple expires or is deleted according to sec 8.2. According to these rules, addition of a 2-hop nbr tuple will not trigger MPR re-calculation. This does not seem to be correct. Please comment if my understanding is incorrect. In a MANET simulation, if two hop nbrs appear later in time, it would be changing the reachability of neighbor nodes, and MPR set should be re-calculated according to current reachability status. Your comments will be of great help. Thanks in advance. -MU --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs --0-1583197423-1083521348=:66045 Content-Type: text/html; charset=us-ascii
Hi,
 
According to RFC 3626 section 8.5, MPR set is re-calculated when neighbor loss or appearance is detected, or when a change in 2-hop neighborhood is detected. 2-hop neighborhood change is detected when a 2-hop nbr tuple expires or is deleted according to sec 8.2.
 
According to these rules, addition of a 2-hop nbr tuple will not trigger MPR re-calculation. This does not seem to be correct. Please comment if my understanding is incorrect.
 
In a MANET simulation, if two hop nbrs appear later in time, it would be changing the reachability of neighbor nodes, and MPR set should be re-calculated according to current reachability status.
 
Your comments will be of great help. Thanks in advance.
-MU

Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs --0-1583197423-1083521348=:66045-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 12:42:22 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12075 for ; Mon, 3 May 2004 12:42:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKgHi-0005Hj-Av for manet-archive@odin.ietf.org; Mon, 03 May 2004 12:27:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43GREm3020310 for manet-archive@odin.ietf.org; Mon, 3 May 2004 12:27:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKgDf-0004Ox-KS for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 12:23:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10944 for ; Mon, 3 May 2004 12:23:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKgDe-0004g9-7c for manet-web-archive@ietf.org; Mon, 03 May 2004 12:23:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKgCj-0004aM-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 12:22:06 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKgCB-0004UC-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 12:21:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKfyA-00078L-Io; Mon, 03 May 2004 12:07:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKfmL-0004If-Do for manet@optimus.ietf.org; Mon, 03 May 2004 11:54:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09454 for ; Mon, 3 May 2004 11:54:46 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKfmK-0002bq-4R for manet@ietf.org; Mon, 03 May 2004 11:54:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKflN-0002Yl-00 for manet@ietf.org; Mon, 03 May 2004 11:53:49 -0400 Received: from web40604.mail.yahoo.com ([66.218.78.141]) by ietf-mx with smtp (Exim 4.12) id 1BKfl7-0002VJ-00 for manet@ietf.org; Mon, 03 May 2004 11:53:33 -0400 Message-ID: <20040503155302.43270.qmail@web40604.mail.yahoo.com> Received: from [132.204.100.226] by web40604.mail.yahoo.com via HTTP; Mon, 03 May 2004 17:53:02 CEST Date: Mon, 3 May 2004 17:53:02 +0200 (CEST) From: =?iso-8859-1?q?redouane?= To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA09455 Subject: [manet] fixed nodes in 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hello I am looking for, articles, works... about routing in ad hoc network with the presence of fixed nodes( wireless not wired). I am interested to routing protocols that use the fixed nodes informations to improve network traffic. Thank you. Redouane =09 =09 =09 Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !=20 Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis gr=E2ce =E0 Yahoo! Messenger !T=E9l=E9c= hargez Yahoo! Messenger sur http://fr.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 14:03:44 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17101 for ; Mon, 3 May 2004 14:03:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKhd1-0001o9-5W for manet-archive@odin.ietf.org; Mon, 03 May 2004 13:53:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43HrJIU006947 for manet-archive@odin.ietf.org; Mon, 3 May 2004 13:53:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKhTl-0007zg-9z for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 13:43:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16068 for ; Mon, 3 May 2004 13:43:42 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKhTj-0005ge-5i for manet-web-archive@ietf.org; Mon, 03 May 2004 13:43:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKhSn-0005ZL-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 13:42:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKhRo-0005SW-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 13:41:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKhLK-0005S7-QT; Mon, 03 May 2004 13:35:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKh3m-0001cd-In for manet@optimus.ietf.org; Mon, 03 May 2004 13:16:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14781 for ; Mon, 3 May 2004 13:16:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKh3k-00035A-LK for manet@ietf.org; Mon, 03 May 2004 13:16:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKh2y-0002zF-00 for manet@ietf.org; Mon, 03 May 2004 13:16:05 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BKh23-0002m6-00 for manet@ietf.org; Mon, 03 May 2004 13:15:07 -0400 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i43HEUW9006210; Mon, 3 May 2004 10:14:30 -0700 (PDT) Received: from CSCOAMERA19540.cisco.com (dhcp-171-71-200-134.cisco.com [171.71.200.134]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id ASV60791; Mon, 3 May 2004 10:13:42 -0700 (PDT) Message-Id: <6.1.0.6.2.20040503101025.04bde600@mira-sjc5-b.cisco.com> X-Sender: fred@mira-sjc5-b.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Mon, 03 May 2004 10:14:41 -0700 To: redouane From: Fred Baker Subject: Re: [manet] fixed nodes in ad hoc network Cc: manet@ietf.org In-Reply-To: <20040503155302.43270.qmail@web40604.mail.yahoo.com> References: <20040503155302.43270.qmail@web40604.mail.yahoo.com> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.3 required=5.0 tests=AWL autolearn=no version=2.60 At 05:53 PM 05/03/04 +0200, redouane wrote: >I am interested to routing protocols that use the >fixed nodes informations to improve network traffic. I should think that in this environment, a fixed node is a mobile node that has higher bandwidth/higher availability links. It may be a very, perhaps the most, "mobile" node in a manet sense. consider a highway with manet nodes traveling in both directions. From the point of view of a vehicle headed south, the most "mobile" nodes (those that come and go most rapidly) are those headed north, the most "stable" nodes are the nodes headed south along with it, and the stationary nodes are simply changing neighbor relationships half as rapidly as the vehicles. In this example, the stationary nodes are pointless if they are located in a narrow valley, but can be tremendously useful if they are located on a hill or are orbiting in aircraft overhead. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 15:14:12 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22522 for ; Mon, 3 May 2004 15:14:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKijV-0006Ul-IX for manet-archive@odin.ietf.org; Mon, 03 May 2004 15:04:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43J45j0024967 for manet-archive@odin.ietf.org; Mon, 3 May 2004 15:04:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiZZ-0007pN-Q6 for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 14:53:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20175 for ; Mon, 3 May 2004 14:53:46 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKiZX-0005rI-4v for manet-web-archive@ietf.org; Mon, 03 May 2004 14:53:47 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKiYc-0005j8-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 14:52:51 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKiY8-0005df-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 14:52:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiLG-0004AD-BV; Mon, 03 May 2004 14:39:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiAT-00016W-TY for manet@optimus.ietf.org; Mon, 03 May 2004 14:27:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18521 for ; Mon, 3 May 2004 14:27:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKiAR-0002n4-Az for manet@ietf.org; Mon, 03 May 2004 14:27:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKi9Z-0002gX-00 for manet@ietf.org; Mon, 03 May 2004 14:26:58 -0400 Received: from aples1.dom1.jhuapl.edu ([128.244.26.85] helo=aples1.jhuapl.edu) by ietf-mx with esmtp (Exim 4.12) id 1BKi8m-0002Sx-00 for manet@ietf.org; Mon, 03 May 2004 14:26:08 -0400 Received: by aples1.dom1.jhuapl.edu with Internet Mail Service (5.5.2653.19) id ; Mon, 3 May 2004 14:25:40 -0400 Message-ID: From: "Farrag, Osama" To: "'redouane'" , manet@ietf.org Subject: RE: [manet] fixed nodes in ad hoc network Date: Mon, 3 May 2004 14:24:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable In response to=20 Farooq email Subject: [manet] Consideration of a wired link in an = ad-hoc network and=20 Redouane email Subject: [manet] fixed nodes in ad hoc network=20 Using Hierarchical networks/routing approach allows you to have = networks consisting of fixed (assume base-Station type analogy) and mobile = nodes, if fixed nodes are connected also using wired network (or through other = long range wireless channel) then these fixed nodes will operate/participate = in two network domains. One domain will use ad-hoc routing protocol and = the other will use some other distance vector or link state protocol.) =20 If fixed nodes are not connected directly, by wired or wireless links) = then there are link layer techniques that support dynamic clustering and = allow nodes to select cluster leader (fixed mobility property could be used = to insure that fixed node is chosen as cluster leader by all nodes in its range.) Cluster leader in these data link schemes manages access to = shared wireless media and acts as Radio port, all packets are relayed through = it. Kind regards Osama Farrag Johns Hopkins University Applied Physics Lab ----------------------------- All statements in this email are my personnel opinions They should not be considered as statements of JHU APL =20 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi, I was just wondering if there is any routing protocol for ad-hoc that considers a link having wired network network in between. For example I have two nodes connected to each other via Ethernet link. = both of them also have wireless cards. They may communicate with each other = using ad-hoc network as well as the wired link. If they are intermediate = nodes of two other nodes (of ad-hoc), priority of routing should be given = through wired link, not the ad-hoc link. Any routing protocol/scheme that does = it? Regards, Shakeel Farooq Undergrad Student, National University of Computer & Emerging Sciences Lahore, Pakistan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet -----Original Message----- From: redouane [mailto:redouane43@yahoo.fr]=20 Sent: Monday, May 03, 2004 11:53 AM To: manet@ietf.org Subject: [manet] fixed nodes in ad hoc network Hello I am looking for, articles, works... about routing in ad hoc network with the presence of fixed nodes( wireless not wired). I am interested to routing protocols that use the fixed nodes informations to improve network traffic. Thank you. Redouane =09 =09 =09 Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! = Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis gr=E2ce =E0 Yahoo! Messenger = !T=E9l=E9chargez Yahoo! Messenger sur http://fr.messenger.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 exim@www1.ietf.org Mon May 3 15:16:59 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22937 for ; Mon, 3 May 2004 15:16:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKikz-0007K4-3W for manet-archive@odin.ietf.org; Mon, 03 May 2004 15:05:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43J5bcr028142 for manet-archive@odin.ietf.org; Mon, 3 May 2004 15:05:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKigT-0002o0-AD for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 15:00:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20602 for ; Mon, 3 May 2004 15:00:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKigQ-0006fn-EX for manet-web-archive@ietf.org; Mon, 03 May 2004 15:00:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKifX-0006Yo-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 15:00:00 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKies-0006Sc-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 14:59:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiMI-0004fg-AQ; Mon, 03 May 2004 14:40:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiFC-0002Lo-GX for manet@optimus.ietf.org; Mon, 03 May 2004 14:32:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18763 for ; Mon, 3 May 2004 14:32:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKiF9-0003MQ-T6 for manet@ietf.org; Mon, 03 May 2004 14:32:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKiEB-0003Ca-00 for manet@ietf.org; Mon, 03 May 2004 14:31:43 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 1BKiDC-00030m-00 for manet@ietf.org; Mon, 03 May 2004 14:30:42 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 029932017; Mon, 3 May 2004 12:30:41 -0600 (MDT) From: "John Mullen" To: "'Fred Baker'" , "'redouane'" Cc: Subject: RE: [manet] fixed nodes in ad hoc network Date: Mon, 3 May 2004 12:30:42 -0600 Message-ID: <000701c4313c$bd8930a0$67f57b80@IEngr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <6.1.0.6.2.20040503101025.04bde600@mira-sjc5-b.cisco.com> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi. I agree. There is one study I'm aware of in which the stationary nodes were given information about other stationary nodes and that did improve performance, but I don't think these nodes would necessarily know anything important about the mobile nodes that they don't already know. The study was: "Implementation Experience with MANET Routing Protocols," by Kwan-Wu Chin, John Judge, Aidan Williams and Roger Kermode. You can get a copy at: http://www.acm.org/sigcomm/ccr/archive/ccr-toc/ccr-toc-2002.html John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Fred Baker Sent: Monday, May 03, 2004 10:15 AM To: redouane Cc: manet@ietf.org Subject: Re: [manet] fixed nodes in ad hoc network At 05:53 PM 05/03/04 +0200, redouane wrote: >I am interested to routing protocols that use the >fixed nodes informations to improve network traffic. I should think that in this environment, a fixed node is a mobile node that has higher bandwidth/higher availability links. It may be a very, perhaps the most, "mobile" node in a manet sense. consider a highway with manet nodes traveling in both directions. From the point of view of a vehicle headed south, the most "mobile" nodes (those that come and go most rapidly) are those headed north, the most "stable" nodes are the nodes headed south along with it, and the stationary nodes are simply changing neighbor relationships half as rapidly as the vehicles. In this example, the stationary nodes are pointless if they are located in a narrow valley, but can be tremendously useful if they are located on a hill or are orbiting in aircraft overhead. _______________________________________________ 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 exim@www1.ietf.org Mon May 3 17:32:03 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03494 for ; Mon, 3 May 2004 17:32:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKkcU-0002MY-9A for manet-archive@odin.ietf.org; Mon, 03 May 2004 17:04:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43L4w01009083 for manet-archive@odin.ietf.org; Mon, 3 May 2004 17:04:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKjjC-0008O9-Vi for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 16:07:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26277 for ; Mon, 3 May 2004 16:07:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKjjB-0006oq-FW for manet-web-archive@ietf.org; Mon, 03 May 2004 16:07:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKjiJ-0006hi-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 16:06:56 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKjhW-0006bg-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 16:06:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKjZi-0005lj-LS; Mon, 03 May 2004 15:58:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKjL4-0002lo-Vv for manet@optimus.ietf.org; Mon, 03 May 2004 15:42:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24938 for ; Mon, 3 May 2004 15:42:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKjL3-000429-Dc for manet@ietf.org; Mon, 03 May 2004 15:42:53 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKjKA-0003v4-00 for manet@ietf.org; Mon, 03 May 2004 15:41:59 -0400 Received: from web50004.mail.yahoo.com ([206.190.38.19]) by ietf-mx with smtp (Exim 4.12) id 1BKjJJ-0003h9-00 for manet@ietf.org; Mon, 03 May 2004 15:41:05 -0400 Message-ID: <20040503194035.36026.qmail@web50004.mail.yahoo.com> Received: from [129.110.39.12] by web50004.mail.yahoo.com via HTTP; Mon, 03 May 2004 12:40:35 PDT Date: Mon, 3 May 2004 12:40:35 -0700 (PDT) From: Shobit Mazumdar To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1935680106-1083613235=:33905" Subject: [manet] 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE autolearn=no version=2.60 --0-1935680106-1083613235=:33905 Content-Type: text/plain; charset=us-ascii Hi, if anyone could kindly let me know if there is a way in OPNET to run from the command prompt ....the way we do in ns-2 and glomosim... specifically i would like to plug in some printf statement in the source code and see the out put in the screen....how do we do it in OPNET.... I Went through the documentation but all they talk there is regarding building a particular scenario and running the aprticular protocol from the Gui options that we have ....i want to do it from the command prompt ...like including some configuration files...mobiliy models ... choose the protocol...and then run the simulation from the command prompt..... If there is a way do this OPNET please help me .... the op_runsim probably is the way to do it but what other files do i need to include...also where can i insert the printfs....for example if i need to print out some info from he DSR source code .... Regards Shobit --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs --0-1935680106-1083613235=:33905 Content-Type: text/html; charset=us-ascii
Hi,
     
if anyone  could kindly let me know if there is a way in OPNET to
run from the command prompt ....the way we do in ns-2 and glomosim...

specifically i would like to plug in some printf statement in the source code and see the
out put in the screen....how do we do it in OPNET....

I Went through the documentation but all they talk there is regarding building a particular
scenario and running the aprticular protocol from the Gui options that we have ....i want to
do it from the command prompt ...like including some configuration files...mobiliy models ...
choose the protocol...and then run the simulation from the command prompt.....

If there is a way do this OPNET please help me ....
 
the op_runsim probably is the way to do it but what other files do i need to include...also where can i insert the printfs....for example if i need to print out some info from he DSR source code ....

Regards
Shobit 

Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs --0-1935680106-1083613235=:33905-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 19:07:47 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10556 for ; Mon, 3 May 2004 19:07:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmP5-00089r-3w for manet-archive@odin.ietf.org; Mon, 03 May 2004 18:59:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43MxFkM031355 for manet-archive@odin.ietf.org; Mon, 3 May 2004 18:59:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmN5-0007Ut-8T for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 18:57:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09995 for ; Mon, 3 May 2004 18:57:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKmN2-0001c3-3s for manet-web-archive@ietf.org; Mon, 03 May 2004 18:57:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKmM8-0001Tw-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 18:56:14 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKmLX-0001La-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 18:55:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmDH-00052C-Q9; Mon, 03 May 2004 18:47:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKm2a-0002Gp-AR for manet@optimus.ietf.org; Mon, 03 May 2004 18:36:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09120 for ; Mon, 3 May 2004 18:35:55 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKm2X-0006mR-AA for manet@ietf.org; Mon, 03 May 2004 18:35:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKm1d-0006fO-00 for manet@ietf.org; Mon, 03 May 2004 18:35:02 -0400 Received: from web61108.mail.yahoo.com ([216.155.196.110]) by ietf-mx with smtp (Exim 4.12) id 1BKm0k-0006Ri-00 for manet@ietf.org; Mon, 03 May 2004 18:34:06 -0400 Message-ID: <20040503223337.74636.qmail@web61108.mail.yahoo.com> Received: from [141.156.71.10] by web61108.mail.yahoo.com via HTTP; Mon, 03 May 2004 15:33:37 PDT Date: Mon, 3 May 2004 15:33:37 -0700 (PDT) From: manet user Subject: Re: [manet] Opnet!! To: Shobit Mazumdar , manet@ietf.org In-Reply-To: <20040503194035.36026.qmail@web50004.mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-867028092-1083623617=:74213" 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 --0-867028092-1083623617=:74213 Content-Type: text/plain; charset=us-ascii Hi Shobit, If you have support for your OPNET product, you can find many answers from FAQ at www.opnet.com/support I found one for your current question. Just pasting it here. Hope it helps. Also, you can enable ODB debugger option while running from GUI which can provide many debugging capabilities and you can see your printfs as well. FAQ ID: 375 When a simulation is launched from the OPNET GUI (project editor or simulation set editor), the OPNET GUI passes many arguments to the simulation program op_runsim. If you instead run a simulation from the command line (using op_runsim or a static simulation executable built using op_mksim), and you want to get the same results as the simulation launched from the OPNET GUI, you must pass almost all of the same arguments to the simulation program on the command line. To see the exact arguments passed by the OPNET GUI: 1) Start a simulation from the GUI 2) Open the file /op_admin/session_log. 3) Scroll to the end of the file. 4) Observe the arguments passed to op_runsim. 5) The values of the arguments (such as "duration") will be different depending how you have configured your simulation attributes in the OPNET GUI. 6) You can copy these arguments from the session_log, then reuse them by pasting them when you run your simulation from the command line (using op_runsim or a static simulation executable). Note that one argument passed to op_runsim from the GUI is particularly important: the "-ef" argument, which by default has a value in 8.0 and later. This .ef file contains the values of simulation attributes specified in the OPNET GUI. The rest of the FAQ applies to versions 7.0 and earlier ------------------------------------------------------- In 7.0 and earlier, the default value of the "-ef" argument is "sim_attrs". The "sim_attrs.ef" is a temporary file that contains the values of simulation attributes specified in the OPNET GUI. To get the same results by running the simulation on the command line, you will have to copy and rename that "sim_attrs.ef" file: 1) First, run your simulation from the GUI and pause it before it completes. 2) You should see a file called "sim_attrs.ef" in your primary models directory (the directory listed first in your mod_dirs). The file will be deleted when the simulation completes. 3) Copy "sim_attrs.ef" it to a unique name (such as "my_sim_attrs_1"). 4) Click on the "Stop Run" button in the GUI. 5) When you run the simulation from the command line, use the same arguments as you found in the session_log file above, but instead of using the argument "-ef sim_attrs", use the argument "-ef my_sim_attrs_1". 6) For additional details on the sim_attrs.ef file, you can read the FAQ "How can I generate an example environment file for running simulations?"). EXAMPLES Example A: Sample op_runsim command recorded by the OPNET 7.0 GUI in the /session_log: ---------------------- 21:22:05 Sun Jan 12 1999: modeler issued the following command: op_runsim -opnet_user_home c:/users/opnet -net_name ACE-local_net -child_id 1 -opnet_port 3456 -verbose_sim true -verbose_load true -duration 3600 -probe ACE-local_net -noprompt TRUE -ov_file ACE-local_net -log_file ACE-local_net -parallel_sim.num_processors 1 -ef sim_attrs ---------------------- Example B: In order to get the exact same results running the simulation at the command line, you would have to copy the sim_attrs file, then the following command: prompt% op_runsim -opnet_user_home c:/users/opnet -net_name ACE-local_net -duration 3600 -probe ACE-local_net -noprompt TRUE -ov_file ACE-local_net -log_file ACE-local_net -ef my_sim_attrs_1 In the above example, note that the last argument is the renamed my_sim_attrs_1. Also, note that we omitted the following arguments (but we would also get the same results if we chose not to omit them): child_id, opnet_port, verbose_sim, verbose_load, and parallel_sim.num_processors. Shobit Mazumdar wrote: Hi, if anyone could kindly let me know if there is a way in OPNET to run from the command prompt ....the way we do in ns-2 and glomosim... specifically i would like to plug in some printf statement in the source code and see the out put in the screen....how do we do it in OPNET.... I Went through the documentation but all they talk there is regarding building a particular scenario and running the aprticular protocol from the Gui options that we have ....i want to do it from the command prompt ...like including some configuration files...mobiliy models ... choose the protocol...and then run the simulation from the command prompt..... If there is a way do this OPNET please help me .... the op_runsim probably is the way to do it but what other files do i need to include...also where can i insert the printfs....for example if i need to print out some info from he DSR source code .... Regards Shobit --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs --0-867028092-1083623617=:74213 Content-Type: text/html; charset=us-ascii
Hi Shobit,
 
If you have support for your OPNET product, you can find many answers from FAQ at www.opnet.com/support
I found one for your current question. Just pasting it here. Hope it helps. Also, you can enable ODB debugger option while running from GUI which can provide many debugging capabilities and you can see your printfs as well.
 
FAQ ID: 375
When a simulation is launched from the OPNET GUI (project editor or simulation set editor), the OPNET GUI passes many arguments to the simulation program op_runsim. If you instead run a simulation from the command line (using op_runsim or a static simulation executable built using op_mksim), and you want to get the same results as the simulation launched from the OPNET GUI, you must pass almost all of the same arguments to the simulation program on the command line.

To see the exact arguments passed by the OPNET GUI:
1) Start a simulation from the GUI
2) Open the file <user_home_dir>/op_admin/session_log.
3) Scroll to the end of the file.
4) Observe the arguments passed to op_runsim.
5) The values of the arguments (such as "duration") will be different depending how you have configured your simulation attributes in the OPNET GUI.
6) You can copy these arguments from the session_log, then reuse them by pasting them when you run your simul! ation from the command line (using op_runsim or a static simulation executable).

Note that one argument passed to op_runsim from the GUI is particularly important: the "-ef" argument, which by default has a value <project-scenario> in 8.0 and later. This .ef file contains the values of simulation attributes specified in the OPNET GUI.

The rest of the FAQ applies to versions 7.0 and earlier
-------------------------------------------------------
In 7.0 and earlier, the default value of the "-ef" argument is "sim_attrs". The "sim_attrs.ef" is a temporary file that contains the values of simulation attributes specified in the OPNET GUI. To get the same results by running the simulation on the command line, you will have to copy and rename that "sim_attrs.ef" file:
1) First, run your simulation from the GUI and pause it before it completes.
2) You should see a file called "sim_attrs.ef" in your primary models directory (the directory listed first in ! your mod_dirs). The file will be deleted when the simulation completes.
3) Copy "sim_attrs.ef" it to a unique name (such as "my_sim_attrs_1").
4) Click on the "Stop Run" button in the GUI.
5) When you run the simulation from the command line, use the same arguments as you found in the session_log file above, but instead of using the argument "-ef sim_attrs", use the argument "-ef my_sim_attrs_1".
6) For additional details on the sim_attrs.ef file, you can read the FAQ "How can I generate an example environment file for running simulations?").

EXAMPLES

Example A:
Sample op_runsim command recorded by the OPNET 7.0 GUI in the <user_home_dir>/session_log:
----------------------
21:22:05 Sun Jan 12 1999: modeler issued the following command:
op_runsim -opnet_user_home c:/users/opnet -net_name ACE-local_net -child_id 1 -opnet_port 3456 -verbose_sim true -verbose_load true -duration 3600 -probe ACE-local_net -noprompt TRUE -ov_file ACE-loca! l_net -log_file ACE-local_net -parallel_sim.num_processors 1 -ef sim_attrs
----------------------

Example B:
In order to get the exact same results running the simulation at the command line, you would have to copy the sim_attrs file, then the following command:

prompt% op_runsim -opnet_user_home c:/users/opnet -net_name ACE-local_net -duration 3600 -probe ACE-local_net -noprompt TRUE -ov_file ACE-local_net -log_file ACE-local_net -ef my_sim_attrs_1

In the above example, note that the last argument is the renamed my_sim_attrs_1. Also, note that we omitted the following arguments (but we would also get the same results if we chose not to omit them): child_id, opnet_port, verbose_sim, verbose_load, and parallel_sim.num_processors.


Shobit Mazumdar <shobit_mazumdar@yahoo.com> wrote:
Hi,
     
if anyone  could kindly let me know if there is a way in OPNET to
run from the command prompt ....the way we do in ns-2 and glomosim...

specifically i would like to plug in some printf statement in the source code and see the
out put in the screen....how do we do it in OPNET....

I Went through the documentation but all they talk there is regarding building a particular
scenario and running the aprticular protocol from the Gui options that we have ....i want to
do it from the command prompt ...like including some configuration files...mobiliy models ...
choose the protocol...and then run the simulation from the command prompt.....

If there is a way do this OPNET please help me ....
 
the op_runsim probably is the way to do it but what other files do i need to include...also where can i insert the printfs....for example if i need to print out some info from he DSR source code ....

Regards
Shobit 

Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs

Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs --0-867028092-1083623617=:74213-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 19:38:44 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11872 for ; Mon, 3 May 2004 19:38:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmuF-0007Gl-H9 for manet-archive@odin.ietf.org; Mon, 03 May 2004 19:31:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43NVRHQ027932 for manet-archive@odin.ietf.org; Mon, 3 May 2004 19:31:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmlK-0005Kh-1a for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 19:22:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11253 for ; Mon, 3 May 2004 19:22:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKmlI-0004zj-Jz for manet-web-archive@ietf.org; Mon, 03 May 2004 19:22:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKmkQ-0004rW-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 19:21:18 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKmjw-0004ih-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 19:20:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmfJ-0003e7-L4; Mon, 03 May 2004 19:16:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKmdJ-0003Ar-OP for manet@optimus.ietf.org; Mon, 03 May 2004 19:13:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10889 for ; Mon, 3 May 2004 19:13:54 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKmdI-0003vJ-6C for manet@ietf.org; Mon, 03 May 2004 19:13:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKmcJ-0003mc-00 for manet@ietf.org; Mon, 03 May 2004 19:12:56 -0400 Received: from postman.opnet.com ([192.104.65.25] helo=newpostman.opnet.com) by ietf-mx with esmtp (Exim 4.12) id 1BKmbL-0003YB-00 for manet@ietf.org; Mon, 03 May 2004 19:11:56 -0400 Received: from mpdomain (netscreen3020.opnet.com [172.16.1.39]) by newpostman.opnet.com (8.12.10/8.12.1) with ESMTP id i43NBJLb010468; Mon, 3 May 2004 19:11:20 -0400 (EDT) Message-Id: <5.1.1.6.2.20040503190447.04b43f50@vip.opnet.com> X-Sender: jlee@vip.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Mon, 03 May 2004 19:10:55 -0400 To: Shobit Mazumdar , manet@ietf.org From: Jay Lee Subject: Re: [manet] Opnet!! In-Reply-To: <20040503194035.36026.qmail@web50004.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/html; 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_20_30, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,MIME_HTML_ONLY autolearn=no version=2.60 You can start OPNET from a console and should be able to see the print-out from your printf() calls within the console.  Edit the "Edit->preferences->console" option to true and restart OPNET.

Best of luck, - Jay


At 12:40 PM 5/3/2004 -0700, Shobit Mazumdar wrote:
Hi,
     
if anyone  could kindly let me know if there is a way in OPNET to
run from the command prompt ....the way we do in ns-2 and glomosim...

specifically i would like to plug in some printf statement in the source code and see the
out put in the screen....how do we do it in OPNET....

I Went through the documentation but all they talk there is regarding building a particular
scenario and running the aprticular protocol from the Gui options that we have ....i want to
do it from the command prompt ...like including some configuration files...mobiliy models ...
choose the protocol...and then run the simulation from the command prompt.....

If there is a way do this OPNET please help me ....
 
the op_runsim probably is the way to do it but what other files do i need to include...also where can i insert the printfs....for example if i need to print out some info from he DSR source code ....

Regards
Shobit


Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs

**************************
Junghan (Jay) Lee
Senior Consulting Engineer, Consulting Services
OPNET Technologies, Inc. (NASDAQ:OPNT)
www.opnet.com
jlee@opnet.com
201.928.1648 (home office)
=============================================================
Register for OPNET's Online Technology Workshops
http://www.opnet.com/TechWorkshops/
=============================================================
Register for OPNETWORK 2004 (Aug 30 - Sept 3, Washington DC)
http://www.opnet.com/opnetwork2004/
=============================================================
_______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 3 20:26:46 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13349 for ; Mon, 3 May 2004 20:26:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKniS-0001nt-HJ for manet-archive@odin.ietf.org; Mon, 03 May 2004 20:23:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i440NKKJ006929 for manet-archive@odin.ietf.org; Mon, 3 May 2004 20:23:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKnfF-0001BG-LD for manet-web-archive@optimus.ietf.org; Mon, 03 May 2004 20:20:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13142 for ; Mon, 3 May 2004 20:19:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKnfD-0004cb-Jr for manet-web-archive@ietf.org; Mon, 03 May 2004 20:19:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKneG-0004Tj-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 20:19:00 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKndO-0004KW-00 for manet-web-archive@ietf.org; Mon, 03 May 2004 20:18:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKnZR-0008Eq-7c; Mon, 03 May 2004 20:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKnXf-0007x4-LH for manet@optimus.ietf.org; Mon, 03 May 2004 20:12:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12896 for ; Mon, 3 May 2004 20:12:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKnXd-0003Yf-KM for manet@ietf.org; Mon, 03 May 2004 20:12:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKnWg-0003Qm-00 for manet@ietf.org; Mon, 03 May 2004 20:11:10 -0400 Received: from www4.mail.lycos.com ([209.202.220.170] helo=lycos.com) by ietf-mx with smtp (Exim 4.12) id 1BKnVs-0003An-00 for manet@ietf.org; Mon, 03 May 2004 20:10:20 -0400 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Tue, 04 May 2004 00:09:43 -0000 To: manet@ietf.org Date: Mon, 03 May 2004 17:09:43 -0700 From: "Sayeem Ahmed" Message-ID: Mime-Version: 1.0 Content-Language: en X-Sent-Mail: off Reply-To: sayeem@lycos.com X-Mailer: MailCity Service X-Priority: 3 X-Sender-Ip: 68.63.34.139 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] MANET Simulation 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I want to get the statistics of following measurements for DSR, TORA and AODV in OPNET Modeler 1. Path Optimality 2. Power Efficiency (Energy Consumption) Can any one help me in this regard? I have been working with OPNET 10.5 for a couple of months but still could not figure out the solution. Any help concerning path optimality and power efficiency in case of MANET routing protocols will also help. Please help. Regards, Sayeem ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 4 00:28:41 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23188 for ; Tue, 4 May 2004 00:28:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKrWR-00012x-Vv for manet-archive@odin.ietf.org; Tue, 04 May 2004 00:27:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i444RBI6004023 for manet-archive@odin.ietf.org; Tue, 4 May 2004 00:27:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKrSf-00008l-RN for manet-web-archive@optimus.ietf.org; Tue, 04 May 2004 00:23:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22927 for ; Tue, 4 May 2004 00:23:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKrSd-0006i8-Eb for manet-web-archive@ietf.org; Tue, 04 May 2004 00:23:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKrRf-0006Yi-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 00:22:16 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BKrR0-0006Q0-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 00:21:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKrKg-00069X-NR; Tue, 04 May 2004 00:15:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKrF5-00041T-Pt for manet@optimus.ietf.org; Tue, 04 May 2004 00:09:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22618 for ; Tue, 4 May 2004 00:09:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKrF3-0004mj-Dr for manet@ietf.org; Tue, 04 May 2004 00:09:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKrEC-0004ez-00 for manet@ietf.org; Tue, 04 May 2004 00:08:21 -0400 Received: from ms-smtp-01-qfe0.socal.rr.com ([66.75.162.133] helo=ms-smtp-01-eri0.socal.rr.com) by ietf-mx with esmtp (Exim 4.12) id 1BKrDd-0004Wa-00 for manet@ietf.org; Tue, 04 May 2004 00:07:45 -0400 Received: from SDRCZZ (66-27-113-130.san.rr.com [66.27.113.130]) by ms-smtp-01-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id i4447c6E024550 for ; Mon, 3 May 2004 21:07:38 -0700 (PDT) Message-Id: <200405040407.i4447c6E024550@ms-smtp-01-eri0.socal.rr.com> Reply-To: From: "Zhensheng Zhang" To: Date: Mon, 3 May 2004 21:07:36 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-index: AcQxF52FFHqHvlAnSnypArSj07rplwAasUtwAAKlIeA= X-Virus-Scanned: Symantec AntiVirus Scan Engine Content-Transfer-Encoding: 7bit Subject: [manet] CFP- work in progress papers BroadNet 2004 wireless symposium 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Call for "Work-in-Progress" Poster Papers BroadNets 2004 - Wireless Networking Symposium October 25 - 29, 2004, San Jose, California, USA http://www.broadnets.org BroadNets 2004, the first international conference on broadband networks will be held during October 25-29 in the heart of Silicon Valley -- San Jose, CA. Technical paper submission is now closed. To allow the presentation of recent results and/or research work in progress, BroadNets 2004 Wireless Networking Symposium solicits poster papers demonstrating state-of-the-art research in broadly defined wireless networking area. Poster papers, not previously published, should be a maximum of 3 pages in length (in double column, 10 point font) and will be published in the conference proceedings by IEEE Computer Society. Poster submissions will be reviewed. Important dates: - Deadline for submitting a work-in-progress poster paper: June 1, 2004. - Notification of acceptance: June 15, 2004. - Final manuscript due: July 7, 2004. Authors are invited to submit poster papers directly to TPC co-chairs, Dr. Parmesh Ramanathan (parmesh@ece.wisc.edu) and Dr. Thomas Hou (thou@vt.edu). All submissions should be in Postscript or Adobe PDF format. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 4 14:01:58 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16193 for ; Tue, 4 May 2004 14:01:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL4AK-0006P3-KA for manet-archive@odin.ietf.org; Tue, 04 May 2004 13:57:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44HvCJo024614 for manet-archive@odin.ietf.org; Tue, 4 May 2004 13:57:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL480-0003QI-BP for manet-web-archive@optimus.ietf.org; Tue, 04 May 2004 13:54:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15773 for ; Tue, 4 May 2004 13:54:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL47y-0000vg-3w for manet-web-archive@ietf.org; Tue, 04 May 2004 13:54:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL471-0000qG-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 13:53:47 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL3xa-0000i0-10; Tue, 04 May 2004 13:44:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL3vK-0000Cr-2u for manet@optimus.ietf.org; Tue, 04 May 2004 13:41:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15115 for ; Tue, 4 May 2004 13:41:39 -0400 (EDT) From: redouane43@yahoo.fr Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL3vH-0007Ml-UA for manet@ietf.org; Tue, 04 May 2004 13:41:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL3uI-0007G8-00 for manet@ietf.org; Tue, 04 May 2004 13:40:39 -0400 Received: from plus.ds14.agh.edu.pl ([149.156.124.14] helo=ietf.org ident=coolj) by ietf-mx with esmtp (Exim 4.12) id 1BL3t7-00075K-00 for manet@ietf.org; Tue, 04 May 2004 13:39:25 -0400 To: manet@ietf.org Date: Tue, 4 May 2004 19:42:48 +0200 MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_001B_01C0CA80.6B015D10" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=7.4 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_40_50, HTML_MESSAGE,HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE, MIME_SUSPECT_NAME,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME, PRIORITY_NO_NAME autolearn=no version=2.60 X-Spam-Report: * 0.3 NO_REAL_NAME From: does not include a real name * 0.9 FROM_ENDS_IN_NUMS From: ends in numbers * 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL * 0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content * 0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program * 3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay * 1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE * 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer Subject: [manet] Mail Delivery (failure manet@ietf.org) 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_001B_01C0CA80.6B015D10 Content-Type: multipart/alternative; boundary="----=_NextPart_001_001C_01C0CA80.6B015D10" ------=_NextPart_001_001C_01C0CA80.6B015D10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_001_001C_01C0CA80.6B015D10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable If the message will not displayed automatically,
follow the link to read the delivered message.

Received message is available at:
www.ietf.org/inbox/manet/read.php?sessionid-1092

 
------=_NextPart_001_001C_01C0CA80.6B015D10-- ------=_NextPart_000_001B_01C0CA80.6B015D10 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit [Filename: message.scr, Content-Type: audio/x-wav] The attachment file in the message has been removed by eManager. ------=_NextPart_000_001B_01C0CA80.6B015D10-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 4 17:20:01 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00175 for ; Tue, 4 May 2004 17:20:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7B9-0007he-7y for manet-archive@odin.ietf.org; Tue, 04 May 2004 17:10:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44LAFBu029606 for manet-archive@odin.ietf.org; Tue, 4 May 2004 17:10:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL76B-0006DY-Pw for manet-web-archive@optimus.ietf.org; Tue, 04 May 2004 17:05:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29196 for ; Tue, 4 May 2004 17:05:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL769-0007lA-LU for manet-web-archive@ietf.org; Tue, 04 May 2004 17:05:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL75I-0007dL-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 17:04:13 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL74U-0007Vx-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 17:03:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6wR-0003la-Dt; Tue, 04 May 2004 16:55:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6tL-000303-TX for manet@optimus.ietf.org; Tue, 04 May 2004 16:51:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28551 for ; Tue, 4 May 2004 16:51:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL6tJ-00069L-NR for manet@ietf.org; Tue, 04 May 2004 16:51:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL6sP-00061E-00 for manet@ietf.org; Tue, 04 May 2004 16:50:55 -0400 Received: from aples1.dom1.jhuapl.edu ([128.244.26.85] helo=aples1.jhuapl.edu) by ietf-mx with esmtp (Exim 4.12) id 1BL6rY-0005ny-00 for manet@ietf.org; Tue, 04 May 2004 16:50:00 -0400 Received: by aples1.dom1.jhuapl.edu with Internet Mail Service (5.5.2653.19) id ; Tue, 4 May 2004 16:49:33 -0400 Message-ID: From: "Farrag, Osama" To: "'manet@ietf.org'" Date: Tue, 4 May 2004 16:48:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43219.1EF461C0" Subject: [manet] Consideration of a wired link in an 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43219.1EF461C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In response to=20 Farooq email Subject: [manet] Consideration of a wired link in an = ad-hoc network and=20 Redouane email Subject: [manet] fixed nodes in ad hoc network=20 Using Hierarchical networks/routing approach allows you to have = networks consisting of fixed (assume base-Station type analogy) and mobile = nodes, if fixed nodes are connected also using wired network (or through other = long range wireless channel) then these fixed nodes will operate/participate = in two network domains. One domain will use ad-hoc routing protocol and = the other will use some other distance vector or link state protocol.) = Fixed nodes acts as gateway between these domains.=20 If fixed nodes are not connected directly, by wired or wireless links; there are link layer techniques that support dynamic clustering and = allow nodes to select cluster leader (fixed mobility property could be used = to insure that fixed node is chosen as cluster leader by all nodes in its range.) Cluster leader in these data link schemes manages access to = shared wireless media and acts as Radio port, all packets are relayed through = it. Note that while these data-link technique improve access to media and collision avoidance, they don't necessary improve routing if mobile = nodes have no geographical association with specific fixed nodes. =20 Kind regards Osama Farrag Johns Hopkins University Applied Physics Lab ----------------------------- All statements in this email are my personnel opinions They should not be considered as statements of JHU APL =20 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi, I was just wondering if there is any routing protocol for ad-hoc that considers a link having wired network network in between. For example I have two nodes connected to each other via Ethernet link. = both of them also have wireless cards. They may communicate with each other = using ad-hoc network as well as the wired link. If they are intermediate = nodes of two other nodes (of ad-hoc), priority of routing should be given = through wired link, not the ad-hoc link. Any routing protocol/scheme that does = it? Regards, Shakeel Farooq Undergrad Student, National University of Computer & Emerging Sciences Lahore, Pakistan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet =20 -----Original Message----- From: redouane [mailto:redouane43@yahoo.fr = ]=20 Sent: Monday, May 03, 2004 11:53 AM To: manet@ietf.org Subject: [manet] fixed nodes in ad hoc network Hello I am looking for, articles, works... about routing in ad hoc network with the presence of fixed nodes( wireless not wired). I am interested to routing protocols that use the fixed nodes informations to improve network traffic. Thank you. Redouane =09 =09 =09 Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! = Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ =20 Dialoguez en direct avec vos amis gr=E2ce =E0 Yahoo! Messenger = !T=E9l=E9chargez Yahoo! Messenger sur http://fr.messenger.yahoo.com =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet =20 ------_=_NextPart_001_01C43219.1EF461C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Consideration of a wired link in an ad-hoc network

In response to =

Farooq email = Subject: [manet] Consideration of a wired link in an ad-hoc = network

and

Redouane email = Subject: [manet] fixed nodes in ad hoc network




Using Hierarchical = networks/routing approach allows you to have networks consisting of = fixed (assume base-Station type analogy) and mobile nodes, if fixed = nodes are connected also using wired network (or through other long = range wireless channel) then these fixed nodes will operate/participate = in two network domains. One domain will use ad-hoc routing protocol and = the other will use some other distance vector or link state = protocol.) Fixed nodes acts = as gateway between these domains.


 If fixed = nodes are not connected directly, by wired or wireless = links; there are link layer techniques that support = dynamic clustering and allow nodes to select cluster leader (fixed = mobility property could be used to insure that fixed node is chosen as = cluster leader by all nodes in its range.) Cluster leader in these data = link schemes manages access to shared wireless media and acts as Radio = port, all packets are relayed through it. Note = that while these = data-link technique improve access to = media and collision avoidance, they don't = necessary improve routing if mobile nodes have no geographical = association with specific fixed nodes.

 

Kind = regards

Osama = Farrag

Johns Hopkins = University

Applied Physics = Lab

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

All statements in = this email are my personnel opinions

They should not be = considered as statements of JHU APL  


>>>>>>>>>>>>>>>>>= ;>>>>>>>>>>>>>>>>>>= ;>>>>>>>>>>>>>>>>>>= ;>


Hi,

I was just = wondering if there is any routing protocol for ad-hoc that considers a = link having wired network network in between.

For example I have = two nodes connected to each other via Ethernet link. both of them also = have wireless cards. They may communicate with each other using ad-hoc = network as well as the wired link. If they are intermediate nodes of = two other nodes (of ad-hoc), priority of routing should be given through= wired link, not the ad-hoc link. Any routing protocol/scheme that does = it?

Regards,

Shakeel = Farooq

Undergrad = Student,

National University = of Computer & Emerging Sciences

Lahore, = Pakistan

_______________________________________________

manet mailing = list

manet@ietf.org

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






-----Original = Message-----

From: redouane = [mailto:redouane43@yahoo.fr]

Sent: Monday, May = 03, 2004 11:53 AM

To: = manet@ietf.org

Subject: [manet] = fixed nodes in ad hoc network

Hello

I am looking for, = articles, works... about routing in

ad hoc network with = the presence of fixed nodes(

wireless not = wired).

I am interested to = routing protocols that use the

fixed nodes = informations to improve network traffic.

Thank = you.

Redouane



       

       

        =        

Yahoo! Mail : votre = e-mail personnel et gratuit qui vous suit partout !

Cr=E9ez votre = Yahoo! Mail sur http://fr.benefits.yahoo.com/

Dialoguez en direct = avec vos amis gr=E2ce =E0 Yahoo! Messenger !T=E9l=E9chargez Yahoo! = Messenger sur http://fr.messenger.yahoo.com

_______________________________________________

manet mailing = list

manet@ietf.org

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

------_=_NextPart_001_01C43219.1EF461C0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 4 18:10:46 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02887 for ; Tue, 4 May 2004 18:10:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7y2-0004zL-8E for manet-archive@odin.ietf.org; Tue, 04 May 2004 18:00:46 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44M0kN9019176 for manet-archive@odin.ietf.org; Tue, 4 May 2004 18:00:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7xE-0004T1-HY for manet-web-archive@optimus.ietf.org; Tue, 04 May 2004 17:59:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01839 for ; Tue, 4 May 2004 17:59:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL7xB-0006Na-Tc for manet-web-archive@ietf.org; Tue, 04 May 2004 17:59:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL7wJ-0006GK-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 17:59:00 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL7vU-00069q-00 for manet-web-archive@ietf.org; Tue, 04 May 2004 17:58:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7pb-0002Vw-G4; Tue, 04 May 2004 17:52:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7oV-0002A3-QH for manet@optimus.ietf.org; Tue, 04 May 2004 17:50:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01452 for ; Tue, 4 May 2004 17:50:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL7oT-0005KX-8W for manet@ietf.org; Tue, 04 May 2004 17:50:53 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL7nY-0005Dz-00 for manet@ietf.org; Tue, 04 May 2004 17:49:57 -0400 Received: from smtp-bedford-x.mitre.org ([192.160.51.76] helo=smtp-bedford.mitre.org) by ietf-mx with esmtp (Exim 4.12) id 1BL7ml-00051X-00 for manet@ietf.org; Tue, 04 May 2004 17:49:07 -0400 Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.11.6/8.11.6) with ESMTP id i44Lmb523787 for ; Tue, 4 May 2004 17:48:37 -0400 Received: from linus.mitre.org (rcf-smtp.mitre.org [129.83.10.1]) by smtp-bedford.mitre.org (8.11.6/8.11.6) with ESMTP id i44LmaH23770; Tue, 4 May 2004 17:48:36 -0400 Received: from linus.mitre.org (linus.mitre.org [129.83.10.1]) by linus.mitre.org (8.12.10/8.12.8) with ESMTP id i44LmaK1005686; Tue, 4 May 2004 17:48:36 -0400 (EDT) Message-Id: <200405042148.i44LmaK1005686@linus.mitre.org> To: manet@ietf.org cc: swarup@mitre.org X-Mailer: nmh 1.0.4 From: Vipin Swarup Reply-to: swarup@mitre.org Date: Tue, 04 May 2004 17:48:36 -0400 Subject: [manet] CFP: Security of Ad Hoc and Sensor Networks Workshop (SASN 2004) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 ===================================================================== 2004 ACM Workshop on Security of Ad Hoc and Sensor Networks (SASN 2004) To be held in conjunction with the 11th ACM Conference on Computer and Communications Security October 25, 2004, Wyndham City Hotel, Washington, DC Sponsored by ACM SIGSAC http://www.cs.gmu.edu/sasn CALL FOR PAPERS Ad hoc and sensor networks are expected to become an integral part of the future computing landscape. However, these networks introduce new security challenges due to their dynamic topology, severe resource constraints, and absence of a trusted infrastructure. SASN 2004 seeks submissions from academia and industry presenting novel research on all aspects of security for ad hoc and sensor networks, as well as experimental studies of fielded systems. This one-day workshop builds on the huge success of the first SASN workshop held in Fairfax, VA (http://www.cs.gmu.edu/sasn/2003). Submission of papers based on work-in-progress is encouraged. Topics of interest include, but are not limited to, the following as they relate to wireless networks, mobile ad hoc networks, or sensor networks: * Security under resource constraints, e.g., energy, bandwidth, memory, and computation constraints * Performance and security tradeoffs * Secure roaming across administrative domains * Key management * Cryptographic protocols * Authentication and access control * Trust establishment, negotiation, and management * Intrusion detection and tolerance * Secure location services * Privacy and anonymity * Secure routing * Secure MAC protocols * Denial of service * Prevention of traffic analysis Submission Instructions: Submitted papers must not substantially overlap with papers that have been published or that are simultaneously submitted to a journal or a conference with proceedings. Papers should be at most 15 pages excluding the bibliography and well-marked appendices, using at least 11-point font and reasonable margins on US letter-size paper (8.5 inch x 11 inch). Committee members are not required to read the appendices, and so submissions should be intelligible without them. Each submission should start with the title, abstract, and names and contact information of authors. The introduction should give background and summarize the contributions of the paper at a level appropriate for a non-specialist reader. All paper submissions will be handled electronically. Papers must be submitted in PDF or portable PostScript format and must be received by the deadline of July 2, 2004. Instructions for electronic submission of papers will be posted at: http://www.cs.gmu.edu/sasn/submissions.html Conference proceedings will be published by the ACM and made available at the workshop. Authors of accepted papers must guarantee that their paper will be presented at the workshop. Important Dates: Paper submissions due: July 2, 2004 Acceptance notifications: August 19, 2004 Camera-ready papers due: September 3, 2004 SASN Workshop: October 25, 2004 Program Co-Chairs: Sanjeev Setia, George Mason University (setia@gmu.edu) Vipin Swarup, MITRE (swarup@mitre.org) Program Committee: Wenliang Du, Syracuse University Virgil Gligor, University of Maryland, College Park Zygmunt Haas, Cornell University Rick Han, University of Colorado, Boulder Jean-Pierre Hubaux, Swiss Federal Institute of Technology, Lausanne Jonathan Katz, University of Maryland, College Park Wenke Lee, Georgia Institute of Technology, Atlanta Songwu Lu, University of California, Los Angeles Luigi Mancini, University of Rome Peng Ning, North Carolina State University Radha Poovendran, University of Washington, Seattle Dawn Song, Carnegie Mellon University Roshan Thomas, Network Associates Inc. Gene Tsudik, University of California, Irvine Cliff Wang, U.S. Army Research Office Ron Watro, BBN Technologies Dirk Westhoff, NEC Europe ===================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 5 01:45:00 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24295 for ; Wed, 5 May 2004 01:45:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLF9w-0008M1-8q for manet-archive@odin.ietf.org; Wed, 05 May 2004 01:41:32 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i455fW8r032114 for manet-archive@odin.ietf.org; Wed, 5 May 2004 01:41:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLF5t-0007Cf-Sv for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 01:37:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23988 for ; Wed, 5 May 2004 01:37:19 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLF5q-00074s-PZ for manet-web-archive@ietf.org; Wed, 05 May 2004 01:37:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLF53-0006vC-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 01:36:30 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLF4W-0006kh-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 01:35:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLExq-00056t-Mw; Wed, 05 May 2004 01:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLEuC-0004Ps-VB for manet@optimus.ietf.org; Wed, 05 May 2004 01:25:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23646 for ; Wed, 5 May 2004 01:25:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLEu9-0005EC-Rq for manet@ietf.org; Wed, 05 May 2004 01:25:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLEtG-00055v-00 for manet@ietf.org; Wed, 05 May 2004 01:24:19 -0400 Received: from nn4.excitenetwork.com ([207.159.120.58] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BLEsy-0004wh-00 for manet@ietf.org; Wed, 05 May 2004 01:24:00 -0400 Received: by xprdmailfe15.nwk.excite.com (Postfix, from userid 110) id A8A7CB6AF; Wed, 5 May 2004 01:23:31 -0400 (EDT) To: manet@ietf.org Received: from [139.55.19.60] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 05 May 2004 01:23:31 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 446bc341fc591e66037aff4413e1760e Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040505052331.A8A7CB6AF@xprdmailfe15.nwk.excite.com> Date: Wed, 5 May 2004 01:23:31 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] Question about 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, In AODV, when a node detects a link break, it sends an ERROR message to nodes on its precursor list, so that the upstream nodes can know the broken link and disable the relevant routes. For example, 1-----2----5---X---6 The original route is 1-2-5-6. Assume the link between 5 and 6 is down. Node 5 will send ERROR to 2, then 2 sends ERROR to 1. But if due to some reason, e.g., collision, node 2 does not receive node 5's ERROR message, 2 will not disable the route. So both 1 and 2 store invalid route, which may cause packet dropping. Is my analysis correct? How to prevent the above problem? Thanks, Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 5 02:57:07 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25332 for ; Wed, 5 May 2004 02:57:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLGJi-0001he-P0 for manet-archive@odin.ietf.org; Wed, 05 May 2004 02:55:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i456tgvQ006547 for manet-archive@odin.ietf.org; Wed, 5 May 2004 02:55:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLGHT-0000i1-VF for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 02:53:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25158 for ; Wed, 5 May 2004 02:53:20 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLGHQ-0004Vq-5g for manet-web-archive@ietf.org; Wed, 05 May 2004 02:53:20 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLGGV-0004Ll-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 02:52:24 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLGFX-0004BU-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 02:51:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLG6W-0006as-3P; Wed, 05 May 2004 02:42:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLFy1-0003Yy-4q for manet@optimus.ietf.org; Wed, 05 May 2004 02:33:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24124 for ; Wed, 5 May 2004 02:33:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLFxx-00011x-8o for manet@ietf.org; Wed, 05 May 2004 02:33:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLFx1-0000sL-00 for manet@ietf.org; Wed, 05 May 2004 02:32:16 -0400 Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.24] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1BLFwA-0000ii-00 for manet@ietf.org; Wed, 05 May 2004 02:31:22 -0400 Received: From [192.168.0.100] ([129.94.173.78] == sitcrc.cse.unsw.EDU.AU) (for ) (for ) By note With Smtp ; Wed, 5 May 2004 16:31:14 +1000 From: Justin Lipman To: manet@ietf.org, jw2000@excite.com Date: Wed, 5 May 2004 16:31:13 +1000 Reply-To: justin@titr.uow.edu.au Organization: CRC-SIT Subject: Re: [manet] Question about AODV User-Agent: KMail/1.6.2 References: <20040505052331.A8A7CB6AF@xprdmailfe15.nwk.excite.com> In-Reply-To: <20040505052331.A8A7CB6AF@xprdmailfe15.nwk.excite.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405051631.13279.justin@titr.uow.edu.au> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Jack, I think a possible answer to your question is as follows: Route error messages are unicast. Thus if node 5 sends a route error message back to node 2, it will know if node 2 does not receive the route error message and if it still has a link to node 2, then possibly (not sure in the current revision of aodv) it will try to send the route error message to 2 again. Now lets assume node 2 moves out of transmission range of node 5 and therefore node 5 cant communicate with node 2. Then I assume node 2 will determine a link error with node 5 and inform node 1. What happens to node 5, well it loses both links... possibly there is room for some local route repair? I havent kept up with the aodv spec... so maybe someone more knowledgeable will provide a better answer... :-) Cheers, Justin -- Research Associate Smart Internet Technology Cooperative Research Centre http://www.titr.uow.edu.au/~justin On Wed, 5 May 2004 03:23 pm, Jack Wang wrote: > Hi all, > > In AODV, when a node detects a link break, it sends an ERROR message to > nodes on its precursor list, so that the upstream nodes can know the broken > link and disable the relevant routes. > > For example, > > 1-----2----5---X---6 > > The original route is 1-2-5-6. Assume the link between 5 and 6 is down. > Node 5 will send ERROR to 2, then 2 sends ERROR to 1. But if due to some > reason, e.g., collision, node 2 does not receive node 5's ERROR message, 2 > will not disable the route. So both 1 and 2 store invalid route, which may > cause packet dropping. Is my analysis correct? How to prevent the above > problem? > > Thanks, > > Jack > > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > _______________________________________________ > 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 exim@www1.ietf.org Wed May 5 04:42:58 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00493 for ; Wed, 5 May 2004 04:42:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLHv7-00072K-Pe for manet-archive@odin.ietf.org; Wed, 05 May 2004 04:38:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i458cPRO027029 for manet-archive@odin.ietf.org; Wed, 5 May 2004 04:38:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLHlS-0003tE-Uh for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 04:28:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29687 for ; Wed, 5 May 2004 04:28:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLHlQ-0006zz-3Q for manet-web-archive@ietf.org; Wed, 05 May 2004 04:28:24 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLHkV-0006oG-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 04:27:28 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLHk1-0006cn-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 04:26:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLHXb-00006u-M8; Wed, 05 May 2004 04:14:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLHTI-00070J-45 for manet@optimus.ietf.org; Wed, 05 May 2004 04:09:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28886 for ; Wed, 5 May 2004 04:09:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLHTF-0003NR-3N for manet@ietf.org; Wed, 05 May 2004 04:09:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLHSC-00039m-00 for manet@ietf.org; Wed, 05 May 2004 04:08:33 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 1BLHRM-0002wE-00 for manet@ietf.org; Wed, 05 May 2004 04:07:40 -0400 Received: from ww2.telecom.lth.se (lina36.tts.lth.se [130.235.18.156]) by anyida.tts.lth.se (8.9.3/8.9.3) with SMTP id KAA08608; Wed, 5 May 2004 10:08:24 +0200 (MET DST) Received: from 130.235.18.83 (SquirrelMail authenticated user andersn) by ww2.telecom.lth.se with HTTP; Wed, 5 May 2004 10:05:51 +0200 (CEST) Message-ID: <32940.130.235.18.83.1083744351.squirrel@ww2.telecom.lth.se> In-Reply-To: <000701c4313c$bd8930a0$67f57b80@IEngr.ad.nmsu.edu> References: <6.1.0.6.2.20040503101025.04bde600@mira-sjc5-b.cisco.com> <000701c4313c$bd8930a0$67f57b80@IEngr.ad.nmsu.edu> Date: Wed, 5 May 2004 10:05:51 +0200 (CEST) Subject: RE: [manet] fixed nodes in ad hoc network From: "Anders Nilsson" To: "John Mullen" Cc: manet@ietf.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,PRIORITY_NO_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Here is an other paper that discuss routing in hybrid networks. The approach is a slightly different one; the routing protocol is signalling over the hybrid wired/wireless network, while the routing process itself takes place in the wireless domain. "Routing in hybrid ad hoc networks using service points", Nilsson, A, Garcia-Luna-Aceves, J.J, Spohn, M, Vehicular Technology Conference, 2003. VTC 2003-Fall. 2003 IEEE 58th http://ieeexplore.ieee.org/xpls/abs_all.jsp?isNumber=28570&prod=CNF&arnumber=1285391&arSt=+2078&ared=+2082&arAuthor=+Nilsson%2C+A.%3B++Garcia-Luna-Aceves%2C+J.J.%3B++Spohn%2C+M.&arNumber=1285391&a_id0=1285388&a_id1=1285389&a_id2=1285390&a_id3=1285391&a_id4=1285392&a_id5=1285393&a_id6=1285394&a_id7=1285395&a_id8=1285396&a_id9=1285397&a_id10=1285398&a_id11=1285399&a_id12=1285400&a_id13=1285401&a_id14=1285402&count=15 regards, Anders > Hi. > > I agree. There is one study I'm aware of in which the stationary nodes > were given information about other stationary nodes and that did improve > performance, but I don't think these nodes would necessarily know > anything important about the mobile nodes that they don't already know. > > The study was: "Implementation Experience with MANET Routing Protocols," > by Kwan-Wu Chin, John Judge, Aidan Williams and Roger Kermode. You can > get a copy at: > > http://www.acm.org/sigcomm/ccr/archive/ccr-toc/ccr-toc-2002.html > > John Mullen > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Fred Baker > Sent: Monday, May 03, 2004 10:15 AM > To: redouane > Cc: manet@ietf.org > Subject: Re: [manet] fixed nodes in ad hoc network > > > At 05:53 PM 05/03/04 +0200, redouane wrote: >>I am interested to routing protocols that use the >>fixed nodes informations to improve network traffic. > > I should think that in this environment, a fixed node is a mobile node > that > has higher bandwidth/higher availability links. It may be a very, > perhaps > the most, "mobile" node in a manet sense. consider a highway with manet > nodes traveling in both directions. From the point of view of a vehicle > headed south, the most "mobile" nodes (those that come and go most > rapidly) > are those headed north, the most "stable" nodes are the nodes headed > south > along with it, and the stationary nodes are simply changing neighbor > relationships half as rapidly as the vehicles. In this example, the > stationary nodes are pointless if they are located in a narrow valley, > but > can be tremendously useful if they are located on a hill or are orbiting > in > aircraft overhead. > > > _______________________________________________ > 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 exim@www1.ietf.org Wed May 5 05:27:50 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02262 for ; Wed, 5 May 2004 05:27:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLIWf-0000LH-2z for manet-archive@odin.ietf.org; Wed, 05 May 2004 05:17:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i459HCFL001275 for manet-archive@odin.ietf.org; Wed, 5 May 2004 05:17:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLIOD-0006k2-UA for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 05:08:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01346 for ; Wed, 5 May 2004 05:08:26 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLIOA-00074X-Q3 for manet-web-archive@ietf.org; Wed, 05 May 2004 05:08:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLINC-0006r4-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 05:07:27 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLIMH-0006fE-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 05:06:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLICC-0003IS-6t; Wed, 05 May 2004 04:56:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLI5o-0001jJ-Fq for manet@optimus.ietf.org; Wed, 05 May 2004 04:49:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00769 for ; Wed, 5 May 2004 04:49:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLI5l-0003SW-FK for manet@ietf.org; Wed, 05 May 2004 04:49:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLI4q-0003Fm-00 for manet@ietf.org; Wed, 05 May 2004 04:48:29 -0400 Received: from sam.comnets.uni-bremen.de ([134.102.186.10] helo=bugs.comnets.uni-bremen.de) by ietf-mx with esmtp (Exim 4.12) id 1BLI3p-00033N-00 for manet@ietf.org; Wed, 05 May 2004 04:47:25 -0400 Received: from scoobydoo (scoobydoo.comnets.uni-bremen.de [134.102.155.152]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id i458krm09735; Wed, 5 May 2004 10:46:53 +0200 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host scoobydoo.comnets.uni-bremen.de [134.102.155.152] claimed to be scoobydoo From: "Koojana Kuladinithi" To: , Subject: AW: [manet] Question about AODV Date: Wed, 5 May 2004 10:46:52 +0200 Message-ID: <000e01c4327d$830acb40$989b6686@scoobydoo> 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.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <20040505052331.A8A7CB6AF@xprdmailfe15.nwk.excite.com> Importance: Normal 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Jack > > For example, > > 1-----2----5---X---6 > > The original route is 1-2-5-6. Assume the link between 5 and 6 is down. > Node 5 will send ERROR to 2, then 2 sends ERROR to 1. > But if due to some reason, e.g., collision, node 2 does not receive node > 5's ERROR message, 2 will not disable the route. So both 1 and 2 store > invalid route, which may cause packet dropping. > Is my analysis correct? How to prevent the above problem? RFC 3561 (section 6.11) says that RERR will be generated if data comes to the invalid route if the node has not initiated the local repair. For your example, though the first RERR was not propagated to 2, node 5 has another opportunity to inform node 2 again with RERR, when its get data packets to 6. > > Thanks, > > Jack > > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > _______________________________________________ > 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 exim@www1.ietf.org Wed May 5 06:14:04 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04474 for ; Wed, 5 May 2004 06:14:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLJE6-0005Hc-OK for manet-archive@odin.ietf.org; Wed, 05 May 2004 06:02:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i45A265k020309 for manet-archive@odin.ietf.org; Wed, 5 May 2004 06:02:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLJCR-0004id-Pn for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 06:00:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03603 for ; Wed, 5 May 2004 06:00:20 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLJCO-0001gM-4Y for manet-web-archive@ietf.org; Wed, 05 May 2004 06:00:20 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLJ8e-0001BG-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 05:56:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLJ0U-00013f-5j; Wed, 05 May 2004 05:48:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLInN-0005aL-Ls for manet@optimus.ietf.org; Wed, 05 May 2004 05:34:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02600 for ; Wed, 5 May 2004 05:34:26 -0400 (EDT) From: jlee@vip.opnet.com Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLInK-0004gY-7P for manet@ietf.org; Wed, 05 May 2004 05:34:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLImH-0004Tc-00 for manet@ietf.org; Wed, 05 May 2004 05:33:22 -0400 Received: from plus.ds14.agh.edu.pl ([149.156.124.14] helo=ietf.org ident=coolj) by ietf-mx with esmtp (Exim 4.12) id 1BLIlJ-0004Go-00 for manet@ietf.org; Wed, 05 May 2004 05:32:21 -0400 To: manet@ietf.org Date: Wed, 5 May 2004 11:35:49 +0200 MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_001B_01C0CA80.6B015D10" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=6.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_SUSPECT_NAME, MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no version=2.60 X-Spam-Report: * 0.3 NO_REAL_NAME From: does not include a real name * 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL * 0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content * 0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program * 3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay * 1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE * 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer Subject: [manet] Mail Delivery (failure manet@ietf.org) 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_001B_01C0CA80.6B015D10 Content-Type: multipart/alternative; boundary="----=_NextPart_001_001C_01C0CA80.6B015D10" ------=_NextPart_001_001C_01C0CA80.6B015D10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_001_001C_01C0CA80.6B015D10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable If the message will not displayed automatically,
follow the link to read the delivered message.

Received message is available at:
www.ietf.org/inbox/manet/read.php?sessionid-11327
 
------=_NextPart_001_001C_01C0CA80.6B015D10-- ------=_NextPart_000_001B_01C0CA80.6B015D10 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit [Filename: message.scr, Content-Type: audio/x-wav] The attachment file in the message has been removed by eManager. ------=_NextPart_000_001B_01C0CA80.6B015D10-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 5 14:41:09 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03818 for ; Wed, 5 May 2004 14:41:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLRD7-0005o3-NF for manet-archive@odin.ietf.org; Wed, 05 May 2004 14:33:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i45IXbjx022320 for manet-archive@odin.ietf.org; Wed, 5 May 2004 14:33:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLR6S-00024u-FL for manet-web-archive@optimus.ietf.org; Wed, 05 May 2004 14:26:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02808 for ; Wed, 5 May 2004 14:26:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLR6P-00033o-TW for manet-web-archive@ietf.org; Wed, 05 May 2004 14:26:42 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLR4a-0002KP-00 for manet-web-archive@ietf.org; Wed, 05 May 2004 14:24:49 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BLR1h-0001Io-01 for manet-web-archive@ietf.org; Wed, 05 May 2004 14:21:49 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BLQmC-0007Yd-OX for manet-web-archive@ietf.org; Wed, 05 May 2004 14:05:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLQZy-0005L8-Sf; Wed, 05 May 2004 13:53:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLQVm-0002s9-TO for manet@optimus.ietf.org; Wed, 05 May 2004 13:48:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29199 for ; Wed, 5 May 2004 13:48:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLQVk-0007Yy-LK for manet@ietf.org; Wed, 05 May 2004 13:48:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLQUh-0007Fm-00 for manet@ietf.org; Wed, 05 May 2004 13:47:44 -0400 Received: from nn6.excitenetwork.com ([207.159.120.60] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BLQTh-0006k5-00 for manet@ietf.org; Wed, 05 May 2004 13:46:41 -0400 Received: by xprdmailfe17.nwk.excite.com (Postfix, from userid 110) id 53610B6EC; Wed, 5 May 2004 13:46:07 -0400 (EDT) To: justin@titr.uow.edu.au, manet@ietf.org, jw2000@excite.com Subject: Re: [manet] Question about AODV Received: from [204.198.72.206] by xprdmailfe17.nwk.excite.com via HTTP; Wed, 05 May 2004 13:46:07 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 89659a7ff4ddd332408b0a759a1a101b Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040505174607.53610B6EC@xprdmailfe17.nwk.excite.com> Date: Wed, 5 May 2004 13:46:07 -0400 (EDT) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.9 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Justin, Thanks for the comment. The current version of AODV code in NS2 still broadcast ERROR messages. I implement unicast for ERROR in AODV. But it can not completely eliminate the invalid routes. Some nodes still store broken routes. I think that it is possible unicast packet may be dropped, so some upstream nodes can not receive it. I do not know if my consideration is correct or not. Jack --- On Wed 05/05, Justin Lipman < justin@titr.uow.edu.au > wrote: From: Justin Lipman [mailto: justin@titr.uow.edu.au] To: manet@ietf.org, jw2000@excite.com Date: Wed, 5 May 2004 16:31:13 +1000 Subject: Re: [manet] Question about AODV Hi Jack,

I think a possible answer to your question is as follows:

Route error messages are unicast. Thus if node 5 sends a route error message
back to node 2, it will know if node 2 does not receive the route error
message and if it still has a link to node 2, then possibly (not sure in the
current revision of aodv) it will try to send the route error message to 2
again. Now lets assume node 2 moves out of transmission range of node 5 and
therefore node 5 cant communicate with node 2. Then I assume node 2 will
determine a link error with node 5 and inform node 1. What happens to node 5,
well it loses both links... possibly there is room for some local route
repair? I havent kept up with the aodv spec... so maybe someone more
knowledgeable will provide a better answer... :-)

Cheers,
Justin

--
Research Associate
Smart Internet Technology Cooperative Research Centre
http://www.titr.uow.edu.au/~justin
On Wed, 5 May 2004 03:23 pm, Jack Wang wrote:
> Hi all,
>
> In AODV, when a node detects a link break, it sends an ERROR message to
> nodes on its precursor list, so that the upstream nodes can know the broken
> link and disable the relevant routes.
>
> For example,
>
> 1-----2----5---X---6
>
> The original route is 1-2-5-6. Assume the link between 5 and 6 is down.
> Node 5 will send ERROR to 2, then 2 sends ERROR to 1. But if due to some
> reason, e.g., collision, node 2 does not receive node 5's ERROR message, 2
> will not disable the route. So both 1 and 2 store invalid route, which may
> cause packet dropping. Is my analysis correct? How to prevent the above
> problem?
>
> Thanks,
>
> Jack
>
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
>
> _______________________________________________
! > manet mailing list
> manet@ietf.org
> https://www1.ietf.org/ma ilman/listinfo/manet

_______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 6 03:54:59 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25141 for ; Thu, 6 May 2004 03:54:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLdbM-0006s4-Gy for manet-archive@odin.ietf.org; Thu, 06 May 2004 03:47:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i467lSlg026410 for manet-archive@odin.ietf.org; Thu, 6 May 2004 03:47:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLdWX-0005ts-Kq for manet-web-archive@optimus.ietf.org; Thu, 06 May 2004 03:42:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24556 for ; Thu, 6 May 2004 03:42:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLdWV-0002IX-CG for manet-web-archive@ietf.org; Thu, 06 May 2004 03:42:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLdVe-0001w7-00 for manet-web-archive@ietf.org; Thu, 06 May 2004 03:41:35 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLdUp-0001Zt-00 for manet-web-archive@ietf.org; Thu, 06 May 2004 03:40:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLdON-0002Pm-Hd; Thu, 06 May 2004 03:34:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLdLp-0000uZ-J6 for manet@optimus.ietf.org; Thu, 06 May 2004 03:31:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24045 for ; Thu, 6 May 2004 03:31:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLdLn-000691-9I for manet@ietf.org; Thu, 06 May 2004 03:31:23 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLdKt-0005oF-00 for manet@ietf.org; Thu, 06 May 2004 03:30:27 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 1BLdK5-00058E-00 for manet@ietf.org; Thu, 06 May 2004 03:29:38 -0400 Received: from ns.sait.samsung.co.kr (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 369AD1F431 for ; Thu, 6 May 2004 16:29:06 +0900 (KST) Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP; Thu, 06 May 2004 16:29:00 +0900 (KST) Received: from LocalHost (unknown [75.2.47.237]) by ns.sait.samsung.co.kr (Postfix) with SMTP id:11C8E1F46D for ; Thu, 6 May 2004 16:12:17 +0900 (KST) Message-ID: <001d01c43339$76fbea70$ed2f024b@LocalHost> From: "Jihoon Lee" To: Subject: [manet] Question about AODV Date: Thu, 6 May 2004 16:12:17 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01C43384.E6C9A1D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.2 required=5.0 tests=FORGED_OUTLOOK_TAGS, MIME_BASE64_TEXT autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_001A_01C43384.E6C9A1D0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 SGkgYWxsLA0KDQpJbiBBT0RWLCBBIG5vZGUgTUFZIG9mZmVyIGNvbm5lY3Rpdml0eSBpbmZvcm1h dGlvbiBieSBicm9hZGNhc3RpbmcgbG9jYWwgSGVsbG8gbWVzc2FnZXMuDQoNCkluIHRoZSBzcGVj LiwgdGhlIGZvbGxvd2luZyBzZW50ZW5jZSBpcyBwcmVzZW50ZWQuIA0KIkEgbm9kZSBTSE9VTEQg b25seSB1c2UgaGVsbG8gbWVzc2FnZXMgaWYgaXQgaXMgcGFydCBvZiBhbiBhY3RpdmUgcm91dGUu Ig0KDQpJIHRoaW5rIHRoZSBzZW50ZW5jZSBjYW4gaGF2ZSB0aGUgb25lIG1lYW5pbmcgb2YgdGhl IGZvbGxvd2luZ3M6DQoxLiBFdmVuIGlmIHRoZSBub2RlIGRvZXMgbm90IGhhdmUgYW55IGFjdGl2 ZSByb3V0ZSBpbmZvcm1hdGlvbiwgdGhlIG5vZGUgc2hvdWxkIHBlcmlvZGljYWxseSBzZW5kIEhl bGxvIG1lc3NhZ2UgdG8gdGhlIG5laWdoYm9ycy4gVGhhdCBpcywgZXZlcnkgbm9kZSBjYW4gc2Vu ZCBIZWxsbyBtZXNzYWdlcy4NCjIuIE9ubHkgbm9kZXMgd2l0aCBhY3RpdmUgcm91dGVzIGNhbiBz ZW5kIEhlbGxvIG1lc3NhZ2UgdG8gdGhlIG5laWdoYm9ycy4NCg0KV2hpY2ggb25lIGlzIGNvcnJl Y3Q/DQoNClRoYW5rcywNCg0KSmlob29uIExlZQ== ------=_NextPart_000_001A_01C43384.E6C9A1D0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA2LjAwLjI4MDAuMTQwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+SGkgYWxsLDxCUj48QlI+SW4gQU9E ViwgQSBub2RlIE1BWSBvZmZlciBjb25uZWN0aXZpdHkgaW5mb3JtYXRpb24gYnkgDQpicm9hZGNh c3RpbmcgbG9jYWwgSGVsbG8mbmJzcDttZXNzYWdlcy48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+ DQo8RElWPkluIHRoZSBzcGVjLiwgdGhlIGZvbGxvd2luZyBzZW50ZW5jZSBpcyBwcmVzZW50ZWQu IDwvRElWPg0KPERJVj4iQSBub2RlIFNIT1VMRCBvbmx5IHVzZSBoZWxsbyBtZXNzYWdlcyBpZiBp dCBpcyBwYXJ0IG9mIGFuJm5ic3A7YWN0aXZlIA0Kcm91dGUuIjwvRElWPg0KPERJVj48Rk9OVCBz aXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj5JIHRoaW5rIHRoZSBzZW50ZW5jZSBjYW4g aGF2ZSB0aGUgb25lIG1lYW5pbmcgb2YgdGhlIGZvbGxvd2luZ3M6PC9ESVY+DQo8RElWPjEuIEV2 ZW4gaWYgdGhlIG5vZGUgZG9lcyBub3QgaGF2ZSBhbnkgYWN0aXZlIHJvdXRlIGluZm9ybWF0aW9u LCZuYnNwO3RoZSANCm5vZGUgc2hvdWxkIHBlcmlvZGljYWxseSBzZW5kIEhlbGxvIG1lc3NhZ2Ug dG8gdGhlIG5laWdoYm9ycy4gVGhhdCBpcywgZXZlcnkgDQpub2RlIGNhbiBzZW5kIEhlbGxvIG1l c3NhZ2VzLjwvRElWPg0KPERJVj4yLiBPbmx5IG5vZGVzIHdpdGggYWN0aXZlIHJvdXRlcyBjYW4g c2VuZCBIZWxsbyBtZXNzYWdlIHRvIHRoZSANCm5laWdoYm9ycy48L0RJVj4NCjxESVY+PEZPTlQg c2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+V2hpY2ggb25lIGlzIGNvcnJlY3Q/PC9E SVY+DQo8RElWPjxCUj5UaGFua3MsPEJSPjxCUj5KaWhvb24gTGVlPC9ESVY+PC9CT0RZPjwvSFRN TD4NCg== ------=_NextPart_000_001A_01C43384.E6C9A1D0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 6 04:54:47 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28509 for ; Thu, 6 May 2004 04:54:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLeVx-0006VC-AF for manet-archive@odin.ietf.org; Thu, 06 May 2004 04:45:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i468jv6l024995 for manet-archive@odin.ietf.org; Thu, 6 May 2004 04:45:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLeTx-0004nz-KN for manet-web-archive@optimus.ietf.org; Thu, 06 May 2004 04:43:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27840 for ; Thu, 6 May 2004 04:43:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLeTk-0002F6-S5 for manet-web-archive@ietf.org; Thu, 06 May 2004 04:43:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLeSi-0001og-00 for manet-web-archive@ietf.org; Thu, 06 May 2004 04:42:37 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLeRo-0001Pn-00 for manet-web-archive@ietf.org; Thu, 06 May 2004 04:41:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLeKX-0001R2-8f; Thu, 06 May 2004 04:34:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLeBC-0005mf-Js for manet@optimus.ietf.org; Thu, 06 May 2004 04:24:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27062 for ; Thu, 6 May 2004 04:24:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLeB9-0002q1-Qz for manet@ietf.org; Thu, 06 May 2004 04:24:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLeAR-0002Ua-00 for manet@ietf.org; Thu, 06 May 2004 04:23:43 -0400 Received: from evaki.its.uow.edu.au ([130.130.68.32]) by ietf-mx with esmtp (Exim 4.12) id 1BLe9i-00027R-00 for manet@ietf.org; Thu, 06 May 2004 04:22:58 -0400 Received: from evaki (localhost [127.0.0.1]) by evaki.its.uow.edu.au (8.12.9/8.12.9) with ESMTP id i468Ms32026567; Thu, 6 May 2004 18:22:54 +1000 (EST) Received: from inti.its.uow.edu.au ([130.130.37.4]) by evaki.its.uow.edu.au (MailMonitor for SMTP v1.2.2 ) ; Thu, 6 May 2004 18:22:54 +1000 (EST) Received: from sendmail by inti.its.uow.edu.au with local (Exim 4.30) id 1BLe9d-0006j2-V7; Thu, 06 May 2004 18:22:53 +1000 Received: from eros.snrc.uow.edu.au (eros.snrc.uow.edu.au[130.130.10.74]) by inti.its.uow.edu.au (UWSMTPD 1.61) with ESMTP id 1701337.25825; Thursday, 06 May 2004 18:22:49 +1000 From: Mehran Abolhasan To: "Jihoon Lee" , Subject: Re: [manet] Question about AODV Date: Thu, 6 May 2004 18:23:28 +1000 User-Agent: KMail/1.5.3 References: <001d01c43339$76fbea70$ed2f024b@LocalHost> In-Reply-To: <001d01c43339$76fbea70$ed2f024b@LocalHost> MIME-Version: 1.0 Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200405061823.28437.mehrana@uow.edu.au> X-MessageID: 1701337.25825 X-EnvelopeFrom: 1701337.25825 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I think the second one is correct. This is done to reduce the amount of overhead introduced by hello messages and reduce redundancy. It can also be used to detect if a node in an active route has become inactive. -- Mehran Abolhasan B.E Computer, PhD Smart Internet Technology CRC (SITCRC) Research Fellow Telecommunications and IT Research Institute (TITR) University of Wollongong Northfields Avenue, NSW, 2522, Australia Phone: +61 2 4221 5491 Fax: +61 2 4221 3277 Email 1: mehrana@uow.edu.au Email 2: mehran@titr.uow.edu.au On Thu, 6 May 2004 05:12 pm, Jihoon Lee wrote: > Hi all, > > In AODV, A node MAY offer connectivity information by broadcasting local > Hello messages. > > In the spec., the following sentence is presented. > "A node SHOULD only use hello messages if it is part of an active route." > > I think the sentence can have the one meaning of the followings: > 1. Even if the node does not have any active route information, the node > should periodically send Hello message to the neighbors. That is, every > node can send Hello messages. 2. Only nodes with active routes can send > Hello message to the neighbors. > > Which one is correct? > > Thanks, > > Jihoon Lee _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 7 00:05:10 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09342 for ; Fri, 7 May 2004 00:05:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLwaN-0002Uz-Ff for manet-archive@odin.ietf.org; Fri, 07 May 2004 00:03:44 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4743hJY009605 for manet-archive@odin.ietf.org; Fri, 7 May 2004 00:03:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLwZ1-0001rH-Rm for manet-web-archive@optimus.ietf.org; Fri, 07 May 2004 00:02:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09221 for ; Fri, 7 May 2004 00:02:16 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLwYz-0007Ag-Lg for manet-web-archive@ietf.org; Fri, 07 May 2004 00:02:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLwXz-0006kC-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 00:01:16 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLwWu-0005wm-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 00:00:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLwQ1-00088y-Fg; Thu, 06 May 2004 23:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLwNN-0007Sb-P8 for manet@optimus.ietf.org; Thu, 06 May 2004 23:50:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08703 for ; Thu, 6 May 2004 23:50:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLwNL-000277-KI for manet@ietf.org; Thu, 06 May 2004 23:50:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLwMS-0001hL-00 for manet@ietf.org; Thu, 06 May 2004 23:49:21 -0400 Received: from [203.197.98.27] (helo=sandesh.iitkgp.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 1BLwLM-0007Tf-00 for manet@ietf.org; Thu, 06 May 2004 23:48:12 -0400 Received: from ece.iitkgp.ernet.in (localhost [127.0.0.1]) by iitkgp.iitkgp.ernet.in (8.9.3/8.9.3) with ESMTP id JAA23190 for ; Fri, 7 May 2004 09:04:50 -0500 (GMT) X-Authentication-Warning: iitkgp.iitkgp.ernet.in: iscan owned process doing -bs Received: from localhost (rkc@localhost) by ece.iitkgp.ernet.in (8.9.3/8.8.7) with ESMTP id JAA01552 for ; Fri, 7 May 2004 09:18:31 +0400 Date: Fri, 7 May 2004 09:18:31 +0400 (RET) From: "C.Rama Krishna" To: manet@ietf.org In-Reply-To: <20040506160011.14846.8285.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re: manet digest, Vol 1 #834 - 3 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 *********************************************** This Mail is Certified to be Virus Free. CIC Network Security Group, IIT Kharagpur *********************************************** **************************************************** This Mail is certifiled to be Virus Free CIC Network Security Group **************************************************** Hi, I am using GloMoSim 2.03 for my work. can anyone tell me about how given node say X is in the range of another node say Y,Z,and so on... ? I mean where exactly (which file should I like into) the range of nodes is calculated during simulation time? In fact, radio_range.exe gives me the Tx range of all nodes, but it does not say how the range of a node is calculated during simulation. Any help on this is appreciated. Thanks. **************************************************************************** C.Rama Krishna, R/S,E & ECE Department, Indian Institute of Technology, KHARAGPUR - 721 302 India. Phone: 91-3222-281500 **************************************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 7 03:49:24 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03138 for ; Fri, 7 May 2004 03:49:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM04K-0003DX-Ku for manet-archive@odin.ietf.org; Fri, 07 May 2004 03:46:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i477kqBk012346 for manet-archive@odin.ietf.org; Fri, 7 May 2004 03:46:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLzyq-0001SP-8T for manet-web-archive@optimus.ietf.org; Fri, 07 May 2004 03:41:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02588 for ; Fri, 7 May 2004 03:41:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLzyn-0003qW-RR for manet-web-archive@ietf.org; Fri, 07 May 2004 03:41:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLzwT-0003OT-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 03:38:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLzvI-0002wW-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 03:37:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLzn4-0005Qb-SO; Fri, 07 May 2004 03:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLzhn-0003q2-MU for manet@optimus.ietf.org; Fri, 07 May 2004 03:23:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01802 for ; Fri, 7 May 2004 03:23:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLzhl-0004vt-Ap for manet@ietf.org; Fri, 07 May 2004 03:23:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLzgp-0004Wb-00 for manet@ietf.org; Fri, 07 May 2004 03:22:36 -0400 Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27] helo=i2r.a-star.edu.sg) by ietf-mx with esmtp (Exim 4.12) id 1BLzfz-00046j-00 for manet@ietf.org; Fri, 07 May 2004 03:21:44 -0400 Received: from newmailhost (localhost [127.0.0.1]) by i2r.a-star.edu.sg (8.12.10/8.12.10) with ESMTP id i477LNTC014550 for ; Fri, 7 May 2004 15:21:23 +0800 (SGT) Received: from localhost.localdomain ([192.168.152.135]) by mailhost.lit.org.sg (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0HXC009Z71RXAJ@mailhost.lit.org.sg> for manet@ietf.org; Fri, 07 May 2004 15:21:36 +0800 (SGT) Received: by localhost.localdomain (Postfix, from userid 1000) id 5E58D30C2D; Fri, 07 May 2004 15:21:29 +0800 (SGT) Date: Fri, 07 May 2004 15:21:29 +0800 From: "Sukanta K. Hazra" Subject: Re: [manet] Re: manet digest, Vol 1 #834 - 3 msgs In-reply-to: To: "C.Rama Krishna" Cc: manet@ietf.org Mail-followup-to: "C.Rama Krishna" , manet@ietf.org Message-id: <20040507072129.GA28160@i2r.a-star.edu.sg> Organization: Institute for Infocomm Research MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline PGP-ID: 0x8E084AD5 Key-Fingerprint: 9C0D B00C C62A 7059 5314 99FC CE90 478A 8E08 4AD5 User-Agent: Mutt/1.5.4i References: <20040506160011.14846.8285.Mailman@www1.ietf.org> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT > I am using GloMoSim 2.03 for my work. can anyone tell me about how given > node say X is in the range of another node say Y,Z,and so on... ? I mean > where exactly (which file should I like into) the range of nodes is > calculated during simulation time? In fact, radio_range.exe gives me the > Tx range of all nodes, but it does not say how the range of a node is > calculated during simulation. Any help on this is appreciated. > Depends on the pathloss model used, the transmission power, and the threshold SNR of the receiver. Look into the radio subdirectory for pathloss models. Try posting to the glomosim list for more information. - Sukanta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 7 11:13:27 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29993 for ; Fri, 7 May 2004 11:13:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6e1-0006TZ-Ms for manet-archive@odin.ietf.org; Fri, 07 May 2004 10:48:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47Em95B024876 for manet-archive@odin.ietf.org; Fri, 7 May 2004 10:48:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6Vb-00039a-Ck for manet-web-archive@optimus.ietf.org; Fri, 07 May 2004 10:39:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26740 for ; Fri, 7 May 2004 10:39:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM6VZ-0002EP-3a for manet-web-archive@ietf.org; Fri, 07 May 2004 10:39:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM6U3-0001bq-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 10:37:52 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM6Rr-0000dD-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 10:35:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM5vx-0001Hy-5R; Fri, 07 May 2004 10:02:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM4Vw-0003sr-SN for manet@optimus.ietf.org; Fri, 07 May 2004 08:31:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18390 for ; Fri, 7 May 2004 08:31:38 -0400 (EDT) From: shyama@cc.iitkgp.ernet.in Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM4Vv-0000do-MX for manet@ietf.org; Fri, 07 May 2004 08:31:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM4V1-0000EH-00 for manet@ietf.org; Fri, 07 May 2004 08:30:43 -0400 Received: from [203.197.98.4] (helo=avmx.iitkgp.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 1BM4Tw-0005yO-00 for manet@ietf.org; Fri, 07 May 2004 08:29:37 -0400 Received: from localhost (shyama@localhost) by cc.iitkgp.ernet.in (8.11.2/8.11.2) with ESMTP id i47Cat415081 for ; Fri, 7 May 2004 18:06:55 +0530 Date: Fri, 7 May 2004 18:06:55 +0530 (IST) To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] NO NAV on 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,DEAR_SOMETHING, NO_REAL_NAME autolearn=no version=2.60 *********************************************** This Mail is Certified to be Virus Free. CIC Network Security Group, IIT Kharagpur *********************************************** **************************************************** This Mail is certifiled to be Virus Free CIC Network Security Group **************************************************** Dear Sir, I have been looking for any comperative study available between the "normal CSMA/CA protocol" and "CSMA/CA with no NAV on CTS". Regards, shyam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 7 12:52:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05012 for ; Fri, 7 May 2004 12:52:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM8Rs-0005ON-KE for manet-archive@odin.ietf.org; Fri, 07 May 2004 12:43:44 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47GhipP020727 for manet-archive@odin.ietf.org; Fri, 7 May 2004 12:43:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM8MO-0003gc-Rs for manet-web-archive@optimus.ietf.org; Fri, 07 May 2004 12:38:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04277 for ; Fri, 7 May 2004 12:38:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM8MN-000195-6a for manet-web-archive@ietf.org; Fri, 07 May 2004 12:38:03 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM8LS-0000hg-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 12:37:07 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM8Kg-0000Gr-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 12:36:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM89m-0007Pj-5W; Fri, 07 May 2004 12:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM7tB-0000Y1-Pi for manet@optimus.ietf.org; Fri, 07 May 2004 12:07:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02959 for ; Fri, 7 May 2004 12:07:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM7tA-0003T8-Et for manet@ietf.org; Fri, 07 May 2004 12:07:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM7sD-00033M-00 for manet@ietf.org; Fri, 07 May 2004 12:06:54 -0400 Received: from snowhite.cis.uoguelph.ca ([131.104.48.1]) by ietf-mx with esmtp (Exim 4.12) id 1BM7rH-0002cw-00 for manet@ietf.org; Fri, 07 May 2004 12:05:55 -0400 Received: from localhost (denko@localhost) by snowhite.cis.uoguelph.ca (8.9.3/8.9.3) with ESMTP id MAA58751 for ; Fri, 7 May 2004 12:05:17 -0400 (EDT) Date: Fri, 7 May 2004 12:05:17 -0400 (EDT) From: Mieso Denko To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] First Announcement and Call for Papers 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 --- ----------------------------------------------------------------------- (** Our apologies if you receive multiple copies of this message **) First Announcement and Call for Papers The 3rd Workshop on the Internet, Telecommunications and Signal Processing WITSP'2004 Adelaide, Australia, 20-22 December 2004 Workshop website: http://www.dspcs-witsp.com/WITSP_04/CFP.html -------------------------------------------------------------------------- After the success of two previous Workshops, held in Wollongong in 2002 and Coolangatta in 2003, the Organising Committee decided to hold the 3rd Workshop on the Internet, Telecommunications and Signal Processing, WITSP'04 at Stamford Grand Hotel in Adelaide. The topics of interest range from those of the physical layer to the application layer through all aspects of the protocols and processes required for the future Internet to operate better and the applications to utilise the full potential offered by the current and the emerging networking infrastructure. Previously unpublished contributions to the following technical areas, but not limited to, are solicited: ----------------------------------------------------------------------- Internet * Traffic modelling * Protocols * Embedded Internet devices * New and enhanced services * Resource and information management * Adaptive QoS provisioning * End-to-end QoS * Internet2 Wireless Networks * Mobile ad hoc networking * Personal area networking * Convergence of different network types * Broadband Wireless Access * Vertical handovers * IP and Mobility * Home networking Network Security * Security primitives and algorithms * Security of wireless and distribution networks * Programmable networks security * Authentication and authorization Fixed networks * Optical networks and switching * Network architectures and equipment * Programmable networks * Access technologies * Test-beds and trials Telecommunication technology * Channel measurements and characterisation * Coding and modulation techniques * Modelling and simulation * Spread Spectrum and CDMA systems * OFDM technology * Space-time coding Multimedia signal processing * Streamed multimedia applications * Algorithms and implementations * Image and video processing * Error concealment techniques ------------------------------------------------------------------------- The procedure for submitting papers will be announced shortly. Each paper of up to 6 double column pages of A4 (single space, font size 10 points minimum) will be peer-reviewed by two independent reviewers and the authors will be notified about the acceptance via email. Important Dates: ---------------- * Full Paper Submission Deadline: 30 July 2004 * Notification of acceptance: 15 September 2004 * Camera-Ready Copy: 15 October 2004 * Registration: 15 October 2004 For further information please contact: Assoc. Prof. T Wysocki Fax: +61 2 4285 7576, E-mail: chair@dspcs-witsp.com -------------------------------------------------------------------------- Organising Committee -------------------- Arek Dadej, University of South Australia Jennifer Seberry, University of Wollongong Lang White, University of Adelaide Beata Wysocki, University of Wollongong Tadeusz Wysocki, University of Wollongong - Chairman Hans-Juergen Zepernick, Western Australian Telecommunications Research Institute Technical Program Committee --------------------------- Jean Armstrong, La Trobe University Arek Dadej, University of South Australia Mieso Denko, University of Guelph Peter Farkas, Slovak Technical University Alfred Mertins, University of Oldenburg Jennifer Seberry, University of Wollongong Miroslaw Slominski, Warsaw University of Technology Lang White, University of Adelaide Hamid Sharif, University of Nebraska-Lincoln Beata Wysocki, University of Wollongong Tadeusz Wysocki, University of Wollongong Hans-Juergen Zepernick, Western Australian Telecommunications Research Institute _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 7 20:07:04 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29575 for ; Fri, 7 May 2004 20:07:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMFGg-0005s2-LU for manet-archive@odin.ietf.org; Fri, 07 May 2004 20:00:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4800cmV022567 for manet-archive@odin.ietf.org; Fri, 7 May 2004 20:00:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMFGN-0005bf-Mh for manet-web-archive@optimus.ietf.org; Fri, 07 May 2004 20:00:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29362 for ; Fri, 7 May 2004 20:00:17 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BMFGL-0007OA-SE for manet-web-archive@ietf.org; Fri, 07 May 2004 20:00:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BMFFO-0006wX-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 19:59:18 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BMFEp-0006WA-00 for manet-web-archive@ietf.org; Fri, 07 May 2004 19:58:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMF8M-0003RH-O8; Fri, 07 May 2004 19:52:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMF5d-0002ev-Da for manet@optimus.ietf.org; Fri, 07 May 2004 19:49:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29031 for ; Fri, 7 May 2004 19:49:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BMF5b-0002jT-Kn for manet@ietf.org; Fri, 07 May 2004 19:49:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BMF4l-0002HH-00 for manet@ietf.org; Fri, 07 May 2004 19:48:20 -0400 Received: from auds953.usa.alcatel.com ([143.209.238.6]) by ietf-mx with esmtp (Exim 4.12) id 1BMF3e-0001Rl-00 for manet@ietf.org; Fri, 07 May 2004 19:47:10 -0400 Received: from alcatel.com (localhost [127.0.0.1]) by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i47NkeFq015759 for ; Fri, 7 May 2004 18:46:40 -0500 (CDT) Message-ID: <409C210B.CC432A3B@alcatel.com> Date: Fri, 07 May 2004 18:51:39 -0500 From: Tim Ozugur X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] BroadNets 2004: Call for "Work-in-Progress" Poster Papers 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit (Apologies if you are receiving this message more than once) ------------------------------------------------------------ Call for "Work-in-Progress" Poster Papers BroadNets 2004 - Wireless Networking Symposium October 25 - 29, 2004, San Jose, California, USA http://www.broadnets.org BroadNets 2004, the first international conference on broadband networks will be held during October 25-29 in the heart of Silicon Valley -- San Jose, CA. Technical paper submission is now closed. To allow the presentation of recent results and/or research work in progress, BroadNets 2004 Wireless Networking Symposium solicits poster papers demonstrating state-of-the-art research in broadly defined wireless networking area. Poster papers, not previously published, should be a maximum of 3 pages in length (in double column, 10 point font) and will be published in thenbconference proceedings by IEEE Computer Society. Poster submissions will be reviewed. Important dates: - Deadline for submitting a work-in-progress poster paper: June 1, 2004. - Notification of acceptance: June 15, 2004. - Final manuscript due: July 7, 2004. Authors are invited to submit poster papers directly to TPC co-chairs, Dr.Parmesh Ramanathan (parmesh@ece.wisc.edu) and Dr. Thomas Hou (thou@vt.edu). All submissions should be in Postscript or Adobe PDF format. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 10 16:05:26 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00241 for ; Mon, 10 May 2004 16:05:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGuI-0006v6-Rd for manet-archive@odin.ietf.org; Mon, 10 May 2004 15:57:46 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJvkmu026600 for manet-archive@odin.ietf.org; Mon, 10 May 2004 15:57:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGmv-0005kk-Ax for manet-web-archive@optimus.ietf.org; Mon, 10 May 2004 15:50:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29151 for ; Mon, 10 May 2004 15:50:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNGmt-0001jv-TJ for manet-web-archive@ietf.org; Mon, 10 May 2004 15:50:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNGlr-0001MH-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 15:49:03 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNGks-00010z-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 15:48:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGeA-0004DA-M4; Mon, 10 May 2004 15:41:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGWf-000262-Ck for manet@optimus.ietf.org; Mon, 10 May 2004 15:33:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27956 for ; Mon, 10 May 2004 15:33:18 -0400 (EDT) From: sallyhan@rogers.com Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNGWe-0003Ua-29 for manet@ietf.org; Mon, 10 May 2004 15:33:20 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNGVz-00039m-00 for manet@ietf.org; Mon, 10 May 2004 15:32:39 -0400 Received: from fep01-mail.bloor.is.net.cable.rogers.com ([66.185.86.71]) by ietf-mx with esmtp (Exim 4.12) id 1BNGV3-0002ik-00 for manet@ietf.org; Mon, 10 May 2004 15:31:41 -0400 Received: from localhost ([127.0.0.1]) by fep01-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040510192916.QILY82372.fep01-mail.bloor.is.net.cable.rogers.com@localhost> for ; Mon, 10 May 2004 15:29:16 -0400 X-Mailer: Openwave WebEngine, version 2.8.11 (webedge20-101-194-20030622) To: Date: Mon, 10 May 2004 15:29:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep01-mail.bloor.is.net.cable.rogers.com from [127.0.0.1] using ID at Mon, 10 May 2004 15:29:16 -0400 Message-Id: <20040510192916.QILY82372.fep01-mail.bloor.is.net.cable.rogers.com@localhost> Content-Transfer-Encoding: 7bit Subject: [manet] data replication 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello everyone, I'm a new research student focusing on data replication in MANET. I may work on improving data accessibility and maintaining data consistency through replication in MANET. I would like to know if anyone is doing related work in this area or know of any good sources of information. Thanks Regards sally Han 1 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 10 17:22:07 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06660 for ; Mon, 10 May 2004 17:22:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNI4x-0002jb-9w for manet-archive@odin.ietf.org; Mon, 10 May 2004 17:12:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ALCphD010508 for manet-archive@odin.ietf.org; Mon, 10 May 2004 17:12:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNHXQ-0006xe-JF for manet-web-archive@optimus.ietf.org; Mon, 10 May 2004 16:38:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02175 for ; Mon, 10 May 2004 16:38:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNHXO-0002xY-KD for manet-web-archive@ietf.org; Mon, 10 May 2004 16:38:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNHWU-0002c1-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 16:37:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNHVe-0002H8-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 16:36:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNHOX-0004rO-BY; Mon, 10 May 2004 16:29:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNHE3-0002Xm-1y for manet@optimus.ietf.org; Mon, 10 May 2004 16:18:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00790 for ; Mon, 10 May 2004 16:18:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNHE1-0003OC-7K for manet@ietf.org; Mon, 10 May 2004 16:18:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNHC6-00030l-00 for manet@ietf.org; Mon, 10 May 2004 16:16:10 -0400 Received: from vitalstatistix.cs.uoregon.edu ([128.223.4.19] helo=cs.uoregon.edu ident=root) by ietf-mx with esmtp (Exim 4.12) id 1BNHBN-0002gD-00 for manet@ietf.org; Mon, 10 May 2004 16:15:25 -0400 Received: from ix.cs.uoregon.edu (manoj@ix.cs.uoregon.edu [128.223.4.21]) by cs.uoregon.edu (8.12.11/8.12.11) with ESMTP id i4AKF0Nv020676 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 May 2004 13:15:01 -0700 (PDT) Date: Mon, 10 May 2004 13:15:00 -0700 (PDT) From: Manoj K Pandey To: "C.Rama Krishna" cc: manet@ietf.org Subject: Re: [manet] Re: manet digest, Vol 1 #834 - 3 msgs In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: clamd / ClamAV version 0.70-rc, clamav-milter version 0.70 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 hi Rama, Distance is estimated in radio/propagation.pc file, upon which depending upon the model ones uses, path_loss for that distance is estimated. Estimated path_loss is then substraced from the tranmission power to estimate the signal at the receiver. If this signal level is less than the propagation limit (specified in the config.in input file) then the receiver is presumed to be non_reachable. hope I wasn't too late in replying! -manoj ****************************** Manoj Pandey, PhD student, #207C, Network Research Lab, Deschutes, Computer and Information Science, University of Oregon, Phone# 541-346-0892 [Office], www.cs.uoregon.edu/~manoj ****************************** On Fri, 7 May 2004, C.Rama Krishna wrote: > *********************************************** > This Mail is Certified to be Virus Free. > > CIC Network Security Group, IIT Kharagpur > *********************************************** > > **************************************************** > This Mail is certifiled to be Virus Free > > CIC Network Security Group > **************************************************** > > Hi, > > I am using GloMoSim 2.03 for my work. can anyone tell me about how given > node say X is in the range of another node say Y,Z,and so on... ? I mean > where exactly (which file should I like into) the range of nodes is > calculated during simulation time? In fact, radio_range.exe gives me the > Tx range of all nodes, but it does not say how the range of a node is > calculated during simulation. Any help on this is appreciated. > > Thanks. > > > **************************************************************************** > C.Rama Krishna, > R/S,E & ECE Department, > Indian Institute of Technology, > KHARAGPUR - 721 302 > India. > > Phone: 91-3222-281500 > **************************************************************************** > > > > > > > _______________________________________________ > 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 exim@www1.ietf.org Mon May 10 18:23:10 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12076 for ; Mon, 10 May 2004 18:23:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNJ4f-000860-81 for manet-archive@odin.ietf.org; Mon, 10 May 2004 18:16:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AMGblc031112 for manet-archive@odin.ietf.org; Mon, 10 May 2004 18:16:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNIuu-0002cc-UD for manet-web-archive@optimus.ietf.org; Mon, 10 May 2004 18:06:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10198 for ; Mon, 10 May 2004 18:06:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNIus-0003jl-75 for manet-web-archive@ietf.org; Mon, 10 May 2004 18:06:30 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNItx-0003LT-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 18:05:33 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNIss-0002uZ-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 18:04:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNId0-0004cp-FM; Mon, 10 May 2004 17:48:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNIZL-00035n-F4 for manet@optimus.ietf.org; Mon, 10 May 2004 17:44:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08486 for ; Mon, 10 May 2004 17:44:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNIZI-0003kK-SE for manet@ietf.org; Mon, 10 May 2004 17:44:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNIYN-0003Ot-00 for manet@ietf.org; Mon, 10 May 2004 17:43:15 -0400 Received: from smtp2.stanford.edu ([171.67.16.125]) by ietf-mx with esmtp (Exim 4.12) id 1BNIXi-000327-00 for manet@ietf.org; Mon, 10 May 2004 17:42:34 -0400 Received: from saga17.Stanford.EDU (saga17.Stanford.EDU [171.64.15.147]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i4ALg4lg009532; Mon, 10 May 2004 14:42:04 -0700 Received: (from mukesh@localhost) by saga17.Stanford.EDU (8.12.10/8.12.9) id i4ALg3Cb021600; Mon, 10 May 2004 14:42:03 -0700 (PDT) Date: Mon, 10 May 2004 14:42:03 -0700 (PDT) From: Mukesh Hira To: sallyhan@rogers.com cc: manet@ietf.org Subject: Re: [manet] data replication in MANET In-Reply-To: <20040510192916.QILY82372.fep01-mail.bloor.is.net.cable.rogers.com@localhost> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Check out the MONET research group at UIUC (http://cairo.cs.uiuc.edu/adhoc/accessibility/) - Mukesh On Mon, 10 May 2004 sallyhan@rogers.com wrote: > Hello everyone, > > I'm a new research student focusing on data replication in MANET. I may work on improving data accessibility and maintaining data consistency through replication in MANET. I would like to know if anyone is doing related work in this area or know of any good sources of information. > > Thanks > > Regards > > sally Han > > > 1 > > > _______________________________________________ > 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 exim@www1.ietf.org Mon May 10 20:08:27 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17704 for ; Mon, 10 May 2004 20:08:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKgM-0006nJ-HC for manet-archive@odin.ietf.org; Mon, 10 May 2004 19:59:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ANxctt026118 for manet-archive@odin.ietf.org; Mon, 10 May 2004 19:59:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKd1-0005oz-Bd for manet-web-archive@optimus.ietf.org; Mon, 10 May 2004 19:56:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17194 for ; Mon, 10 May 2004 19:56:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNKcz-0003N9-JS for manet-web-archive@ietf.org; Mon, 10 May 2004 19:56:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNKc3-00032O-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 19:55:12 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNKb9-0002iG-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 19:54:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKSF-0003aT-1e; Mon, 10 May 2004 19:45:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKJm-0001pu-1d for manet@optimus.ietf.org; Mon, 10 May 2004 19:36:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16490 for ; Mon, 10 May 2004 19:36:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNKJk-0004Pw-8M for manet@ietf.org; Mon, 10 May 2004 19:36:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNKIj-00045B-00 for manet@ietf.org; Mon, 10 May 2004 19:35:13 -0400 Received: from ocean.ise.eng.osaka-u.ac.jp ([133.1.172.134]) by ietf-mx with smtp (Exim 4.12) id 1BNKI7-0003bp-00 for manet@ietf.org; Mon, 10 May 2004 19:34:35 -0400 Received: (qmail 29904 invoked from network); 11 May 2004 08:15:55 +0900 Received: from unknown (HELO localhost) (127.0.0.1) by 0 with SMTP; 11 May 2004 08:15:55 +0900 Date: Tue, 11 May 2004 08:33:59 +0900 From: Takahiro Hara X-Mailer: EdMax Ver2.85.5F MIME-Version: 1.0 To: sallyhan@rogers.com Cc: Subject: Re: [manet] data replication in MANET Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: <20040510192916.QILY82372.fep01-mail.bloor.is.net.cable.rogers.com@localhost> References: <20040510192916.QILY82372.fep01-mail.bloor.is.net.cable.rogers.com@localhost> Message-Id: 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Sally, I'm working on the research topic for improving data accessibility through replication in MANET. Some of my papers on this topic are listed below: T. Hara, ``Effective replica allocation in ad hoc networks for improving data accessibility,'' Proc. IEEE Infocom 2001, pp.1568-1576, 2001. T. Hara, ``Replica allocation methods in ad hoc networks with data update,'' ACM-Kluwer Journal on Mobile Networks and Applications, Vol.8, No.4, pp.343-354, 2003. T. Hara and S.K. Madria, ``Dynamic data replication schemes for mobile ad-hoc network based on aperiodic updates,'' Proc. Int'l Conf. on Database Systems for Advanced Applications (DASFAA 2004), pp.869-881, 2004. T. Hara, N. Murakami, and S. Nishio: ``Replica Allocation for Correlated Data Items in Ad-Hoc Sensor Networks,'' ACM SIGMOD Record, Vol.33, No.1, pp.38-43, 2004. H. Hayashi, T. Hara, and S. Nishio, ``Cache Invalidation for Updated Data in Ad Hoc Net-works,'' Proc. Int'l Conf. on Cooperative Information Systems (CoopIS'03), pp.516-535, 2003. Also, there are several other related works on improving data accessibility and maintaining data consistency in MANET: G. Cao, L. Yin, C.R. Das, ``Cooperative Cache-Based Data Access in Ad Hoc Networks,'' IEEE Computer Magagine, Vol.37, No.2, pp. 32-39, 2004. L.D. Fife and L. Gruenwald, ``Research issues for data communication in mobile ad-hoc network database systems,'' ACM SIGMOD Record, Vol.32, No.2, pp.42-47, 2003. G. Karumanchi, S. Muralidharan, and R. Prakash, ``Information dissemination in partitionable mobile ad hoc networks,'' Proc. Symposium on Reliable Distributed Systems (SRDS'99), pp.4-13, 1999. J. Luo, J.P. Hubaux, and P. Eugster, ``PAN: Providing reliable storage in mobile ad hoc networks with probabilistic quorum systems,'' Proc. ACM MobiHoc 2003, pp.1-12, 2003. K. Rothermel, C. Becker, and J. Hahner, ``Consistent update diffusion in mobile ad hoc networks,'' Technical Report 2002/04, Computer Science Department, University of Stuttgart, 2002. F. Sailhan and V. Issarny, ``Cooperative caching in ad hoc networks,'' Proc. Int'l Conf. on Mobile Data Management (MDM'03), pp.13-28, 2003. K. Wang and B. Li, ``Efficient and guaranteed service coverage in partitionable mobile ad-hoc networks,'' Proc. IEEE Infocom'02, Vol.2, pp.1089-1098, 2002. I am glad if this information helps you. --------------------- Dr. Takahiro Hara Dept. of Multimedia Eng, Grad. Sch. of Information Science and Tech., Osaka University sallyhan@rogers.com wrote: > Hello everyone, > > I'm a new research student focusing on data replication in MANET. I may work on improving data accessibility and maintaining data consistency through replication in MANET. I would like to know if anyone is doing related work in this area or know of any good sources of information. > > Thanks > > Regards > > sally Han > > > 1 > > > _______________________________________________ > 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 exim@www1.ietf.org Mon May 10 20:34:34 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18779 for ; Mon, 10 May 2004 20:34:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNL8N-0004VY-0E for manet-archive@odin.ietf.org; Mon, 10 May 2004 20:28:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B0SYwJ017321 for manet-archive@odin.ietf.org; Mon, 10 May 2004 20:28:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNL2X-0003Pt-4d for manet-web-archive@optimus.ietf.org; Mon, 10 May 2004 20:22:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18158 for ; Mon, 10 May 2004 20:22:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNL2S-0004Ml-60 for manet-web-archive@ietf.org; Mon, 10 May 2004 20:22:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNL1V-00040t-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 20:21:30 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNL0k-0003fK-00 for manet-web-archive@ietf.org; Mon, 10 May 2004 20:20:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKrP-0000l7-Ou; Mon, 10 May 2004 20:11:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKhz-00075A-KD for manet@optimus.ietf.org; Mon, 10 May 2004 20:01:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17520 for ; Mon, 10 May 2004 20:01:17 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNKhx-0005AT-No for manet@ietf.org; Mon, 10 May 2004 20:01:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNKh5-0004qM-00 for manet@ietf.org; Mon, 10 May 2004 20:00:23 -0400 Received: from web20801.mail.yahoo.com ([216.136.226.190]) by ietf-mx with smtp (Exim 4.12) id 1BNKgb-0004Vj-00 for manet@ietf.org; Mon, 10 May 2004 19:59:53 -0400 Message-ID: <20040510235952.88399.qmail@web20801.mail.yahoo.com> Received: from [161.200.255.161] by web20801.mail.yahoo.com via HTTP; Mon, 10 May 2004 16:59:52 PDT Date: Mon, 10 May 2004 16:59:52 -0700 (PDT) From: Sigit Basuki Wibowo To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] QoS 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Dear Everyone, I am new student interested in QoS Routing in MANET. I may work in finding optimum algorithm. Does anyone have suggestions or resources about that ? Thankyou. Regards, Sigit __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 11 06:35:31 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17877 for ; Tue, 11 May 2004 06:35:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUYc-0005rX-Nq for manet-archive@odin.ietf.org; Tue, 11 May 2004 06:32:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BAWIG7022517 for manet-archive@odin.ietf.org; Tue, 11 May 2004 06:32:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUWM-0005MT-4I for manet-web-archive@optimus.ietf.org; Tue, 11 May 2004 06:29:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17324 for ; Tue, 11 May 2004 06:29:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNUWI-0004rU-8B for manet-web-archive@ietf.org; Tue, 11 May 2004 06:29:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNUVD-0004Qy-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 06:28:47 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNUUE-00042i-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 06:27:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUNi-0003io-3v; Tue, 11 May 2004 06:21:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUJn-0002mD-TS for manet@optimus.ietf.org; Tue, 11 May 2004 06:16:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16744 for ; Tue, 11 May 2004 06:16:55 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNUJk-0007a3-3c for manet@ietf.org; Tue, 11 May 2004 06:16:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNUHf-0006xT-00 for manet@ietf.org; Tue, 11 May 2004 06:14:48 -0400 Received: from eri.interia.pl ([217.74.65.138]) by ietf-mx with esmtp (Exim 4.12) id 1BNUHA-0006b1-00 for manet@ietf.org; Tue, 11 May 2004 06:14:16 -0400 Received: from poczta.interia.pl (naos.interia.pl [217.74.65.50]) by eri.interia.pl (Postfix) with ESMTP id 8D12C266D8 for ; Tue, 11 May 2004 12:14:16 +0200 (CEST) Received: from 127.0.0.1 (naos.interia.pl [127.0.0.1]) by system.wewnetrzny9 (poczta.interia.pl) with SMTP id 68064146C8C for ; Tue, 11 May 2004 12:14:16 +0200 (CEST) Received: by poczta.interia.pl (poczta.interia.pl, from userid 502) id 2DE7D146C9F; Tue, 11 May 2004 12:14:16 +0200 (CEST) Received: from gawlin (194.gw.ip.pl [195.116.22.194]) by poczta.fm (poczta.fm) with ESMTP id 48C24AF50F for ; Tue, 11 May 2004 12:14:13 +0200 (CEST) Message-ID: <007f01c43741$1d98eda0$8b000b0a@gawlin> From: "gawlin" To: Date: Tue, 11 May 2004 12:17:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Content-Transfer-Encoding: 7bit Subject: [manet] IBSS mode of 802.11i 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello! Can someone help me answer such a question? Why in IBSS mode of 802.11i the whole IBSS has to use the same authentication and key management protocol? I can't find any explaination of such a restriction. Thanks in advance Marcin Gawlinski _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 11 10:06:27 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27249 for ; Tue, 11 May 2004 10:06:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXrP-0004Vh-Lg for manet-archive@odin.ietf.org; Tue, 11 May 2004 10:03:55 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BE3twH017337 for manet-archive@odin.ietf.org; Tue, 11 May 2004 10:03:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXmg-0001W8-PQ for manet-web-archive@optimus.ietf.org; Tue, 11 May 2004 09:59:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26558 for ; Tue, 11 May 2004 09:58:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNXme-0000gv-Ub for manet-web-archive@ietf.org; Tue, 11 May 2004 09:59:00 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNXlm-0000IY-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 09:58:08 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNXlI-0007hF-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 09:57:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXfx-0000Js-9c; Tue, 11 May 2004 09:52:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXcu-00081E-TO for manet@optimus.ietf.org; Tue, 11 May 2004 09:48:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26100 for ; Tue, 11 May 2004 09:48:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNXcs-0004Ub-Sf for manet@ietf.org; Tue, 11 May 2004 09:48:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNXbt-000461-00 for manet@ietf.org; Tue, 11 May 2004 09:47:54 -0400 Received: from mx1.iit.cnr.it ([146.48.98.40] helo=mx.iit.cnr.it) by ietf-mx with esmtp (Exim 4.12) id 1BNXb0-0003K7-00 for manet@ietf.org; Tue, 11 May 2004 09:46:58 -0400 Received: from localhost (mx.iit.cnr.it [127.0.0.1]) by mx.iit.cnr.it (Postfix) with ESMTP id 6E3DF2EE1B for ; Tue, 11 May 2004 15:46:23 +0200 (CEST) Received: from mx.iit.cnr.it ([127.0.0.1]) by localhost (mx.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24602-16 for ; Tue, 11 May 2004 15:46:21 +0200 (CEST) Received: from [146.48.98.87] (conti.iit.cnr.it [146.48.98.87]) by mx.iit.cnr.it (Postfix) with ESMTP id B0E6D2EE2F for ; Tue, 11 May 2004 15:46:20 +0200 (CEST) Mime-Version: 1.0 X-Sender: marco.conti@iit.cnr.it@mx.iit.cnr.it Message-Id: Date: Tue, 11 May 2004 15:46:17 +0200 To: From: Marco Conti Content-Type: multipart/alternative; boundary="============_-1127839315==_ma============" X-Virus-Scanned: by Content Checker at iit.cnr.it Subject: [manet] IEEE PerCom2005 Call for Workshops - final call 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_MESSAGE, LINES_OF_YELLING,LINES_OF_YELLING_2 autolearn=no version=2.60 --============_-1127839315==_ma============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" ------------------------------------------------------------------------ *** OUR SINCERE APOLOGIES IF YOU RECEIVE MULTIPLE COPIES OF THIS CFP *** ------------------------------------------------------------------------ CALL FOR WORKSHOPS PROPOSALS Third IEEE International Conference on Pervasive Computing and Communications PerCom 2005 (http//www.percom.org) Hawaii, March 8-11, 2005 ------------------------------------------------------------------------ **** Workshop Proposals Deadline --- May 15, 2004 **** Sponsored by The IEEE Computer Society and The University of Texas at Arlington Co-sponsored by the IEEE TCCC and the IEEE TCPP ------------------------------------------------------------------------ IEEE PerCom 2005 will be the third annual conference on the emerging area of pervasive computing and communications aimed at providing an exciting platform and paradigm for all the time, everywhere services. The PerCom2005 Organizing Committee invites proposals for one-day workshops affiliated with the conference. The workshops will be held prior to, or after, the main conference. The purpose of these workshops is to provide a platform for presenting novel ideas in a less formal and possibly more focused way than at the conference itself. Workshops Proposals are solicited in all areas and topics pertaining to pervasive computing and communications research and applications. ------------------------------- Proposal Submission Guidelines: ------------------------------- Each workshop proposal must include: 1. The name of the workshop. 2. The names, addresses, and a short bio (up to 200 words) of the organizers (up to three). 3. A brief description (up to 1 page) of the technical issues that the workshop will address, and the reasons why the workshop is of interest this time. 4. The names of potential participants, such as program committee members 5. If appropriate, a description of past versions of the workshop, including: number of submitted and accepted papers, and number of attendees. 6. A description of the publicity plans. 7. A call for papers 8. The workshop URL Workshop proposals should be submitted, no later than May 15 2004, by e-mail (pdf or text format) with "PerCom2005 Workshop Proposal" in the subject, to both PerCom 2005 Workshop Chairs: Marco Conti Istituto Informatica e Telematica (IIT) Consiglio Nazionale delle Ricerche Via G. Moruzzi 1, 56124 Pisa - Italy marco.conti@iit.cnr.it and Ali R Hurson Computer Science and Engineering Dept. The Pennsylvania State University 111 IST Building, University Park, PA 16802 hurson@cse.psu.edu ---------------- IMPORTANT DATES: ---------------- Proposals submission deadline: May 15, 2004 Acceptance notification: June 1, 2004 Papers due by September 15, 2004 Paper selections due by November 15, 2004 Final papers due to IEEE: December 18, 2004 --============_-1127839315==_ma============ Content-Type: text/html; charset="us-ascii" IEEE PerCom2005 Call for Workshops - final call
------------------------------------------------------------------------

*** OUR SINCERE APOLOGIES IF YOU RECEIVE MULTIPLE COPIES OF THIS CFP ***

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

CALL FOR WORKSHOPS PROPOSALS
 
Third IEEE International Conference on Pervasive Computing and Communications
PerCom 2005 (http//www.percom.org)
Hawaii, March 8-11, 2005

------------------------------------------------------------------------
**** Workshop Proposals Deadline --- May 15, 2004 ****

                   Sponsored by The IEEE Computer Society and
                      The University of Texas at Arlington
                 Co-sponsored by the IEEE TCCC and the IEEE TCPP
------------------------------------------------------------------------

IEEE PerCom 2005 will be the third annual conference on the emerging area of pervasive computing and communications aimed at providing an exciting platform and paradigm for all the time, everywhere services.
The PerCom2005 Organizing Committee invites proposals for one-day workshops affiliated with the conference. The workshops will be held  prior to, or after, the main conference.
The purpose of these workshops is to provide a platform for presenting novel ideas in a less formal and possibly more focused way than at the conference itself.
Workshops Proposals are solicited in all areas and topics pertaining to pervasive computing and communications research and applications.


-------------------------------
Proposal Submission Guidelines:
-------------------------------

Each workshop proposal must include:
1. The name of the workshop.
2. The names, addresses, and a short bio (up to 200 words) of the organizers (up to three).
3. A brief description (up to 1 page) of the technical issues that the workshop will address, and the reasons why the workshop is of interest this time.
4. The names of potential participants, such as program committee members
5. If appropriate, a description of past versions of the workshop, including: number of submitted and accepted papers, and number of attendees.
6. A description of the publicity plans.
7. A call for papers
8. The workshop URL

Workshop proposals should be submitted, no later than May 15 2004, by e-mail (pdf or text format) with "PerCom2005 Workshop Proposal" in the subject, to both PerCom 2005 Workshop Chairs:

Marco Conti
Istituto Informatica e Telematica (IIT)
Consiglio Nazionale delle Ricerche
Via G. Moruzzi 1, 56124 Pisa - Italy
marco.conti@iit.cnr.it
and

Ali R Hurson
Computer Science and Engineering Dept.
The Pennsylvania State University
111 IST Building, University Park, PA 16802
hurson@cse.psu.edu
----------------
IMPORTANT DATES:
----------------
Proposals submission deadline: May 15, 2004
Acceptance notification: June 1, 2004
Papers due by September 15, 2004
Paper selections due by November 15, 2004
Final papers due to IEEE: December 18, 2004
 
--============_-1127839315==_ma============-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 11 12:35:05 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07017 for ; Tue, 11 May 2004 12:35:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNa6o-0006ob-8j for manet-archive@odin.ietf.org; Tue, 11 May 2004 12:28:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BGRwV3026197 for manet-archive@odin.ietf.org; Tue, 11 May 2004 12:27:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNZmt-0001rs-W9 for manet-web-archive@optimus.ietf.org; Tue, 11 May 2004 12:07:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05455 for ; Tue, 11 May 2004 12:07:20 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNZms-0007Sr-NU for manet-web-archive@ietf.org; Tue, 11 May 2004 12:07:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNZlV-0006zx-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 12:05:59 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNZjG-0006AS-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 12:03:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNZY8-0007nN-Lp; Tue, 11 May 2004 11:52:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNZV2-00078A-OK for manet@optimus.ietf.org; Tue, 11 May 2004 11:48:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04823 for ; Tue, 11 May 2004 11:48:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNZV1-0000JU-Ie for manet@ietf.org; Tue, 11 May 2004 11:48:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNZU5-0007hr-00 for manet@ietf.org; Tue, 11 May 2004 11:47:58 -0400 Received: from ext-nj2gw-2.online-age.net ([216.35.73.164]) by ietf-mx with esmtp (Exim 4.12) id 1BNZT6-0006tW-00 for manet@ietf.org; Tue, 11 May 2004 11:46:56 -0400 Received: from int-nj2gw-5.online-age.net (int-nj2gw-5 [3.159.236.69]) by ext-nj2gw-2.online-age.net (8.12.9/8.12.9/990426-RLH) with ESMTP id i4BFkLAW006983 for ; Tue, 11 May 2004 11:46:25 -0400 (EDT) Received: from crdns.crd.ge.com (localhost [127.0.0.1]) by int-nj2gw-5.online-age.net (8.12.9/8.12.8/990426-RLH) with ESMTP id i4BFkKId014338 for ; Tue, 11 May 2004 11:46:20 -0400 (EDT) Received: from xbh01crdge.crd.ge.com (xbh01crdge.crd.ge.com [3.159.72.22]) by crdns.crd.ge.com (8.11.6p2/8.11.6) with ESMTP id i4BFkIe08330 for ; Tue, 11 May 2004 11:46:19 -0400 (EDT) Received: by xbh01crdge.crd.ge.com with Internet Mail Service (5.5.2653.19) id ; Tue, 11 May 2004 11:46:18 -0400 Message-ID: From: "Bush, Stephen F (Research)" To: "'manet@ietf.org'" Date: Tue, 11 May 2004 11:46:17 -0400 X-Mailer: Internet Mail Service (5.5.2653.19) Subject: [manet] Journal of Network and System Management Call for Papers 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Dear Colleagues, Below please find a call-for-papers for a JSNM Special Issue on Active and Programmable Networks. Draft manuscripts are due Mar 30, 2005 with Notification of Acceptance by May 31, 2005. Stephen F. Bush and Shivkumar Kalyanaraman, co-editors ------------------------------------------------------------ ** CALL FOR PAPERS ** JOURNAL OF NETWORK AND SYSTEMS MANAGEMENT Special Issue on Management of Active and Programmable Networks Manuscript due March 30, 2005 ------------------------------------------------------------ Active networks provide a framework enabling code and data to reside within network packets such that injected code can modify behavior of low-level network layers. Programmable networks allow customization o data-plane and control-plane services (e.g.: using network processor methods in high- speed routers or software radio methods in wireless networks). This raises fundamental management issues regarding the relation and tradeoffs among communication and computation, configuration, fault, security, performance, and accounting management. AD HOC WIRELESS NETWORKS and SOFTWARE RADIOS are being facilitated by the advancement of active networks; however, they add another level of complexity to active and programmable network management. The relationship between computation and communication can be addressed by concepts from algorithmic information theory (e.g.: Kolmogorov- Chaitin Complexity). Active and programmable networks form an ideal environment in which to study the effects of tradeoffs in algorithmic and static information representation. Active code can contain either the protocol or a compressed form of the data to be transported. Other divisions of code and state are possible between packets (e.g.: routers with dynamic packet state and customizable data-plane code). ------------------------------------------------------------ This special issue of the Journal of Network and Systems Management will consider topics associated with the management of active and programmable networks. Submissions will span a broad range of topics, e.g.: * Bridging the gap among the large and growing body of work in algorithmic information theory and applications to the health, management, and security of an active or programmable network * Fundamental relationships between computation and communication applied to active or programmable networks; relationship of code vs. data tradeoffs utilized to control access of information, system vulnerability detection, policy enforcement, etc. within an active or programmable network * Self-organization and composition of active network services; self-configuration of active or programmable networks * Case studies involving the management of dynamic adaptation and performance enabled by active networks * Active or programmable networks used to manage and control mobile ad hoc network operation and legacy networks * Active or programmable network management of QoS: controlled amounts of code vs. data that adapt to link quality * Management of active packets in constrained devices such as sensors * Active and programmable network management techniques applied to link and physical layer network components e.g. software radio waveforms * Improvement or replacement of defacto management standard access and control such as SNMP with active or programmable mechanisms ------------------------------------------------------------ Instructions to Contributors: Authors are invited to submit papers for peer-review to the guest editors. Only electronic submissions will be accepted. Please prepare the manuscripts in single-column, double- spaced format and submit Word, PDF, or Postscript files. ------------------------------------------------------------ Guest Editors: Dr. Stephen F. Bush Research Scientist GE Global Research Niskayuna, NY bushsf@research.ge.com Email: http://www.research.ge.com/~bushsf Dr. Shivkumar Kalyanaraman Associate Professor, Dept of ECSE Rensselaer Polytechnic Institute (RPI) Troy NY 12180-3590 Email: shivkuma@ecse.rpi.edu http://www.ecse.rpi.edu/Homepages/shivkuma ------------------------------------------------------------ Schedule: Optional letter of intent: Jan 15, 2005 Manuscript due: Mar 30, 2005 Notification of Acceptance: May 31, 2005 Final Manuscript due: Jul 30, 2005 Publication Date: Mar 2006 ------------------------------------------------------------ Stephen F Bush (http://www.research.ge.com/~bushsf) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 11 13:50:24 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11959 for ; Tue, 11 May 2004 13:50:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNb8v-0004zh-Ts for manet-archive@odin.ietf.org; Tue, 11 May 2004 13:34:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BHYD9u019198 for manet-archive@odin.ietf.org; Tue, 11 May 2004 13:34:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNaxM-0002AT-Rd for manet-web-archive@optimus.ietf.org; Tue, 11 May 2004 13:22:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09952 for ; Tue, 11 May 2004 13:22:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNaxK-0000ra-UH for manet-web-archive@ietf.org; Tue, 11 May 2004 13:22:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNawV-0000QQ-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 13:21:23 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNavb-0007md-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 13:20:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNac2-0005Xl-Mm; Tue, 11 May 2004 13:00:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNaU3-0003J1-GU for manet@optimus.ietf.org; Tue, 11 May 2004 12:51:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08125 for ; Tue, 11 May 2004 12:51:55 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNaU1-0003Uw-QZ for manet@ietf.org; Tue, 11 May 2004 12:51:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNaTA-00034t-00 for manet@ietf.org; Tue, 11 May 2004 12:51:05 -0400 Received: from nn7.excitenetwork.com ([207.159.120.61] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BNaSL-0002Cz-00 for manet@ietf.org; Tue, 11 May 2004 12:50:13 -0400 Received: by xprdmailfe2.nwk.excite.com (Postfix, from userid 110) id 7BF768AF07; Tue, 11 May 2004 12:49:42 -0400 (EDT) To: manet@ietf.org Received: from [139.55.21.238] by xprdmailfe2.nwk.excite.com via HTTP; Tue, 11 May 2004 12:49:42 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040511164942.7BF768AF07@xprdmailfe2.nwk.excite.com> Date: Tue, 11 May 2004 12:49:42 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk. 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all: For Ad Hoc network simulation in NS2, I can use setdest to genenate a mobility pattern. After I get the output from setdest, can I modify the output? For example, if want a node to be stationary during the whole simulation, I only keep the original coordinates of the node and delete all other lines, like: $ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655 6.978688752644" If I want to change the destination and speed of a node, I can also modify the lines containing these information, like the above line. Am I right? Will it cause any error? Thanks. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue May 11 14:44:38 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15309 for ; Tue, 11 May 2004 14:44:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNc2i-0000s8-Po for manet-archive@odin.ietf.org; Tue, 11 May 2004 14:31:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BIVql6003352 for manet-archive@odin.ietf.org; Tue, 11 May 2004 14:31:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNc0e-0008Sp-TZ for manet-web-archive@optimus.ietf.org; Tue, 11 May 2004 14:29:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14310 for ; Tue, 11 May 2004 14:29:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNc0c-0006hm-CC for manet-web-archive@ietf.org; Tue, 11 May 2004 14:29:42 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNbzI-0006Bk-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 14:28:21 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNbyD-0005if-00 for manet-web-archive@ietf.org; Tue, 11 May 2004 14:27:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNbge-0004Hd-6W; Tue, 11 May 2004 14:09:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNbcy-0003D8-Ce for manet@optimus.ietf.org; Tue, 11 May 2004 14:05:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12963 for ; Tue, 11 May 2004 14:05:13 -0400 (EDT) From: voberoi@mtu.edu Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNbcw-00045v-0n for manet@ietf.org; Tue, 11 May 2004 14:05:14 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNbbz-0003fp-00 for manet@ietf.org; Tue, 11 May 2004 14:04:15 -0400 Received: from mailoff.mtu.edu ([141.219.70.111]) by ietf-mx with esmtp (Exim 4.12) id 1BNbbU-0003F3-00 for manet@ietf.org; Tue, 11 May 2004 14:03:44 -0400 Received: from node5.services.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id i4BI3hU14060 for ; Tue, 11 May 2004 14:03:43 -0400 (EDT) Received: from node9.services.dcsint.mtu.edu (node9.mtu.edu [141.219.69.9]) by node5.services.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id i4BI3hX2027654 for ; Tue, 11 May 2004 14:03:43 -0400 Received: from campus4.mtu.edu ([141.219.70.7]) by node9.services.dcsint.mtu.edu (MailMonitor for SMTP v1.2.2 ) ; Tue, 11 May 2004 14:03:43 -0400 (EDT) Received: from node5.services.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id i4BI3gG25932 for ; Tue, 11 May 2004 14:03:42 -0400 (EDT) Received: from huskymail.mtu.edu (node75.mtu.edu [141.219.69.75]) by node5.services.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with SMTP id i4BI3giv027646 for ; Tue, 11 May 2004 14:03:42 -0400 Received: from 141.219.21.168 (SquirrelMail authenticated user voberoi) by huskymail.mtu.edu with HTTP; Tue, 11 May 2004 14:03:42 -0400 (EDT) Message-ID: <33766.141.219.21.168.1084298622.squirrel@huskymail.mtu.edu> Date: Tue, 11 May 2004 14:03:42 -0400 (EDT) To: manet@ietf.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit Subject: [manet] question about changes in 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,NO_REAL_NAME, PRIORITY_NO_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, iam trying to add two new parameters to the AODV packet to make routing decisions rather than just considering shortest hop can anybody help me with where to make the changes in the AODV.cc and Aodv.h files. thanks vikram oberoi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 01:29:19 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22110 for ; Wed, 12 May 2004 01:29:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNmAG-0007Ik-Mm for manet-archive@odin.ietf.org; Wed, 12 May 2004 01:20:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C5KKc1028066 for manet-archive@odin.ietf.org; Wed, 12 May 2004 01:20:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNm66-0006Po-8E for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 01:16:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21320 for ; Wed, 12 May 2004 01:16:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNm63-0002Zu-BO for manet-web-archive@ietf.org; Wed, 12 May 2004 01:15:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNm4y-00025s-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 01:14:53 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNm4I-0001cz-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 01:14:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNloj-0002HU-GN; Wed, 12 May 2004 00:58:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNlhU-0000p7-3h for manet@optimus.ietf.org; Wed, 12 May 2004 00:50:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20271 for ; Wed, 12 May 2004 00:50:31 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNlhR-00079X-B0 for manet@ietf.org; Wed, 12 May 2004 00:50:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNlgW-0006il-00 for manet@ietf.org; Wed, 12 May 2004 00:49:37 -0400 Received: from mails.tsinghua.edu.cn ([166.111.8.16]) by ietf-mx with smtp (Exim 4.12) id 1BNlfk-0005vB-00 for manet@ietf.org; Wed, 12 May 2004 00:48:48 -0400 Received: (eyou send program); Wed, 12 May 2004 12:43:47 +0800 Message-ID: <284337027.29823@mails.tsinghua.edu.cn> Received: from unknown (HELO mails.tsinghua.edu.cn) (unknown@127.0.0.1) by 127.0.0.1 with SMTP; Wed, 12 May 2004 12:43:47 +0800 X-scanvirus: By Symantec Scan Engine X-scanresult: CLEAN Received: (eqmail ); 12 May 2004 04:43:46 -0000 Received: from tu161189.tsinghua.edu.cn (HELO tsu) (wangxh00@166.111.161.189) by mails.tsinghua.edu.cn with SMTP; 12 May 2004 04:43:46 -0000 From: "WXH" To: "manet@ietf.org" X-mailer: Foxmail 4.2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 May 2004 12:48:10 +0800 Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.7 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, MAILTO_TO_SPAM_ADDR,MSGID_FROM_MTA_HEADER,TO_ADDRESS_EQ_REAL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hello everyone=A3=AC I want to design a routing auto-configure protocol- dynamic= routing configure protocol(DRCP), when a node jion an ad hoc network, and it does not know which= routing protocol the network uses, the node can query the other nodes about the= routing protocol , and configure itself. I don't know if somebody has do the same work, and can you tell me about if such a auto-configure protocol is= needed, the key point, and so on. Advise is welcome. thanks. =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1WXH =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1wangxh00@mails.tsinghua.edu.cn =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-05-12 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 12:59:40 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26466 for ; Wed, 12 May 2004 12:59:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNwrp-0005bP-31 for manet-archive@odin.ietf.org; Wed, 12 May 2004 12:46:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CGk15d021530 for manet-archive@odin.ietf.org; Wed, 12 May 2004 12:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNwkB-0001qq-MA for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 12:38:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24762 for ; Wed, 12 May 2004 12:38:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNwkA-0000dt-25 for manet-web-archive@ietf.org; Wed, 12 May 2004 12:38:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNwh6-00078z-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 12:34:56 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNwdw-0005sU-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 12:31:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNwL5-0006hp-3V; Wed, 12 May 2004 12:12:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNvnp-0006SD-R6 for manet@optimus.ietf.org; Wed, 12 May 2004 11:37:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18366 for ; Wed, 12 May 2004 11:37:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNvno-0003Vo-Px for manet@ietf.org; Wed, 12 May 2004 11:37:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNvlj-0002SZ-00 for manet@ietf.org; Wed, 12 May 2004 11:35:40 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 1BNvjn-0001Cf-00 for manet@ietf.org; Wed, 12 May 2004 11:33:39 -0400 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id i4CFWuxp014184 for ; Wed, 12 May 2004 11:32:56 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.0.59) with SMTP id M2004051211325502959 for ; Wed, 12 May 2004 11:32:55 -0400 Message-Id: <6.0.3.0.2.20040512112246.02dea2a0@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 12 May 2004 11:30:58 -0400 To: manet@ietf.org From: Joe Macker Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [manet] Draft MANET Problem Statement and Direction 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable ALL: This discussion is a little overdue but we have run this draft outline past= the Routing ADs and are posting it here for the WG to kick around. Within= the next 2 weeks we would like to have a reasonable WG framework to proceed= with. I don't think there are many surprises here as the WG has been openly= discussing the next steps for awhile. ----------------------------------------------------------------------------= ------------------------- DRAFT MANET PROBLEM STATEMENT AND DIRECTION=20 (REALLY A CHARTER UPDATE) The purpose of the MANET working group is to standardize IP routing protocol= functionality suitable for wireless routing application within both static= and dynamic topologies. The fundamental problem issues are that wireless= link interfaces have some unique routing interface characteristics and that= node topologies within a wireless routing region may experience increased= dynamics, due to motion or other factors. The continued proliferation of a= wide variety of wireless device technologies and embedded network devices= is opening up new wireless networking challenges. MANET specifications= fundamentally provide improved operational IP routing performance for= dynamic, wireless routing regions. Approaches are intended to be= relatively lightweight in nature and suitable for heterogeneous adaptation= across multiple hardware and wireless environments. While MANET routing areas may operate in isolation from a larger connected= Internet, a primary focus of the MANET WG is to address use as a routing= technology extension at the edges of an IP infrastructure. The deployment= of hybrid infrastructures (e.g., a mixture of preferred fixed grid and= mobile routers) should also be supported by MANET specifications and= management features. In the past, this WG has focused on exploring a broad= range of MANET problems, performance issues, and related candidate= protocols and has developed several EXPERIMENTAL RFCs with associated= working prototypes along with an INFORMATIONAL RFC (2501) discussing= performance and design considerations. The present protocol frameworks= provide Experimental MANET specifications covering both reactive and= proactive design spaces and many of the concepts have reached a significant= level of engineering maturity. Building off this work, the MANET WG will= now concentrate its scope on developing several Proposed Standard= specification efforts. Two central routing protocol approaches will be= developed. - MANET Reactive Routing Protocol (MRRP) - MANET Proactive Routing Protocol (MPRP) For this goal, it is expected that MRRP will become a convergence of mature= reactive design components. Likewise, it is expected that MPRP would be a= convergence of mature proactive design components. At this point, the WG= has rough consensus that a split between proactive and reactive taxonomies= appears sensible from a design complexity and application space= perspective. The WG will begin its work with development of protocols along= these tracks. If the WG sees significant commonality among the design= spaces common building blocks may be developed. The WG will develop both= IPv4 and IPv6 support within these protocols. Routing security= requirements and issues will also be addressed. Within the MANET WG, the development of a common ALL_MANET_NODES forwarding= protocol building block for use withing a MANET routing area has also been= identified as a useful work item. The potential for the "broadcast storm= problem" to arise is exacerbated in a MANET wireless interface scenario,= where each node may have a different set of single hop neighbors. Present= MANET routing protocol work has developed a number of flooding= optimizations suitable for MANET environments that can reduce significantly= the number of redundant transmissions when forwarding packets to= ALL_MANET_NODES. A generic MANET flooding building block can be adapted to= a routing protocol instantiation and may also be useful in designing= service discovery and autoconfiguration mechanisms within MANET areas. The= MANET WG will develop a generic flooding building block and related= instantiations that will be useful for the intended wireless network= environments. =20 Additional WG items that are to be covered by a small set of INFORMATIONAL= documents and possible PROPOSED STANDARD specifications relate to issues of= address autoconfiguration, MANET gateway discovery and operation, and= network service discovery. The MANET WG will work with other IETF WGs to= determine and support the working of related issues within the appropriate= working groups. Some related work the MANET WG will pay particular attention to will be the= OSPF-MANET protocol work within the OSPF WG and the ANS IRTF work that is= addressing research topics related to MANET environments. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 14:10:16 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00779 for ; Wed, 12 May 2004 14:10:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNy0R-0002nz-QE for manet-archive@odin.ietf.org; Wed, 12 May 2004 13:58:59 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CHwxKV010784 for manet-archive@odin.ietf.org; Wed, 12 May 2004 13:58:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNxyC-0002AK-I2 for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 13:56:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29887 for ; Wed, 12 May 2004 13:56:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNxyA-0002IR-Am for manet-web-archive@ietf.org; Wed, 12 May 2004 13:56:38 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNxx8-0001iq-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 13:55:34 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNxw0-0000vo-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 13:54:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNxps-0007v8-Rl; Wed, 12 May 2004 13:48:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNxZP-00026T-AH for manet@optimus.ietf.org; Wed, 12 May 2004 13:31:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28287 for ; Wed, 12 May 2004 13:31:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNxZN-0004IK-8o for manet@ietf.org; Wed, 12 May 2004 13:31:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNxYH-0003ix-00 for manet@ietf.org; Wed, 12 May 2004 13:29:53 -0400 Received: from postal.usc.edu ([128.125.253.6] ident=sjes) by ietf-mx with esmtp (Exim 4.12) id 1BNxXL-0003CT-00 for manet@ietf.org; Wed, 12 May 2004 13:28:55 -0400 Received: from aludra.usc.edu (aludra.usc.edu [128.125.253.184]) by postal.usc.edu (Sun ONE Messaging Server 6.0 HotFix 1.03 (built Apr 23 2004)) with ESMTP id <0HXM003DS37A3O80@postal.usc.edu> for manet@ietf.org; Wed, 12 May 2004 10:28:22 -0700 (PDT) Date: Wed, 12 May 2004 10:28:23 -0700 (PDT) From: Shshank Sharma Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk In-reply-to: <20040512160046.1028.66564.Mailman@www1.ietf.org> To: manet@ietf.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT > Message: 1 > To: manet@ietf.org > Reply-To: jw2000@excite.com > From: "Jack Wang" > Date: Tue, 11 May 2004 12:49:42 -0400 (EDT) > Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk. > > Hi all: > > For Ad Hoc network simulation in NS2, I can use setdest to genenate a mobility pattern. > After I get the output from setdest, can I modify the output? > For example, if want a node to be stationary during the whole simulation, I only keep the original coordinates of the node and delete all other lines, like: > $ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655 6.978688752644" > If I want to change the destination and speed of a node, I can also modify the lines containing these information, like the above line. > Am I right? Will it cause any error? > > Thanks. > > Jack You sure can modify the output to enforce the desired behavior. However, you will need to define the state of the node for the entire length of the simulation. -Shshank http://www.shshank.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 14:13:53 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00958 for ; Wed, 12 May 2004 14:13:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNyCc-0006cJ-EL for manet-archive@odin.ietf.org; Wed, 12 May 2004 14:11:34 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CIBYpE025431 for manet-archive@odin.ietf.org; Wed, 12 May 2004 14:11:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNy7r-00050Y-3k for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 14:06:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00601 for ; Wed, 12 May 2004 14:06:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNy7o-0007Sf-Op for manet-web-archive@ietf.org; Wed, 12 May 2004 14:06:36 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNy6s-0006x3-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 14:05:39 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNy5i-0006EN-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 14:04:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNxzZ-0002XO-2r; Wed, 12 May 2004 13:58:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNxwL-0001e0-IO for manet@optimus.ietf.org; Wed, 12 May 2004 13:54:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29798 for ; Wed, 12 May 2004 13:54:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNxwJ-0001Cj-6a for manet@ietf.org; Wed, 12 May 2004 13:54:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNxvD-0000ee-00 for manet@ietf.org; Wed, 12 May 2004 13:53:36 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 1BNxu9-0007QJ-00 for manet@ietf.org; Wed, 12 May 2004 13:52:29 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Wed, 12 May 2004 13:49:01 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Wed, 12 May 2004 13:48:34 -0400 From: "Pete Sholander" To: , Subject: Re: [manet] Draft MANET Problem Statement and Direction Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Joe, Looks good!!! =20 Q1: Does the WG intend to focus on unicast routing protocols only? Or are = simple multicast protocols in scope? (I would guess unicast only, since = you're aiming at Proposed Standards.) Q2: Do you a notional schedule in mind for completing this work? (The = last round of RFCs took a while for various reasons. Hopefully, this = effort can be faster.) --Pete Sholander Atlanta, GA >>> Joe Macker 05/12/04 11:30AM >>> ALL: This discussion is a little overdue but we have run this draft outline = past the Routing ADs and are posting it here for the WG to kick around. = Within the next 2 weeks we would like to have a reasonable WG framework to = proceed with. I don't think there are many surprises here as the WG has = been openly discussing the next steps for awhile. ---------------------------------------------------------------------------= -------------------------- DRAFT MANET PROBLEM STATEMENT AND DIRECTION=20 (REALLY A CHARTER UPDATE) The purpose of the MANET working group is to standardize IP routing = protocol functionality suitable for wireless routing application within = both static and dynamic topologies. The fundamental problem issues are = that wireless link interfaces have some unique routing interface characteri= stics and that node topologies within a wireless routing region may = experience increased dynamics, due to motion or other factors. The = continued proliferation of a wide variety of wireless device technologies = and embedded network devices is opening up new wireless networking = challenges. MANET specifications fundamentally provide improved operationa= l IP routing performance for dynamic, wireless routing regions. Approaches= are intended to be relatively lightweight in nature and suitable for = heterogeneous adaptation across multiple hardware and wireless environments= . While MANET routing areas may operate in isolation from a larger connected = Internet, a primary focus of the MANET WG is to address use as a routing = technology extension at the edges of an IP infrastructure. The deployment = of hybrid infrastructures (e.g., a mixture of preferred fixed grid and = mobile routers) should also be supported by MANET specifications and = management features. In the past, this WG has focused on exploring a broad = range of MANET problems, performance issues, and related candidate = protocols and has developed several EXPERIMENTAL RFCs with associated = working prototypes along with an INFORMATIONAL RFC (2501) discussing = performance and design considerations. The present protocol frameworks = provide Experimental MANET specifications covering both reactive and = proactive design spaces and many of the concepts have reached a significant= level of engineering maturity. Building off this work, the MANET WG will = now concentrate its scope on developing several Proposed Standard = specification efforts. Two central routing protocol approaches will be = developed. - MANET Reactive Routing Protocol (MRRP) - MANET Proactive Routing Protocol (MPRP) For this goal, it is expected that MRRP will become a convergence of = mature reactive design components. Likewise, it is expected that MPRP = would be a convergence of mature proactive design components. At this = point, the WG has rough consensus that a split between proactive and = reactive taxonomies appears sensible from a design complexity and = application space perspective. The WG will begin its work with development = of protocols along these tracks. If the WG sees significant commonality = among the design spaces common building blocks may be developed. The WG = will develop both IPv4 and IPv6 support within these protocols. Routing = security requirements and issues will also be addressed. Within the MANET WG, the development of a common ALL_MANET_NODES forwarding= protocol building block for use withing a MANET routing area has also = been identified as a useful work item. The potential for the "broadcast = storm problem" to arise is exacerbated in a MANET wireless interface = scenario, where each node may have a different set of single hop neighbors.= Present MANET routing protocol work has developed a number of flooding = optimizations suitable for MANET environments that can reduce significantly= the number of redundant transmissions when forwarding packets to = ALL_MANET_NODES. A generic MANET flooding building block can be adapted = to a routing protocol instantiation and may also be useful in designing = service discovery and autoconfiguration mechanisms within MANET areas. = The MANET WG will develop a generic flooding building block and related = instantiations that will be useful for the intended wireless network = environments. =20 Additional WG items that are to be covered by a small set of INFORMATIONAL = documents and possible PROPOSED STANDARD specifications relate to issues = of address autoconfiguration, MANET gateway discovery and operation, and = network service discovery. The MANET WG will work with other IETF WGs to = determine and support the working of related issues within the appropriate = working groups. Some related work the MANET WG will pay particular attention to will be = the OSPF-MANET protocol work within the OSPF WG and the ANS IRTF work that = is addressing research topics related to MANET environments. _______________________________________________ manet mailing list manet@ietf.org=20 https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 15:52:07 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06889 for ; Wed, 12 May 2004 15:52:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNzci-0005FX-KA for manet-archive@odin.ietf.org; Wed, 12 May 2004 15:42:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CJgabl020179 for manet-archive@odin.ietf.org; Wed, 12 May 2004 15:42:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNzX1-0003Hf-3E for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 15:36:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05926 for ; Wed, 12 May 2004 15:36:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNzWz-00062I-PX for manet-web-archive@ietf.org; Wed, 12 May 2004 15:36:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNzVz-0005UP-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 15:35:39 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNzUo-0004cb-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 15:34:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNzI2-0006YO-QE; Wed, 12 May 2004 15:21:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNzCJ-00037h-8w for manet@optimus.ietf.org; Wed, 12 May 2004 15:15:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01464 for ; Wed, 12 May 2004 14:27:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNySB-0002OY-26 for manet@ietf.org; Wed, 12 May 2004 14:27:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNyRD-0001uC-00 for manet@ietf.org; Wed, 12 May 2004 14:26:40 -0400 Received: from ellis.ad.nps.navy.mil ([131.120.18.61]) by ietf-mx with esmtp (Exim 4.12) id 1BNyQI-0001HL-00 for manet@ietf.org; Wed, 12 May 2004 14:25:42 -0400 Received: from [131.120.179.249] ([131.120.179.249]) by ellis.ad.nps.navy.mil with Microsoft SMTPSVC(5.0.2195.6713); Wed, 12 May 2004 11:25:30 -0700 Subject: Re: [manet] Draft MANET Problem Statement and Direction From: Rex Buddenberg To: Pete Sholander Cc: manet@ietf.org, macker@itd.nrl.navy.mil In-Reply-To: References: Content-Type: text/plain Message-Id: <1084386330.16357.346.camel@antony> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 12 May 2004 11:25:30 -0700 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 May 2004 18:25:30.0925 (UTC) FILETIME=[81C8EDD0:01C4384E] 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Wed, 2004-05-12 at 10:48, Pete Sholander wrote: > Joe, > > Looks good!!! I'll second that. > > Q1: Does the WG intend to focus on unicast routing protocols only? Or are simple multicast protocols in scope? (I would guess unicast only, since you're aiming at Proposed Standards.) Astute question, Pete. Let me contribute some information. I can think of lots of situations where the character of the data is multicast. The military has a lot. And every time I envision the kind of volatile topology that MANET is trying to cope with, there is present a ton of data that is multicast in nature. In opposition, I can think of no situations where the volatile topology would be present but not multicast data. The current illustration (only the latest) is Blue Force Tracker which is a system that relays nav positions of nodes which are then put into the common tactical picture database. The database is displayed at all echelons of command from the 4-star in Qatar down to the truck driver on the road from Kuwait to Baghdad. If you look at public safety (fire, police departments) you get much the same logic. But the operational take needs to be leavened with Joe's entirely necessary attitude that we need to get something out the door. If we can get some standards-track MANET RFCs out that ignore, but do not do violence to multicast, then OK. We don't have to take a step back on MANET in order to take a step forward with multicast routing info protocols later. If this is not the case, then the answer to your question should be yes -- we don't get much if we don't include multicast. -- b _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 12 22:43:40 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27954 for ; Wed, 12 May 2004 22:43:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO69C-00016G-KC for manet-archive@odin.ietf.org; Wed, 12 May 2004 22:40:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4D2eYIg004227 for manet-archive@odin.ietf.org; Wed, 12 May 2004 22:40:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO68D-0000sT-5M for manet-web-archive@optimus.ietf.org; Wed, 12 May 2004 22:39:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27786 for ; Wed, 12 May 2004 22:39:29 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BO689-0003XH-VY for manet-web-archive@ietf.org; Wed, 12 May 2004 22:39:29 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BO679-00031w-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 22:38:28 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BO663-0002Jr-00 for manet-web-archive@ietf.org; Wed, 12 May 2004 22:37:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO5zy-0006le-6I; Wed, 12 May 2004 22:31:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO5wb-0005uy-Np for manet@optimus.ietf.org; Wed, 12 May 2004 22:27:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27408 for ; Wed, 12 May 2004 22:27:30 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BO5wY-0005PU-Gn for manet@ietf.org; Wed, 12 May 2004 22:27:30 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BO5va-0004uT-00 for manet@ietf.org; Wed, 12 May 2004 22:26:31 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com ident=root) by ietf-mx with esmtp (Exim 4.12) id 1BO5ud-0004Oy-00 for manet@ietf.org; Wed, 12 May 2004 22:25:31 -0400 Received: from [68.100.124.243] (account ) by multicasttech.com (CommuniGate Pro WebUser 3.4.8) with HTTP id 2333421; Wed, 12 May 2004 22:25:21 -0400 From: "Marshall Eubanks" Subject: Re: [manet] Draft MANET Problem Statement and Direction To: Rex Buddenberg , Pete Sholander Cc: manet@ietf.org, macker@itd.nrl.navy.mil, almeroth@cs.ucsb.edu, dino@procket.com X-Mailer: CommuniGate Pro Web Mailer v.3.4.8 Date: Wed, 12 May 2004 22:25:21 -0400 Message-ID: In-Reply-To: <1084386330.16357.346.camel@antony> MIME-Version: 1.0 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit On 12 May 2004 11:25:30 -0700 Rex Buddenberg wrote: > On Wed, 2004-05-12 at 10:48, Pete Sholander wrote: > > Joe, > > > > Looks good!!! > I'll second that. > > > > Q1: Does the WG intend to focus on unicast routing protocols only? Or are simple multicast > protocols in scope? (I would guess unicast only, since you're aiming at Proposed Standards.) > I, at least, am very interested in multicast routing on ad hoc networks, but have just begun to dig into the manet archives. Can you provide me some pointers to list discussion or other resources as to why Single Source Multicast at least would be problematic in this context ? Regards Marshall Eubanks > > Astute question, Pete. Let me contribute some information. > > I can think of lots of situations where the character of the data is > multicast. The military has a lot. And every time I envision the kind > of volatile topology that MANET is trying to cope with, there is present > a ton of data that is multicast in nature. In opposition, I can think > of no situations where the volatile topology would be present but not > multicast data. > > The current illustration (only the latest) is Blue Force Tracker which > is a system that relays nav positions of nodes which are then put into > the common tactical picture database. The database is displayed at all > echelons of command from the 4-star in Qatar down to the truck driver on > the road from Kuwait to Baghdad. > > If you look at public safety (fire, police departments) you get much the > same logic. > > But the operational take needs to be leavened with Joe's entirely > necessary attitude that we need to get something out the door. > > If we can get some standards-track MANET RFCs out that ignore, but do > not do violence to multicast, then OK. We don't have to take a step > back on MANET in order to take a step forward with multicast routing > info protocols later. If this is not the case, then the answer to your > question should be yes -- we don't get much if we don't include > multicast. > -- > b > > > _______________________________________________ > 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 exim@www1.ietf.org Thu May 13 01:52:19 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06467 for ; Thu, 13 May 2004 01:52:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO94x-0008QF-CH for manet-archive@odin.ietf.org; Thu, 13 May 2004 01:48:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4D5mN5H032376 for manet-archive@odin.ietf.org; Thu, 13 May 2004 01:48:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO8zj-00079z-73 for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 01:42:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05968 for ; Thu, 13 May 2004 01:42:57 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BO8zg-00062w-2g for manet-web-archive@ietf.org; Thu, 13 May 2004 01:42:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BO8yg-0005XJ-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 01:41:54 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BO8y1-000527-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 01:41:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO8sz-00058c-OS; Thu, 13 May 2004 01:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BO8p7-0004f8-Sc for manet@optimus.ietf.org; Thu, 13 May 2004 01:32:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05296 for ; Thu, 13 May 2004 01:31:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BO8p4-0000Br-NV for manet@ietf.org; Thu, 13 May 2004 01:31:58 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BO8nz-0007Su-00 for manet@ietf.org; Thu, 13 May 2004 01:30:52 -0400 Received: from nn4.excitenetwork.com ([207.159.120.58] helo=xprdmailfe23.nwk.excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BO8n3-0006Wz-00 for manet@ietf.org; Thu, 13 May 2004 01:29:53 -0400 Received: by xprdmailfe23.nwk.excite.com (Postfix, from userid 110) id 74BB21BCD2; Thu, 13 May 2004 01:29:24 -0400 (EDT) To: kimaya@cs.ucsb.edu Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk. Received: from [139.55.21.238] by xprdmailfe23.nwk.excite.com via HTTP; Thu, 13 May 2004 01:29:24 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: shshanks@aludra.usc.edu, manet@ietf.org Message-Id: <20040513052924.74BB21BCD2@xprdmailfe23.nwk.excite.com> Date: Thu, 13 May 2004 01:29:24 -0400 (EDT) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.5 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thanks a lot. When I modify the output of setdest, I should ensure that it is reasonable, right? For example, assume pause time is 10 seconds. The following two lines are impossible case. $ns_ at 1.00 "$node_(11) setdest 1.0 10.0 2.0 $ns_ at 5.00 "$node_(11) setdest 1.0 100.0 2.0 Am I right? Jack --- On Tue 05/11, Kimaya M. Sanzgiri < kimaya@cs.ucsb.edu > wrote: From: Kimaya M. Sanzgiri [mailto: kimaya@cs.ucsb.edu] To: jw2000@excite.com Date: Tue, 11 May 2004 11:39:58 -0700 (PDT) Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk.
Yes, you can do this. It won't cause any error.

Kimaya


On Tue, 11 May 2004, Jack Wang wrote:

>
> Hi all:
>
> For Ad Hoc network simulation in NS2, I can use setdest to genenate a mobility pattern.
> After I get the output from setdest, can I modify the output?
> For example, if want a node to be stationary during the whole simulation, I only keep the original coordinates of the node and delete all other lines, like:
> $ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655 6.978688752644"
> If I want to change the destination and speed of a node, I can also modify the lines containing these information, like the above line.
> Am I right? Will it cause any error?
>
> Thanks.
>
> Jack
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
>
> _______________________________________________!
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>

_______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 13 06:42:01 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03812 for ; Thu, 13 May 2004 06:42:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BODai-0003Zr-SZ for manet-archive@odin.ietf.org; Thu, 13 May 2004 06:37:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DAbSi2013752 for manet-archive@odin.ietf.org; Thu, 13 May 2004 06:37:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BODXX-0002Yv-1B for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 06:34:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03386 for ; Thu, 13 May 2004 06:34:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BODXT-0002He-20 for manet-web-archive@ietf.org; Thu, 13 May 2004 06:34:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BODWS-0001iM-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 06:33:05 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BODVk-0001Ab-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 06:32:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BODKx-0000Hj-2D; Thu, 13 May 2004 06:21:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BODF8-0006xv-EF for manet@optimus.ietf.org; Thu, 13 May 2004 06:15:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02395 for ; Thu, 13 May 2004 06:15:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BODF4-0007O4-Hh for manet@ietf.org; Thu, 13 May 2004 06:15:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BODDl-0006ni-00 for manet@ietf.org; Thu, 13 May 2004 06:13:46 -0400 Received: from outbound.kcl.ac.uk ([137.73.2.214]) by ietf-mx with esmtp (Exim 4.12) id 1BODCl-0006Bu-00 for manet@ietf.org; Thu, 13 May 2004 06:12:43 -0400 Received: from smtpredi.kcl.ac.uk ([137.73.66.123] helo=redwood) by outbound.kcl.ac.uk outbound with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) id 1BODCU-0007JP-Jg; Thu, 13 May 2004 11:12:26 +0100 Received: from ee014.eee.kcl.ac.uk ([137.73.10.115] helo=MONA) by redwood smtpred with esmtp id 1BODCO-0003zY-3e; Thu, 13 May 2004 11:12:21 +0100 Message-ID: <006601c438d2$c8db9d60$730a4989@MONA> From: "Mona" To: Cc: Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk. Date: Thu, 13 May 2004 11:12:21 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0063_01C438DB.292C0300" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-KCLSpamScore: 11 X-KCLRealSpamScore: 1.1 X-KCLZStatus: 11 X-KCLSpamBar: + X-KCLSpamReport: HTML_MESSAGE=0.001,MAILTO_TO_SPAM_ADDR=1.052 X-KCL-MailScanner: Found to be clean X-MailScanner-From: mona.ghassemian@kcl.ac.uk 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_MESSAGE, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_0063_01C438DB.292C0300 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Jack, If you want to create a mobility file with some fixed specific nodes, = the easiest way is to create your mobility file for number of mobile = nodes. Then set the position of the fix nodes in the tcl file. For example you want to generate a scenario with 10 mobile nodes and 4 = fixed nodes. Simply create a mobility file for 10 nodes, set you number = of mobile nodes in your tcl file as 14 and define the position of fixed = nodes in the tcl file. If you want to change the speed or the destination of an specific mobile = node, then you need to change parameters of setdest as you have = mentioned yourself. Kind Regards, Mona ----------------------------------------------------------- Mona Ghassemian, PhD student Centre for Telecommunications Research King's College London Drury Lane, London WC2R 5RL T: +44 20 7848 2889 F: +44 20 7848 2664 E: Mona.Ghassemian@kcl.ac.uk ----------------------------------------------------------- To: manet@ietf.org Reply-To: jw2000@excite.com From: "Jack Wang" Date: Tue, 11 May 2004 12:49:42 -0400 (EDT) Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk. Hi all: For Ad Hoc network simulation in NS2, I can use setdest to genenate a = mobility pattern. After I get the output from setdest, can I modify the output? For example, if want a node to be stationary during the whole = simulation, I only keep the original coordinates of the node and delete = all other lines, like: $ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 = 841.668771362655 6.978688752644" =20 If I want to change the destination and speed of a node, I can also = modify the lines containing these information, like the above line. Am I right? Will it cause any error? Thanks. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! ------=_NextPart_000_0063_01C438DB.292C0300 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hi Jack,
 
If you want to create a mobility file with some = fixed specific=20 nodes, the easiest way is to create your mobility file for number of = mobile=20 nodes. Then set the position of the fix nodes in the tcl = file.
 
For example you want to generate a scenario with 10 = mobile=20 nodes and 4 fixed nodes. Simply create a mobility file for 10 nodes, set = you=20 number of mobile nodes in your tcl file as 14 and define the position of = fixed=20 nodes in the tcl file.
 
If you want to change the speed or the destination = of an=20 specific mobile node, then you need to change parameters of setdest as = you have=20 mentioned yourself.
 
Kind Regards,
Mona
-----------------------------------------------------------
M= ona=20 Ghassemian, PhD student
Centre for Telecommunications = Research
King's=20 College London
Drury Lane, London WC2R 5RL
T: +44 20 7848 = 2889
F: +44=20 20 7848 2664
E: Mona.Ghassemian@kcl.ac.uk-----------------------------------------------------------
To: manet@ietf.org
Reply-To: jw2000@excite.com
From: "Jack = Wang"=20 <jw2000@excite.com>
Date: = Tue,=20 11 May 2004 12:49:42 -0400 (EDT)
Subject: [manet] Question about NS2=20 simulation of Ad Hoc netowrk.


Hi all:

For Ad Hoc = network=20 simulation in NS2, I can use setdest to genenate a mobility = pattern.
After I=20 get the output from setdest, can I modify the output?
For example, if = want a=20 node to be stationary during the whole simulation, I only keep the = original=20 coordinates of the node and delete all other lines, like:
$ns_ at=20 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655=20 6.978688752644" 
If I want to change the destination and speed = of a=20 node, I can also modify the lines containing these information, like the = above=20 line.
Am I right? Will it cause any=20 error?

Thanks.

Jack

________________________________= _______________
Join=20 Excite! - http://www.excite.com
The most=20 personalized portal on the Web!
------=_NextPart_000_0063_01C438DB.292C0300-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 13 10:22:31 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15289 for ; Thu, 13 May 2004 10:22:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGxu-00072I-Dw for manet-archive@odin.ietf.org; Thu, 13 May 2004 10:13:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DEDcJT027041 for manet-archive@odin.ietf.org; Thu, 13 May 2004 10:13:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGrh-0003fO-U8 for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:07:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13905 for ; Thu, 13 May 2004 10:07:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOGrf-00074F-Sk for manet-web-archive@ietf.org; Thu, 13 May 2004 10:07:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOGqf-0006UJ-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 10:06:10 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOGpN-0005e6-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 10:04:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGhr-0006pQ-RP; Thu, 13 May 2004 09:57:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGdD-0005rV-Qj for manet@optimus.ietf.org; Thu, 13 May 2004 09:52:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12991 for ; Thu, 13 May 2004 09:52:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOGdB-0006Zn-QZ for manet@ietf.org; Thu, 13 May 2004 09:52:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOGc9-00061o-00 for manet@ietf.org; Thu, 13 May 2004 09:51:10 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 1BOGbE-0004wU-00 for manet@ietf.org; Thu, 13 May 2004 09:50:12 -0400 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id i4DDndxp029127; Thu, 13 May 2004 09:49:39 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.6.45) with SMTP id M2004051309493802421 ; Thu, 13 May 2004 09:49:38 -0400 Message-Id: <6.0.3.0.2.20040513093813.025efc88@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Thu, 13 May 2004 09:47:44 -0400 To: "Pete Sholander" , From: Joe Macker Subject: Re: [manet] Draft MANET Problem Statement and Direction In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable At 01:48 PM 5/12/2004, Pete Sholander wrote: >Joe, > >Looks good!!! =20 > >Q1: Does the WG intend to focus on unicast routing protocols only? Or are= simple multicast protocols in scope? (I would guess unicast only, since= you're aiming at Proposed Standards.) Yes, I believe simple multicast forwarding is in scope. Paragraph 4 could= be seen as a possibility. We have a running prototype similar to MPR-F along these lines.. Common building block needs (e.g., duplicate packet detection) are certainly= different than typical wired approaches and can be engineered. =20 >Q2: Do you a notional schedule in mind for completing this work? (The= last round of RFCs took a while for various reasons. Hopefully, this= effort can be faster.) Let's get consensus on the problem and the work items first. I certainly think we can speed up the process once we scope in on the items >--Pete Sholander >Atlanta, GA > >>>> Joe Macker 05/12/04 11:30AM >>> >ALL: > >This discussion is a little overdue but we have run this draft outline past= the Routing ADs and are posting it here for the WG to kick around. Within= the next 2 weeks we would like to have a reasonable WG framework to proceed= with. I don't think there are many surprises here as the WG has been openly= discussing the next steps for awhile. > >---------------------------------------------------------------------------= -------------------------- >DRAFT MANET PROBLEM STATEMENT AND DIRECTION=20 >(REALLY A CHARTER UPDATE) > >The purpose of the MANET working group is to standardize IP routing= protocol functionality suitable for wireless routing application within= both static and dynamic topologies. The fundamental problem issues are that= wireless link interfaces have some unique routing interface characteristics= and that node topologies within a wireless routing region may experience= increased dynamics, due to motion or other factors. The continued= proliferation of a wide variety of wireless device technologies and= embedded network devices is opening up new wireless networking challenges. = MANET specifications fundamentally provide improved operational IP routing= performance for dynamic, wireless routing regions. Approaches are intended= to be relatively lightweight in nature and suitable for heterogeneous= adaptation across multiple hardware and wireless environments. > >While MANET routing areas may operate in isolation from a larger connected= Internet, a primary focus of the MANET WG is to address use as a routing= technology extension at the edges of an IP infrastructure. The deployment= of hybrid infrastructures (e.g., a mixture of preferred fixed grid and= mobile routers) should also be supported by MANET specifications and= management features. In the past, this WG has focused on exploring a broad= range of MANET problems, performance issues, and related candidate= protocols and has developed several EXPERIMENTAL RFCs with associated= working prototypes along with an INFORMATIONAL RFC (2501) discussing= performance and design considerations. The present protocol frameworks= provide Experimental MANET specifications covering both reactive and= proactive design spaces and many of the concepts have reached a significant= level of engineering maturity. Building off this work, the MANET WG will= now concentrate its scope on developing several Proposed Standard= specification efforts. Two central routing protocol approaches will be= developed. > >- MANET Reactive Routing Protocol (MRRP) >- MANET Proactive Routing Protocol (MPRP) > >For this goal, it is expected that MRRP will become a convergence of mature= reactive design components. Likewise, it is expected that MPRP would be a= convergence of mature proactive design components. At this point, the WG= has rough consensus that a split between proactive and reactive taxonomies= appears sensible from a design complexity and application space= perspective. The WG will begin its work with development of protocols along= these tracks. If the WG sees significant commonality among the design= spaces common building blocks may be developed. The WG will develop both= IPv4 and IPv6 support within these protocols. Routing security= requirements and issues will also be addressed. > >Within the MANET WG, the development of a common ALL_MANET_NODES forwarding= protocol building block for use withing a MANET routing area has also been= identified as a useful work item. The potential for the "broadcast storm= problem" to arise is exacerbated in a MANET wireless interface scenario,= where each node may have a different set of single hop neighbors. Present= MANET routing protocol work has developed a number of flooding= optimizations suitable for MANET environments that can reduce significantly= the number of redundant transmissions when forwarding packets to= ALL_MANET_NODES. A generic MANET flooding building block can be adapted to= a routing protocol instantiation and may also be useful in designing= service discovery and autoconfiguration mechanisms within MANET areas. The= MANET WG will develop a generic flooding building block and related= instantiations that will be useful for the intended wireless network= environments. =20 > >Additional WG items that are to be covered by a small set of INFORMATIONAL= documents and possible PROPOSED STANDARD specifications relate to issues of= address autoconfiguration, MANET gateway discovery and operation, and= network service discovery. The MANET WG will work with other IETF WGs to= determine and support the working of related issues within the appropriate= working groups. > >Some related work the MANET WG will pay particular attention to will be the= OSPF-MANET protocol work within the OSPF WG and the ANS IRTF work that is= addressing research topics related to MANET environments. > > >_______________________________________________ >manet mailing list >manet@ietf.org=20 >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 13 10:59:17 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17474 for ; Thu, 13 May 2004 10:59:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOHWF-0000BL-5Q for manet-archive@odin.ietf.org; Thu, 13 May 2004 10:49:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DEn7ld000700 for manet-archive@odin.ietf.org; Thu, 13 May 2004 10:49:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOHVP-0008S8-GA for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:48:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16967 for ; Thu, 13 May 2004 10:48:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOHVN-0006U8-19 for manet-web-archive@ietf.org; Thu, 13 May 2004 10:48:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOHUO-0005vm-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 10:47:13 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOHTl-0005O0-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 10:46:33 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOHNU-0006NH-Gq; Thu, 13 May 2004 10:40:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOHIe-0004oQ-5g for manet@optimus.ietf.org; Thu, 13 May 2004 10:35:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16162 for ; Thu, 13 May 2004 10:35:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOHIb-0006zX-Ef for manet@ietf.org; Thu, 13 May 2004 10:35:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOHHZ-0006RE-00 for manet@ietf.org; Thu, 13 May 2004 10:33:58 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 1BOHGQ-0005Tb-00 for manet@ietf.org; Thu, 13 May 2004 10:32:46 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 9397C2007; Thu, 13 May 2004 08:32:45 -0600 (MDT) From: "John Mullen" To: "'Joe Macker'" , Subject: RE: [manet] Draft MANET Problem Statement and Direction Date: Thu, 13 May 2004 08:32:45 -0600 Message-ID: <000001c438f7$28384370$67f57b80@IEngr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <6.0.3.0.2.20040512112246.02dea2a0@pop.itd.nrl.navy.mil> Importance: Normal 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, We have been working on stochastic models of wireless link behavior and feel, at this point, that at least some of the fine-grained variability of received power will bleed through to the MANET routing protocol layer. The variability introduced by typical shadowing and multipath fading has an immense impact on protocol performance. For example, end to end delay may be several orders of magnitude greater when fading is considered than when it is ignored. At this time, however, this critical aspect is not widely addressed in the MANET community. It is unlikely that reliable MANET protocols can be developed without considering this effect. I suggest that the line: "increased dynamics, due to motion or other factors" be changed to "increased dynamics, due to motion, residual effects of fine-grained variation in wireless propagation, or other factors" Thanks, John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Joe Macker Sent: Wednesday, May 12, 2004 8:31 AM To: manet@ietf.org Subject: [manet] Draft MANET Problem Statement and Direction ALL: This discussion is a little overdue but we have run this draft outline past the Routing ADs and are posting it here for the WG to kick around. Within the next 2 weeks we would like to have a reasonable WG framework to proceed with. I don't think there are many surprises here as the WG has been openly discussing the next steps for awhile. ------------------------------------------------------------------------ ----------------------------- DRAFT MANET PROBLEM STATEMENT AND DIRECTION (REALLY A CHARTER UPDATE) The purpose of the MANET working group is to standardize IP routing protocol functionality suitable for wireless routing application within both static and dynamic topologies. The fundamental problem issues are that wireless link interfaces have some unique routing interface characteristics and that node topologies within a wireless routing region may experience increased dynamics, due to motion or other factors. The continued proliferation of a wide variety of wireless device technologies and embedded network devices is opening up new wireless networking challenges. MANET specifications fundamentally provide improved operational IP routing performance for dynamic, wireless routing regions. Approaches are intended to be relatively lightweight in nature and suitable for heterogeneous adaptation across multiple hardware and wireless environments. While MANET routing areas may operate in isolation from a larger connected Internet, a primary focus of the MANET WG is to address use as a routing technology extension at the edges of an IP infrastructure. The deployment of hybrid infrastructures (e.g., a mixture of preferred fixed grid and mobile routers) should also be supported by MANET specifications and management features. In the past, this WG has focused on exploring a broad range of MANET problems, performance issues, and related candidate protocols and has developed several EXPERIMENTAL RFCs with associated working prototypes along with an INFORMATIONAL RFC (2501) discussing performance and design considerations. The present protocol frameworks provide Experimental MANET specifications covering both reactive and proactive design spaces and many of the concepts have reached a significant level of engineering maturity. Building off this work, the MANET WG will now concentrate its scope on developing several Proposed Standard specification efforts. Two central routing protocol approaches will be developed. - MANET Reactive Routing Protocol (MRRP) - MANET Proactive Routing Protocol (MPRP) For this goal, it is expected that MRRP will become a convergence of mature reactive design components. Likewise, it is expected that MPRP would be a convergence of mature proactive design components. At this point, the WG has rough consensus that a split between proactive and reactive taxonomies appears sensible from a design complexity and application space perspective. The WG will begin its work with development of protocols along these tracks. If the WG sees significant commonality among the design spaces common building blocks may be developed. The WG will develop both IPv4 and IPv6 support within these protocols. Routing security requirements and issues will also be addressed. Within the MANET WG, the development of a common ALL_MANET_NODES forwarding protocol building block for use withing a MANET routing area has also been identified as a useful work item. The potential for the "broadcast storm problem" to arise is exacerbated in a MANET wireless interface scenario, where each node may have a different set of single hop neighbors. Present MANET routing protocol work has developed a number of flooding optimizations suitable for MANET environments that can reduce significantly the number of redundant transmissions when forwarding packets to ALL_MANET_NODES. A generic MANET flooding building block can be adapted to a routing protocol instantiation and may also be useful in designing service discovery and autoconfiguration mechanisms within MANET areas. The MANET WG will develop a generic flooding building block and related instantiations that will be useful for the intended wireless network environments. Additional WG items that are to be covered by a small set of INFORMATIONAL documents and possible PROPOSED STANDARD specifications relate to issues of address autoconfiguration, MANET gateway discovery and operation, and network service discovery. The MANET WG will work with other IETF WGs to determine and support the working of related issues within the appropriate working groups. Some related work the MANET WG will pay particular attention to will be the OSPF-MANET protocol work within the OSPF WG and the ANS IRTF work that is addressing research topics related to MANET environments. _______________________________________________ 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 exim@www1.ietf.org Thu May 13 11:56:06 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20068 for ; Thu, 13 May 2004 11:56:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOIUg-0005bS-Ty for manet-archive@odin.ietf.org; Thu, 13 May 2004 11:51:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DFpYu7021539 for manet-archive@odin.ietf.org; Thu, 13 May 2004 11:51:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOIMq-0003sP-BW for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 11:43:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19476 for ; Thu, 13 May 2004 11:43:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOIMp-0004Wh-AM for manet-web-archive@ietf.org; Thu, 13 May 2004 11:43:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOIM3-0003yx-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 11:42:40 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BOIL4-0003PJ-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 11:41:38 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BOIL4-0004mV-Q5 for manet-web-archive@ietf.org; Thu, 13 May 2004 11:41:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOIDi-0001zU-8o; Thu, 13 May 2004 11:34:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOI9q-00019i-Es for manet@optimus.ietf.org; Thu, 13 May 2004 11:30:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18827 for ; Thu, 13 May 2004 11:29:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOI9p-0005FW-36 for manet@ietf.org; Thu, 13 May 2004 11:30:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOI8w-0004kL-00 for manet@ietf.org; Thu, 13 May 2004 11:29:07 -0400 Received: from nn1.excitenetwork.com ([207.159.120.55] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BOI82-0003jK-00 for manet@ietf.org; Thu, 13 May 2004 11:28:10 -0400 Received: by xprdmailfe12.nwk.excite.com (Postfix, from userid 110) id F2F6D3DE5; Thu, 13 May 2004 11:27:34 -0400 (EDT) To: Mona.Ghassemian@kcl.ac.uk, jw2000@excite.com Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk. Received: from [139.55.21.238] by xprdmailfe12.nwk.excite.com via HTTP; Thu, 13 May 2004 11:27:34 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Cc: manet@ietf.org Message-Id: <20040513152734.F2F6D3DE5@xprdmailfe12.nwk.excite.com> Date: Thu, 13 May 2004 11:27:34 -0400 (EDT) Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA18828 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, HTML_20_30,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Thanks a lot. That is a good idea. I will try it. Another question is, if I want to limit the movement of some nodes within= a small part of the whole simulation region, what should I do? One meth= od is to modify the output of setdest. But it is complex.=20 Any better approaches? Jack --- On Thu 05/13, Mona < Mona.Ghassemian@kcl.ac.uk > wrote: From: Mona [mailto: Mona.Ghassemian@kcl.ac.uk] To: jw2000@excite.com Cc: manet@ietf.org Date: Thu, 13 May 2004 11:12:21 +0100 Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk.
Hi Jack,
=A0
If you want to create a mobility file with some fixed= specific=20 nodes, the easiest way is to create your mobility file for number of mobi= le=20 nodes. Then set the position of the fix nodes in the tcl file.
=A0
For example you want to generate a scenario with 10 m= obile=20 nodes and 4 fixed nodes. Simply create a mobility file for 10 nodes, set = you=20 number of mobile nodes in your tcl file as 14 and define the position of = fixed=20 nodes in the tcl file.
=A0
If you want to change the speed or the destination of= an=20 specific mobile node, then you need to change parameters of setdest as yo= u have=20 mentioned yourself.
=A0
Kind Regards,
Mona
-----------------------------------------------------------
M= ona=20 Ghassemian, PhD student
Centre for Telecommunications Research
King= 's=20 College London
Drury Lane, London WC2R 5RL
T: +44 20 7848 2889
F= : +44=20 20 7848 2664
E: Mona.Ghassemian@kcl.ac.uk-----------------------------------------------------------
To: manet@ietf.org
Reply-To= : jw2000@excite.com
From: "Jack Wa= ng"=20 <jw2000@excite.com>
Date: Tue= ,=20 11 May 2004 12:49:42 -0400 (EDT)
Subject: [manet] Question about NS2=20 simulation of Ad Hoc netowrk.


Hi all:

For Ad Hoc networ= k=20 simulation in NS2, I can use setdest to genenate a mobility pattern.
A= fter I=20 get the output from setdest, can I modify the output?
For example, if = want a=20 node to be stationary during the whole simulation, I only keep the origin= al=20 coordinates of the node and delete all other lines, like:
$ns_ at=20 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655=20 6.978688752644"=A0
If I want to change the destination and speed of a= =20 node, I can also modify the lines containing these information, like the = above=20 line.
Am I right? Will it cause any=20 error?

Thanks.

Jack

________________________________= _______________
Join=20 Excite! - http://www.excite.com
= The most=20 personalized portal on the Web!

_______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 13 14:45:14 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04968 for ; Thu, 13 May 2004 14:45:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOL9L-0005La-VD for manet-archive@odin.ietf.org; Thu, 13 May 2004 14:41:48 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DIfheo020555 for manet-archive@odin.ietf.org; Thu, 13 May 2004 14:41:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOL6G-0003oz-Ku for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 14:38:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04426 for ; Thu, 13 May 2004 14:38:29 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOL6D-0003ZJ-W0 for manet-web-archive@ietf.org; Thu, 13 May 2004 14:38:30 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOL4M-0002IS-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 14:36:34 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BOL2b-0001OH-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 14:34:45 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BOL2b-0007Qd-PI for manet-web-archive@ietf.org; Thu, 13 May 2004 14:34:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOKrT-0004zu-Br; Thu, 13 May 2004 14:23:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOKb1-0005ij-2C for manet@optimus.ietf.org; Thu, 13 May 2004 14:06:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00199 for ; Thu, 13 May 2004 14:06:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOKay-0002Vo-Lm for manet@ietf.org; Thu, 13 May 2004 14:06:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOKYa-0001UO-00 for manet@ietf.org; Thu, 13 May 2004 14:03:45 -0400 Received: from [203.197.98.4] (helo=avmx.iitkgp.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 1BOKV3-0006F8-00 for manet@ietf.org; Thu, 13 May 2004 14:00:06 -0400 Received: from ece.iitkgp.ernet.in (localhost [127.0.0.1]) by iitkgp.iitkgp.ernet.in (8.9.3/8.9.3) with ESMTP id XAA17262 for ; Thu, 13 May 2004 23:16:37 -0500 (GMT) X-Authentication-Warning: iitkgp.iitkgp.ernet.in: iscan owned process doing -bs Received: from localhost (rkc@localhost) by ece.iitkgp.ernet.in (8.9.3/8.8.7) with ESMTP id XAA07045 for ; Thu, 13 May 2004 23:30:25 +0400 Date: Thu, 13 May 2004 23:30:25 +0400 (RET) From: "C.Rama Krishna" To: manet@ietf.org In-Reply-To: <20040513160007.26727.5908.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Throughput calculation 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 For the follwoing network scenario, how to calculate the throughput(node wise and overall)? Number of nodes = 50 No. of CBR source-destination pairs = 10 Radio range of each node = 250 meters Data rate = 2 Mbps Simulation time = 30 minutes all CBR sources are Transmitting from 1000s to 1800s of simulation time. I am using glomosim-2.03. Any help on this is appreciated. Rama krishna IITKGP, India ***************************************** This Mail is Certified to be Virus Free. CIC Network Security Group, IIT Kharagpur ***************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 13 17:43:01 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18417 for ; Thu, 13 May 2004 17:43:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONxq-00017v-3a for manet-archive@odin.ietf.org; Thu, 13 May 2004 17:42:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DLg2fw004331 for manet-archive@odin.ietf.org; Thu, 13 May 2004 17:42:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONtk-0007Qc-08 for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 17:37:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17688 for ; Thu, 13 May 2004 17:37:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BONtg-0005qw-Pi for manet-web-archive@ietf.org; Thu, 13 May 2004 17:37:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BONqo-0004k1-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 17:34:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BONmR-0003Cd-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 17:30:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONbj-00005J-7l; Thu, 13 May 2004 17:19:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONEN-0008W5-IH for manet@optimus.ietf.org; Thu, 13 May 2004 16:55:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12957 for ; Thu, 13 May 2004 16:55:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BONEL-0000NH-BM for manet@ietf.org; Thu, 13 May 2004 16:55:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BONCh-0007DQ-00 for manet@ietf.org; Thu, 13 May 2004 16:53:19 -0400 Received: from smtp2.stanford.edu ([171.67.16.125]) by ietf-mx with esmtp (Exim 4.12) id 1BONBE-0005pn-00 for manet@ietf.org; Thu, 13 May 2004 16:51:48 -0400 Received: from fable10.Stanford.EDU (fable10.Stanford.EDU [171.64.12.152]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i4DKoVON028146; Thu, 13 May 2004 13:50:31 -0700 Received: (from mukesh@localhost) by fable10.Stanford.EDU (8.12.10/8.12.9) id i4DKoUXL024951; Thu, 13 May 2004 13:50:30 -0700 (PDT) Date: Thu, 13 May 2004 13:50:30 -0700 (PDT) From: Mukesh Hira To: "C.Rama Krishna" cc: manet@ietf.org Subject: Re: [manet] Throughput calculation 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 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 For each source-destination pair, you can get the number of bytes sent by the source and the number of bytes received by the destination, from the AppCbrClient and AppCbrServer statistics in the output file produced by GloMoSim. Dividing the number of bits received by the destination node's AppCbrServer by the CBR session time (800 sec in your case) will give you the throughput in bps for this source-destination pair. Adding the number of bits received by AppCbrServers on all destination nodes and dividing this sum by 800 sec will give you the aggregate network throughput in bps. Hope that helps. - Mukesh On Thu, 13 May 2004, C.Rama Krishna wrote: > > For the follwoing network scenario, how to calculate the throughput(node > wise and overall)? > > Number of nodes = 50 > No. of CBR source-destination pairs = 10 > Radio range of each node = 250 meters > Data rate = 2 Mbps > Simulation time = 30 minutes > all CBR sources are Transmitting from 1000s to 1800s of simulation time. > > I am using glomosim-2.03. > > Any help on this is appreciated. > > Rama krishna > IITKGP, India > > > > > > ***************************************** > This Mail is Certified to be Virus Free. > CIC Network Security Group, IIT Kharagpur > ***************************************** > > _______________________________________________ > 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 exim@www1.ietf.org Thu May 13 22:06:52 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02037 for ; Thu, 13 May 2004 22:06:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOS2o-0000aP-BW for manet-archive@odin.ietf.org; Thu, 13 May 2004 22:03:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4E23QUB002249 for manet-archive@odin.ietf.org; Thu, 13 May 2004 22:03:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOS1D-00006b-Se for manet-web-archive@optimus.ietf.org; Thu, 13 May 2004 22:01:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01839 for ; Thu, 13 May 2004 22:01:44 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOS1A-0007ST-Tc for manet-web-archive@ietf.org; Thu, 13 May 2004 22:01:45 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOS06-0006v5-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 22:00:38 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BORzc-0006OX-00 for manet-web-archive@ietf.org; Thu, 13 May 2004 22:00:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BORrl-0005uG-Si; Thu, 13 May 2004 21:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BORnh-0005GY-Kw for manet@optimus.ietf.org; Thu, 13 May 2004 21:47:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01322 for ; Thu, 13 May 2004 21:47:46 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BORne-0007k6-LV for manet@ietf.org; Thu, 13 May 2004 21:47:46 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BORmk-0007By-00 for manet@ietf.org; Thu, 13 May 2004 21:46:51 -0400 Received: from web50002.mail.yahoo.com ([206.190.38.17]) by ietf-mx with smtp (Exim 4.12) id 1BORlr-0006I2-00 for manet@ietf.org; Thu, 13 May 2004 21:45:55 -0400 Message-ID: <20040513234533.44794.qmail@web50002.mail.yahoo.com> Received: from [136.159.15.15] by web50002.mail.yahoo.com via HTTP; Thu, 13 May 2004 16:45:33 PDT Date: Thu, 13 May 2004 16:45:33 -0700 (PDT) From: Icy Termite To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Time between the RREQs 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,UPPERCASE_25_50 autolearn=no version=2.60 Hi all, It says on the AODV draft 13 that a node waits NET_TRAVERSAL_TIME for a RREP after broadcasting a RREQ and if it doesn't get a reply the node MAY try again by sending another RREQ. For default AODV UU settings NET_TRAVERSAL_TIME = 2 * NODE_TRAVERSAL_TIME * NET_DIAMETER where NODE_TRAVERSAL_TIME is 40 and NET_DIAMETER is 35 making NET_TRAVERSAL_TIME 2800 milliseconds where as I have observed RREQ go out after 330 milliseconds in AODV UU. Could anybody give me an explanation of what I am missing here? Thanks in advance, Icy __________________________________ Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' http://movies.yahoo.com/showtimes/movie?mid=1808405861 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 14 04:28:38 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06880 for ; Fri, 14 May 2004 04:28:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOXzZ-0003Yf-6S for manet-archive@odin.ietf.org; Fri, 14 May 2004 04:24:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4E8OT41013677 for manet-archive@odin.ietf.org; Fri, 14 May 2004 04:24:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOXyX-00035M-Qw for manet-web-archive@optimus.ietf.org; Fri, 14 May 2004 04:23:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06631 for ; Fri, 14 May 2004 04:23:22 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOXyU-0006Sp-RL for manet-web-archive@ietf.org; Fri, 14 May 2004 04:23:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOXx8-0005cB-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 04:21:59 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOXvW-0004m8-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 04:20:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOXnm-0000VQ-In; Fri, 14 May 2004 04:12:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOXlO-0008Ms-7m for manet@optimus.ietf.org; Fri, 14 May 2004 04:09:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05773 for ; Fri, 14 May 2004 04:09:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOXlL-0007IT-EM for manet@ietf.org; Fri, 14 May 2004 04:09:47 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOXkP-0006le-00 for manet@ietf.org; Fri, 14 May 2004 04:08:49 -0400 Received: from aun.it.uu.se ([130.238.12.36] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1BOXjR-0006CO-00 for manet@ietf.org; Fri, 14 May 2004 04:07:49 -0400 Received: from [130.238.8.241] (dhcp-8-241.it.uu.se [130.238.8.241]) by aun.it.uu.se (8.12.11/8.12.10) with ESMTP id i4E87lRD005480; Fri, 14 May 2004 10:07:47 +0200 (MEST) Subject: Re: [manet] Time between the RREQs From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: Icy Termite Cc: manet@ietf.org In-Reply-To: <20040513234533.44794.qmail@web50002.mail.yahoo.com> References: <20040513234533.44794.qmail@web50002.mail.yahoo.com> Content-Type: text/plain Message-Id: <1084522062.17046.2.camel@dhcp-8-241.it.uu.se> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Fri, 14 May 2004 10:07:42 +0200 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The timeouts are different depending on whether you use an expanding ring search or not. Since the ring starts at TTL=1 the wait time is quite short in the beginning, but increases as the ring expands. It is all explained in the RFC/draft. Erik On Fri, 2004-05-14 at 01:45, Icy Termite wrote: > Hi all, > > It says on the AODV draft 13 that a node waits > NET_TRAVERSAL_TIME for a RREP after broadcasting a > RREQ and if it doesn't get a reply the node MAY try > again by sending another RREQ. > > For default AODV UU settings > NET_TRAVERSAL_TIME = 2 * NODE_TRAVERSAL_TIME * > NET_DIAMETER where NODE_TRAVERSAL_TIME is 40 and > NET_DIAMETER is 35 making NET_TRAVERSAL_TIME 2800 > milliseconds where as I have observed RREQ go out > after 330 milliseconds in AODV UU. Could anybody give > me an explanation of what I am missing here? > > Thanks in advance, > Icy > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Movies - Buy advance tickets for 'Shrek 2' > http://movies.yahoo.com/showtimes/movie?mid=1808405861 > > _______________________________________________ > 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 exim@www1.ietf.org Fri May 14 05:55:43 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10410 for ; Fri, 14 May 2004 05:55:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOZNA-0007za-SF for manet-archive@odin.ietf.org; Fri, 14 May 2004 05:52:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4E9quDL030723 for manet-archive@odin.ietf.org; Fri, 14 May 2004 05:52:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOZKU-0007IR-Ao for manet-web-archive@optimus.ietf.org; Fri, 14 May 2004 05:50:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10230 for ; Fri, 14 May 2004 05:50:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOZKQ-0003P4-NG for manet-web-archive@ietf.org; Fri, 14 May 2004 05:50:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOZJP-0002sO-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 05:49:04 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOZIK-0002K1-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 05:47:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOZDc-0005nS-0h; Fri, 14 May 2004 05:43:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOZ9Y-00052j-Ls for manet@optimus.ietf.org; Fri, 14 May 2004 05:38:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09596 for ; Fri, 14 May 2004 05:38:48 -0400 (EDT) From: mmul@itu.dk Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOZ9V-0005cZ-0R for manet@ietf.org; Fri, 14 May 2004 05:38:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOZ8Z-000583-00 for manet@ietf.org; Fri, 14 May 2004 05:37:51 -0400 Received: from tarzan.itu.dk ([130.226.133.3] helo=mail.itu.dk) by ietf-mx with esmtp (Exim 4.12) id 1BOZ7d-0004dC-00 for manet@ietf.org; Fri, 14 May 2004 05:36:53 -0400 Received: from secure.itu.dk (localhost.localdomain [127.0.0.1]) by mail.itu.dk (Postfix) with SMTP id E9E427D85AD for ; Fri, 14 May 2004 11:36:10 +0200 (CEST) Received: from 62.79.7.36 (SquirrelMail authenticated user mmul) by secure.itu.dk with HTTP; Fri, 14 May 2004 11:36:10 +0200 (CEST) Message-ID: <4815.62.79.7.36.1084527370.squirrel@secure.itu.dk> Date: Fri, 14 May 2004 11:36:10 +0200 (CEST) To: manet@ietf.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [manet] GPSR - Perimeter 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,NO_REAL_NAME, PRIORITY_NO_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, I have looked into GPSR and I seem to have missed a point in the perimeter mode forwarding: I understand it the following way: When a packet enters perimeter mode at node x, destined to node d, its starts to forward by the right hand rule. GPSR determines whether the edge to the next hop n intersects the line from x to d, and if so, the packet is forwarded along the next edge bordering the point that is intersected by line x to d. As soon as it reaches a node closer to destination d than x, it goes back into the greedy mode. My problem is: If a packet in perimeter mode reached a node, which borders an edge that intersects line x to d, it would return to greedy mode since the node is bound to be closer to d than x is. Thus the whole idea of checking if the edge intersects line x to d makes no sence. (Unless of course if you use perimeter mode all the way from source to destination, which clearly is not the idea.) Regards Mark M=FCllertz _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 14 07:22:11 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14935 for ; Fri, 14 May 2004 07:22:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOag6-00027O-NO for manet-archive@odin.ietf.org; Fri, 14 May 2004 07:16:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EBGYts008142 for manet-archive@odin.ietf.org; Fri, 14 May 2004 07:16:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaWt-0007xL-Pc for manet-web-archive@optimus.ietf.org; Fri, 14 May 2004 07:07:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14407 for ; Fri, 14 May 2004 07:07:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOaWp-0004LU-IU for manet-web-archive@ietf.org; Fri, 14 May 2004 07:06:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOaVq-0003qU-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 07:05:59 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOaVF-0003MV-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 07:05:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaR4-0006gg-Nf; Fri, 14 May 2004 07:01:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaPB-0006If-KO for manet@optimus.ietf.org; Fri, 14 May 2004 06:59:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14103 for ; Fri, 14 May 2004 06:59:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOaP7-0000Mj-D4 for manet@ietf.org; Fri, 14 May 2004 06:59:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOaOC-0007d6-00 for manet@ietf.org; Fri, 14 May 2004 06:58:04 -0400 Received: from mr2-n.kom.tuwien.ac.at ([128.131.2.110] helo=mr.tuwien.ac.at) by ietf-mx with esmtp (Exim 4.12) id 1BOaNA-0006cR-00 for manet@ietf.org; Fri, 14 May 2004 06:57:00 -0400 Received: from ecs.tuwien.ac.at (xanadu.ecs.tuwien.ac.at [128.130.40.153]) by mr.tuwien.ac.at (8.12.10/8.12.8) with ESMTP id i4EAuTQ5006921; Fri, 14 May 2004 12:56:29 +0200 (MEST) Message-ID: <40A4A5DD.5070500@ecs.tuwien.ac.at> Date: Fri, 14 May 2004 12:56:29 +0200 From: Hannes Stratil User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020918 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mmul@itu.dk CC: manet@ietf.org Subject: Re: [manet] GPSR - Perimeter mode References: <4815.62.79.7.36.1084527370.squirrel@secure.itu.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mr.tuwien.ac.at id i4EAuTQ5006921 Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Mark, Your observation is correct! It does not make sense, if the planar subgraph is a Gabriel Graph or a=20 Relative Neighborhood Graph. Kind Regards, Hannes mmul@itu.dk wrote: >Hi, > >I have looked into GPSR and I seem to have missed a point >in the perimeter mode forwarding: > >I understand it the following way: >When a packet enters perimeter mode at node x, destined to node d, >its starts to forward by the right hand rule. GPSR determines >whether the edge to the next hop n intersects the line from x to d, >and if so, the packet is forwarded along the next edge bordering the >point that is intersected by line x to d. >As soon as it reaches a node closer to destination d than x, it goes >back into the greedy mode. > >My problem is: >If a packet in perimeter mode reached a node, which borders an edge >that intersects line x to d, it would return to greedy mode since >the node is bound to be closer to d than x is. >Thus the whole idea of checking if the edge intersects line x to d >makes no sence. >(Unless of course if you use perimeter mode all the way from source >to destination, which clearly is not the idea.) > > >Regards > >Mark M=FCllertz > > > > > > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 14 07:23:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15035 for ; Fri, 14 May 2004 07:23:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOahw-0002hJ-7a for manet-archive@odin.ietf.org; Fri, 14 May 2004 07:18:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EBIS89010363 for manet-archive@odin.ietf.org; Fri, 14 May 2004 07:18:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaeb-0001fd-VU for manet-web-archive@optimus.ietf.org; Fri, 14 May 2004 07:15:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14712 for ; Fri, 14 May 2004 07:15:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOaeb-0000a1-GO for manet-web-archive@ietf.org; Fri, 14 May 2004 07:15:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOadm-00005Q-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 07:14:11 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOad8-0007Nz-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 07:13:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaT0-00070m-73; Fri, 14 May 2004 07:03:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOaQ1-0006UA-4x for manet@optimus.ietf.org; Fri, 14 May 2004 06:59:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14155 for ; Fri, 14 May 2004 06:59:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOaPw-0000rO-PP for manet@ietf.org; Fri, 14 May 2004 06:59:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOaP1-0000Lr-00 for manet@ietf.org; Fri, 14 May 2004 06:58:55 -0400 Received: from web90007.mail.scd.yahoo.com ([66.218.94.65]) by ietf-mx with smtp (Exim 4.12) id 1BOaO5-00078l-00 for manet@ietf.org; Fri, 14 May 2004 06:57:57 -0400 Message-ID: <20040514093430.56043.qmail@web90007.mail.scd.yahoo.com> Received: from [193.95.33.18] by web90007.mail.scd.yahoo.com via HTTP; Fri, 14 May 2004 11:34:30 CEST Date: Fri, 14 May 2004 11:34:30 +0200 (CEST) From: =?iso-8859-1?q?Fehmi?= To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA14156 Subject: [manet] Ad hoc 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi everybody! I would like to do some changes on an ad hoc implementation to make some experimental change to aodv and other routing protocols in Ad hoc wireless network. Instead of having only one route from the source and destination nodes,I target to keep another routes in cache and this to try to use them if the actif route breaks down and this without losing time (extra delai) to start another routing request... My question is what is the most appropriate implementation to download and to work on!=20 Thanks a lot everybody =09 =09 =09 Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !=20 Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis gr=E2ce =E0 Yahoo! Messenger !T=E9l=E9c= hargez Yahoo! Messenger sur http://fr.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 14 17:33:35 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29247 for ; Fri, 14 May 2004 17:33:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOk7K-0008KY-5a for manet-archive@odin.ietf.org; Fri, 14 May 2004 17:21:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ELLIxb032015 for manet-archive@odin.ietf.org; Fri, 14 May 2004 17:21:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOk3R-0006ou-R2 for manet-web-archive@optimus.ietf.org; Fri, 14 May 2004 17:17:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28084 for ; Fri, 14 May 2004 17:17:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOk3P-00050a-Ed for manet-web-archive@ietf.org; Fri, 14 May 2004 17:17:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOk1B-00047J-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 17:14:58 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BOjxC-0002tA-00 for manet-web-archive@ietf.org; Fri, 14 May 2004 17:10:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOjre-0002NH-AY; Fri, 14 May 2004 17:05:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOjbl-0004pH-H8 for manet@optimus.ietf.org; Fri, 14 May 2004 16:48:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24827 for ; Fri, 14 May 2004 16:48:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOjbj-0001FS-F4 for manet@ietf.org; Fri, 14 May 2004 16:48:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOjXu-0007b0-00 for manet@ietf.org; Fri, 14 May 2004 16:44:42 -0400 Received: from nn1.excitenetwork.com ([207.159.120.55] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BOjUG-00067V-00 for manet@ietf.org; Fri, 14 May 2004 16:40:56 -0400 Received: by xprdmailfe12.nwk.excite.com (Postfix, from userid 110) id EB0D83E96; Fri, 14 May 2004 16:40:23 -0400 (EDT) To: manet@ietf.org Received: from [139.55.21.238] by xprdmailfe12.nwk.excite.com via HTTP; Fri, 14 May 2004 16:40:23 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040514204023.EB0D83E96@xprdmailfe12.nwk.excite.com> Date: Fri, 14 May 2004 16:40:23 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] NS2 memory consumption 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I run a ad hoc network simulation with 200 nodes for 60 seconds. But when the simulation reachs about 50 seconds, the memory is used up, then segmentation fault. I use "gdb ns core" and find that the error comes from /gcc/frame.c. The machine is SUN workstation with 1G memory. What is the problem? Thanks, Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 15 12:16:47 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28717 for ; Sat, 15 May 2004 12:16:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP1oZ-0001yi-KZ for manet-archive@odin.ietf.org; Sat, 15 May 2004 12:15:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4FGF78n007578 for manet-archive@odin.ietf.org; Sat, 15 May 2004 12:15:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP1e3-0007UX-UB for manet-web-archive@optimus.ietf.org; Sat, 15 May 2004 12:04:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28265 for ; Sat, 15 May 2004 12:04:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP1e2-0000n4-NM for manet-web-archive@ietf.org; Sat, 15 May 2004 12:04:14 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP1cw-0000MW-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 12:03:07 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BP1c2-0007lU-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 12:02:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP1NO-0005QI-GS; Sat, 15 May 2004 11:47:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP1Lq-0005B3-JD for manet@optimus.ietf.org; Sat, 15 May 2004 11:45:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27726 for ; Sat, 15 May 2004 11:45:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP1Lp-00012h-G9 for manet@ietf.org; Sat, 15 May 2004 11:45:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP1L4-0000dT-00 for manet@ietf.org; Sat, 15 May 2004 11:44:39 -0400 Received: from nn5.excitenetwork.com ([207.159.120.59] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BP1Jt-0007j3-00 for manet@ietf.org; Sat, 15 May 2004 11:43:25 -0400 Received: by xprdmailfe24.nwk.excite.com (Postfix, from userid 110) id 812261E433; Sat, 15 May 2004 11:42:51 -0400 (EDT) To: hvimadal@usc.edu Subject: Re: [manet] NS2 memory consumption Received: from [139.55.21.238] by xprdmailfe24.nwk.excite.com via HTTP; Sat, 15 May 2004 11:42:51 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: manet@ietf.org Message-Id: <20040515154251.812261E433@xprdmailfe24.nwk.excite.com> Date: Sat, 15 May 2004 11:42:51 -0400 (EDT) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.7 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Hemen: Thanks for your information. What cause the problem? My SUN workstation has 1G RAM and 1G swap. Is the memory not enough? or memory leak? Jack --- On Fri 05/14, hemen vimadalal < hvimadal@usc.edu > wrote: From: hemen vimadalal [mailto: hvimadal@usc.edu] To: jw2000@excite.com Date: Fri, 14 May 2004 19:00:11 -0700 Subject: Re: [manet] NS2 memory consumption NS supports up to 120 nodes thats what i have tried last successfully beyond that the same error i get too

HEMEN R.VIMADALAL
B.S. ELECTRONICS ENGINEERING(Mumbai University)
M.S. ELECTRICAL ENGINEERING(U S C)
Phone # (323)620 6279

_______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 15 15:06:54 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05601 for ; Sat, 15 May 2004 15:06:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP4QN-0002Ey-EW for manet-archive@odin.ietf.org; Sat, 15 May 2004 15:02:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4FJ2JDE008611 for manet-archive@odin.ietf.org; Sat, 15 May 2004 15:02:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP4MV-0006rw-W3 for manet-web-archive@optimus.ietf.org; Sat, 15 May 2004 14:58:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04859 for ; Sat, 15 May 2004 14:58:17 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP4MT-0001IT-6f for manet-web-archive@ietf.org; Sat, 15 May 2004 14:58:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP4LX-0000so-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 14:57:20 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BP4KU-0000Sd-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 14:56:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP4Bc-00054r-2s; Sat, 15 May 2004 14:47:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP44A-0004ES-KM for manet@optimus.ietf.org; Sat, 15 May 2004 14:39:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04381 for ; Sat, 15 May 2004 14:39:19 -0400 (EDT) From: haas@ece.cornell.edu Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP447-0001Ub-S1 for manet@ietf.org; Sat, 15 May 2004 14:39:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP43A-00016T-00 for manet@ietf.org; Sat, 15 May 2004 14:38:20 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 1BP42R-0000i8-00 for manet@ietf.org; Sat, 15 May 2004 14:37:35 -0400 Received: from zeno.ece.cornell.edu (zeno.ece.cornell.edu [128.84.81.136]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 340281E8008; Sat, 15 May 2004 14:37:35 -0400 (EDT) Date: Sat, 15 May 2004 14:40:01 -0400 (EDT) To: Jack Wang Cc: hvimadal@usc.edu, barr@cs.cornell.edu, manet@ietf.org Subject: Re: [manet] NS2 memory consumption In-Reply-To: <20040515154251.812261E433@xprdmailfe24.nwk.excite.com> 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,NO_REAL_NAME autolearn=no version=2.60 Hi Jack and Hemen, --- On Fri 05/14, hemen vimadalal < hvimadal@usc.edu > wrote: > NS supports up to 120 nodes thats what i have tried last successfully > beyond that the same error i get too Can't resist to put (another) plug to our work - JiST, developed at Cornell's WNL, has been used to simulate hundreds of thousand of nodes ... see: http://www.cs.cornell.edu/barr/repository/jist/ Enjoy! Zygmunt. ==-==-==== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- 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(at)ece(dot)cornell(dot)edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Sat, 15 May 2004, Jack Wang wrote: > > > Hi Hemen: > > Thanks for your information. > What cause the problem? My SUN workstation has 1G RAM and 1G swap. Is the memory not enough? or memory leak? > > Jack > > > --- On Fri 05/14, hemen vimadalal < hvimadal@usc.edu > wrote: > From: hemen vimadalal [mailto: hvimadal@usc.edu] > To: jw2000@excite.com > Date: Fri, 14 May 2004 19:00:11 -0700 > Subject: Re: [manet] NS2 memory consumption > > NS supports up to 120 nodes thats what i have tried last successfully beyond that the same error i get too

HEMEN R.VIMADALAL
B.S. ELECTRONICS ENGINEERING(Mumbai University)
M.S. ELECTRICAL ENGINEERING(U S C)
Phone # (323)620 6279

> > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > _______________________________________________ > 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 exim@www1.ietf.org Sat May 15 20:53:40 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20905 for ; Sat, 15 May 2004 20:53:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP9qI-0003Mf-0A for manet-archive@odin.ietf.org; Sat, 15 May 2004 20:49:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4G0nPb3012933 for manet-archive@odin.ietf.org; Sat, 15 May 2004 20:49:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP9pN-00039a-Rw for manet-web-archive@optimus.ietf.org; Sat, 15 May 2004 20:48:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20729 for ; Sat, 15 May 2004 20:48:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP9pL-00058W-It for manet-web-archive@ietf.org; Sat, 15 May 2004 20:48:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP9oU-0004kO-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 20:47:35 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BP9nx-0004M7-00 for manet-web-archive@ietf.org; Sat, 15 May 2004 20:47:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP9dK-000180-4B; Sat, 15 May 2004 20:36:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BP9Z2-0000eJ-S9 for manet@optimus.ietf.org; Sat, 15 May 2004 20:31:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20124 for ; Sat, 15 May 2004 20:31:34 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BP9Z0-0005xx-Hs for manet@ietf.org; Sat, 15 May 2004 20:31:34 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BP9Y8-0005Yx-00 for manet@ietf.org; Sat, 15 May 2004 20:30:41 -0400 Received: from nn6.excitenetwork.com ([207.159.120.60] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BP9XO-00059E-00 for manet@ietf.org; Sat, 15 May 2004 20:29:54 -0400 Received: by xprdmailfe1.nwk.excite.com (Postfix, from userid 110) id 3BC4B109ED6; Sat, 15 May 2004 20:29:25 -0400 (EDT) To: manet@ietf.org Received: from [139.55.21.238] by xprdmailfe1.nwk.excite.com via HTTP; Sat, 15 May 2004 20:29:25 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040516002925.3BC4B109ED6@xprdmailfe1.nwk.excite.com> Date: Sat, 15 May 2004 20:29:25 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] Packet dropping problem 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am simulating routing protocol for Ad Hoc network with 200 nodes. I find that about 30 percent of the data packet is dropped in IFQ. Below are some lines from the trace file: D 82.416615074 _106_ IFQ --- 279 cbr 532 [13a bd 6a 800] ------- [53:1 55:0 27 189] [2] 3 6 D 82.416615074 _106_ IFQ --- 314 cbr 532 [13a bd 6a 800] ------- [53:1 55:0 27 189] [4] 3 6 D 82.416615074 _106_ IFQ --- 342 cbr 532 [13a bd 6a 800] ------- [53:1 55:0 26 189] [6] 4 5 D 83.309369563 _108_ IFQ --- 324 cbr 532 [13a 7a 6c 800] ------- [53:1 55:0 20 122] [5] 10 5 D 114.010025000 _65_ IFQ --- 779 cbr 532 [0 b8 41 800] ------- [65:0 66:0 30 184] [39] 0 5 D 114.010025000 _65_ IFQ --- 322 cbr 532 [13a b8 41 800] ------- [62:2 64:0 24 184] [18] 6 4 D 114.010025000 _65_ IFQ --- 802 cbr 532 [0 b8 41 800] ------- [65:0 66:0 30 184] [40] 0 5 D 114.010025000 _78_ IFQ --- 197 cbr 532 [13a 7d 4e 800] ------- [6:1 7:0 26 125] [9] 4 3 D 114.010025000 _78_ IFQ --- 216 cbr 532 [13a 7d 4e 800] ------- [6:1 7:0 26 125] [10] 4 3 D 114.010025000 _78_ IFQ --- 223 cbr 532 [13a 7d 4e 800] ------- [6:1 7:0 26 125] [11] 4 3 What cause the data packet dropping? The length of the queue is 800. I am using Queue/DropTail/PriQueue. Is the queue too short? Thanks a lot. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 17 02:09:24 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23758 for ; Mon, 17 May 2004 02:09:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPbEQ-0005xu-MF for manet-archive@odin.ietf.org; Mon, 17 May 2004 02:04:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4H64Af4022925 for manet-archive@odin.ietf.org; Mon, 17 May 2004 02:04:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPb69-0003eV-UU for manet-web-archive@optimus.ietf.org; Mon, 17 May 2004 01:55:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16422 for ; Mon, 17 May 2004 01:55:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPb66-0005ZU-PQ for manet-web-archive@ietf.org; Mon, 17 May 2004 01:55:34 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPb57-0005GZ-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 01:54:34 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPb47-0004sb-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 01:53:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPaty-0002PP-8Y; Mon, 17 May 2004 01:43:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPath-0002J3-GR for manet@optimus.ietf.org; Mon, 17 May 2004 01:42:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15976 for ; Mon, 17 May 2004 01:42:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPate-0001fs-9T for manet@ietf.org; Mon, 17 May 2004 01:42:42 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPase-0001NF-00 for manet@ietf.org; Mon, 17 May 2004 01:41:41 -0400 Received: from [203.197.196.2] (helo=mail2.iitk.ac.in) by ietf-mx with esmtp (Exim 4.12) id 1BParn-0000nR-00 for manet@ietf.org; Mon, 17 May 2004 01:40:47 -0400 Received: from antivirus.cc.iitk.ac.in (antivirus.cc.iitk.ac.in [172.31.1.102]) by mail2.iitk.ac.in (8.12.8/8.12.8) with SMTP id i4H5uA65019846; Mon, 17 May 2004 11:26:11 +0530 Received: from mailhost.cse.iitk.ac.in ([172.27.16.2]) by antivirus.cc.iitk.ac.in (SAVSMTP 3.1.0.29) with SMTP id M2004051711145232056 ; Mon, 17 May 2004 11:14:52 +0530 Received: from csews35.cse.iitk.ac.in (csews35.cse.iitk.ac.in [172.27.19.35]) by mailhost.cse.iitk.ac.in (8.12.8/8.12.8) with ESMTP id i4H5Xsol001476; Mon, 17 May 2004 11:03:54 +0530 Date: Mon, 17 May 2004 11:03:54 +0530 (IST) From: Nilesh Bansal To: manet@ietf.org cc: jw2000@excite.com, Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Interesting question Jack, But i got a doubt in the earlier solution itself. If u change the mobility file as u said, or add some fix nodes in the tcl file as suggested by mona, then won't it be required to provide this (n other coz of this) information to "god"? If yes, then how to do it? Actually the doubt arises bcoz of mysterious working/significance of god... Any i/ps why exactly it's needed? regards, --nilesh ------------------------------------------------------------------ Thanks a lot. That is a good idea. I will try it. Another question is, if I want to limit the movement of some nodes within a small part of the whole simulation region, what should I do? One method is to modify the output of setdest. But it is complex. Any better approaches? Jack --- On Thu 05/13, Mona < Mona.Ghassemian@kcl.ac.uk > wrote: From: Mona [mailto: Mona.Ghassemian@kcl.ac.uk] To: jw2000@excite.com Cc: manet@ietf.org Date: Thu, 13 May 2004 11:12:21 +0100 Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk. Hi Jack, If you want to create a mobility file with some fixed specific nodes, the easiest way is to create your mobility file for number of mobile nodes. Then set the position of the fix nodes in the tcl file. For example you want to generate a scenario with 10 mobile nodes and 4 fixed nodes. Simply create a mobility file for 10 nodes, set you number of mobile nodes in your tcl file as 14 and define the position of fixed nodes in the tcl file. If you want to change the speed or the destination of an specific mobile node, then you need to change parameters of setdest as you have mentioned yourself. Kind Regards, Mona ----------------------------------------------------------- Mona Ghassemian, PhD student Centre for Telecommunications Research King's College London Drury Lane, London WC2R 5RL T: +44 20 7848 2889 F: +44 20 7848 2664 E: Mona.Ghassemian@kcl.ac.uk ----------------------------------------------------------- To: manet@ietf.org Reply-To: jw2000@excite.com From: "Jack Wang" Date: Tue, 11 May 2004 12:49:42 -0400 (EDT) Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk. Hi all: For Ad Hoc network simulation in NS2, I can use setdest to genenate a mobility pattern. After I get the output from setdest, can I modify the output? For example, if want a node to be stationary during the whole simulation, I only keep the original coordinates of the node and delete all other lines, like: $ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 841.668771362655 6.978688752644" If I want to change the destination and speed of a node, I can also modify the lines containing these information, like the above line. Am I right? Will it cause any error? Thanks. Jack _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 17 12:46:43 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04273 for ; Mon, 17 May 2004 12:46:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPl3p-00073g-Ek for manet-archive@odin.ietf.org; Mon, 17 May 2004 12:33:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HGXr1e027133 for manet-archive@odin.ietf.org; Mon, 17 May 2004 12:33:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkv9-0005X9-27 for manet-web-archive@optimus.ietf.org; Mon, 17 May 2004 12:24:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02786 for ; Mon, 17 May 2004 12:24:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPkv7-0004lh-H8 for manet-web-archive@ietf.org; Mon, 17 May 2004 12:24:53 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPku0-0004Kc-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 12:23:45 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPksI-0003Ym-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 12:21:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkZx-0000CH-Ka; Mon, 17 May 2004 12:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkTW-0007p7-T9 for manet@optimus.ietf.org; Mon, 17 May 2004 11:56:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00449 for ; Mon, 17 May 2004 11:56:20 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPkTV-0002LW-E3 for manet@ietf.org; Mon, 17 May 2004 11:56:21 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPkSR-00020b-00 for manet@ietf.org; Mon, 17 May 2004 11:55:16 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 1BPkRm-0001g1-00 for manet@ietf.org; Mon, 17 May 2004 11:54:34 -0400 Received: from Panacea_2.cornell.edu (dhcp-128-84-210-143-r3a-desktop.ece.cornell.edu [128.84.210.143]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id B01EC1E8008; Mon, 17 May 2004 11:54:33 -0400 (EDT) Message-Id: <5.2.1.1.2.20040517115011.02c1fbf0@postoffice7.mail.cornell.edu> X-Sender: papadp@pop.ece.cornell.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 17 May 2004 11:54:32 -0400 To: manet@ietf.org From: Panos Papadimitratos Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] ESAS 2004 - Call for Participation 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Call for Participation 1st European Workshop on Security in Ad-Hoc and Sensor Networks - ESAS 2004 August 5-6, 2004 Heidelberg, Germany Dear Friends of ESAS, The technical program and registration information is now available on the ESAS web page http://www.netlab.nec.de/esas/esas2004.html Invited talks will be given by Jean-Pierre Hubaux (EPFL) and Antonis Galetsas (European Commission). Please note that we offer an early registration fee until June 30, 2004. A few words about numbers From 55 submissions, 18 papers have been accepted for presentation at the Workshop. With best regards, Claude Castelluccia, INRIA, France Hannes Hartenstein, University of Karlsruhe, Germany Christof Paar, University of Bochum, Germany Dirk Westhoff, NEC Network Labs Heidelberg, Germany ********************************************************************* ESAS 2004 Technical Program All talks will be held at EURESCOM Day 1 - Thursday, August 5, 2004 ========================== 08:30 - 09:20 Registration 09:20 - 09:30 Opening remarks Invited Talk I ----------------- 09:30 - 10:25 "TBA" Jean-Pierre Hubaux (EPFL Lausanne, Switzerland) Session I - Sensor Networks I ---------------------------------------- 10:25 - 10:50 "Public-key Cryptography in Sensor Networks - Revisited" Gunnar Gaubatz, Jens-Peter Kaps, Berk Sunar (Worcester Polytechnic Institute - USA) 10:50 - 11:15 "Key Management in Wireless Sensor Networks" Yann-Hang Lee, Amit Deshmukh, Vikram Phadke, Jin Wook Lee (Arizona State University - USA) 11:15 - 11:40 "Exploring Message Authentication in Sensor Networks" Harald Vogt (ETH Zuerich - Switzerland) 11:40 - 12:10 Refreshment Break Session II - Single-hop and Radio --------------------------------------------- 12:10 - 12:35 "Secure Initialization in Single-Hop Radio Networks" Miroslaw Kutylowski, Wojciech Rutkowski (Wroclaw University of Technology, CC Signet - Poland) 12:35 - 13:00 "Enhancing RFID Privacy via Energy Analysis - Invited Talk" Kenneth P. Fishkin, Summit Roy, Bing Jiang (Intel Research Seattle, University of Washington - USA) 13:00 - 14:00 Lunch Session III - Cryptography I ------------------------------------- 14:00 - 14:25 "Ring Signature Schemes for General Ad-hoc Access Structures" Javier Herranz, German Saez (Universitat Politecnica de Catalunya - Spain) 14:25 - 14:50 "Blind Spontaneous Anonymous Group Signatures for Ad Hoc Groups," Tony K. Chan, Karyin Pung, Joseph K. Lin, V. K. Wei (Chinese University of Hong Kong - Hong Kong) 14:50 - 15:15 "Secure AES Hardware Module for Resource Constrained Devices" Elena Trichina, Tymur Korkisko (Samsung - Korea) Session IV - Ad Hoc Networks I ------------------------------------------ 15:15 - 15:40 "Security for Interactions in Pervasive Networks" Seamus Moloney, Phillip Ginzboorg (Nokia Research Center - Finland) 15:40 - 16:05 "Securely Propagating Authentication In An Ensemble of Personal Devices Using Single Sign-On," Prakash Reddy, Eamonn O'Brien-Strain, Jim Rowson (HP Labs - USA) 16:05 - 16:30 "Pseudonym Generation Scheme for Ad-Hoc Group Communication based on IDF," Marc Manulis, Joerg Schwenk (University of Bochum - Germany) 16:30 - 17:00 Refreshment Break Session V - Peer-to-Peer and Charging ----------------------------------------------------- 17:00 - 17:25 "Secure Overlay for Service Centric Wireless Sensor Networks" Hans-Joachim Hof, Erik-Oliver Blass, Martina Zitterbart (University of Karlsruhe - Germany) 17:25 - 17:50 "Linking Ad hoc Charging Schemes to AAAC Architectures" Joao Girao, Bernd Lamparter, Dirk Westhoff, Rui L. Agiur, J. P. Barraca (NEC Europe Ltd. - Germany, University of Aveiro - Portugal) 18:30 - 21:30 Banquet Day 2 - Friday, August 6 =================== Invited Talk II ------------------- 09:00 - 9:55 "Title not confirmed yet" Antonis Galetsas (European Commission) 09:55 - 10:25 Refreshment Break Session VI - Ad Hoc Networks II ------------------------------------------- 10:25 - 10:50 "IKE in Ad Hoc IP Networking" Kaisa Nyberg (Nokia Group - Finland) 10:50 - 11:15 "Advanced Detection of Selfish or Malicious Nodes in Ad hoc Networks," Frank Kargl, Andreas Klenk, Michael Weber, Stefan Schlott (University of Ulm - Germany) Session VII - Sensor Networks II -------------------------------------------- 11:15 - 11:40 "A security architecture for mobile wireless sensor networks" Stefan Schmidt, Holger Krahn, Stefan Fischer, Dietmar Watjan (TU Braunschweig - Germany) 11:40 - 12:05 "Efficient Key Pre-distribution Schemes for Sensor Networks" Lydia Ray, Rajgopal Kannan, Arjan Durresi (Louisiana State University - USA) 12:05 - 12:30 "SDD Secure Distributed Diffusion Protocol for Sensor Networks" Xiaoyun Wang, Lizhen Yang, Kefei Chen (Shanghai Jiaoung University - Shanghai) 12:30 - 13:30 Lunch _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon May 17 14:30:22 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12226 for ; Mon, 17 May 2004 14:30:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPmdE-0006aP-5C for manet-archive@odin.ietf.org; Mon, 17 May 2004 14:14:34 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HIEWwx025317 for manet-archive@odin.ietf.org; Mon, 17 May 2004 14:14:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPmZQ-0005th-56 for manet-web-archive@optimus.ietf.org; Mon, 17 May 2004 14:10:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09597 for ; Mon, 17 May 2004 14:10:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPmZN-0002mC-MR for manet-web-archive@ietf.org; Mon, 17 May 2004 14:10:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPmY6-0002FJ-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 14:09:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPmWl-0001Y4-00 for manet-web-archive@ietf.org; Mon, 17 May 2004 14:07:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPmGU-0002Pz-46; Mon, 17 May 2004 13:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPm7z-0000y9-8H for manet@optimus.ietf.org; Mon, 17 May 2004 13:42:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07841 for ; Mon, 17 May 2004 13:42:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPm7w-0000gs-JT for manet@ietf.org; Mon, 17 May 2004 13:42:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPm71-0000NG-00 for manet@ietf.org; Mon, 17 May 2004 13:41:16 -0400 Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx with esmtp (Exim 4.12) id 1BPm6Q-00000z-00 for manet@ietf.org; Mon, 17 May 2004 13:40:38 -0400 Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id E146018807; Mon, 17 May 2004 19:40:06 +0200 (CEST) Received: from correo.um.es (zape.um.es [155.54.212.102]) by smtp.um.es (Postfix) with ESMTP id BBCCD17982; Mon, 17 May 2004 19:40:06 +0200 (CEST) Received: from dif.um.es (dibulibu.um.es [155.54.1.250]) by correo.um.es (Postfix) with ESMTP id DFA9F5CC4; Mon, 17 May 2004 19:40:02 +0200 (MEST) Message-ID: <40A8F927.3020700@dif.um.es> Date: Mon, 17 May 2004 19:40:55 +0200 From: "Pedro M. Ruiz" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030821 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nilesh Bansal Cc: manet@ietf.org, jw2000@excite.com, Mona.Ghassemian@kcl.ac.uk Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk References: In-Reply-To: X-Enigmail-Version: 0.76.5.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 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit AFAIK, God is an object with a perfect knowledge about the topology. It was used by CMU to assess the performance of ad hoc routing protocols compared to the optimal routes. I think that if you are not interested in making the same comparisons, then you can change those files without the need to update God with those changes. Regards, Pedro Nilesh Bansal wrote: >Interesting question Jack, But i got a doubt in the earlier solution >itself. If u change the mobility file as u said, or add some fix nodes >in the tcl file as suggested by mona, then won't it be required to provide >this (n other coz of this) information to "god"? If yes, then how to do >it? > >Actually the doubt arises bcoz of mysterious working/significance of >god... Any i/ps why exactly it's needed? > >regards, >--nilesh > >------------------------------------------------------------------ >Thanks a lot. That is a good idea. I will try it. >Another question is, if I want to limit the movement of some nodes within >a small part of the whole simulation region, what should I do? One method >is to modify the output of setdest. But it is complex. >Any better approaches? > >Jack > > > --- On Thu 05/13, Mona < Mona.Ghassemian@kcl.ac.uk > wrote: >From: Mona [mailto: Mona.Ghassemian@kcl.ac.uk] >To: jw2000@excite.com > Cc: manet@ietf.org >Date: Thu, 13 May 2004 11:12:21 +0100 >Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk. > > Hi >Jack, > >If you want to create a mobility file with some fixed specific nodes, the >easiest way is to create your mobility file for number of mobile nodes. >Then set the position of the fix nodes in the tcl file. > >For example you want to generate a scenario with 10 mobile nodes and 4 >fixed nodes. Simply create a mobility file for 10 nodes, set you number of >mobile nodes in your tcl file as 14 and define the position of fixed nodes >in the tcl file. > >If you want to change the speed or the destination of an specific mobile >node, then you need to change parameters of setdest as you have mentioned >yourself. > >Kind Regards, >Mona >----------------------------------------------------------- >Mona Ghassemian, PhD student >Centre for Telecommunications Research >King's College London >Drury Lane, London WC2R 5RL >T: +44 20 7848 2889 >F: +44 20 7848 2664 >E: Mona.Ghassemian@kcl.ac.uk >----------------------------------------------------------- > >To: manet@ietf.org >Reply-To: jw2000@excite.com >From: "Jack Wang" >Date: Tue, 11 May 2004 12:49:42 -0400 (EDT) >Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk. > > >Hi all: > >For Ad Hoc network simulation in NS2, I can use setdest to genenate a >mobility pattern. >After I get the output from setdest, can I modify the output? >For example, if want a node to be stationary during the whole simulation, >I only keep the original coordinates of the node and delete all other >lines, like: >$ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036 >841.668771362655 6.978688752644" >If I want to change the destination and speed of a node, I can also modify >the lines containing these information, like the above line. >Am I right? Will it cause any error? > >Thanks. > >Jack > > >_______________________________________________ >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 exim@www1.ietf.org Tue May 18 09:50:02 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14949 for ; Tue, 18 May 2004 09:50:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ4x4-00088J-Eu for manet-archive@odin.ietf.org; Tue, 18 May 2004 09:48:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IDmEri031261 for manet-archive@odin.ietf.org; Tue, 18 May 2004 09:48:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ4nl-0005mS-3c for manet-web-archive@optimus.ietf.org; Tue, 18 May 2004 09:38:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14459 for ; Tue, 18 May 2004 09:38:34 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ4nj-0007RR-34 for manet-web-archive@ietf.org; Tue, 18 May 2004 09:38:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ4mi-00070a-00 for manet-web-archive@ietf.org; Tue, 18 May 2004 09:37:33 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQ4ln-0006an-00 for manet-web-archive@ietf.org; Tue, 18 May 2004 09:36:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ4ba-0001X4-UD; Tue, 18 May 2004 09:26:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ4Su-0006QW-ML for manet@optimus.ietf.org; Tue, 18 May 2004 09:17:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12892 for ; Tue, 18 May 2004 09:17:02 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ4Ss-0006n8-Ok for manet@ietf.org; Tue, 18 May 2004 09:17:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ4Ry-0006RC-00 for manet@ietf.org; Tue, 18 May 2004 09:16:07 -0400 Received: from bay1-f76.bay1.hotmail.com ([65.54.245.76] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1BQ4RA-0005ig-00 for manet@ietf.org; Tue, 18 May 2004 09:15:16 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 18 May 2004 06:14:45 -0700 Received: from 221.11.5.35 by by1fd.bay1.hotmail.msn.com with HTTP; Tue, 18 May 2004 13:14:45 GMT X-Originating-IP: [221.11.5.35] X-Originating-Email: [zhaoyuting77@hotmail.com] X-Sender: zhaoyuting77@hotmail.com From: "z yt" To: manet@ietf.org Date: Tue, 18 May 2004 21:14:45 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 18 May 2004 13:14:45.0415 (UTC) FILETIME=[16AC6370:01C43CDA] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id JAA12894 Subject: [manet] Source code of Fisheye? 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable hello,all, We are examming the routing protocols in MANET. I need the source code of Fisheye routing, is there any good man tell me=20 how can I get it? God Bless U! Good luck! Yuting Zhao _________________________________________________________________ =D3=EB=C1=AA=BB=FA=B5=C4=C5=F3=D3=D1=BD=F8=D0=D0=BD=BB=C1=F7=A3=AC=C7=EB=CA= =B9=D3=C3 MSN Messenger: http://messenger.msn.com/cn =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed May 19 18:08:26 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23622 for ; Wed, 19 May 2004 18:08:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQZ4J-0003HD-G5 for manet-archive@odin.ietf.org; Wed, 19 May 2004 17:57:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JLvhru012596 for manet-archive@odin.ietf.org; Wed, 19 May 2004 17:57:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQZ18-0001Pj-AM for manet-web-archive@optimus.ietf.org; Wed, 19 May 2004 17:54:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22073 for ; Wed, 19 May 2004 17:54:22 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQZ15-0007DJ-MK for manet-web-archive@ietf.org; Wed, 19 May 2004 17:54:23 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQZ07-00075F-00 for manet-web-archive@ietf.org; Wed, 19 May 2004 17:53:25 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQYzQ-0006xV-00 for manet-web-archive@ietf.org; Wed, 19 May 2004 17:52:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQYgq-0003Rk-EF; Wed, 19 May 2004 17:33:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQXz9-0000i8-MP for manet@optimus.ietf.org; Wed, 19 May 2004 16:48:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14312 for ; Wed, 19 May 2004 16:48:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQXz6-0003Sr-2o for manet@ietf.org; Wed, 19 May 2004 16:48:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQXy4-0003Ki-00 for manet@ietf.org; Wed, 19 May 2004 16:47:13 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 1BQXxI-00036N-00 for manet@ietf.org; Wed, 19 May 2004 16:46:25 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Wed, 19 May 2004 16:42:53 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Wed, 19 May 2004 16:42:35 -0400 From: "Pete Sholander" To: , Subject: Re: [manet] Draft MANET Problem Statement and Direction Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Thanks Joe! As my last round of comments ... My group has an "optimized flooding" approach to multicast that we've been = field demoing lately. ODMRP seems popular for larger networks with a few = multicast sources. Multicast based on MPR-F approaches that leverage = underlying topology info from a proactive unicast routing protocol also = seem reasonable. So, there are indeed working, multi-OS code-bases that = the WG can draw real-life experience from :) The academic folks can help = us with simulations. etc.=20 So, I humbly suggest that we consider both proactive and reactive = solutions for multicast routing. As you mention, the multicast approach = might leverage technology concepts from the unicast MPRP and MRRP. As in = unicast routing, a proactive approach and a reactive approach should well = cover the application space between large/dense/static networks vs. other = networks where robustness against mobility and RF effects is paramount. Consideration of multicast routing should *not* (IMHO) be allowed to delay = the next versions of the unicast MANET routing standards though. >>> Joe Macker 05/13/04 09:47AM >>> At 01:48 PM 5/12/2004, Pete Sholander wrote: >Joe, > >Looks good!!! =20 > >Q1: Does the WG intend to focus on unicast routing protocols only? Or = are simple multicast protocols in scope? (I would guess unicast only, = since you're aiming at Proposed Standards.) Yes, I believe simple multicast forwarding is in scope. Paragraph 4 could = be seen as a possibility. We have a running prototype similar to MPR-F along these lines.. Common building block needs (e.g., duplicate packet detection) are = certainly different than typical wired approaches and can be engineered. = =20 >Q2: Do you a notional schedule in mind for completing this work? (The = last round of RFCs took a while for various reasons. Hopefully, this = effort can be faster.) Let's get consensus on the problem and the work items first. I certainly think we can speed up the process once we scope in on the = items >--Pete Sholander >Atlanta, GA > >>>> Joe Macker 05/12/04 11:30AM >>> >ALL: > >This discussion is a little overdue but we have run this draft outline = past the Routing ADs and are posting it here for the WG to kick around. = Within the next 2 weeks we would like to have a reasonable WG framework to = proceed with. I don't think there are many surprises here as the WG has = been openly discussing the next steps for awhile. > >--------------------------------------------------------------------------= --------------------------- >DRAFT MANET PROBLEM STATEMENT AND DIRECTION=20 >(REALLY A CHARTER UPDATE) > >The purpose of the MANET working group is to standardize IP routing = protocol functionality suitable for wireless routing application within = both static and dynamic topologies. The fundamental problem issues are = that wireless link interfaces have some unique routing interface characteri= stics and that node topologies within a wireless routing region may = experience increased dynamics, due to motion or other factors. The = continued proliferation of a wide variety of wireless device technologies = and embedded network devices is opening up new wireless networking = challenges. MANET specifications fundamentally provide improved operationa= l IP routing performance for dynamic, wireless routing regions. Approaches= are intended to be relatively lightweight in nature and suitable for = heterogeneous adaptation across multiple hardware and wireless environments= . > >While MANET routing areas may operate in isolation from a larger = connected Internet, a primary focus of the MANET WG is to address use as a = routing technology extension at the edges of an IP infrastructure. The = deployment of hybrid infrastructures (e.g., a mixture of preferred fixed = grid and mobile routers) should also be supported by MANET specifications = and management features. In the past, this WG has focused on exploring a = broad range of MANET problems, performance issues, and related candidate = protocols and has developed several EXPERIMENTAL RFCs with associated = working prototypes along with an INFORMATIONAL RFC (2501) discussing = performance and design considerations. The present protocol frameworks = provide Experimental MANET specifications covering both reactive and = proactive design spaces and many of the concepts have reached a significant= level of engineering maturity. Building off this work, the MANET WG will = now concentrate its scope on developing several Proposed Standard = specification efforts. Two central routing protocol approaches will be = developed. > >- MANET Reactive Routing Protocol (MRRP) >- MANET Proactive Routing Protocol (MPRP) > >For this goal, it is expected that MRRP will become a convergence of = mature reactive design components. Likewise, it is expected that MPRP = would be a convergence of mature proactive design components. At this = point, the WG has rough consensus that a split between proactive and = reactive taxonomies appears sensible from a design complexity and = application space perspective. The WG will begin its work with development = of protocols along these tracks. If the WG sees significant commonality = among the design spaces common building blocks may be developed. The WG = will develop both IPv4 and IPv6 support within these protocols. Routing = security requirements and issues will also be addressed. > >Within the MANET WG, the development of a common ALL_MANET_NODES = forwarding protocol building block for use withing a MANET routing area = has also been identified as a useful work item. The potential for the = "broadcast storm problem" to arise is exacerbated in a MANET wireless = interface scenario, where each node may have a different set of single hop = neighbors. Present MANET routing protocol work has developed a number of = flooding optimizations suitable for MANET environments that can reduce = significantly the number of redundant transmissions when forwarding = packets to ALL_MANET_NODES. A generic MANET flooding building block can = be adapted to a routing protocol instantiation and may also be useful in = designing service discovery and autoconfiguration mechanisms within MANET = areas. The MANET WG will develop a generic flooding building block and = related instantiations that will be useful for the intended wireless = network environments. =20 > >Additional WG items that are to be covered by a small set of INFORMATIONAL= documents and possible PROPOSED STANDARD specifications relate to issues = of address autoconfiguration, MANET gateway discovery and operation, and = network service discovery. The MANET WG will work with other IETF WGs to = determine and support the working of related issues within the appropriate = working groups. > >Some related work the MANET WG will pay particular attention to will be = the OSPF-MANET protocol work within the OSPF WG and the ANS IRTF work that = is addressing research topics related to MANET environments. > > >_______________________________________________ >manet mailing list >manet@ietf.org=20 >https://www1.ietf.org/mailman/listinfo/manet=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 12:05:45 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27824 for ; Thu, 20 May 2004 12:05:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQplF-0001ID-9K for manet-archive@odin.ietf.org; Thu, 20 May 2004 11:47:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KFl9Vo004960 for manet-archive@odin.ietf.org; Thu, 20 May 2004 11:47:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpJc-0007ai-19 for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 11:18:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22769 for ; Thu, 20 May 2004 11:18:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQpJb-0001sn-6U for manet-web-archive@ietf.org; Thu, 20 May 2004 11:18:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQpII-0001Vl-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 11:17:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQpHS-0001Cq-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 11:16:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQp5l-0004EN-Pl; Thu, 20 May 2004 11:04:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQleK-0006Uj-5g for manet@optimus.ietf.org; Thu, 20 May 2004 07:23:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12358 for ; Thu, 20 May 2004 07:23:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQleJ-0007Iv-Jd for manet@ietf.org; Thu, 20 May 2004 07:23:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQldQ-00077V-00 for manet@ietf.org; Thu, 20 May 2004 07:22:49 -0400 Received: from bay14-f3.bay14.hotmail.com ([64.4.49.3] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1BQlcd-0006kN-00 for manet@ietf.org; Thu, 20 May 2004 07:21:59 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 20 May 2004 04:21:27 -0700 Received: from 195.12.26.4 by by14fd.bay14.hotmail.msn.com with HTTP; Thu, 20 May 2004 11:21:27 GMT X-Originating-IP: [195.12.26.4] X-Originating-Email: [jianwu53@hotmail.com] X-Sender: jianwu53@hotmail.com From: "jian wu" To: manet@ietf.org Date: Thu, 20 May 2004 11:21:27 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 May 2004 11:21:27.0639 (UTC) FILETIME=[97B59670:01C43E5C] Subject: [manet] a question in dsdv 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no version=2.60 Dear all I am currently in the process of modifying the routing metrics used in DSDV. Basically I want to use a link quality based metric instead of the hop count. Since I'm a new user of ns-2, I wonder if someone can tell me where to look at (e.g. the class name etc.) in the file dsdv.cc if I want to change the routing metric. Thanks in advance. Jian Wu _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 12:06:14 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27943 for ; Thu, 20 May 2004 12:06:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQplf-0001Rq-HG for manet-archive@odin.ietf.org; Thu, 20 May 2004 11:47:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KFlZOT005561 for manet-archive@odin.ietf.org; Thu, 20 May 2004 11:47:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpOi-0000Wv-2G for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 11:23:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23282 for ; Thu, 20 May 2004 11:23:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQpOh-0003NC-5U for manet-web-archive@ietf.org; Thu, 20 May 2004 11:23:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQpNe-0003EY-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 11:22:47 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQpMe-0002wM-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 11:21:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQp6D-0004PF-RH; Thu, 20 May 2004 11:04:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQmyX-00021f-OO for manet@optimus.ietf.org; Thu, 20 May 2004 08:48:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14819 for ; Thu, 20 May 2004 08:48:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQmyW-0000Ze-DF for manet@ietf.org; Thu, 20 May 2004 08:48:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQmxb-0000NC-00 for manet@ietf.org; Thu, 20 May 2004 08:47:44 -0400 Received: from bay14-f27.bay14.hotmail.com ([64.4.49.27] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1BQmwu-0007nN-00 for manet@ietf.org; Thu, 20 May 2004 08:47:00 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 20 May 2004 05:46:29 -0700 Received: from 210.42.48.12 by by14fd.bay14.hotmail.msn.com with HTTP; Thu, 20 May 2004 12:46:29 GMT X-Originating-IP: [210.42.48.12] X-Originating-Email: [changchun_xu@hotmail.com] X-Sender: changchun_xu@hotmail.com From: "Changchun Xu" To: manet@ietf.org Date: Thu, 20 May 2004 20:46:29 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 May 2004 12:46:29.0735 (UTC) FILETIME=[78CBA770:01C43E68] Subject: [manet] Questions about hidden terminal and hops 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Hi,every one! The questions proposed by me may be quite simple, sorry for I'm a beginner. 1. when we say that node i and j are hidden terminals with each other, does the definition of hidden terminals also be expressed as "node i and j are 2 hops apart with each other"? I think these two expressions are same. 2. The effective wireless communication range is R, the distance between node i and j is 1.8R, but there is no middlenode serves as bridge between them, then we can't say that node i and j are 2 hops apart? _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 12:47:11 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00801 for ; Thu, 20 May 2004 12:47:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQqUS-0000tV-As for manet-archive@odin.ietf.org; Thu, 20 May 2004 12:33:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KGXqIJ003432 for manet-archive@odin.ietf.org; Thu, 20 May 2004 12:33:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQq6H-0000mR-Cb for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 12:08:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28193 for ; Thu, 20 May 2004 12:08:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQq6G-0001du-22 for manet-web-archive@ietf.org; Thu, 20 May 2004 12:08:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQq5J-0001Wh-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 12:07:54 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQq4R-0001Po-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 12:06:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpmF-0001on-4n; Thu, 20 May 2004 11:48:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpId-00076V-9G for manet@optimus.ietf.org; Thu, 20 May 2004 11:17:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22691 for ; Thu, 20 May 2004 11:17:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQpIc-0001Y4-D3 for manet@ietf.org; Thu, 20 May 2004 11:17:34 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQpHe-0001Fb-00 for manet@ietf.org; Thu, 20 May 2004 11:16:35 -0400 Received: from nn4.excitenetwork.com ([207.159.120.58] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BQpEe-0000jO-00 for manet@ietf.org; Thu, 20 May 2004 11:13:28 -0400 Received: by xprdmailfe23.nwk.excite.com (Postfix, from userid 110) id 57C421BCD6; Thu, 20 May 2004 11:12:55 -0400 (EDT) To: manet@ietf.org Received: from [139.55.21.238] by xprdmailfe23.nwk.excite.com via HTTP; Thu, 20 May 2004 11:12:55 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040520151255.57C421BCD6@xprdmailfe23.nwk.excite.com> Date: Thu, 20 May 2004 11:12:55 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] Question about length of IFQ? 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am simulating a 200 nodes Ad Hoc network. In general, how long should the ifqlen be? Thanks. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 12:47:15 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00822 for ; Thu, 20 May 2004 12:47:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQqUV-00015J-MR for manet-archive@odin.ietf.org; Thu, 20 May 2004 12:33:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KGXtLl004165 for manet-archive@odin.ietf.org; Thu, 20 May 2004 12:33:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQq7O-0001BA-EK for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 12:10:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28309 for ; Thu, 20 May 2004 12:09:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQq7N-0001mZ-4M for manet-web-archive@ietf.org; Thu, 20 May 2004 12:10:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQq6S-0001fa-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 12:09:05 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQq5b-0001Z7-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 12:08:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpmI-0001qV-8r; Thu, 20 May 2004 11:48:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQpLC-0007yE-7c for manet@optimus.ietf.org; Thu, 20 May 2004 11:20:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22957 for ; Thu, 20 May 2004 11:20:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQpLA-0002QT-6B for manet@ietf.org; Thu, 20 May 2004 11:20:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQpJu-000275-00 for manet@ietf.org; Thu, 20 May 2004 11:18:55 -0400 Received: from nn4.excitenetwork.com ([207.159.120.58] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BQpIi-0001VM-00 for manet@ietf.org; Thu, 20 May 2004 11:17:40 -0400 Received: by xprdmailfe23.nwk.excite.com (Postfix, from userid 110) id 3F66E1BCE4; Thu, 20 May 2004 11:17:07 -0400 (EDT) To: pedrom@dif.um.es, nileshkb@cse.iitk.ac.in Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk Received: from [139.55.21.238] by xprdmailfe23.nwk.excite.com via HTTP; Thu, 20 May 2004 11:17:06 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, jw2000@excite.com, Mona.Ghassemian@kcl.ac.uk Message-Id: <20040520151707.3F66E1BCE4@xprdmailfe23.nwk.excite.com> Date: Thu, 20 May 2004 11:17:07 -0400 (EDT) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS, HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I think so, too. Jack --- On Mon 05/17, Pedro M. Ruiz < pedrom@dif.um.es > wrote: From: Pedro M. Ruiz [mailto: pedrom@dif.um.es] To: nileshkb@cse.iitk.ac.in Cc: manet@ietf.org, jw2000@excite.com, Mona.Ghassemian@kcl.ac.uk Date: Mon, 17 May 2004 19:40:55 +0200 Subject: Re: [manet] Question about NS2 simulation of Ad Hoc netowrk
AFAIK, God is an object with a perfect knowledge about the topology. It
was used by CMU to assess the performance of ad hoc routing protocols
compared to the optimal routes. I think that if you are not interested
in making the same comparisons, then you can change those files without
the need to update God with those changes.

Regards, Pedro

Nilesh Bansal wrote:

>Interesting question Jack, But i got a doubt in the earlier solution
>itself. If u change the mobility file as u said, or add some fix nodes
>in the tcl file as suggested by mona, then won't it be required to provide
>this (n other coz of this) information to "god"? If yes, then how to do
>it?
>
>Actually the doubt arises bcoz of mysterious working/significance of
>god... Any i/ps why exactly it's needed?
>
>regards,
>--nilesh
>
>------------------------------------------------------------------
>Thanks a lot. That is a good idea. ! I will try it.
>Another question is, if I want to limit the movement of some nodes within
>a small part of the whole simulation region, what should I do? One method
>is to modify the output of setdest. But it is complex.
>Any better approaches?
>
>Jack
>
>
> --- On Thu 05/13, Mona < Mona.Ghassemian@kcl.ac.uk > wrote:
>From: Mona [mailto: Mona.Ghassemian@kcl.ac.uk]
>To: jw2000@excite.com
> Cc: manet@ietf.org
>Date: Thu, 13 May 2004 11:12:21 +0100
>Subject: RE: [manet] Question about NS2 simulation of Ad Hoc netowrk.
>
> Hi
>Jack,
>
>If you want to create a mobility file with some fixed specific nodes, the
>easiest way is to create your mobility file for number of mobile nodes.
>Then set the position of the fix nodes in the tcl file.
>
>For example you want to generate a scenario with 10 mobile nodes and 4
>fixed nodes. Simply create a mobility file for 10 nodes, set you number of
>mobil! e nodes in your tcl file as 14 and define the position of fixed nodes
>in the tcl file.
>
>If you want to change the speed or the destination of an specific mobile
>node, then you need to change parameters of setdest as you have mentioned
>yourself.
>
>Kind Regards,
>Mona
>-----------------------------------------------------------
>Mona Ghassemian, PhD student
>Centre for Telecommunications Research
>King's College London
>Drury Lane, London WC2R 5RL
>T: +44 20 7848 2889
>F: +44 20 7848 2664
>E: Mona.Ghassemian@kcl.ac.uk
>-----------------------------------------------------------
>
>To: manet@ietf.org
>Reply-To: jw2000@excite.com
>From: "Jack Wang"
>Date: Tue, 11 May 2004 12:49:42 -0400 (EDT)
>Subject: [manet] Question about NS2 simulation of Ad Hoc netowrk.
>
>
>Hi all:
>
>For Ad Hoc network simulation in NS2, I can use setdest to genenate a
>mobility pattern.
>After I get the output from setdest, can I modify the output?
>! For example, if want a node to be stationary during the whole simulation,
>I only keep the original coordinates of the node and delete all other
>lines, like:
>$ns_ at 9.000000000000 "$node_(11) setdest 952.680251940036
>841.668771362655 6.978688752644"
>If I want to change the destination and speed of a node, I can also modify
>the lines containing these information, like the above line.
>Am I right? Will it cause any error?
>
>Thanks.
>
>Jack
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>
>
>


_______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 14:21:06 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08868 for ; Thu, 20 May 2004 14:21:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQrzF-0004NB-3D for manet-archive@odin.ietf.org; Thu, 20 May 2004 14:09:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KI9iGa016801 for manet-archive@odin.ietf.org; Thu, 20 May 2004 14:09:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQrpl-0001cr-BP for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 13:59:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07458 for ; Thu, 20 May 2004 13:59:54 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQrpj-0005Dy-34 for manet-web-archive@ietf.org; Thu, 20 May 2004 13:59:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQrou-00058b-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 13:59:04 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQro5-00054S-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 13:58:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQreE-00070b-K0; Thu, 20 May 2004 13:48:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQrRw-0003jy-Oz for manet@optimus.ietf.org; Thu, 20 May 2004 13:35:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05260 for ; Thu, 20 May 2004 13:35:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQrRu-0002Tw-Iz for manet@ietf.org; Thu, 20 May 2004 13:35:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQrPi-00025g-00 for manet@ietf.org; Thu, 20 May 2004 13:33:03 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 1BQrMU-0001bj-00 for manet@ietf.org; Thu, 20 May 2004 13:29:42 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 264AF2010; Thu, 20 May 2004 11:29:41 -0600 (MDT) From: "John Mullen" To: "'Changchun Xu'" , Subject: RE: [manet] Questions about hidden terminal and hops in ad hoc networks. Date: Thu, 20 May 2004 11:29:41 -0600 Message-ID: <001d01c43e90$08793370$67f57b80@IEngr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, The hidden terminal problem can be defined in terms of the receiver. If a node can receive transmissions from two different transmitters that are unaware of each other, you have a hidden terminal problem. There are two classic situations. In the first, there are three nodes, A, B, C, arranged so that links AB and BC are usable, but AC is not. Then, A and C are unaware of each other and could both send packets intended for B, which would cause a data collision. In the second situation, there is some sort of barrier between A and C, such as a building, but both can still reach B. Now, A and C could be closer than 1.8R and still be unaware of each other. Bearing in mind that carrier and hello messages travel further than transmitted packets, the second scenario is actually more common in the field than the first. This also means "hidden terminal" and "two-hop" are not the same. For example, if nodes in the first scenario are 0.7R apart, they are within two hops of each other, but would probably detect each other's presence, hence not be hidden. Generally, Node i and Node j are said to be two hops apart if there is an intermediate node that they can relay through, but direct comm is not possible. In the situation you describe in #2, the two nodes would be disconnected. Hope this helps, John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Changchun Xu Sent: Thursday, May 20, 2004 5:46 AM To: manet@ietf.org Subject: [manet] Questions about hidden terminal and hops in ad hoc networks. Hi,every one! The questions proposed by me may be quite simple, sorry for I'm a beginner. 1. when we say that node i and j are hidden terminals with each other, does the definition of hidden terminals also be expressed as "node i and j are 2 hops apart with each other"? I think these two expressions are same. 2. The effective wireless communication range is R, the distance between node i and j is 1.8R, but there is no middlenode serves as bridge between them, then we can't say that node i and j are 2 hops apart? _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _______________________________________________ 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 exim@www1.ietf.org Thu May 20 18:02:22 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29512 for ; Thu, 20 May 2004 18:02:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvaj-0001tX-QP for manet-archive@odin.ietf.org; Thu, 20 May 2004 18:00:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KM0f3Y007281 for manet-archive@odin.ietf.org; Thu, 20 May 2004 18:00:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvQU-0007Dk-GG for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 17:50:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28575 for ; Thu, 20 May 2004 17:50:02 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvQR-0003Fp-PT for manet-web-archive@ietf.org; Thu, 20 May 2004 17:50:03 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvPO-00037W-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 17:48:58 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQvOO-00032Z-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 17:47:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvBB-000849-L3; Thu, 20 May 2004 17:34:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQuxP-0001dX-IT for manet@optimus.ietf.org; Thu, 20 May 2004 17:20:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25844 for ; Thu, 20 May 2004 17:19:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQuxN-0007lx-8o for manet@ietf.org; Thu, 20 May 2004 17:20:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQuva-0007Vm-00 for manet@ietf.org; Thu, 20 May 2004 17:18:11 -0400 Received: from nn6.excitenetwork.com ([207.159.120.60] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BQutG-00078A-00 for manet@ietf.org; Thu, 20 May 2004 17:15:46 -0400 Received: by xprdmailfe17.nwk.excite.com (Postfix, from userid 110) id 5DCF5B6DE; Thu, 20 May 2004 17:15:11 -0400 (EDT) To: manet@ietf.org Received: from [139.55.21.238] by xprdmailfe17.nwk.excite.com via HTTP; Thu, 20 May 2004 17:15:11 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = cd3de8c6015e38e542eab42318cf4fa3 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040520211511.5DCF5B6DE@xprdmailfe17.nwk.excite.com> Date: Thu, 20 May 2004 17:15:11 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] About cbrgen.tcl 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, I am simulationg Ad Hoc network and using cbrgen.tcl to generate data traffic. If the simulation time is 500 seconds, the data packets will be generated althrough the 500 seconds. Is possible to let cbrgen.tcl generate data packet for the first 200 seconds, then stop generating data packets for 100 seconds, then generate data packet for the rest 200 seconds? Thanks a lot. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu May 20 18:28:00 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02290 for ; Thu, 20 May 2004 18:28:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvxA-0006Tl-7q for manet-archive@odin.ietf.org; Thu, 20 May 2004 18:23:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KMNqKx024896 for manet-archive@odin.ietf.org; Thu, 20 May 2004 18:23:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvl2-0000vP-4K for manet-web-archive@optimus.ietf.org; Thu, 20 May 2004 18:11:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00875 for ; Thu, 20 May 2004 18:11:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvkz-0004sX-EQ for manet-web-archive@ietf.org; Thu, 20 May 2004 18:11:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvjv-0004mt-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 18:10:12 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQvjO-0004ih-00 for manet-web-archive@ietf.org; Thu, 20 May 2004 18:09:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvcz-0004hJ-V2; Thu, 20 May 2004 18:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvax-0002L8-5f for manet@optimus.ietf.org; Thu, 20 May 2004 18:00:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29374 for ; Thu, 20 May 2004 18:00:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvau-00040Y-F0 for manet@ietf.org; Thu, 20 May 2004 18:00:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvZx-0003wf-00 for manet@ietf.org; Thu, 20 May 2004 17:59:54 -0400 Received: from web61106.mail.yahoo.com ([216.155.196.108]) by ietf-mx with smtp (Exim 4.12) id 1BQvZ1-0003qP-00 for manet@ietf.org; Thu, 20 May 2004 17:58:55 -0400 Message-ID: <20040520215826.96822.qmail@web61106.mail.yahoo.com> Received: from [141.156.71.10] by web61106.mail.yahoo.com via HTTP; Thu, 20 May 2004 14:58:26 PDT Date: Thu, 20 May 2004 14:58:26 -0700 (PDT) From: manet user To: manet@ietf.org Cc: olsr@inria.fr MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-56759177-1085090306=:91298" Subject: [manet] Olsr reference papers 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 --0-56759177-1085090306=:91298 Content-Type: text/plain; charset=us-ascii Hi, I have been trying to implement OLSR according to RFC 3626. I am looking for any generally available reference papers that can help towards conformance of OLSR implementation. Any help (suggestions) will be greatly appreciated. With some initial experiments, I have observed that being a proactive protocol, the control overhead in OLSR is lot more than a reactive protocol. The main source of overhead is TC message flooding throughout the network every 5 seconds. In a 50 node network (1000 x 1000 m), 35-38 nodes are chosen as MPR. Each of these nodes generate TC msgs, that are re-broadcasted 35-38 times by every other MPR, leading to aprox. 1200 control packets broadcast. The overhead between OLSR and other reactive protocol becomes comparable with increased number of sources (while making source traffic sporadic than one time start). Controlled flooding through MPR is manily effective in a dense network, but with dense networks, interference kicks in. This causes mesg loss (TC/Hello) and makes route tables unstable. I am not sure, if my observations of this trade-of between controlled flooding & routing table stability and control overhead comparisons are correct. Any comments on these observations will be helpful to understand the correctness of the implementation. Thanks in advance, -MU --------------------------------- Do you Yahoo!? Yahoo! Domains - Claim yours for only $14.70/year --0-56759177-1085090306=:91298 Content-Type: text/html; charset=us-ascii

Hi,
 
I have been trying to implement OLSR according to RFC 3626. I am looking for any generally available reference papers that can help towards conformance of OLSR implementation. Any help (suggestions) will be greatly appreciated.
 
With some initial experiments, I have observed that being a proactive protocol, the control overhead in OLSR is lot more than a reactive protocol. The main source of overhead is TC message flooding throughout the network every 5 seconds. In a 50 node network (1000 x 1000 m), 35-38 nodes are chosen as MPR. Each of these nodes generate TC msgs, that are re-broadcasted 35-38 times by every other MPR, leading to aprox. 1200 control packets broadcast. The overhead between OLSR and other reactive protocol becomes comparable with increased number of sources (while making source traffic sporadic than one time start).
 
Controlled flooding through MPR is manily effective in a dense network, but with dense networks, interference kicks in. This causes mesg loss (TC/Hello) and makes route tables unstable. I am not sure, if my observations of this trade-of between controlled flooding & routing table stability and control overhead comparisons are correct.
 
Any comments on these observations will be helpful to understand the correctness of the implementation.
 
Thanks in advance,
-MU 

Do you Yahoo!?
Yahoo! Domains - Claim yours for only $14.70/year --0-56759177-1085090306=:91298-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 21 09:15:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29713 for ; Fri, 21 May 2004 09:15:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9mA-0002Li-DR for manet-archive@odin.ietf.org; Fri, 21 May 2004 09:09:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LD9Qbl009026 for manet-archive@odin.ietf.org; Fri, 21 May 2004 09:09:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9jY-00019U-30 for manet-web-archive@optimus.ietf.org; Fri, 21 May 2004 09:06:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29182 for ; Fri, 21 May 2004 09:06:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR9jW-0007EU-GW for manet-web-archive@ietf.org; Fri, 21 May 2004 09:06:42 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR9ia-00072i-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 09:05:45 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BR9iC-0006qT-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 09:05:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9QX-00057o-Rz; Fri, 21 May 2004 08:47:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9LK-0002yr-8s for manet@optimus.ietf.org; Fri, 21 May 2004 08:41:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27532 for ; Fri, 21 May 2004 08:41:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR9LI-0001pc-P9 for manet@ietf.org; Fri, 21 May 2004 08:41:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR9KT-0001dd-00 for manet@ietf.org; Fri, 21 May 2004 08:40:50 -0400 Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net) by ietf-mx with smtp (Exim 4.12) id 1BR9Ji-0001Ok-00 for manet@ietf.org; Fri, 21 May 2004 08:40:02 -0400 Received: (qmail 10244 invoked by uid 65534); 21 May 2004 12:39:30 -0000 Received: from unknown (EHLO NicoLaptop) (192.166.62.145) by mail.gmx.net (mp015) with SMTP; 21 May 2004 14:39:30 +0200 X-Authenticated: #15262315 From: "Nico Bayer" To: "IETF-MANET" Date: Fri, 21 May 2004 14:41:56 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E6_01C43F41.C3DBC2C0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Thread-Index: AcQ/MQAF7HCKFHH9RhaNXr3AMW4R1A== Message-Id: Subject: [manet] AODV6 and sidelocal multicast address 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_FONTCOLOR_UNKNOWN, HTML_MESSAGE,MISSING_OUTLOOK_NAME autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_00E6_01C43F41.C3DBC2C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello list, is it possible for AODV6 to do a route discovery for a sidelocal multicast address? For example can AODV6 search for all DHCPv6 servers that use the sidelocal multicast address FF05::1:3? I think it is possible. The only difference to a route discovery for a normal address is that the searching node will receive multiple answers if multiple servers are present. I hope someone can help me with this. Regards, Nico ----- Nico Bayer ------=_NextPart_000_00E6_01C43F41.C3DBC2C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello list,

 

is it possible for AODV6 to do a route discovery = for a sidelocal multicast address? For example can AODV6 = search for all DHCPv6 servers that use the sidelocal multicast address FF05::1:3?

I think it is = possible. The only difference to a route discovery for a normal address is that the = searching node will receive multiple answers if multiple servers are = present.

I hope someone can = help me with this.

 

Regards, = Nico

 

 = ;

 = ;

-----

Nico = Bayer

 

 

------=_NextPart_000_00E6_01C43F41.C3DBC2C0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 21 09:58:56 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01900 for ; Fri, 21 May 2004 09:58:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAFK-0001lm-Pp for manet-archive@odin.ietf.org; Fri, 21 May 2004 09:39:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LDdY4a006800 for manet-archive@odin.ietf.org; Fri, 21 May 2004 09:39:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAEU-0001Qd-40 for manet-web-archive@optimus.ietf.org; Fri, 21 May 2004 09:38:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00889 for ; Fri, 21 May 2004 09:38:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAES-0005uY-7P for manet-web-archive@ietf.org; Fri, 21 May 2004 09:38:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRADX-0005gm-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 09:37:44 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRACe-0005Ts-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 09:36:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRA57-00070h-TA; Fri, 21 May 2004 09:29:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9v1-0004vh-3Z for manet@optimus.ietf.org; Fri, 21 May 2004 09:18:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29994 for ; Fri, 21 May 2004 09:18:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR9uz-0001uH-Cm for manet@ietf.org; Fri, 21 May 2004 09:18:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR9u6-0001hs-00 for manet@ietf.org; Fri, 21 May 2004 09:17:39 -0400 Received: from royk.itea.ntnu.no ([129.241.190.230]) by ietf-mx with esmtp (Exim 4.12) id 1BR9tG-0001V1-00 for manet@ietf.org; Fri, 21 May 2004 09:16:46 -0400 Received: from localhost (localhost [127.0.0.1]) by royk.itea.ntnu.no (Postfix) with ESMTP id 84BD767CE3 for ; Fri, 21 May 2004 15:16:44 +0200 (CEST) Received: from minihenrix (dhcp208-231.ed.ntnu.no [129.241.208.231]) by royk.itea.ntnu.no (Postfix) with ESMTP id 350E867D9D for ; Fri, 21 May 2004 15:16:44 +0200 (CEST) From: =?iso-8859-1?Q?Audun_S=F8berg_Henriksen?= To: "Manet" Date: Fri, 21 May 2004 15:16:40 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C43F46.9E4DB590" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcQ+qBIs2sufiZrYRIi95jcUzdx82QAjaveA Message-Id: <20040521131644.350E867D9D@royk.itea.ntnu.no> X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Subject: [manet] Replication protocol for disaster area 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_70_80,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C43F46.9E4DB590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone! I=92m writing a master thesis about the use of ad-hoc routing protocols = on PDA=92s/laptops used by ancillary workers in disaster areas. The network = has to manage private messages, group messages, and broadcast messages that should be replicated and stored on all devices. New nodes connecting to = the network should receive all messages sent since the network was = established. The database only need insert operations, because delete and modify are = not allowed (everything should be logged). =20 Does anyone know if there has been any research around this kind of = ad-hoc network? And what do you think would be the most suitable ad-hoc protocol for = this scenario? =20 =20 Yours Audun S=F8berg Henriksen Institute of Telematics Norwegian University of Science and Technology (NTNU) ------=_NextPart_000_0006_01C43F46.9E4DB590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi = everyone!

I’m writing a = master thesis about the use of ad-hoc routing protocols on PDA’s/laptops = used by ancillary workers in disaster areas. The network has to manage private = messages, group messages, and broadcast messages that should be replicated and = stored on all devices. New nodes connecting to the network should receive all = messages sent since the network was established. The database only need insert operations, because delete and modify are not allowed (everything should = be logged).

 

Does anyone know if = there has been any research around this kind of ad-hoc = network?

And what do you think = would be the most suitable ad-hoc protocol for this = scenario?

 

 

Yours=

Audun S=F8berg = Henriksen

Institute of Telematics

Norwegian University of Science and Technology (NTNU)

------=_NextPart_000_0006_01C43F46.9E4DB590-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 21 10:35:08 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05520 for ; Fri, 21 May 2004 10:35:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAur-0008HA-Di for manet-archive@odin.ietf.org; Fri, 21 May 2004 10:22:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LEMTE2031714 for manet-archive@odin.ietf.org; Fri, 21 May 2004 10:22:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAmS-0004ZU-2o for manet-web-archive@optimus.ietf.org; Fri, 21 May 2004 10:13:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03075 for ; Fri, 21 May 2004 10:13:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAmO-0005cg-UV for manet-web-archive@ietf.org; Fri, 21 May 2004 10:13:45 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRAlT-0005Oh-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 10:12:47 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRAka-0005Bs-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 10:11:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAZO-0006CE-ET; Fri, 21 May 2004 10:00:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAOA-0003Az-50 for manet@optimus.ietf.org; Fri, 21 May 2004 09:48:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01383 for ; Fri, 21 May 2004 09:48:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAO8-0000DS-6t for manet@ietf.org; Fri, 21 May 2004 09:48:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRANG-00000c-00 for manet@ietf.org; Fri, 21 May 2004 09:47:46 -0400 Received: from promet2.deis.unibo.it ([137.204.59.2]) by ietf-mx with esmtp (Exim 4.12) id 1BRAMS-0007cY-00 for manet@ietf.org; Fri, 21 May 2004 09:46:56 -0400 Received: from manson.deis.unibo.it ([137.204.45.201]) by promet2.deis.unibo.it (8.12.2-20030924/8.12.2) with ESMTP id i4LDknLH015890; Fri, 21 May 2004 15:46:49 +0200 (MEST) Message-Id: <5.2.0.9.0.20040521153517.0307c6c0@mail.deis.unibo.it> X-Sender: p30820@mail.deis.unibo.it X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 21 May 2004 15:46:48 +0200 To: manet@ietf.org From: Dario Bottazzi Subject: Re: [manet] Replication protocol for disaster area In-Reply-To: <20040521131644.350E867D9D@royk.itea.ntnu.no> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_21669734==.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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_FONTCOLOR_GREEN, HTML_MESSAGE autolearn=no version=2.60 --=====================_21669734==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi Audun, we are working in this scenario. recently we have published the paper Context-Aware Group Communication in Mobile Ad-Hoc Networks http://springerlink.metapress.com/app/home/contribution.asp?wasp=n2v6e33098cqrp4e721h&referrer=parent&backto=issue,4,26;journal,87,1568;linkingpublicationresults,1:105633,1 AGAPE: a location-aware group membership middleware for pervasive computing environments (this is tailored to cell-based environemts) zeus.elet.polimi.it/is-manet/Documenti/pap-deis-18.pdf for any problem (and to have further references) feel free to contact me best regards dario bottazzi --=====================_21669734==.ALT Content-Type: text/html; charset="us-ascii" Hi Audun,
   we are working in this scenario.

recently we have published the paper Context-Aware Group Communication in Mobile Ad-Hoc Networks
http://springerlink.metapress.com/app/home/contribution.asp?wasp=n2v6e33098cqrp4e721h&referrer=parent&backto=issue,4,26;journal,87,1568;linkingpublicationresults,1:105633,1

AGAPE: a location-aware group membership middleware for pervasive computing environments (this is tailored to cell-based environemts)
zeus.elet.polimi.it/is-manet/Documenti/pap-deis-18.pdf

for any problem (and to have further references) feel free to contact me
best regards
    dario bottazzi --=====================_21669734==.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 21 10:43:18 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06232 for ; Fri, 21 May 2004 10:43:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRB3I-0003UB-0d for manet-archive@odin.ietf.org; Fri, 21 May 2004 10:31:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LEVBiI013391 for manet-archive@odin.ietf.org; Fri, 21 May 2004 10:31:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAt9-0007W7-U5 for manet-web-archive@optimus.ietf.org; Fri, 21 May 2004 10:20:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03690 for ; Fri, 21 May 2004 10:20:40 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAt7-0007Bj-Ms for manet-web-archive@ietf.org; Fri, 21 May 2004 10:20:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRAsJ-0006yS-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 10:19:52 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRArc-0006lM-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 10:19:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAc3-0008S5-TQ; Fri, 21 May 2004 10:03:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAXl-0005e8-Du for manet@optimus.ietf.org; Fri, 21 May 2004 09:58:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01884 for ; Fri, 21 May 2004 09:58:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAXj-0002Nj-B3 for manet@ietf.org; Fri, 21 May 2004 09:58:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRAWp-0002BB-00 for manet@ietf.org; Fri, 21 May 2004 09:57:40 -0400 Received: from bells.cs.ucl.ac.uk ([128.16.5.31]) by ietf-mx with smtp (Exim 4.12) id 1BRAW5-0001yO-00 for manet@ietf.org; Fri, 21 May 2004 09:56:54 -0400 Received: from cellini.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Fri, 21 May 2004 14:56:35 +0100 From: Adam Greenhalgh To: manet@ietf.org Content-Type: text/plain Message-Id: <1085147777.23040.25.camel@cellini.cs.ucl.ac.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 21 May 2004 14:56:17 +0100 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] What is the current GPSR status in simulators ? 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I'm interested in comparing GPSR with a routing protocol we are developing. I've contacted Brad Karp and the latest version of GPSR he knows about for ns is in ns-2.1b8, does any one know of a later implementation ? Specifically I'm interested in implementations for recent versions of ns (2.26 + ) or opnet. Thanks in advance Adam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri May 21 17:22:26 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04862 for ; Fri, 21 May 2004 17:22:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRHKn-0003MT-B8 for manet-archive@odin.ietf.org; Fri, 21 May 2004 17:13:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LLDfHb012917 for manet-archive@odin.ietf.org; Fri, 21 May 2004 17:13:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRHB9-0000Tq-FI for manet-web-archive@optimus.ietf.org; Fri, 21 May 2004 17:03:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03227 for ; Fri, 21 May 2004 17:03:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRHB6-0004Fz-UJ for manet-web-archive@ietf.org; Fri, 21 May 2004 17:03:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRHA8-00047Q-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 17:02:41 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRH9B-0003yT-00 for manet-web-archive@ietf.org; Fri, 21 May 2004 17:01:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRGww-0002Ht-S4; Fri, 21 May 2004 16:49:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRGcJ-0000dO-71 for manet@optimus.ietf.org; Fri, 21 May 2004 16:27:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28590 for ; Fri, 21 May 2004 16:27:40 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRGcH-0005q2-BD for manet@ietf.org; Fri, 21 May 2004 16:27:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRGbG-0005ei-00 for manet@ietf.org; Fri, 21 May 2004 16:26:39 -0400 Received: from mailscan.satnet.net ([200.63.212.11] helo=avirus.satnet.net) by ietf-mx with esmtp (Exim 4.12) id 1BRGaG-0005LZ-00 for manet@ietf.org; Fri, 21 May 2004 16:25:36 -0400 Received: from uio.satnet.net (internal.satnet.net [10.102.101.21]) Received: from [200.63.218.206] (helo=OPERADOR5) by uio.satnet.net with smtp (Exim 3.36 #1) id 1BRGiU-0006kL-00 for manet@ietf.org; Fri, 21 May 2004 15:34:06 -0500 Message-ID: <002401c43f71$ab7da8d0$6a0a0a0a@OPERADOR5> From: =?iso-8859-1?Q?Carlos_Arturo_Fern=E1ndez?= To: Date: Fri, 21 May 2004 15:24:46 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C43F47.C0002780" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-SatNet-MessageScanner-Information: Please contact the ISP for more information X-SatNet-MessageScanner: Found to be clean X-MailScanner-From: cfernand@uio.satnet.net Subject: [manet] help 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_50_60,HTML_MESSAGE autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C43F47.C0002780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I need some help about how give QoS on manets Any suggestion or reference I will really appreciated Thanks ------=_NextPart_000_001C_01C43F47.C0002780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I need some help about how give QoS on=20 manets
 
Any suggestion or reference I will = really=20 appreciated
 
Thanks
------=_NextPart_000_001C_01C43F47.C0002780-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 22 00:23:35 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25628 for ; Sat, 22 May 2004 00:23:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNyK-0002l2-T9 for manet-archive@odin.ietf.org; Sat, 22 May 2004 00:18:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M4IuhA010450 for manet-archive@odin.ietf.org; Sat, 22 May 2004 00:18:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNsx-0001Pr-2r for manet-web-archive@optimus.ietf.org; Sat, 22 May 2004 00:13:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25081 for ; Sat, 22 May 2004 00:13:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRNst-0001J8-8L for manet-web-archive@ietf.org; Sat, 22 May 2004 00:13:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRNqy-00016F-00 for manet-web-archive@ietf.org; Sat, 22 May 2004 00:11:21 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRNq6-0000zI-00 for manet-web-archive@ietf.org; Sat, 22 May 2004 00:10:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNfE-000749-5F; Fri, 21 May 2004 23:59:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNVK-00059S-9T for manet@optimus.ietf.org; Fri, 21 May 2004 23:48:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24123 for ; Fri, 21 May 2004 23:48:54 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRNVH-0006IK-Dt for manet@ietf.org; Fri, 21 May 2004 23:48:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRNUM-00068o-00 for manet@ietf.org; Fri, 21 May 2004 23:47:59 -0400 Received: from smtp-send.myrealbox.com ([192.108.102.143]) by ietf-mx with esmtp (Exim 4.12) id 1BRNTM-00060b-00 for manet@ietf.org; Fri, 21 May 2004 23:46:56 -0400 Received: from nppham [203.219.237.10] by myrealbox.com with NetMail ModWeb Module; Sat, 22 May 2004 13:16:56 +0930 Subject: Re: [manet] help Reply-To: nppham@ieee.org From: "Peter Pham" To: cfernand@uio.satnet.net CC: manet@ietf.org Date: Sat, 22 May 2004 13:16:56 +0930 X-Mailer: NetMail ModWeb Module X-Sender: nppham MIME-Version: 1.0 Message-ID: <1085197616.5330c85cnppham@myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi For starting, you should look at INSIGNIA. Cheers Peter -----Original Message----- From: Carlos Arturo Fern=C3=A1ndez To: Date: Fri, 21 May 2004 15:24:46 -0500 Subject: [manet] help I need some help about how give QoS on manets Any suggestion or reference I will really appreciated Thanks Peter Phuc Pham _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat May 22 02:12:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12908 for ; Sat, 22 May 2004 02:12:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRPia-00082U-7g for manet-archive@odin.ietf.org; Sat, 22 May 2004 02:10:48 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M6AmZm030903 for manet-archive@odin.ietf.org; Sat, 22 May 2004 02:10:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRPcE-00061U-DV for manet-web-archive@optimus.ietf.org; Sat, 22 May 2004 02:04:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04726 for ; Sat, 22 May 2004 02:04:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRPcA-00000o-JC for manet-web-archive@ietf.org; Sat, 22 May 2004 02:04:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRPb8-0007eq-00 for manet-web-archive@ietf.org; Sat, 22 May 2004 02:03:07 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRPaK-0007WW-00 for manet-web-archive@ietf.org; Sat, 22 May 2004 02:02:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRPSU-00049z-5v; Sat, 22 May 2004 01:54:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRPMe-0002xu-33 for manet@optimus.ietf.org; Sat, 22 May 2004 01:48:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29908 for ; Sat, 22 May 2004 01:48:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRPMa-0005mP-U2 for manet@ietf.org; Sat, 22 May 2004 01:48:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRPLj-0005dP-00 for manet@ietf.org; Sat, 22 May 2004 01:47:11 -0400 Received: from smtp1.utdallas.edu ([129.110.10.12]) by ietf-mx with esmtp (Exim 4.12) id 1BRPKt-0005KH-00 for manet@ietf.org; Sat, 22 May 2004 01:46:19 -0400 Received: from babbage.utdallas.edu (babbage.utdallas.edu [129.110.49.22]) by smtp1.utdallas.edu (Postfix) with ESMTP id 49CE5388DD6 for ; Sat, 22 May 2004 00:45:45 -0500 (CDT) Received: by babbage.utdallas.edu (Postfix, from userid 22135) id 1DE0227F4; Sat, 22 May 2004 00:45:45 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by babbage.utdallas.edu (Postfix) with ESMTP id 115D627F3 for ; Sat, 22 May 2004 00:45:45 -0500 (CDT) Date: Sat, 22 May 2004 00:45:45 -0500 (CDT) From: Jorge Cobb To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] CFP QShine '04: Deadline one week away 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 (* Our apologies if you receive multiple copies of this message *) CALL FOR PAPERS QShine 2004 - First International Conference on Quality of Service in Heterogeneous Wired/Wireless Networks October 18-20, 2004, Dallas, TX, USA http://www.qshine.org/ Scope: ------------------------------- Recent technological developments in broadband high-speed networks, peer-to-peer networks, wireless and mobile networks, and grid computing have led to newer challenging problems, such as providing QoS support to the emerging high-speed Internet and multimedia applications across both wired and wireless networks. This conference will focus on all aspects of QoS support for heterogeneous wired and wireless networks. Papers addressing cross-layer design on QoS support for both wired and wireless networks are strongly encouraged. It will serve as a forum for researchers from both academia and industry for presenting recent research results in QoS issues for both wired and wireless networks. The conference features prominent invited speakers as well as papers by top researchers in the field. The scope of the conference includes, but is not limited to: - QoS in wireless local area networks - QoS in sensor networks and wireless ad-hoc networks - QoS support and mobility management in wireless Internet - QoS in wireless and mobile multimedia - QoS provisioning in mobile IP and IPv6 - Scheduling policies for wireless networks - QoS in current and emerging cellular and satellite networks - Differentiated service in wireless multimedia networks - QoS in broadband high-speed networks - QoS in optical networks - QoS support for Internet applications - QoS across heterogeneous link technologies - Middleware support for QoS provision - Policy-based QoS differentiation - Interactive broadband television, gaming, and video distribution - Variable and adaptive QoS - QoS modeling and measurement - QoS routing, resource management, and admission control - QoS pricing and billing - QoS architectures, protocols, and systems - QoS in web systems and storage systems - QoS specification, metrics, and analysis - QoS in peer-to-peer networks, grid and application-layer overlay networks - Security aspects of QoS systems Accepted papers will be published in the conference proceedings. Papers of particular merit will be proposed for publication in ACM / Kluwer Wireless Networks (WINET). Submission Guidelines: ------------------------------- Papers should not exceed 20 pages, must be unpublished and must not be submitted for publication elsewhere. All submissions should be sent electronically in Postscript or Adobe PDF format. Electronic submission instructions will be available at http://www.qshine.org/. Important Dates: -------------------------------- Submission Deadline: May 28, 2004 Notification of Acceptance: July 26, 2004 Camera-ready Manuscripts Due: August 20, 2004 Conference Dates: October 18-20, 2004 Organizing Committee --------------------------------- General Chair: Azzedine Boukerche, University of Ottawa, Canada, Vice Chair: Michael Fang, University of Florida Technical Program Co-Chairs Jorge Cobb, University of Texas at Dallas Shigang Chen, University of Florida Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas Publicity Co-Chairs: Mirela Sechi M. Annoni Notare, Barddal University, Brazil Thomas Hou, Virginia Tech Local Chair & Finance Chair: Hua Zhu, University of Texas at Dallas ========================== Jorge A. Cobb Department of Computer Science (MS EC-31) The University of Texas at Dallas PO Box 830688 Richardson, TX 75083-0688 cobb@utdallas.edu phone 972 883 2479 fax 972 883 2349 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet