From manet-bounces@ietf.org Fri Oct 1 02:44:51 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27854 for ; Fri, 1 Oct 2004 02:44:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDHIL-00078G-Tg for manet-web-archive@ietf.org; Fri, 01 Oct 2004 02:53:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDGr6-0001QR-Ih; Fri, 01 Oct 2004 02:25:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDGgX-0005BW-4P for manet@megatron.ietf.org; Fri, 01 Oct 2004 02:14:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21900 for ; Fri, 1 Oct 2004 02:14:26 -0400 (EDT) Received: from [203.199.93.15] (helo=WS0005.indiatimes.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDGot-0006ez-8W for manet@ietf.org; Fri, 01 Oct 2004 02:23:09 -0400 Received: from 192.168.57.15 (IDENT:demail@[192.168.57.66]) by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id LAA25632 for ; Fri, 1 Oct 2004 11:47:41 +0530 From: "venkata_meghasyam" Message-Id: <200410010617.LAA25632@WS0005.indiatimes.com> To: Date: Fri, 01 Oct 2004 11:40:49 +0530 X-URL: http://indiatimes.com MIME-Version: 1.0 X-Spam-Score: 3.1 (+++) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Subject: [manet] Request For Thesis Help!!!!!!!!!.................. X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: venkata_meghasyam List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2064181202==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.6 (++) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a --===============2064181202== Content-Type: multipart/alternative; boundary="=_MAILER_ATTACH_BOUNDARY1_20041015114049846930886" --=_MAILER_ATTACH_BOUNDARY1_20041015114049846930886 Content-Type: text/plain; charset=us-ascii repected sir, This time i have come with new idea. i would like to propose an autoconfiguration protocol with the following idea An autoconfiguration protocol with hybrid approach , 1. initially ,every node randomly chooses an address . 2. now ,it starts the process of weak DAD (with some modifacations). 3. here, the set of allocated addresses will be registered in a distributed fashion.i.e. may be in common way or disjoint way. 4. additionally ,consider the issues of security,connection to internet etc. So, the proposed idea is different from the existing ideas. additionally ,it outperforms PACCMAN ,because this is independent of routing alogorithm. This is a better idea because there is even no optimal(best in all means) routing algorithm for MANET. So plz , make this idea clear so that it will be easy to carry out my thesis work . waiting for a quick reply thakning u sir Y.V.MEGHASYAM M.TECH(SOFTWARE) MNNIT,ALLAHABAD, INDIA. Indiatimes Email now powered by APIC Advantage. Help! HelpClick on the image to chat with me --=_MAILER_ATTACH_BOUNDARY1_20041015114049846930886 Content-Type: text/html; charset=us-ascii repected sir, This time i have come with new idea. i would like to propose an autoconfiguration protocol with the following idea An autoconfiguration protocol with hybrid approach , 1. initially ,every node randomly chooses an address . 2. now ,it starts the process of weak DAD (with some modifacations). 3. here, the set of allocated addresses will be registered in a distributed fashion.i.e. may be in common way or disjoint way. 4. additionally ,consider the issues of security,connection to internet etc. So, the proposed idea is different from the existing ideas. additionally ,it outperforms PACCMAN ,because this is independent of routing alogorithm. This is a better idea because there is even no optimal(best in all means) routing algorithm for MANET. So plz , make this idea clear so that it will be easy to carry out my thesis work . waiting for a quick reply thakning u sir Y.V.MEGHASYAM M.TECH(SOFTWARE) MNNIT,ALLAHABAD, INDIA.
Indiatimes Email now powered by APIC Advantage. Help!
Click on the image to chat with me
--=_MAILER_ATTACH_BOUNDARY1_20041015114049846930886-- --===============2064181202== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2064181202==-- From manet-bounces@ietf.org Fri Oct 1 03:43:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02512 for ; Fri, 1 Oct 2004 03:43:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDID7-0008Vg-Vi for manet-web-archive@ietf.org; Fri, 01 Oct 2004 03:52:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDHsa-0002ys-P9; Fri, 01 Oct 2004 03:31:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDHil-0000bj-6X for manet@megatron.ietf.org; Fri, 01 Oct 2004 03:20:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01152 for ; Fri, 1 Oct 2004 03:20:49 -0400 (EDT) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDHqU-0007xm-2d for manet@ietf.org; Fri, 01 Oct 2004 03:28:51 -0400 Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 41563896001A390D for manet@ietf.org; Fri, 1 Oct 2004 09:20:08 +0200 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Fri, 01 Oct 2004 09:18:42 +0200 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 415BC88D0000A04E for manet@ietf.org; Fri, 1 Oct 2004 09:18:42 +0200 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Fri, 01 Oct 2004 09:18:42 +0200 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 4152F54B000352B3 for manet@ietf.org; Fri, 1 Oct 2004 09:17:43 +0200 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Fri, 01 Oct 2004 09:17:43 +0200 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Fri, 1 Oct 2004 09:18:41 +0200 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E99A@khephren.clb.tcfr.thales> To: vramana@cs.iitm.ernet.in Subject: RE: [manet] TCP for MANETs Date: Fri, 1 Oct 2004 09:18:48 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.4 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Hi, You can read "A Comparison of TCP Performance aver Three Routing Protocols for Mobile Ad Hoc Networks", from Thomas D. Dyer Rajendra V. Boppana. In this document a heuristique is used on the TCP sender to avoid doubling more than once the TCP RTO when route is considered broken. Raphael -----Message d'origine----- De : B. Venkata Ramana [mailto:vramana@cs.iitm.ernet.in] Envoye : vendredi 1 octobre 2004 05:37 A : manet@ietf.org Objet : [manet] TCP for MANETs hi all Are there any proposals on TCP for ad hoc networks that do NOT require (obtain) any explicit feedback from the network. I had come across to see such proposals some time back. But i am unable to trace them back now. can you please give me some info on this. regards ramana, HPCN Lab, Dept. of CSE IIT-Madras India _______________________________________________ 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 mailman-bounces@ietf.org Fri Oct 1 07:04:51 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17798 for ; Fri, 1 Oct 2004 07:04:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDLM1-0004Rq-Dz for manet-web-archive@ietf.org; Fri, 01 Oct 2004 07:13:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDJna-0006xY-Hj for manet-web-archive@ietf.org; Fri, 01 Oct 2004 05:33:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: manet-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Oct 2004 05:14:30 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for manet-web-archive@ietf.org: List Password // URL ---- -------- manet@ietf.org pKoU https://www1.ietf.org/mailman/options/manet/manet-web-archive%40ietf.org From manet-bounces@ietf.org Fri Oct 1 15:05:42 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07512 for ; Fri, 1 Oct 2004 15:05:42 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDSrQ-00087o-IO for manet-web-archive@ietf.org; Fri, 01 Oct 2004 15:14:33 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDSMw-0000VV-V9; Fri, 01 Oct 2004 14:43:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDS4F-0005zQ-Dn for manet@megatron.ietf.org; Fri, 01 Oct 2004 14:23:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04127 for ; Fri, 1 Oct 2004 14:23:40 -0400 (EDT) Received: from web61103.mail.yahoo.com ([216.155.196.105]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDSCZ-0006dV-Gz for manet@ietf.org; Fri, 01 Oct 2004 14:32:31 -0400 Message-ID: <20041001182240.53227.qmail@web61103.mail.yahoo.com> Received: from [66.208.44.5] by web61103.mail.yahoo.com via HTTP; Fri, 01 Oct 2004 11:22:40 PDT Date: Fri, 1 Oct 2004 11:22:40 -0700 (PDT) From: manet user To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Subject: [manet] RERRs in AODV X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2069928334==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe --===============2069928334== Content-Type: multipart/alternative; boundary="0-1488349173-1096654960=:50818" --0-1488349173-1096654960=:50818 Content-Type: text/plain; charset=us-ascii Hi, According to RFC 3561 Section 6.11, it says that A node initiates processing for a RERR message in three situations: (i) if it detects a link break for the next hop of an active route in its routing table while transmitting data (and route repair, if attempted, was unsuccessful), or (ii) if it gets a data packet destined to a node for which it does not have an active route and is not repairing (if using local repair), or My question is, when does the case (i) happen apart from route repair failure, if AODV imeplementation uses hello messages rather than lower layer feedback for link maintenance? Also, if a neighbor loss is detected by ALLOWED_HELLO_LOSS, RFC says this will not trigger a RERR message due to empty precursor list. But do we still increase the destination sequence number after expiring the route? If yes, then we'll not be able to add the same neighbor if we happen to receive Hello message right after the loss. Any comments will be helpful. Thanks in advance, -MU --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. --0-1488349173-1096654960=:50818 Content-Type: text/html; charset=us-ascii
Hi,
 
According to RFC 3561 Section 6.11, it says that
 
A node initiates processing for a RERR message in three situations:

   (i)       if it detects a link break for the next hop of an active
             route in its routing table while transmitting data (and
             route repair, if attempted, was unsuccessful), or

   (ii)      if it gets a data packet destined to a node for which it
             does not have an active route and is not repairing (if
             using local repair), or
My question is, when does the case (i) happen apart from route repair failure, if AODV imeplementation uses hello messages rather than lower layer feedback for link maintenance?
 
Also, if a neighbor loss is detected by ALLOWED_HELLO_LOSS, RFC says this will not trigger a RERR message due to empty precursor list. But do we still increase the destination sequence number after expiring the route? If yes, then we'll not be able to add the same neighbor if we happen to receive Hello message right after the loss.
 
Any comments will be helpful. Thanks in advance,
-MU

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses. --0-1488349173-1096654960=:50818-- --===============2069928334== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2069928334==-- From manet-bounces@ietf.org Fri Oct 1 21:45:06 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16545 for ; Fri, 1 Oct 2004 21:45:05 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDZ60-0003U8-Un for manet-web-archive@ietf.org; Fri, 01 Oct 2004 21:54:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDYgk-0003G0-9l; Fri, 01 Oct 2004 21:27:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDUTP-00010i-84 for manet@megatron.ietf.org; Fri, 01 Oct 2004 16:57:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17418 for ; Fri, 1 Oct 2004 16:57:48 -0400 (EDT) Received: from vitalstatistix.cs.uoregon.edu ([128.223.4.19] helo=cs.uoregon.edu ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDUbu-0007KP-R5 for manet@ietf.org; Fri, 01 Oct 2004 17:06:39 -0400 Received: from ix.cs.uoregon.edu (manoj@ix [128.223.4.21]) by cs.uoregon.edu (8.13.1/8.13.1) with ESMTP id i91Kvbhv008076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Oct 2004 13:57:38 -0700 (PDT) Date: Fri, 1 Oct 2004 13:57:37 -0700 (PDT) From: Manoj K Pandey To: "B. Venkata Ramana" Subject: Re: [manet] TCP for MANETs 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, clamav-milter version 0.70j X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 hi Ramana, There is a paper, which focuses on identifying congestion based losses from "random" wireless losses. Here is the reference: @inproceedings{tcp-adhoc-door, author = "Feng Wang and Yongguang Zhang", title = "Improving TCP Performance over Mobile Ad-Hoc Networks with Out-of-Order Detection and Response", booktitle = "Mobihoc", year = "2002"} There is some work done in the area of differentiating congestion losses from wireless losses in TCP for an infrastructured wireless network [wired + base station] (but this is not ad hoc network). You can find comparision of some of these in this: @misc{tcp-wireless-differentiating-losses-comparison, author = "S. Cen and P. Cosman and G. Voelker", title = "End-to-end differentiation of congestion and wireless Losses", text = "S. Cen,P. Cosman, G.M. Voelker,End-to-end differentiation of congestion and wireless Losses, Proceedings of ACM Mul year = "2002", url = "citeseer.ist.psu.edu/cen02endtoend.html" } thnx, Manoj On Fri, 1 Oct 2004, B. Venkata Ramana wrote: > > hi all > > Are there any proposals on TCP for ad hoc networks that do NOT require > (obtain) any explicit feedback from the network. I had come across to see > such proposals some time back. But i am unable to trace them back now. can > you please give me some info on this. > > regards > ramana, > HPCN Lab, > Dept. of CSE > IIT-Madras > India > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 00:34:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02374 for ; Mon, 4 Oct 2004 00:34:14 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEKhD-00071a-Dd for manet-web-archive@ietf.org; Mon, 04 Oct 2004 00:43:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEKN5-0004K0-VV; Mon, 04 Oct 2004 00:22:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEKBe-00030Y-Ct for manet@megatron.ietf.org; Mon, 04 Oct 2004 00:10:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24619 for ; Mon, 4 Oct 2004 00:10:54 -0400 (EDT) Received: from bay16-f14.bay16.hotmail.com ([65.54.186.64] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CE5DZ-0007DT-FF for manet@ietf.org; Sun, 03 Oct 2004 08:11:58 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 3 Oct 2004 05:02:00 -0700 Received: from 218.76.63.35 by by16fd.bay16.hotmail.msn.com with HTTP; Sun, 03 Oct 2004 12:01:33 GMT X-Originating-IP: [218.76.63.35] X-Originating-Email: [zongmng@hotmail.com] X-Sender: zongmng@hotmail.com From: "Zong Ming" To: manet@ietf.org Date: Sun, 03 Oct 2004 20:01:33 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 03 Oct 2004 12:02:00.0771 (UTC) FILETIME=[CA261130:01C4A940] X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA24619 Subject: [manet] a bandwidth problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: quoted-printable Hello all, This is a mathmatics problem. In ad hoc network,n nodes are arbitrarily located in a disk of unit=20 area in the plane.Each transmission's range is the same.Each node has an=20 arbitraily chosen destination to which it wished to send traffic at an=20 given rate.We suppose all packages are successfully sended and=20 received.what is the relation between a node's distance to the center and= =20 its throughput?Is there any formula describing this relationship? Thanks in advance Zong _________________________________________________________________ =CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF= =B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 00:35:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14269 for ; Sun, 3 Oct 2004 23:43:29 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEJu5-0001vj-Cf for manet-web-archive@ietf.org; Sun, 03 Oct 2004 23:52:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEJj6-0004T5-UU; Sun, 03 Oct 2004 23:41:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEJht-0003wH-S8 for manet@megatron.ietf.org; Sun, 03 Oct 2004 23:40:13 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11317 for ; Sun, 3 Oct 2004 23:40:10 -0400 (EDT) From: skurkows@mines.edu Received: from data.mines.edu ([138.67.4.74]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEJje-0000ZL-EP for manet@ietf.org; Sun, 03 Oct 2004 23:42:02 -0400 Received: from data.Mines.EDU (localhost.localdomain [127.0.0.1]) by data.Mines.EDU (8.12.8/8.12.8) with ESMTP id i943WAfs021534 for ; Sun, 3 Oct 2004 21:32:10 -0600 Received: (from apache@localhost) by data.Mines.EDU (8.12.8/8.12.8/Submit) id i943WAuE021532 for manet@ietf.org; Sun, 3 Oct 2004 21:32:10 -0600 X-Authentication-Warning: data.Mines.EDU: apache set sender to skurkows@mines.edu using -f Received: from AC932546.ipt.aol.com (AC932546.ipt.aol.com [172.147.37.70]) by webmail.mines.edu (IMP) with HTTP for ; Sun, 3 Oct 2004 21:32:10 -0600 Message-ID: <1096860730.4160c43aa5213@webmail.mines.edu> Date: Sun, 3 Oct 2004 21:32:10 -0600 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 172.147.37.70 X-Spam-Score: 0.5 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 8bit Subject: [manet] Preliminary agenda now available for the NSF NOSS Informational Meeting X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 8bit ******** Apologies if you have received multiple copies. ******** The call for NSF NOSS proposals should be available soon, with an expected January due date. We invite you to participate in a NOSS Informational Meeting to learn about the NOSS focus area's direction and the open research challenges that exist in this focus area. (All presentations are by leading experts.) Attendees of the Informational Meeting will also have the chance to interact with recent NOSS awardees both formally and socially. Preliminary agenda: http://toilers.mines.edu/NOSS/Infoagenda.html Date and time: Begins: Monday, October 18th, 2:30pm Ends: Tuesday, October 19th, 3:15pm Location: On the campus of the Colorado School of Mines in Golden, CO Registration: The early registration fee is $50. Contact us: noss@mines.edu Visit http://toilers.mines.edu/NOSS for more information, including details on registration, lodging, and agendas. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 06:41:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21751 for ; Mon, 4 Oct 2004 06:41:47 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQQy-0008QH-PG for manet-web-archive@ietf.org; Mon, 04 Oct 2004 06:51:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQDQ-0005cP-3P; Mon, 04 Oct 2004 06:37:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQ7R-0004Cz-MW for manet@megatron.ietf.org; Mon, 04 Oct 2004 06:31:01 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20816 for ; Mon, 4 Oct 2004 06:30:58 -0400 (EDT) Received: from bay19-f24.bay19.hotmail.com ([64.4.53.74] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQGI-0006es-IH for manet@ietf.org; Mon, 04 Oct 2004 06:40:23 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 4 Oct 2004 03:27:12 -0700 Received: from 62.8.24.95 by by19fd.bay19.hotmail.msn.com with HTTP; Mon, 04 Oct 2004 10:26:59 GMT X-Originating-IP: [62.8.24.95] X-Originating-Email: [yann_eads@hotmail.com] X-Sender: yann_eads@hotmail.com From: "Yann -EADS-" To: manet@ietf.org Date: Mon, 04 Oct 2004 12:26:59 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 04 Oct 2004 10:27:12.0980 (UTC) FILETIME=[B65FC940:01C4A9FC] X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [manet] Hop count in OLSR X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Hello, I wonder if the 'hop count' field of the message header is used and for what purpose. I can't see in the RFC where this field is used. For me, knowing that D is advertised by C, which is advertised by B, which is a neighbor is sufficient for A to deduce that D is 3 hops away. A ------ B ------ C ------ D Am I wrong ? _________________________________________________________________ MSN Messenger http://g.msn.fr/FR1001/866 : dialoguez en direct et gratuitement avec vos amis ! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 07:27:22 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25224 for ; Mon, 4 Oct 2004 07:27:22 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CER93-0007Y4-C7 for manet-web-archive@ietf.org; Mon, 04 Oct 2004 07:36:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQwr-0004XW-08; Mon, 04 Oct 2004 07:24:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQoK-0003Tr-H7 for manet@megatron.ietf.org; Mon, 04 Oct 2004 07:15:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24382 for ; Mon, 4 Oct 2004 07:15:17 -0400 (EDT) Received: from space1.inet.it ([213.92.5.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQxG-0004vF-Ou for manet@ietf.org; Mon, 04 Oct 2004 07:24:43 -0400 Received: from wifi027.smaw.unive.it [::ffff:157.138.142.27] by space1.inet.it via I-SMTP-5.1.15-51B id ::ffff:157.138.142.27+ARMaYUqQl3; Mon, 04 Oct 2004 13:14:49 +0200 From: Andrea Passarella To: vramana@cs.iitm.ernet.in Subject: RE: [manet] TCP for MANETs Date: Mon, 4 Oct 2004 13:09:49 +0200 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200410041309.49260.a.passarella@iet.unipi.it> X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: a.passarella@iet.unipi.it List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 7bit Hi, you can take a look at "G. Anastasi and A. Passarella, Towards a Novel Transport Protocol for Ad hoc Networks, Proceedings of the Eighth International Conference on Personal Wireless Communications (PWC 2003) - LNCS Series, Venice (I), September 23-25, 2003." (if you wish, you can download it from my home, the address is in the signature). Our protocol benefits from explicit feedbacks from the network, but is designed to work also when such support is very very limited (we just assume some routing-layer feedback that is quite common). Hope this may help, Andrea -- Andrea Passarella ======================================= Ph.D. Student Pervasive Computing & Networking Lab. (PerLab) University of Pisa Dept. of Information Engineering Via Diotisalvi, 2 56122 Pisa, Italy ======================================= voice: +39 050 2217 554 fax: +39 050 2217 600 web: http://www.ing.unipi.it/~o783499/research/index.html email: a.passarella@iet.unipi.it ======================================= _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 08:51:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01568 for ; Mon, 4 Oct 2004 08:51:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CESSy-0002aI-4d for manet-web-archive@ietf.org; Mon, 04 Oct 2004 09:01:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CESHj-00035H-AP; Mon, 04 Oct 2004 08:49:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CESHA-00030W-A4 for manet@megatron.ietf.org; Mon, 04 Oct 2004 08:49:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01328 for ; Mon, 4 Oct 2004 08:49:10 -0400 (EDT) Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CESQF-0001yd-FC for manet@ietf.org; Mon, 04 Oct 2004 08:58:35 -0400 Received: from 7C-517.bbn.com (ramblo.bbn.com [128.33.0.51]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id i94Cmbjf003196; Mon, 4 Oct 2004 08:48:37 -0400 (EDT) Message-Id: <6.1.2.0.2.20041004084916.059488d0@127.0.0.1> X-Sender: celliott@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 04 Oct 2004 08:51:09 -0400 To: "Zong Ming" , manet@ietf.org From: Chip Elliott Subject: Re: [manet] a bandwidth problem In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: quoted-printable Check out the following paper for an excellent treatment of this general area: A. Agarwal, P. R. Kumar, "Capacity Bounds for Ad hoc and Hybrid Wireless=20 Networks," ACM SIGCOMM Computer Communication Review, v. 34, no. 3, July 2004. Chip Elliott BBN Technologies At 08:01 AM 10/3/2004, Zong Ming wrote: >Hello all, > This is a mathmatics problem. > In ad hoc network,n nodes are arbitrarily located in a disk of unit=20 > area in the plane.Each transmission's range is the same.Each node has an= =20 > arbitraily chosen destination to which it wished to send traffic at an=20 > given rate.We suppose all packages are successfully sended and=20 > received.what is the relation between a node's distance to the center and= =20 > its throughput?Is there any formula describing this relationship? > Thanks in advance > Zong > >_________________________________________________________________ >=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF= =B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 11:11:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12705 for ; Mon, 4 Oct 2004 11:11:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEUdy-0000hx-8e for manet-web-archive@ietf.org; Mon, 04 Oct 2004 11:20:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEUNa-0007sC-9m; Mon, 04 Oct 2004 11:03:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEUND-0007ig-CI for manet@megatron.ietf.org; Mon, 04 Oct 2004 11:03:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12137 for ; Mon, 4 Oct 2004 11:03:32 -0400 (EDT) Received: from web15802.mail.cnb.yahoo.com ([202.165.102.82]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEUWI-0007cH-4q for manet@ietf.org; Mon, 04 Oct 2004 11:12:59 -0400 Message-ID: <20041004150259.66632.qmail@web15802.mail.cnb.yahoo.com> Received: from [218.76.18.53] by web15802.mail.cnb.yahoo.com via HTTP; Mon, 04 Oct 2004 23:02:59 CST Date: Mon, 4 Oct 2004 23:02:59 +0800 (CST) From: Yuan-long Jiang To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA12137 Subject: [manet] Help: Codes for NRL's Sensor Network Extension X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: quoted-printable Sir: Anyone has the code for NRL's Sensor Network Extension to ns-2? I am doing some comparison works on some routing algorithms, Now I'm in great need for the source code of NRLSensorSim. The authors provide their homepage and download links as the following: http://nrlsensorsim.pf.itd.nrl.navy.mil/=20 But I can't download it. Anyone can Email it directly to me? Your help is greatly appreciated! Louis jiangyuanlong@yahoo.com _________________________________________________________ Do You Yahoo!? 150=CD=F2=C7=FAMP3=B7=E8=BF=F1=CB=D1=A3=AC=B4=F8=C4=FA=B4=B3=C8=EB=D2=F4=C0= =D6=B5=EE=CC=C3 http://music.yisou.com/ =C3=C0=C5=AE=C3=F7=D0=C7=D3=A6=D3=D0=BE=A1=D3=D0=A3=AC=CB=D1=B1=E9=C3=C0=CD= =BC=A1=A2=D1=DE=CD=BC=BA=CD=BF=E1=CD=BC http://image.yisou.com 1G=BE=CD=CA=C71000=D5=D7=A3=AC=D1=C5=BB=A2=B5=E7=D3=CA=D7=D4=D6=FA=C0=A9=C8= =DD=A3=A1 http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mai= l_1g/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 11:29:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14342 for ; Mon, 4 Oct 2004 11:29:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEUvq-0001bx-CB for manet-web-archive@ietf.org; Mon, 04 Oct 2004 11:39:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEUhE-0003X4-W5; Mon, 04 Oct 2004 11:24:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEUct-0003Li-5M for manet@megatron.ietf.org; Mon, 04 Oct 2004 11:19:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13857 for ; Mon, 4 Oct 2004 11:19:44 -0400 (EDT) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEUlz-00016s-6P for manet@ietf.org; Mon, 04 Oct 2004 11:29:11 -0400 Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 415F73150006E512 for manet@ietf.org; Mon, 4 Oct 2004 17:19:47 +0200 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Mon, 04 Oct 2004 17:18:19 +0200 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 415BC88D00023C68 for manet@ietf.org; Mon, 4 Oct 2004 17:18:19 +0200 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Mon, 04 Oct 2004 17:18:18 +0200 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 4152F54B00048B67 for manet@ietf.org; Mon, 4 Oct 2004 17:17:20 +0200 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Mon, 04 Oct 2004 17:17:20 +0200 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Mon, 4 Oct 2004 17:18:18 +0200 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E9A9@khephren.clb.tcfr.thales> To: manet@ietf.org Date: Mon, 4 Oct 2004 17:18:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.4 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable Subject: [manet] AODV : receiving and forwarding route replies X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable Hi all, As it is described in RFC 3561, AODV incorrectly handles RREP = forwarding when route reply by intermediate nodes is not activated. Let's consider the following network : S1 --- S2 --- S3 --- S4 First, S2 establishes a route to S4. Then S1 wants to do the same thing. If intermediate node reply is not activated, the route research reaches S4, that sends a RREP back to S1. Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if = a forward route (to the destination) has been updated (or created). As = this is not the case here, the RREP is not forwarded and the route to S4 is = never established on S1. Any comment ? Rapha=EBl _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 12:27:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20539 for ; Mon, 4 Oct 2004 12:27:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEVp6-00010w-0l for manet-web-archive@ietf.org; Mon, 04 Oct 2004 12:36:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEVVT-0003GN-AK; Mon, 04 Oct 2004 12:16:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEVNm-00010s-7x for manet@megatron.ietf.org; Mon, 04 Oct 2004 12:08:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16610 for ; Mon, 4 Oct 2004 12:08:11 -0400 (EDT) Received: from bay19-f18.bay19.hotmail.com ([64.4.53.68] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEVWs-000679-53 for manet@ietf.org; Mon, 04 Oct 2004 12:17:39 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 4 Oct 2004 09:02:08 -0700 Received: from 62.8.24.95 by by19fd.bay19.hotmail.msn.com with HTTP; Mon, 04 Oct 2004 16:01:55 GMT X-Originating-IP: [62.8.24.95] X-Originating-Email: [yann_eads@hotmail.com] X-Sender: yann_eads@hotmail.com From: "Yann -EADS-" To: manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Mon, 04 Oct 2004 18:01:55 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 04 Oct 2004 16:02:09.0202 (UTC) FILETIME=[80A7E920:01C4AA2B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA16610 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable Hello, I guess that the forward route is actually updated upon receiving the RRE= P.=20 In my mind, the sequence number received by S2 is greater than the one wh= ich=20 created its route to S4. And if this route is updated, it fowards the RRE= P=20 to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP forwarding >when route reply by intermediate nodes is not activated. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if = a >forward route (to the destination) has been updated (or created). As thi= s=20 >is >not the case here, the RREP is not forwarded and the route to S4 is neve= r >established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage !=20 http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 13:24:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25432 for ; Mon, 4 Oct 2004 13:24:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEWie-0003XZ-Kn for manet-web-archive@ietf.org; Mon, 04 Oct 2004 13:33:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEWOA-0003uH-MO; Mon, 04 Oct 2004 13:12:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEWHl-0002jq-OC for manet@megatron.ietf.org; Mon, 04 Oct 2004 13:06:05 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23472 for ; Mon, 4 Oct 2004 13:06:01 -0400 (EDT) Received: from 209-254-158-42.ip.mcleodusa.net ([209.254.158.42] helo=che.ojctech.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEWQs-000805-Cc for manet@ietf.org; Mon, 04 Oct 2004 13:15:30 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id i94H5UKb009922 for ; Mon, 4 Oct 2004 12:05:30 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id i94H5TwB009917 for manet@ietf.org; Mon, 4 Oct 2004 12:05:29 -0500 Date: Mon, 4 Oct 2004 12:05:29 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] Hop count in OLSR Message-ID: <20041004170529.GC654@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 On Mon, Oct 04, 2004 at 12:26:59PM +0200, Yann -EADS- wrote: > Hello, > > I wonder if the 'hop count' field of the message header is used and for > what purpose. I can't see in the RFC where this field is used. A router may use both 'hop count' and 'hop limit' fields to detect and discard packets that have been flooded too far or for too long. The reason is redundancy: even if routers stop decreasing the 'hop limit' field, or stop discarding packets with hop-limit <= 0, because of a software defect, they may still increase the 'hop count', check it against a maximum allowed value, and discard packets that exceed the maximum. In this way, the network is still protected against flood-packet "storms" in spite of a single router defect. Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 4 18:16:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03552 for ; Mon, 4 Oct 2004 18:16:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEbHY-0004Bk-SZ for manet-web-archive@ietf.org; Mon, 04 Oct 2004 18:26:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEat1-0005OR-84; Mon, 04 Oct 2004 18:00:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEasO-0004qs-IX for manet@megatron.ietf.org; Mon, 04 Oct 2004 18:00:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01539 for ; Mon, 4 Oct 2004 18:00:09 -0400 (EDT) Received: from auds951.usa.alcatel.com ([143.209.238.80]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEb1Y-0000ud-KU for manet@ietf.org; Mon, 04 Oct 2004 18:09:41 -0400 Received: from alcatel.com (localhost [127.0.0.1]) by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i94Lxe2Q004140 for ; Mon, 4 Oct 2004 16:59:40 -0500 (CDT) Message-ID: <4161C7CC.4E2F2074@alcatel.com> Date: Mon, 04 Oct 2004 16:59:40 -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@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 Content-Transfer-Encoding: 7bit Subject: [manet] BroadNets 2004: Early Registration extended to Oct. 10, 2004 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Content-Transfer-Encoding: 7bit (Apologies if you are receiving this message more than once) ----------------------------------------------------------------------- CALL FOR PARTICIPATION BroadNets 2004 First International Conference on Broadband Networking Technically Co-Sponsored by IEEE Communications Society In-Cooperation with ACM SIGMOBILE Co-sponsored by: CreateNet, Inc. ICST National Science Foundation (Student Travel Awards) Philips, Inc. (Bronze Level Sponsor; Student Best Paper Awards) Hilton San Jose and Towers San Jose, California, USA October 25 - 29, 2004 http://www.broadnets.org Early Registration Deadline: Oct. 10, 2004 Discounted Hotel Reservation Deadline: Oct. 4, 2004 ----------------------------------------------------------------------- BroadNets 2004 is a new conference focusing on broadband networking and covers the entire gamut of next generation networks with ultra-high bandwidth available all the way from access networks (xDSL, Cable, EPON, Broadband Wireless, multi-Gigabit uplinks), to regional and metropolitan networks to wide-area core networks. Keynote speakers include: * Vinton Cerf, Senior Vice President of Technology Strategy for MCI * Dr. Lawrence G. Roberts, CEO of Anagran and Founder and Vice Chairman of Caspian Networks The conference will consist of two symposia, panels, six tutorials and seven workshops: * Broadband Optical Symposium includes 32 papers covering topics such as optical burst and packet switching, IP over optical networks, survivability, routing and wavelength assignment, traffic and wavelength grooming, switching and routing, and optical network design and resource allocation. * Broadband Wireless Symposium includes 38 papers covering topics such as 802.11 networks, UWB and 802.15 based networks, performance analysis, wireless multimedia, resource management, multimedia transport, contention and media access, routing in ad hoc networks, and sensor networks. * TUTORIALS (on Oct 25 and Oct 29): - Broadband Metro and Access Networks (Full-day), Dr. Raj Jain - Optical Mesh Survivability (Half-day), Dr. Suresh Subramaniam and Dr. Srinivasan Ramasubramanian - Advancements in Metro Optical Network Architecture and Technologies (Half-day) Dr. Loukas Paraschis - Wireless Broadband: Services, Networks, and Management (Full-day), Dr. Mani Subramanian - Multimedia Transmission over Spectrum Agile Radio Wireless Networks (Half-day) Dr. Mihaela van der Schaar - A Practical Perspective on the Role of Optical Layer Protection (Half-day) Dr. Ori Gerstel WORKSHOPS co-located with BroadNets 2004: - Broadband Wireless Multimedia (BroadWim) - Broadband Advanced Sensor Networks (BaseNets) - Broadband Wireless Services and Applications (BroadWise) - Networks for Grid Applications (GridNets) - Optical Burst Switching (OBS) - Provisioning and Transport for Hybrid Networks (PathNets) - Traffic Grooming Workshops will be held on Monday, October 25 and Friday, October 29. For the advance program of BroadNets 2004, as well as registration and travel information, please visit: http://www.broadnets.org. CONFERENCE ORGANIZING COMMITTEE ------------------------------- BroadNets Conference General Chair: Dr. Raj Jain, Nayna Networks/Ohio State University, raj@nayna.com _________________________________ Broadband Optical Networking Symposium Co-Chairs: Dr. Ori Gerstel, Cisco Systems, ogerstel@cisco.com Dr. Jason Jue, University of Texas at Dallas, jjue@utdallas.edu Technical Program Co-Chairs: Dr. Galen Sasaki, University of Hawaii, sasaki@spectra.eng.hawaii.edu Dr. Suresh Subramaniam, George Washington University, suresh@gwu.edu __________________________________ Broadband Wireless Networking Symposium Chair: Dr. Zhensheng Zhang, San Diego Research Center, zzhang@ieee.org Technical Program Co-Chairs: Dr. Parameswaran Ramanathan, University of Wisconsin-Madison, parmesh@ece.wisc.edu Dr. Thomas Hou, Virginia Tech, thou@vt.edu _____________________________ Panels Co-Chairs: Dr. Byrav Ramamurthy, University of Nebraska - Lincoln, byrav@cse.unl.edu Dr. Loukas Paraschis, Cisco Systems, loukas@cisco.com Dr. Mohammed Atiquzzaman, University of Oklahoma, atiq@ou.edu Tutorials Co-Chairs: Dr. Hakki Candan Cankaya, Alcatel USA, hakki.cankaya@alcatel.com Dr. Surendar Chandra, Univ of Notre Dame, surendar@cse.nd.edu Workshops Chair: Dr. Nasir Ghani, Tennessee Tech University, nghani@ieee.org Dr. Rajeev Shorey, National University of Singapore and IBM Research India, rajeev@comp.nus.edu.sg Exhibits and Sponsorships Chairs: Dr. Samrat Ganguly, NEC Labs, samrat@nec-labs.com Dr. Javier Aracil, Universidad Publica de Navarra, Spain, javier.aracil@unavarra.es Publicity Co-Chairs: Dr. Tim Ozugur, Alcatel USA, tim.ozugur@alcatel.com Dr. Gaoxi Xiao, Nanyang Technological Univ. Singapore, egxxiao@ntu.edu.sg Dr. Marcos Rogerio Salvador, CPqD Telecom & IT Solutions, marcosrs@cpqd.com.br Local Arrangements Chair: Dr. Subhankar Dhar, San Jose State University, dhar_s@cob.sjsu.edu Sukesh Pai, Microsoft Corp. sukeshp@microsoft.com Steering Committee Co-Chairs: Dr. Imrich Chlamtac, UT Dallas, chlamtac@utdallas.edu Dr. Krishna Sivalingam, University of Maryland, Baltimore County, krishna@umbc.edu -------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 01:23:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03924 for ; Tue, 5 Oct 2004 01:23:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEhwY-00021n-LJ for manet-web-archive@ietf.org; Tue, 05 Oct 2004 01:33:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEhkw-0000Mi-1r; Tue, 05 Oct 2004 01:20:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEhkU-0000Ew-R6 for manet@megatron.ietf.org; Tue, 05 Oct 2004 01:20:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03760 for ; Tue, 5 Oct 2004 01:20:29 -0400 (EDT) Received: from [202.41.85.90] (helo=universe.uohyd.ernet.in) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEhtS-0001UI-55 for manet@ietf.org; Tue, 05 Oct 2004 01:30:02 -0400 Received: from ailab.uohyd.ernet.in (ailab.uohyd.ernet.in [202.41.85.117]) by universe.uohyd.ernet.in (8.9.0/8.9.0) with ESMTP id KAA26325 for ; Tue, 5 Oct 2004 10:47:47 -0500 (GMT) Received: from ailab.uohyd.ernet.in (ailab [127.0.0.1]) by ailab.uohyd.ernet.in (8.12.8/8.12.8) with ESMTP id i955Kgtm013472 for ; Tue, 5 Oct 2004 10:50:42 +0530 Received: (from apache@localhost) by ailab.uohyd.ernet.in (8.12.8/8.12.8/Submit) id i955KeMC013469; Tue, 5 Oct 2004 10:20:40 +0500 X-Authentication-Warning: ailab.uohyd.ernet.in: apache set sender to shahriar@ailab.uohyd.ernet.in using -f Received: from 202.141.142.23 (proxying for 172.16.17.69) (SquirrelMail authenticated user shahriar) by 202.41.85.117 with HTTP; Tue, 5 Oct 2004 10:20:40 +0500 (MVT) Message-ID: <60842.202.141.142.23.1096953640.squirrel@202.41.85.117> Date: Tue, 5 Oct 2004 10:20:40 +0500 (MVT) From: "Shahriar Shamil Uulu" To: X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.10) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 8bit Subject: [manet] Needed secure routing and transmission source codes X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shahriar@ailab.uohyd.ernet.in List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 8bit How i can get any, secure routing and secure transmission protocols source codes implemented on ns-2. Any help will be apperciated _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 01:52:37 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05937 for ; Tue, 5 Oct 2004 01:52:37 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEiOp-0007LN-49 for manet-web-archive@ietf.org; Tue, 05 Oct 2004 02:02:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEiD2-0004EQ-Sv; Tue, 05 Oct 2004 01:50:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEi9V-0003hW-HP for manet@megatron.ietf.org; Tue, 05 Oct 2004 01:46:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05558 for ; Tue, 5 Oct 2004 01:46:20 -0400 (EDT) Received: from mx2sophos.cqu.edu.au ([138.77.5.126]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEiIj-0006G9-Al for manet@ietf.org; Tue, 05 Oct 2004 01:55:54 -0400 Received: from neutron.staff.ad.cqu.edu.au ([138.77.34.42] helo=ROKEMAIL.staff.ad.cqu.edu.au) by mx2sophos.cqu.edu.au with esmtp (Exim 4.22) id 1CEi9R-0004AT-0G for manet@ietf.org; Tue, 05 Oct 2004 15:46:17 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 5 Oct 2004 15:46:12 +1000 Message-ID: Thread-Topic: MATLAB code for IEEE 802.11 PCF & HCF to share? Thread-Index: AcSqm9g0gA2o6p2NR8elCMSiIoSrUgAAj80A From: "Amoakoh Gyasi-Agyei" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: quoted-printable Subject: [manet] MATLAB code for IEEE 802.11 PCF & HCF to share? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable Dear all; My apologies for using this list, but didn't know the best place to ask than here. Does anybody have to share MATLAB codes simulating the IEEE 802.11/e PCF and/or HCCA schemes? That would be appreciative. Any piece of info (e.g. reference to someone's work, www) relating to this will be of help. Thanks, Amoakoh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 02:32:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23152 for ; Tue, 5 Oct 2004 02:32:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEj14-0005xP-JW for manet-web-archive@ietf.org; Tue, 05 Oct 2004 02:41:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEimL-00019b-PG; Tue, 05 Oct 2004 02:26:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEij0-00082Y-Q7 for manet@megatron.ietf.org; Tue, 05 Oct 2004 02:23:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22392 for ; Tue, 5 Oct 2004 02:23:01 -0400 (EDT) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEisC-000490-6A for manet@ietf.org; Tue, 05 Oct 2004 02:32:35 -0400 Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 415F73150009A58D for manet@ietf.org; Tue, 5 Oct 2004 08:23:01 +0200 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Tue, 05 Oct 2004 08:21:32 +0200 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 415BC88D0002783A for manet@ietf.org; Tue, 5 Oct 2004 08:21:32 +0200 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Tue, 05 Oct 2004 08:21:31 +0200 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 4152F54B0004B824 for manet@ietf.org; Tue, 5 Oct 2004 08:20:34 +0200 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Tue, 05 Oct 2004 08:20:33 +0200 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Tue, 5 Oct 2004 08:21:30 +0200 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E9AA@khephren.clb.tcfr.thales> To: yann_eads@hotmail.com, manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Tue, 5 Oct 2004 08:21:33 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.4 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Content-Transfer-Encoding: quoted-printable Hi, The destination sequence number of station D is only updated when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the = D is broken increments the destination sequence number of D. Later, this = node sends AODV messages with updated sequence number for destination D. In the example below, the sequence number of S4 is never updated. It is = the reason why S3 never propagates the RREP message corresponding to the = RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I = would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the = RREP.=20 In my mind, the sequence number received by S2 is greater than the one = which created its route to S4. And if this route is updated, it fowards the = RREP=20 to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP = forwarding >when route reply by intermediate nodes is not activated. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not >activated, the route research reaches S4, that sends a RREP back to = S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only = if a >forward route (to the destination) has been updated (or created). As = this=20 >is >not the case here, the RREP is not forwarded and the route to S4 is = never >established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage !=20 http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 12:36:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12516 for ; Tue, 5 Oct 2004 12:36:07 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEsRg-0004qp-Lc for manet-web-archive@ietf.org; Tue, 05 Oct 2004 12:45:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEsBO-0002Q1-BA; Tue, 05 Oct 2004 12:28:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEs6u-0001LB-8G for manet@megatron.ietf.org; Tue, 05 Oct 2004 12:24:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11589 for ; Tue, 5 Oct 2004 12:24:17 -0400 (EDT) Received: from dcs-server2.cs.uiuc.edu ([128.174.252.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEsGB-0003O5-1e for manet@ietf.org; Tue, 05 Oct 2004 12:33:58 -0400 Received: from brooklyn (brooklyn.cs.uiuc.edu [128.174.244.80]) (authenticated bits=0) by dcs-server2.cs.uiuc.edu (8.12.10/8.12.10) with ESMTP id i95GO9UY026446 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 5 Oct 2004 11:24:11 -0500 (CDT) Message-Id: <200410051624.i95GO9UY026446@dcs-server2.cs.uiuc.edu> From: "Robin Kravets" To: Date: Tue, 5 Oct 2004 11:26:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcSq+AYVmP3Pj4AuS5mmNmSb3PRuNg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 93e7fb8fef2e780414389440f367c879 Content-Transfer-Encoding: quoted-printable Subject: [manet] ACM MobiHoc 2005 - Call For Papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Content-Transfer-Encoding: quoted-printable We apologize in advance if you receive multiple copies of this CFP. ---------------------------------------------------------------------- Call for Papers MobiHoc 2005=20 6th ACM International Symposium on=20 Mobile Ad Hoc Networking and Computing=20 May 25-28, 2005, Urbana-Champaign, Illinois, USA=20 http://www.sigmobile.org/mobihoc/2005/=20 Sponsored by ACM SIGMOBILE=20 IMPORTANT DATES: Paper Registration Deadline: =20 December 13, 2004 (5PM US EST)=20 =20 Paper Submission Deadline: December 20, 2004 (5PM US EST) =20 Notification of Acceptance: March 27, 2005 =20 Camera-Ready Version Due: April 10, 2005 ACM MobiHoc is the premier international meeting dedicated to addressing challenges emerging from wireless ad hoc networking and computing. Due = to the growing interest in the field this year's symposium will have an expanded format that will include a highly selective, dual-track = technical program for the first time, as well as hands-on research demonstrations, keynote, panel, and tutorials. We invite paper, poster, and demonstration submissions on mobile ad hoc networks, wireless sensor networks, and ad hoc computing systems, with = the focus being on issues at and above the MAC layer. Areas of interest = include, but are not limited to: * Applications, operating system, and middleware support=20 * Analysis and design of transport, network, and MAC protocols=20 * Energy-efficient algorithms =20 * Location discovery and management techniques=20 * Network scaling and limits=20 * Measurements and practical experience from experimental systems and=20 testbeds=20 * Cross layer design=20 * Network resilience, fault-tolerance, and reliability=20 * Security and defense issues=20 * In-network processing, aggregation and data dissemination=20 * Distributed actuation, control, and coordination * Modeling, performance evaluation, and QoS issues=20 =20 PAPERS: Papers must report new results substantiated by experimentation, = simulation, or analysis. All submissions will be handled electronically and must be = in PDF format. Papers must not exceed 12 pages (US letter size, 8.5 =F011 = inches) including text, figures and references. The font size must be at least = 10 points. Accepted papers will be published in the symposium proceedings. = All submitted papers are judged based on their quality through double -blind reviewing, where the identities of the authors are withheld from the reviewers. Authors' names must not appear in the paper or in the PDF = file. Submitted papers must not be currently under review for any other publication. Instructions on paper submission and formatting are = available on the symposium webpage. Please direct any questions about the paper submission process to the Program Co-Chairs Andrew T. Campbell , and Roger Wattenhofer . POSTERS: Posters presenting early work and preliminary results are solicited. The poster session will provide an excellent opportunity for initial = feedback on early research results. Poster descriptions, of no more than 3 pages, = using font size 10 on 8.5x11in size paper, should be submitted to the Poster Co-Chairs Songwu Lu and Saswati Sarkar before April 1, 2005. Please include the words "Poster Abstract:" to precede the title on the cover page. A selected = subset of poster abstracts will be published in ACM Mobile Computing and Communications Review.=20 DEMOS: Technical demonstration of experimental ad hoc networking and computing systems are solicited. One-page demo descriptions, including a list of = any required supporting equipment, should be sent to the Demo Chair Scott = R. Graham before March 1, 2005. TUTORIALS: Proposals for tutorials are solicited. Evaluation of proposals will be = based on the expertise and experience of the instructors, and on the relevance = of the subject matter. Potential instructors are requested to submit a = tutorial proposal of at most 5 pages, including a biographical sketch, to the Tutorial Co-Chairs Bhaskar Krishnamachari and Richard = J. La before Jan. 15, 2005. PANELS: Panels are solicited that examine innovative, controversial, or = otherwise provocative issues of interest. Panel proposals should not exceed 2 = pages, including biographical sketches of the panelists. Potential panel = organizers should contact the General Chair P. R. Kumar before December 15, 2004. General Chair P. R. Kumar Univ. of Illinois, Urbana-Champaign prkumar@uiuc.edu Program Co-Chairs Andrew T. Campbell Columbia University campbell@comet.columbia.edu Roger Wattenhofer ETH Zurich wattenhofer@tik.ee.ethz.ch For more information contact the General Chair or consult the symposium webpage _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 13:55:16 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20185 for ; Tue, 5 Oct 2004 13:55:16 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEtgG-0000ld-2h for manet-web-archive@ietf.org; Tue, 05 Oct 2004 14:04:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtQv-0007os-Sc; Tue, 05 Oct 2004 13:49:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtPP-0007WC-Ry for manet@megatron.ietf.org; Tue, 05 Oct 2004 13:47:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19660 for ; Tue, 5 Oct 2004 13:47:30 -0400 (EDT) Received: from vitalstatistix.cs.uoregon.edu ([128.223.4.19] helo=cs.uoregon.edu ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEtYj-0007r9-7c for manet@ietf.org; Tue, 05 Oct 2004 13:57:10 -0400 Received: from ix.cs.uoregon.edu (manoj@ix [128.223.4.21]) by cs.uoregon.edu (8.13.1/8.13.1) with ESMTP id i95HlSM7010491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Oct 2004 10:47:28 -0700 (PDT) Date: Tue, 5 Oct 2004 10:47:28 -0700 (PDT) From: Manoj K Pandey To: redouane Subject: Re: [manet] DSR packet salvaging In-Reply-To: <20040930135201.37983.qmail@web53701.mail.yahoo.com> Message-ID: References: <20040930135201.37983.qmail@web53701.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: QUOTED-PRINTABLE hi Redouane, It is a known problem. At high mobility, routes get stale very soon. DSR keeps using them (and also circulating them in the network) in order to salvage packets. I would suggest reading: author=3D"Gavin Holland and Nitin H. Vaidya", title=3D"Analysis of {TCP} Performance Over Mobile Ad Hoc Networks", booktitle=3D"Proceedings of IEEE/ACM MOBICOM '99", month=3D"August", year=3D"1999", -manoj On Thu, 30 Sep 2004, redouane wrote: > Hi, > I test DSR with packet salvaging option, and I found > that this option decrease drasticaly the performance > of the protocol with high mobility. > In do the simulation in Opnet with network of 100 > nodes and 50 sources of traffic, with random waypoint > mobility. For validation,I ask if anyone do this test > in NS-2 and if is the same constat. > Thanks. > redouane > > > > > > > Vous manquez d=92espace pour stocker vos mails ? > Yahoo! Mail vous offre GRATUITEMENT 100 Mo ! > Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ > > Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis. A t=E9l=E9charger grat= uitement 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 manet-bounces@ietf.org Tue Oct 5 14:02:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20797 for ; Tue, 5 Oct 2004 14:02:28 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEtnE-0001im-Cl for manet-web-archive@ietf.org; Tue, 05 Oct 2004 14:12:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtZT-0000np-0T; Tue, 05 Oct 2004 13:57:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtVT-0008Pk-Fy for manet@megatron.ietf.org; Tue, 05 Oct 2004 13:53:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20064 for ; Tue, 5 Oct 2004 13:53:46 -0400 (EDT) Received: from web52502.mail.yahoo.com ([206.190.39.123]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEtec-0000KH-UO for manet@ietf.org; Tue, 05 Oct 2004 14:03:26 -0400 Message-ID: <20041005175059.29491.qmail@web52502.mail.yahoo.com> Received: from [128.4.130.33] by web52502.mail.yahoo.com via HTTP; Tue, 05 Oct 2004 10:50:59 PDT Date: Tue, 5 Oct 2004 10:50:59 -0700 (PDT) From: Leon Martin To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [manet] Is it difficult to receive simultaneously over multiple channels? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Hi, In 802.11 multiple channels are defined. Ususally a node listens on only one of them. I was wondering if it would be possible to let a node listen (scan) multiple channels? Thanks. - Leon __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 14:15:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21869 for ; Tue, 5 Oct 2004 14:15:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEtzb-00040J-Ul for manet-web-archive@ietf.org; Tue, 05 Oct 2004 14:24:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtm9-0003Db-0g; Tue, 05 Oct 2004 14:11:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEthR-0002Li-SI for manet@megatron.ietf.org; Tue, 05 Oct 2004 14:06:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21183 for ; Tue, 5 Oct 2004 14:06:08 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEtqj-0002dE-UF for manet@ietf.org; Tue, 05 Oct 2004 14:15:48 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 0BDEE200E; Tue, 5 Oct 2004 12:06:00 -0600 (MDT) From: "John Mullen" To: Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Tue, 5 Oct 2004 12:05:59 -0600 Message-ID: <000001c4ab05$f8370cc0$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E9AA@khephren.clb.tcfr.thales> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Content-Transfer-Encoding: quoted-printable Hi Raphael, >From Section 2 on p. 3, As long as the endpoints of a communication connection have valid routes to each other, AODV does not play any role. When a route to a new destination is needed, the node broadcasts a RREQ to find a route to the destination. A route can be determined when the RREQ reaches either the destination itself, or an intermediate node with a 'fresh enough' route to the destination. A 'fresh enough' route is a valid route entry for the destination whose associated sequence number is at least as great as that contained in the RREQ. >From the last line, if the route is fresh enough, S2 sends a RREP back to S1. If not, when the RREQ propagation continues to S4, the destination sequence number will be higher (otherwise the route is fresh enough). From p. 12, one of the cases in which a node increments its sequence number is: - Immediately before a destination node originates a RREP in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. So, if the route is not "fresh enough," the destination will increment its own sequence number. (Otherwise it won't see the RREQ). This means that by the time you get to Section 6.7, either the RREP is simply confirming the known route, in which case S2 need not reply to S1 because it already did so earlier, or it is indicating some sort of better route from S2 to S4, in which case S2 will forward the RREP to S1 to correct its earlier misinformation. =20 At least, that is how I understand it. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Monday, October 04, 2004 11:22 PM To: yann_eads@hotmail.com; manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Hi, The destination sequence number of station D is only updated when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the D is broken increments the destination sequence number of D. Later, this node sends AODV messages with updated sequence number for destination D. In the example below, the sequence number of S4 is never updated. It is the reason why S3 never propagates the RREP message corresponding to the RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the RREP.=20 In my mind, the sequence number received by S2 is greater than the one which created its route to S4. And if this route is updated, it fowards the RREP=20 to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP=20 >forwarding when route reply by intermediate nodes is not activated.=20 >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage !=20 http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 14:41:03 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23933 for ; Tue, 5 Oct 2004 14:41:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuOZ-0007jR-9B for manet-web-archive@ietf.org; Tue, 05 Oct 2004 14:50:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEu60-0006WU-1h; Tue, 05 Oct 2004 14:31:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEtyI-0005HS-Eh for manet@megatron.ietf.org; Tue, 05 Oct 2004 14:23:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22592 for ; Tue, 5 Oct 2004 14:23:33 -0400 (EDT) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEu7d-0004yG-5e for manet@ietf.org; Tue, 05 Oct 2004 14:33:13 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id 2222119E77A; Tue, 5 Oct 2004 20:22:54 +0200 (CEST) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17174-06; Tue, 5 Oct 2004 20:22:54 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id 06C8119E708; Tue, 5 Oct 2004 20:22:54 +0200 (CEST) Received: from afontenayssb-152-1-21-106.w83-114.abo.wanadoo.fr ([83.114.51.106]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Tue, 5 Oct 2004 20:22:54 +0200 (CEST) Message-ID: <4090.83.114.51.106.1097000574.squirrel@www.lri.fr> In-Reply-To: <20041005175059.29491.qmail@web52502.mail.yahoo.com> References: <20041005175059.29491.qmail@web52502.mail.yahoo.com> Date: Tue, 5 Oct 2004 20:22:54 +0200 (CEST) Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? To: "Leon Martin" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 8bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 8bit Hi :=), When a host is listening on a particular channel, it cannot hear communication taking place on a diferent channel. Due to this, a new type of hidden terminal problem occurs in this multi-channel environment (multi-channel hidden terminal problem). However, protocols are proposed to enable hosts to utilize multiple channels by switching channels dynamically to increasing network throughput. Hakim. > Hi, > > In 802.11 multiple channels are defined. Ususally a > node listens on only one of them. I was wondering if > it would be possible to let a node listen (scan) > multiple channels? > > Thanks. > > - Leon > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! > http://promotions.yahoo.com/new_mail > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 14:52:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25037 for ; Tue, 5 Oct 2004 14:52:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuZB-0001AY-81 for manet-web-archive@ietf.org; Tue, 05 Oct 2004 15:01:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEuKP-0001B6-Ex; Tue, 05 Oct 2004 14:46:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEu8H-0006n1-2M for manet@megatron.ietf.org; Tue, 05 Oct 2004 14:33:53 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23319 for ; Tue, 5 Oct 2004 14:33:51 -0400 (EDT) Received: from 209-254-158-42.ip.mcleodusa.net ([209.254.158.42] helo=che.ojctech.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuHa-0006mQ-Ki for manet@ietf.org; Tue, 05 Oct 2004 14:43:32 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id i95IXHKb021067 for ; Tue, 5 Oct 2004 13:33:17 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id i95IXG8i021065 for manet@ietf.org; Tue, 5 Oct 2004 13:33:16 -0500 Date: Tue, 5 Oct 2004 13:33:16 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? Message-ID: <20041005183316.GL654@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: <20041005175059.29491.qmail@web52502.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041005175059.29491.qmail@web52502.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 On Tue, Oct 05, 2004 at 10:50:59AM -0700, Leon Martin wrote: > Hi, > > In 802.11 multiple channels are defined. Ususally a > node listens on only one of them. I was wondering if > it would be possible to let a node listen (scan) > multiple channels? Yes. In the 802.11 chipsets by Realtek, ADMtek, and Atheros, there is no firmware mediating access to the synthesizer, so you can rapidly tune the radio from channel to channel. I figure you can tune a new channel in *much* less than a minimal packet transmission time, but somebody would have to try it to see. You cannot listen to all channels at once. At least, not very well. An 802.11b receiver tuned to, say, ch 6, can usually receive packets sent on *any* channel (ch 1 - ch 11), but with high attenuation (tens of dB). Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 15:00:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25994 for ; Tue, 5 Oct 2004 15:00:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuhQ-0002V3-QN for manet-web-archive@ietf.org; Tue, 05 Oct 2004 15:10:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEuOu-0001xB-D4; Tue, 05 Oct 2004 14:51:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEuJO-0000wR-Ae for manet@megatron.ietf.org; Tue, 05 Oct 2004 14:45:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24465 for ; Tue, 5 Oct 2004 14:45:20 -0400 (EDT) Received: from coldfront.acsu.buffalo.edu ([128.205.6.89] helo=front.acsu.buffalo.edu) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEuSi-0000D2-Pg for manet@ietf.org; Tue, 05 Oct 2004 14:55:01 -0400 Received: (qmail 12194 invoked from network); 5 Oct 2004 18:45:15 -0000 Received: from mailscan3.acsu.buffalo.edu (HELO localhost.localdomain) (128.205.6.135) by front.acsu.buffalo.edu with SMTP; 5 Oct 2004 18:45:15 -0000 Received: (mailscan3 scanner-smtpd 1.39 1.9 1.15); 05 Oct 2004 18:45:05 -0000 Received: (qmail 9028 invoked from network); 5 Oct 2004 18:45:05 -0000 Received: from hercules.acsu.buffalo.edu (128.205.7.123) by smtp2.acsu.buffalo.edu with SMTP; 5 Oct 2004 18:45:05 -0000 Received: (qmail 2125 invoked by uid 112170); 5 Oct 2004 18:45:05 -0000 Date: Tue, 5 Oct 2004 14:45:05 -0400 (EDT) From: Geethapriya Thamilarasu X-Sender: gt7@hercules.acsu.buffalo.edu To: Hakim.Badis@lri.fr Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? In-Reply-To: <4090.83.114.51.106.1097000574.squirrel@www.lri.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 1.0 (+) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: manet@ietf.org, Leon Martin X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 hi, I think the use of directional antennas can enable a node to scan multiple channels simultaneously. GP On Tue, 5 Oct 2004 Hakim.Badis@lri.fr wrote: > Hi :=), > > When a host is listening on a particular channel, it cannot hear > communication taking place on a diferent channel. Due to this, a new type > of hidden terminal problem occurs in this multi-channel environment > (multi-channel hidden terminal problem). However, protocols are proposed > to enable hosts to utilize multiple channels by switching channels > dynamically to increasing network throughput. > > Hakim. > > > Hi, > > > > In 802.11 multiple channels are defined. Ususally a > > node listens on only one of them. I was wondering if > > it would be possible to let a node listen (scan) > > multiple channels? > > > > Thanks. > > > > - Leon > > > > > > > > __________________________________ > > Do you Yahoo!? > > New and Improved Yahoo! Mail - Send 10MB messages! > > http://promotions.yahoo.com/new_mail > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 15:26:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29312 for ; Tue, 5 Oct 2004 15:26:17 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEv6N-0006DB-8w for manet-web-archive@ietf.org; Tue, 05 Oct 2004 15:35:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEumx-0007av-H6; Tue, 05 Oct 2004 15:15:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEulP-0006on-Le for manet@megatron.ietf.org; Tue, 05 Oct 2004 15:14:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27789 for ; Tue, 5 Oct 2004 15:14:18 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuuj-0004Ob-4p for manet@ietf.org; Tue, 05 Oct 2004 15:23:59 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 7B340200E; Tue, 5 Oct 2004 13:14:13 -0600 (MDT) From: "John Mullen" To: "'Leon Martin'" , Subject: RE: [manet] Is it difficult to receive simultaneously over multiplechannels? Date: Tue, 5 Oct 2004 13:15:26 -0600 Message-ID: <000001c4ab0f$ab6c5800$67f57b80@engr.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 In-Reply-To: <20041005175059.29491.qmail@web52502.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit Hi Leon, In general, if channels are established by a pattern of slots (e.g., every fourth slot) on a common frequency, it is possible for a receiver to monitor all channels. However, if channels are implemented as distinct transmission or sub-frequencies, then it is possible for more than one channel to be active simultaneously, and you would need a separate receiver for each channel. This is, of course, feasible, but may not be practical. Remember that the node will have to do at least some processing of the off-channel packets and, unless they offer something of value, that could be simply a waste of limited power. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Leon Martin Sent: Tuesday, October 05, 2004 10:51 AM To: manet@ietf.org Subject: [manet] Is it difficult to receive simultaneously over multiplechannels? Hi, In 802.11 multiple channels are defined. Ususally a node listens on only one of them. I was wondering if it would be possible to let a node listen (scan) multiple channels? Thanks. - Leon __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 15:30:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29733 for ; Tue, 5 Oct 2004 15:30:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEvAS-00076F-GS for manet-web-archive@ietf.org; Tue, 05 Oct 2004 15:40:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEurg-0001CS-VS; Tue, 05 Oct 2004 15:20:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEumK-0007Jd-Ic for manet@megatron.ietf.org; Tue, 05 Oct 2004 15:15:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27929 for ; Tue, 5 Oct 2004 15:15:15 -0400 (EDT) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEuvf-0004nv-2o for manet@ietf.org; Tue, 05 Oct 2004 15:24:56 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id 8389119E7B9; Tue, 5 Oct 2004 21:14:44 +0200 (CEST) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21030-06; Tue, 5 Oct 2004 21:14:44 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id 6F80C19E79C; Tue, 5 Oct 2004 21:14:44 +0200 (CEST) Received: from afontenayssb-152-1-21-106.w83-114.abo.wanadoo.fr ([83.114.51.106]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Tue, 5 Oct 2004 21:14:44 +0200 (CEST) Message-ID: <4231.83.114.51.106.1097003684.squirrel@www.lri.fr> In-Reply-To: References: <4090.83.114.51.106.1097000574.squirrel@www.lri.fr> Date: Tue, 5 Oct 2004 21:14:44 +0200 (CEST) Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? To: "Geethapriya Thamilarasu" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: 8bit Cc: manet@ietf.org, Leon Martin , hakim.badis@lri.fr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 8bit > hi, > I think the use of directional antennas can enable a node to scan multiple > channels simultaneously. yes, you are right, The potential benefits of using directional antennas include range extension, better spatial reuse, multipath diversity, interference suppression, capacity increase, and data rate increase. however, the major problem is the power consumption. hakim > > GP > > > On Tue, 5 Oct 2004 Hakim.Badis@lri.fr wrote: > >> Hi :=), >> >> When a host is listening on a particular channel, it cannot hear >> communication taking place on a diferent channel. Due to this, a new >> type >> of hidden terminal problem occurs in this multi-channel environment >> (multi-channel hidden terminal problem). However, protocols are >> proposed >> to enable hosts to utilize multiple channels by switching channels >> dynamically to increasing network throughput. >> >> Hakim. >> >> > Hi, >> > >> > In 802.11 multiple channels are defined. Ususally a >> > node listens on only one of them. I was wondering if >> > it would be possible to let a node listen (scan) >> > multiple channels? >> > >> > Thanks. >> > >> > - Leon >> > >> > >> > >> > __________________________________ >> > Do you Yahoo!? >> > New and Improved Yahoo! Mail - Send 10MB messages! >> > http://promotions.yahoo.com/new_mail >> > >> > _______________________________________________ >> > manet mailing list >> > manet@ietf.org >> > https://www1.ietf.org/mailman/listinfo/manet >> > >> >> >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> >> > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 16:24:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07230 for ; Tue, 5 Oct 2004 16:24:39 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEw0s-0007xk-5w for manet-web-archive@ietf.org; Tue, 05 Oct 2004 16:34:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEvjG-00074B-4y; Tue, 05 Oct 2004 16:16:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEvI8-0007kn-Mb for manet@megatron.ietf.org; Tue, 05 Oct 2004 15:48:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01543 for ; Tue, 5 Oct 2004 15:48:06 -0400 (EDT) Received: from mail.netgate.com ([192.207.126.2] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEvRT-0001L7-ON for manet@ietf.org; Tue, 05 Oct 2004 15:57:48 -0400 Received: by netgate.com (Postfix, from userid 45) id 1FCDDF4022; Tue, 5 Oct 2004 12:48:04 -0700 (PDT) Received: from [192.168.1.2] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 70CBEF4016; Tue, 5 Oct 2004 12:47:59 -0700 (PDT) Message-ID: <4162FA6E.4080105@netgate.com> Date: Tue, 05 Oct 2004 09:47:58 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 0.8 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Young Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? References: <20041005175059.29491.qmail@web52502.mail.yahoo.com> <20041005183316.GL654@che.ojctech.com> In-Reply-To: <20041005183316.GL654@che.ojctech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit David Young wrote: > On Tue, Oct 05, 2004 at 10:50:59AM -0700, Leon Martin wrote: > >>Hi, >> >>In 802.11 multiple channels are defined. Ususally a >>node listens on only one of them. I was wondering if >>it would be possible to let a node listen (scan) >>multiple channels? > > > Yes. In the 802.11 chipsets by Realtek, ADMtek, and Atheros, there is > no firmware mediating access to the synthesizer, so you can rapidly tune > the radio from channel to channel. I figure you can tune a new channel > in *much* less than a minimal packet transmission time, but somebody > would have to try it to see. Likely, but most of the drivers I've seen for Realtek and Atheros currently implement a chip reset after changing channels, which consumes a whole lot of time. So, some work remains to be done. > You cannot listen to all channels at once. At least, not very well. Engim has a chipset that allows this. > An 802.11b receiver tuned to, say, ch 6, can usually receive packets sent > on *any* channel (ch 1 - ch 11), but with high attenuation (tens of dB). This is just a lack of selectivity in the receiver, and is nearly always not a good thing. At a high enough RSSI, it is possible to decode packets sent on say, ch5 and ch7 when the receiver is tuned to ch6. (This is one of the reasons why the channel is advertised in 802.11's beacon frames.) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 16:35:25 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08527 for ; Tue, 5 Oct 2004 16:35:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEwBH-00012I-MG for manet-web-archive@ietf.org; Tue, 05 Oct 2004 16:45:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEvkS-0008Ob-Rg; Tue, 05 Oct 2004 16:17:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEvax-0001IA-PJ for manet@megatron.ietf.org; Tue, 05 Oct 2004 16:07:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04275 for ; Tue, 5 Oct 2004 16:07:32 -0400 (EDT) Received: from coldfront.acsu.buffalo.edu ([128.205.6.89] helo=front.acsu.buffalo.edu) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEvkE-0004fa-AZ for manet@ietf.org; Tue, 05 Oct 2004 16:17:14 -0400 Received: (qmail 14554 invoked from network); 5 Oct 2004 20:07:21 -0000 Received: from mailscan1.acsu.buffalo.edu (HELO localhost.localdomain) (128.205.6.133) by front.acsu.buffalo.edu with SMTP; 5 Oct 2004 20:07:21 -0000 Received: (mailscan1 scanner-smtpd 1.39 1.9 1.15); 05 Oct 2004 20:07:13 -0000 Received: (qmail 27771 invoked from network); 5 Oct 2004 20:07:13 -0000 Received: from hercules.acsu.buffalo.edu (128.205.7.123) by smtp2.acsu.buffalo.edu with SMTP; 5 Oct 2004 20:07:13 -0000 Received: (qmail 9852 invoked by uid 112170); 5 Oct 2004 20:07:12 -0000 Date: Tue, 5 Oct 2004 16:07:12 -0400 (EDT) From: Geethapriya Thamilarasu X-Sender: gt7@hercules.acsu.buffalo.edu To: Hakim.Badis@lri.fr In-Reply-To: <4231.83.114.51.106.1097003684.squirrel@www.lri.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: manet@ietf.org Subject: [manet] power consumption X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a > yes, you are right, The potential benefits of using directional antennas > include range extension, better spatial reuse, multipath diversity, > interference suppression, capacity increase, and data rate increase. > however, the major problem is the power consumption. Hi, Are n't directional antennas providing energy conservation, because of directionally transmitting data instead of wasting power transmitting in all directions? how do you say the major problem is power consumption? Regards GP > > hakim > > > > > GP > > > > > > On Tue, 5 Oct 2004 Hakim.Badis@lri.fr wrote: > > > >> Hi :=), > >> > >> When a host is listening on a particular channel, it cannot hear > >> communication taking place on a diferent channel. Due to this, a new > >> type > >> of hidden terminal problem occurs in this multi-channel environment > >> (multi-channel hidden terminal problem). However, protocols are > >> proposed > >> to enable hosts to utilize multiple channels by switching channels > >> dynamically to increasing network throughput. > >> > >> Hakim. > >> > >> > Hi, > >> > > >> > In 802.11 multiple channels are defined. Ususally a > >> > node listens on only one of them. I was wondering if > >> > it would be possible to let a node listen (scan) > >> > multiple channels? > >> > > >> > Thanks. > >> > > >> > - Leon > >> > > >> > > >> > > >> > __________________________________ > >> > Do you Yahoo!? > >> > New and Improved Yahoo! Mail - Send 10MB messages! > >> > http://promotions.yahoo.com/new_mail > >> > > >> > _______________________________________________ > >> > manet mailing list > >> > manet@ietf.org > >> > https://www1.ietf.org/mailman/listinfo/manet > >> > > >> > >> > >> > >> _______________________________________________ > >> manet mailing list > >> manet@ietf.org > >> https://www1.ietf.org/mailman/listinfo/manet > >> > >> > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 5 16:52:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10626 for ; Tue, 5 Oct 2004 16:52:02 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEwRM-0002wV-59 for manet-web-archive@ietf.org; Tue, 05 Oct 2004 17:01:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEw8L-0004JY-BO; Tue, 05 Oct 2004 16:42:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEw3c-0002VZ-94 for manet@megatron.ietf.org; Tue, 05 Oct 2004 16:37:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09067 for ; Tue, 5 Oct 2004 16:37:10 -0400 (EDT) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEwCu-0001UU-9l for manet@ietf.org; Tue, 05 Oct 2004 16:46:52 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id AF12B19E7D1; Tue, 5 Oct 2004 22:36:36 +0200 (CEST) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27222-06; Tue, 5 Oct 2004 22:36:36 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id 9A4E819E7CD; Tue, 5 Oct 2004 22:36:36 +0200 (CEST) Received: from afontenayssb-152-1-21-106.w83-114.abo.wanadoo.fr ([83.114.51.106]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Tue, 5 Oct 2004 22:36:36 +0200 (CEST) Message-ID: <4410.83.114.51.106.1097008596.squirrel@www.lri.fr> In-Reply-To: References: <4231.83.114.51.106.1097003684.squirrel@www.lri.fr> Date: Tue, 5 Oct 2004 22:36:36 +0200 (CEST) To: "Geethapriya Thamilarasu" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA09067 Cc: manet@ietf.org, hakim.badis@lri.fr Subject: [manet] Re: power consumption X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Content-Transfer-Encoding: quoted-printable Sorry, lot of energy is wasted when nodes equipped omni-directional antennas and not directional antannas. directional transmissions cause some serious problems in an ad-hoc environment. These problems are the increase of the instances of hidden terminal problem, the problem of deafness and the problem of the determination of neighbors=92 location. Hakim > > > > >> >> hakim >> >> > >> > GP >> > >> > >> > On Tue, 5 Oct 2004 Hakim.Badis@lri.fr wrote: >> > >> >> Hi :=3D), >> >> >> >> When a host is listening on a particular channel, it cannot hear >> >> communication taking place on a diferent channel. Due to this, a ne= w >> >> type >> >> of hidden terminal problem occurs in this multi-channel environment >> >> (multi-channel hidden terminal problem). However, protocols are >> >> proposed >> >> to enable hosts to utilize multiple channels by switching channels >> >> dynamically to increasing network throughput. >> >> >> >> Hakim. >> >> >> >> > Hi, >> >> > >> >> > In 802.11 multiple channels are defined. Ususally a >> >> > node listens on only one of them. I was wondering if >> >> > it would be possible to let a node listen (scan) >> >> > multiple channels? >> >> > >> >> > Thanks. >> >> > >> >> > - Leon >> >> > >> >> > >> >> > >> >> > __________________________________ >> >> > Do you Yahoo!? >> >> > New and Improved Yahoo! Mail - Send 10MB messages! >> >> > http://promotions.yahoo.com/new_mail >> >> > >> >> > _______________________________________________ >> >> > manet mailing list >> >> > manet@ietf.org >> >> > https://www1.ietf.org/mailman/listinfo/manet >> >> > >> >> >> >> >> >> >> >> _______________________________________________ >> >> manet mailing list >> >> manet@ietf.org >> >> https://www1.ietf.org/mailman/listinfo/manet >> >> >> >> >> > >> > >> > _______________________________________________ >> > manet mailing list >> > manet@ietf.org >> > https://www1.ietf.org/mailman/listinfo/manet >> > >> >> >> >> > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 02:26:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18050 for ; Wed, 6 Oct 2004 02:26:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5PA-0000Ta-DM for manet-web-archive@ietf.org; Wed, 06 Oct 2004 02:36:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5Cg-0000q1-JK; Wed, 06 Oct 2004 02:23:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF58q-0007ki-8y for manet@megatron.ietf.org; Wed, 06 Oct 2004 02:19:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10656 for ; Wed, 6 Oct 2004 02:19:10 -0400 (EDT) Received: from albatross.ericsson.se ([193.180.251.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5IG-00006u-27 for manet@ietf.org; Wed, 06 Oct 2004 02:28:57 -0400 Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121]) by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i966J8WR028363 for ; Wed, 6 Oct 2004 08:19:08 +0200 (MEST) Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Wed, 6 Oct 2004 08:19:08 +0200 Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 4J5F207R; Wed, 6 Oct 2004 08:19:08 +0200 Received: from nellike.ted.dk.eu.ericsson.se (nellike.ted.dk.eu.ericsson.se [213.159.189.18]) by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id i966J4329654 for ; Wed, 6 Oct 2004 08:19:07 +0200 (MEST) Date: Wed, 6 Oct 2004 08:19:04 +0200 (CEST) X-Sybari-Trust: 0d9b6199 74898554 0e55cabb 00000139 From: =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= X-X-Sender: tedpcn@nellike.ted.dk.eu.ericsson.se To: manet@ietf.org Message-ID: 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 unixmail.ted.dk.eu.ericsson.se id i966J4329654 X-OriginalArrivalTime: 06 Oct 2004 06:19:08.0235 (UTC) FILETIME=[633371B0:01C4AB6C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Subject: [manet] Announcing successful IPv6 MANET/fixed net/MANET demo X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: quoted-printable On June 16th, 2004, a very successful demonstration was held at Ericsson Microwave Systems in Gothenburg, Sweden. The demonstration showed communication between nodes in two different IPv6-based MANETs, a reactive and a proactive one, connected via a fixed IPv6 network. The demonstration was an internal milestone in the B2NCW project (see below); we announce it at the IETF MANET mailing list, because it might be of interest to the readers of the list, and because, to the best of our knowledge, this is the first time any organisation has reached this far in combining Mobile Ad-Hoc Networking and IPv6. (Please let us know if this is not the case.) The demonstration consisted of a MANET running OLSR, a MANET running a proprietary reactive routing protocol and a backbone configured with static routes. The fixed/ad hoc gateways were formed from pairs of routers, one fixed and one ad hoc, with a static route configured between them. Global addresses in the MANETs were pre-configured. The MANETs ran over 802.11b WLAN, and the fixed network ran over Ethernet. Applications demonstrated included web access and streaming video. The system in Gothenburg was put together almost effortlessly following a trial integration between sites in three countries over the 6Bone. The work was carried out on the Building Blocks for Network Centric Warfare project (B2NCW, ), with support from the UK, Swedish and Danish Ministries of Defence and the participating companies: Ericsson Microwave Systems (Sweden), BAE Systems Advanced Technology Centre (UK) and Ericsson Telebit (Denmark). -- Peder Chr. N=F8rgaard Senior System Developer, M. Sc. Ericsson Telebit A/S tel: +45 30 91 84 31 Skanderborgvej 232 fax: +45 89 38 51 01 DK-8260 Viby J, Denmark e-mail: Peder.Chr.Norgaard@ericsson.com (old e-mail 2000-2003: Peder.C.Norgaard@ted.ericsson.se) (old e-mail 1992-2000: pcn@tbit.dk) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 03:06:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25343 for ; Wed, 6 Oct 2004 03:06:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF61g-00034j-63 for manet-web-archive@ietf.org; Wed, 06 Oct 2004 03:15:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5q8-0007s3-4o; Wed, 06 Oct 2004 03:03:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5pX-0007ji-M3 for manet@megatron.ietf.org; Wed, 06 Oct 2004 03:03:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25136 for ; Wed, 6 Oct 2004 03:03:17 -0400 (EDT) Received: from reserv6.univ-lille1.fr ([193.49.225.20] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5yo-0002u6-Qb for manet@ietf.org; Wed, 06 Oct 2004 03:13:05 -0400 Received: from kriek (kriek.lifl.fr [134.206.11.16]) by reserv6.univ-lille1.fr (8.12.11/jtpda-5.3.1) with ESMTP id i9670JnS010454 ; Wed, 6 Oct 2004 09:00:20 +0200 From: "David Simplot-Ryl" To: , , , Date: Wed, 6 Oct 2004 09:00:30 +0200 Message-ID: <000501c4ab72$30d71540$100bce86@lifl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-USTL-MailScanner-Information: Please contact the ISP for more information X-USTL-MailScanner: Found to be clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a Content-Transfer-Encoding: quoted-printable Subject: [manet] 2nd CFP WWAN 2005, Columbus, Ohio, USA, 6-9 June, 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Content-Transfer-Encoding: quoted-printable Please accept our apologies in case you receive this information from multiple sources. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2nd CALL FOR PAPERS WWAN 2005 2nd International Workshop on Wireless Ad Hoc Networking http://www.lifl.fr/RD2P/WWAN2005 to be held in conjunction with The 25th IEEE International Conference on Distributed Computing Systems (ICDCS-2005) Columbus, Ohio, USA, June 6-9, 2005 http://www.cis.ohio-state.edu/icdcs05 ---------------------------------------------------------------------- Purpose Wireless networks and mobile computing research has until recently concentrated on single-hop networks (network nodes communicating directly to a fixed infrastructure), such as cellular or satellite systems. Wireless ad hoc networking covers multi-hop scenarios (network nodes communicating via other network nodes) such as conference, hospital, battlefield, rescue, and monitoring scenarios. Wireless ad-hoc networks are formed by a set of hosts that communicate with each other over a wireless channel. Each node has the ability to communicate directly with another node in its physical neighborhood. They operate in a self-organized and decentralized manner and message communication takes place via multi-hop spreading. A packet is sent to its target node through a set of intermediate nodes that act as routers. Particular ad hoc network systems include packet radio networks, sensor networks, personal communication systems, rooftop networks, and wireless local area networks. This workshop covers the area of ad hoc networking, from physical issues up to applications aspects. In particular, it will cover physical, data link, network and transport layers, as well as applications, security, simulation and power management issues in sensor, local area, personal, and mobile ad hoc networks. It is the goal of this workshop to review ad hoc protocols and models and to reflect the latest in the state of the art in ad hoc networks. It seeks to provide up to date information on research and development activities in the rapidly growing area of ad hoc networks. The first edition of WWAN held last year during ICDCS-2004 (Tokyo, Japan) was organized by David Simplot-Ryl and Ivan Stojmenovic. In response to the Call for Papers, 42 papers from 20 different countries had been submitted. Based on three review reports per paper, they was classified as accept, reject or discuss. For those papers in the discuss list, additional opinions were sought. As a result, a total of 21 papers were selected for presentation at WWAN 2004 and were organized in 7 sessions. Website of this prior workshop: http://www.lifl.fr/RD2P/WWAN2004 Topics of Interest We are seeking papers that describe original and unpublished contributions addressing various aspects of ad hoc networking. Possible topics of interest include, but are not limited to: - Applications and history of ad hoc networks,=20 - Physical layer of ad hoc networks,=20 - Pervasive and wearable computing,=20 - IEEE 802.11 and Bluetooth based medium access control,=20 - Methods and tools for ad hoc networks simulation,=20 - Analytical, mobility and validation models for ad hoc networks,=20 - Hybrid networks and wireless internet,=20 - Security in ad hoc networks,=20 - Data management issues, query processing, data delivery,=20 - Routing, broadcasting and multicasting in ad hoc networks,=20 - Energy-efficient protocols for ad hoc networks,=20 - Quality of service in medium access control and routing,=20 - Topology construction and maintenance in ad hoc networks. Paper Submission Submit a full paper of about 6 pages (IEEE Computer Society proceedings Manuscripts: two column, single-spaced), including figures and references, using 10 font size, and number each page. Accepted papers will be published by IEEE Computer Society Press, as proceedings of the ICDCS'2005 workshops. You can use the IEEE Computer Society Press Proceedings Author Guidelines (http://computer.org/cspress/instruct.htm). Prepare your paper in PDF file only (Adobe format), paper title, authors' names, affiliations, postal address, phone, fax, and e-mail address of the authors, about 200-250 word abstract, and five keywords. Send by mail your submission to both co-chairs (David.Simplot@lifl.fr and ivan@site.uottawa.ca). Important Dates Manuscript Submission: November 12, 2004=20 Acceptance Notification: January 21, 2005=20 Final Manuscript Due: March 1, 2005=20 Program Co-Chairs Dr. David Simplot IRCICA/LIFL, Univ. Lille 1, INRIA Futurs, France David.Simplot@lifl.fr=20 Dr. Ivan Stojmenovic SITE, University of Ottawa, Canada ivan@site.uottawa.ca=20 Program Committee Michel Barbeau, Carleton University, Ottawa, Canada=20 Stefano Basagni, Northeastern University, Boston, USA=20 Ana Cavalli, INT Evry, France=20 Marco Conti, IIT Institute, Pisa, Italy=20 Serge Fdida, University of Paris, France=20 Laura Marie Feeney, SICS, Kista, Sweden=20 Afonso Ferreira, CNRS, France & COST Office, Brussels, Belgium=20 Eric Fleury, CITI Lyon, France=20 Matthias Frank, University of Bonn, Germany=20 Jennifer Hou, University of Illinois, USA=20 Keqin Li, State University of New York, USA=20 Xiang-Yang Li, Illinois Institute of Technology, USA=20 Soung-Chang Liew, The Chinese University of Hong Kong, Hong Kong=20 St=E9phane Maag, INT Evry, France=20 Jelena Misic, University of Manitoba, Winnipeg, Canada=20 Ingrid Moerman, University of Gent, Belgium=20 Amiya Nayak, SITE, University of Ottawa, Canada=20 Stephan Olariu, Old Dominion University, Norfolk, USA=20 Symeon Papavassiliou, University Heights, Newark, USA=20 Pedro Ruiz, University of Murcia, Spain=20 Loren Schwiebert, Wayne University, Detroit, USA=20 Krishna Sivalingam, University of Maryland Baltimore County, USA=20 Ketil St=F8len, SINTEF and University of Oslo, Norway=20 Takashi Watanabe, Shizuoka University, Japan=20 Fr=E9d=E9ric Weis, University of Rennes, France=20 Jie Wu, Florida Atlantic University, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 03:46:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28581 for ; Wed, 6 Oct 2004 03:46:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF6ee-0005Zc-FV for manet-web-archive@ietf.org; Wed, 06 Oct 2004 03:56:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF6SV-0004wI-7n; Wed, 06 Oct 2004 03:43:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF6QR-0004bX-Ja for manet@megatron.ietf.org; Wed, 06 Oct 2004 03:41:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28307 for ; Wed, 6 Oct 2004 03:41:25 -0400 (EDT) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF6Zs-0005Cb-2Z for manet@ietf.org; Wed, 06 Oct 2004 03:51:13 -0400 Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 415F7315000F5A3E for manet@ietf.org; Wed, 6 Oct 2004 09:41:27 +0200 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Wed, 06 Oct 2004 09:39:57 +0200 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 415BC88D00035AE9 for manet@ietf.org; Wed, 6 Oct 2004 09:39:57 +0200 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Wed, 06 Oct 2004 09:39:57 +0200 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 4152F54B00056A02 for manet@ietf.org; Wed, 6 Oct 2004 09:39:00 +0200 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Wed, 06 Oct 2004 09:39:00 +0200 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Wed, 6 Oct 2004 09:39:57 +0200 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E9B4@khephren.clb.tcfr.thales> To: jomullen@nmsu.edu Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Wed, 6 Oct 2004 09:40:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.4 (/) X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186 Content-Transfer-Encoding: quoted-printable John, Thank you for your comments. AODV must behave as you describe when intermediate node are allowed to = reply to RREQ concerning destination they have a route "fresh enough" to. >From section 6.6 on p18 : A node generates a RREP if either (i) it is itself the destination or, (ii) it has an active route to the destination, the destination = sequence number in the node's existing route table entry for the destination is = valid and greater than or equal to the destination sequence number of the = RREQ, and the "destination only" ('D') flag is NOT set So if the "destination only" flag is set in the RREQ, an intermediate = node will not generate a RREP in response to any RREQ. I think that if the sequence number of station S4 is not modified, the = case illustrated by the example below is incorrectly handled in RFC 3561. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not >activated, the route research reaches S4, that sends a RREP back to = S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only = if >a forward route (to the destination) has been updated (or created). As >this is not the case here, the RREP is not forwarded and the route to >S4 is never established on S1. This means that either : - "destination only" flag in RREQs must never be set to 1 or, - a RREP is always forwarded, even if it does not cause an update to = the route to the destination (opposite to what is written in RFC 3561, = section 6.7 page 21) Rapha=EBl -----Message d'origine----- De : John Mullen [mailto:jomullen@nmsu.edu] Envoy=E9 : mardi 5 octobre 2004 20:06 =C0 : Raphael-a.MASSIN@fr.thalesgroup.com Cc : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hi Raphael, >From Section 2 on p. 3, As long as the endpoints of a communication connection have valid routes to each other, AODV does not play any role. When a route to = a new destination is needed, the node broadcasts a RREQ to find a = route to the destination. A route can be determined when the RREQ reaches either the destination itself, or an intermediate node with a 'fresh enough' route to the destination. A 'fresh enough' route is a valid route entry for the destination whose associated sequence number is at least as great as that contained in the RREQ. >From the last line, if the route is fresh enough, S2 sends a RREP back to S1. If not, when the RREQ propagation continues to S4, the destination sequence number will be higher (otherwise the route is = fresh enough). From p. 12, one of the cases in which a node increments its sequence number is: - Immediately before a destination node originates a RREP in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. So, if the route is not "fresh enough," the destination will increment its own sequence number. (Otherwise it won't see the RREQ). This = means that by the time you get to Section 6.7, either the RREP is simply confirming the known route, in which case S2 need not reply to S1 because it already did so earlier, or it is indicating some sort of better route from S2 to S4, in which case S2 will forward the RREP to = S1 to correct its earlier misinformation.=20 At least, that is how I understand it. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Monday, October 04, 2004 11:22 PM To: yann_eads@hotmail.com; manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Hi, The destination sequence number of station D is only updated when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the = D is broken increments the destination sequence number of D. Later, this node sends AODV messages with updated sequence number for destination = D. In the example below, the sequence number of S4 is never updated. It is the reason why S3 never propagates the RREP message corresponding to = the RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I = would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the RREP. In my mind, the sequence number received by S2 is greater than the one which created its route to S4. And if this route is updated, it fowards the RREP to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP >forwarding when route reply by intermediate nodes is not activated. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not >activated, the route research reaches S4, that sends a RREP back to = S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only = if >a forward route (to the destination) has been updated (or created). As >this is not the case here, the RREP is not forwarded and the route to >S4 is never established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage ! http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 05:31:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06096 for ; Wed, 6 Oct 2004 05:31:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF8It-0003yB-6A for manet-web-archive@ietf.org; Wed, 06 Oct 2004 05:41:47 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF87J-0005ez-6l; Wed, 06 Oct 2004 05:29:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF85M-0005S6-Dc for manet@megatron.ietf.org; Wed, 06 Oct 2004 05:27:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05592 for ; Wed, 6 Oct 2004 05:27:45 -0400 (EDT) From: joerg.habetha@philips.com Received: from gw-eur4.philips.com ([161.85.125.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF8Ep-0003kA-BU for manet@ietf.org; Wed, 06 Oct 2004 05:37:35 -0400 Received: from smtpscan-eur5.philips.com (smtpscan-eur5.mail.philips.com [130.144.57.168]) by gw-eur4.philips.com (Postfix) with ESMTP id C967E49B55; Wed, 6 Oct 2004 09:27:15 +0000 (UTC) Received: from smtpscan-eur5.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 6B45417F3; Wed, 6 Oct 2004 09:27:15 +0000 (GMT) Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com [130.144.57.171]) by smtpscan-eur5.philips.com (Postfix) with ESMTP id 3231917F1; Wed, 6 Oct 2004 09:27:15 +0000 (GMT) Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) by smtprelay-eur2.philips.com (8.9.3p3/8.9.3-1.2.2m-20040401) with ESMTP id JAA08655; Wed, 6 Oct 2004 09:27:14 GMT To: David Young Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.9a January 7, 2002 Message-ID: Date: Wed, 6 Oct 2004 11:26:02 +0200 X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.0.2CF1HF706 | September 14, 2004) at 06/10/2004 11:26:04, Serialize complete at 06/10/2004 11:26:04 X-Spam-Score: 0.8 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0546712248==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 This is a multipart message in MIME format. --===============0546712248== Content-Type: multipart/alternative; boundary="=_alternative 0033EDC1C1256F25_=" This is a multipart message in MIME format. --=_alternative 0033EDC1C1256F25_= Content-Type: text/plain; charset="us-ascii" Hi, if you do not double your oscillator or even the complete tranceiver you can assume a channel switching time of about 1ms. We have developed forwarding schemes that are based on frequency switching. You use one frequency on the incoming hop and a different one on the outgoing hop. The forwarder switches in-between the channels. Some overhead is unavoidable due to the switching times. Regards, Joerg David Young Sent by: manet-bounces@ietf.org 05.10.2004 20:33 To: manet@ietf.org cc: (bcc: Joerg Habetha/ACN/RESEARCH/PHILIPS) Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? Classification: On Tue, Oct 05, 2004 at 10:50:59AM -0700, Leon Martin wrote: > Hi, > > In 802.11 multiple channels are defined. Ususally a > node listens on only one of them. I was wondering if > it would be possible to let a node listen (scan) > multiple channels? Yes. In the 802.11 chipsets by Realtek, ADMtek, and Atheros, there is no firmware mediating access to the synthesizer, so you can rapidly tune the radio from channel to channel. I figure you can tune a new channel in *much* less than a minimal packet transmission time, but somebody would have to try it to see. You cannot listen to all channels at once. At least, not very well. An 802.11b receiver tuned to, say, ch 6, can usually receive packets sent on *any* channel (ch 1 - ch 11), but with high attenuation (tens of dB). Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --=_alternative 0033EDC1C1256F25_= Content-Type: text/html; charset="us-ascii"
Hi,

if you do not double your oscillator or even the complete tranceiver you can assume a channel switching time of about 1ms.
We have developed forwarding schemes that are based on frequency switching. You use one frequency on the incoming hop and a different one on the outgoing hop. The forwarder switches in-between the channels. Some overhead is unavoidable due to the switching times.

Regards,
Joerg







David Young <dyoung@pobox.com>

Sent by:
manet-bounces@ietf.org

05.10.2004 20:33

       
        To:        manet@ietf.org
        cc:        (bcc: Joerg Habetha/ACN/RESEARCH/PHILIPS)
        Subject:        Re: [manet] Is it difficult to receive simultaneously over multiple        channels?

        Classification:        




On Tue, Oct 05, 2004 at 10:50:59AM -0700, Leon Martin wrote:
> Hi,
>
> In 802.11 multiple channels are defined. Ususally a
> node listens on only one of them. I was wondering if
> it would be possible to let a node listen (scan)
> multiple channels?

Yes.  In the 802.11 chipsets by Realtek, ADMtek, and Atheros, there is
no firmware mediating access to the synthesizer, so you can rapidly tune
the radio from channel to channel.  I figure you can tune a new channel
in *much* less than a minimal packet transmission time, but somebody
would have to try it to see.

You cannot listen to all channels at once.  At least, not very well.
An 802.11b receiver tuned to, say, ch 6, can usually receive packets sent
on *any* channel (ch 1 - ch 11), but with high attenuation (tens of dB).

Dave

--
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933

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

--=_alternative 0033EDC1C1256F25_=-- --===============0546712248== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0546712248==-- From manet-bounces@ietf.org Wed Oct 6 11:21:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06318 for ; Wed, 6 Oct 2004 11:21:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFDlf-0001Cm-Ii for manet-web-archive@ietf.org; Wed, 06 Oct 2004 11:31:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDX5-0001FQ-QP; Wed, 06 Oct 2004 11:16:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDT2-0000c2-PX for manet@megatron.ietf.org; Wed, 06 Oct 2004 11:12:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05712 for ; Wed, 6 Oct 2004 11:12:34 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFDcW-0000ej-Iu for manet@ietf.org; Wed, 06 Oct 2004 11:22:27 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 6EFD12029; Wed, 6 Oct 2004 09:12:32 -0600 (MDT) From: "John Mullen" To: "'Jim Thompson'" , "'David Young'" Subject: RE: [manet] Is it difficult to receive simultaneously over multiplechannels? Date: Wed, 6 Oct 2004 09:12:37 -0600 Message-ID: <001d01c4abb6$ea261b60$67f57b80@engr.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: <4162FA6E.4080105@netgate.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit Hi, -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Jim Thompson Sent: Tuesday, October 05, 2004 12:48 PM To: David Young Cc: manet@ietf.org Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? David Young wrote: > On Tue, Oct 05, 2004 at 10:50:59AM -0700, Leon Martin wrote: > >>Hi, >> >> > An 802.11b receiver tuned to, say, ch 6, can usually receive packets > sent on *any* channel (ch 1 - ch 11), but with high attenuation (tens > of dB). This is just a lack of selectivity in the receiver, and is nearly always not a good thing. At a high enough RSSI, it is possible to decode packets sent on say, ch5 and ch7 when the receiver is tuned to ch6. (This is one of the reasons why the channel is advertised in 802.11's beacon frames.) ------------------ Actually, it is the other way around. High selectivity would reduce the number of channels that can be simultaneously received. If you want to receive on two or more channels that are simultaneously active, you must have dedicated circuitry for each channel. Otherwise, the RF signals will mix and interfere with each other, causing data collisions, rather than distinct data streams. John Mullen _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 11:34:09 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07074 for ; Wed, 6 Oct 2004 11:34:09 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFDxT-0001zF-3N for manet-web-archive@ietf.org; Wed, 06 Oct 2004 11:44:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDkL-0003de-DC; Wed, 06 Oct 2004 11:30:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDfU-0002mm-31 for manet@megatron.ietf.org; Wed, 06 Oct 2004 11:25:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06562 for ; Wed, 6 Oct 2004 11:25:25 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFDow-0001PC-T9 for manet@ietf.org; Wed, 06 Oct 2004 11:35:18 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id D3281202A; Wed, 6 Oct 2004 09:25:22 -0600 (MDT) From: "John Mullen" To: "'Geethapriya Thamilarasu'" , Subject: RE: [manet] power consumption Date: Wed, 6 Oct 2004 09:25:24 -0600 Message-ID: <001e01c4abb8$b3523d60$67f57b80@engr.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.2900.2180 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: 7bit -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Geethapriya Thamilarasu Sent: Tuesday, October 05, 2004 1:07 PM To: Hakim.Badis@lri.fr Cc: manet@ietf.org Subject: [manet] power consumption > yes, you are right, The potential benefits of using directional > antennas include range extension, better spatial reuse, multipath > diversity, interference suppression, capacity increase, and data rate > increase. however, the major problem is the power consumption. Hi, Are n't directional antennas providing energy conservation, because of directionally transmitting data instead of wasting power transmitting in all directions? how do you say the major problem is power consumption? Regards GP -------------------------------- The main advantage of directional antennas is in reception, because the volume of interference and noise can be sharply reduced. In transmission, the benefits are mixed, especially in an urban environment, where it is not obvious in which direction the transmitter needs to be pointed. Directional transmission can be very effective in point-to-point links, but when things are in motion, the problem is significantly more complicated. The problem in ad hoc nets is that things are in motion and any node might need to communicate with any other. Unless receiving a particular data stream, therefore, a node would need to listen for a signal from any direction. Even when receiving a stream, motion might require adjustments in transmitter and receiver antenna settings. Also, until a transmitter locates a receiver, it will have to broadcast. Thus, the directional antennas need to be adjustable, not just in direction, but also in degree of directional selectivity. This implies some sort of electronic circuitry that will require power to operate. Also, some directional antennas are more lossy than their omnidirectional counterparts. So, the impact on power depends on the fraction of time and degree to which selective transmission can be employed in the transmitter vs. the energy consumed in operating the directional circuitry and antenna in both the transmitter and receiver. John Mullen _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 11:39:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07521 for ; Wed, 6 Oct 2004 11:39:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFE34-0002OY-5V for manet-web-archive@ietf.org; Wed, 06 Oct 2004 11:49:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDqe-0004y1-Vj; Wed, 06 Oct 2004 11:37:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFDma-0003xW-5r for manet@megatron.ietf.org; Wed, 06 Oct 2004 11:32:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07023 for ; Wed, 6 Oct 2004 11:32:45 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFDw5-0001y2-8Z for manet@ietf.org; Wed, 06 Oct 2004 11:42:38 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id B6C96202A; Wed, 6 Oct 2004 09:32:44 -0600 (MDT) From: "John Mullen" To: Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Wed, 6 Oct 2004 09:32:46 -0600 Message-ID: <001f01c4abb9$bae6e4d0$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <1BECC1DBB19ACE41AD81FA2E9B53750C0224E9B4@khephren.clb.tcfr.thales> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Content-Transfer-Encoding: quoted-printable Hi Raphael, What you say is true, but just before the destination generates a RREP, it will increment its sequence number. This would cause S2 to forward the RREP back to S1, since the RREP would indicate S2's current routing table entry is invalid, due to it having an older destination sequence number. I was just thinking. What we really need is a complete state diagram for AODV. :-) John Mullen -----Original Message----- From: Raphael-a.MASSIN@fr.thalesgroup.com [mailto:Raphael-a.MASSIN@fr.thalesgroup.com]=20 Sent: Wednesday, October 06, 2004 12:40 AM To: jomullen@nmsu.edu Cc: manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies John, Thank you for your comments. AODV must behave as you describe when intermediate node are allowed to reply to RREQ concerning destination they have a route "fresh enough" to. >From section 6.6 on p18 : A node generates a RREP if either (i) it is itself the destination or, (ii) it has an active route to the destination, the destination sequence number in the node's existing route table entry for the destination is valid and greater than or equal to the destination sequence number of the RREQ, and the "destination only" ('D') flag is NOT set So if the "destination only" flag is set in the RREQ, an intermediate node will not generate a RREP in response to any RREQ. I think that if the sequence number of station S4 is not modified, the case illustrated by the example below is incorrectly handled in RFC 3561. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. This means that either : - "destination only" flag in RREQs must never be set to 1 or, - a RREP is always forwarded, even if it does not cause an update to the route to the destination (opposite to what is written in RFC 3561, section 6.7 page 21) Rapha=EBl -----Message d'origine----- De : John Mullen [mailto:jomullen@nmsu.edu] Envoy=E9 : mardi 5 octobre 2004 20:06 =C0 : Raphael-a.MASSIN@fr.thalesgroup.com Cc : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hi Raphael, >From Section 2 on p. 3, As long as the endpoints of a communication connection have valid routes to each other, AODV does not play any role. When a route to a new destination is needed, the node broadcasts a RREQ to find a route to the destination. A route can be determined when the RREQ reaches either the destination itself, or an intermediate node with a 'fresh enough' route to the destination. A 'fresh enough' route is a valid route entry for the destination whose associated sequence number is at least as great as that contained in the RREQ. >From the last line, if the route is fresh enough, S2 sends a RREP back to S1. If not, when the RREQ propagation continues to S4, the destination sequence number will be higher (otherwise the route is fresh enough). From p. 12, one of the cases in which a node increments its sequence number is: - Immediately before a destination node originates a RREP in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. So, if the route is not "fresh enough," the destination will increment its own sequence number. (Otherwise it won't see the RREQ). This means that by the time you get to Section 6.7, either the RREP is simply confirming the known route, in which case S2 need not reply to S1 because it already did so earlier, or it is indicating some sort of better route from S2 to S4, in which case S2 will forward the RREP to S1 to correct its earlier misinformation.=20 At least, that is how I understand it. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Monday, October 04, 2004 11:22 PM To: yann_eads@hotmail.com; manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Hi, The destination sequence number of station D is only updated when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the D is broken increments the destination sequence number of D. Later, this node sends AODV messages with updated sequence number for destination D. In the example below, the sequence number of S4 is never updated. It is the reason why S3 never propagates the RREP message corresponding to the RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the RREP. In my mind, the sequence number received by S2 is greater than the one which created its route to S4. And if this route is updated, it fowards the RREP to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP=20 >forwarding when route reply by intermediate nodes is not activated.=20 >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage ! http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 14:27:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20112 for ; Wed, 6 Oct 2004 14:27:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFGf7-0004YM-L4 for manet-web-archive@ietf.org; Wed, 06 Oct 2004 14:37:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFGTv-0000xk-L3; Wed, 06 Oct 2004 14:25:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFGNS-0007YY-3c for manet@megatron.ietf.org; Wed, 06 Oct 2004 14:19:02 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19060 for ; Wed, 6 Oct 2004 14:19:00 -0400 (EDT) Received: from aismtp1g.bellsouth.com ([139.76.165.196]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFGWy-0003pd-VC for manet@ietf.org; Wed, 06 Oct 2004 14:28:54 -0400 Received: from 01al10015010118.ad.bls.com ([90.152.52.46] [90.152.52.46]) by aismtp1g.bellsouth.com with ESMTP; Wed, 6 Oct 2004 14:18:26 -0400 thread-index: AcSr0N8tPdxLV1A0Qoy9sd6Dj05jpw== Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Received: from 01al10015010131.ad.bls.com ([90.152.5.15]) by 01al10015010118.ad.bls.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 6 Oct 2004 13:18:25 -0500 Received: e2k.bls.com 90.152.5.15 from 90.152.52.32 90.152.52.32 via HTTP with MS-WebStorage 6.0.6249 Received: 90.152.52.32 90.152.52.32 from via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Wed, 06 Oct 2004 14:18:26 -0400 Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? From: "Christian Kuhtz" To: "John Mullen" , "'Jim Thompson'" , "'David Young'" Message-Id: In-Reply-To: <001d01c4abb6$ea261b60$67f57b80@engr.ad.nmsu.edu> X-Entourage-Rocks: Got Mac? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 06 Oct 2004 18:18:25.0737 (UTC) FILETIME=[DF13A390:01C4ABD0] X-Spam-Score: 0.2 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: quoted-printable Cc: IETF manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: quoted-printable On 10/6/04 11:12 AM, "John Mullen" wrote: > If you want to receive on two or more channels that are simultaneously > active, you must have dedicated circuitry for each channel. = Otherwise, > the RF signals will mix and interfere with each other, causing data > collisions, rather than distinct data streams. Seems that's a fairly easy to solve problem. Anyone could cobble this together today, and there's no real reason why you couldn't do that in a more integrated fashion if there is market demand. Thanks, Christian ***** "The information transmitted is intended only for the person or entity = to which it is addressed and may contain confidential, proprietary, = and/or privileged material. Any review, retransmission, dissemination = or other use of, or taking of any action in reliance upon, this = information by persons or entities other than the intended recipient is = prohibited. If you received this in error, please contact the sender = and delete the material from all computers." 118 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 17:09:03 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14389 for ; Wed, 6 Oct 2004 17:09:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJBb-0001rK-QF for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:19:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFIfb-0007ZB-IW; Wed, 06 Oct 2004 16:45:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFHwN-0005AH-Tv for manet@megatron.ietf.org; Wed, 06 Oct 2004 15:59:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00618 for ; Wed, 6 Oct 2004 15:59:09 -0400 (EDT) Received: from mail.netgate.com ([192.207.126.2] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFI5w-0002ib-E1 for manet@ietf.org; Wed, 06 Oct 2004 16:09:04 -0400 Received: by netgate.com (Postfix, from userid 45) id B4F08F404E; Wed, 6 Oct 2004 12:59:07 -0700 (PDT) Received: from [192.168.1.2] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id EEC36F4020; Wed, 6 Oct 2004 12:59:01 -0700 (PDT) Message-ID: <41644E84.1030900@netgate.com> Date: Wed, 06 Oct 2004 09:59:00 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 0.8 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Kuhtz Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: John Mullen , IETF manet , "'David Young'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7bit Christian Kuhtz wrote: > > > On 10/6/04 11:12 AM, "John Mullen" wrote: > > >>If you want to receive on two or more channels that are simultaneously >>active, you must have dedicated circuitry for each channel. Otherwise, >>the RF signals will mix and interfere with each other, causing data >>collisions, rather than distinct data streams. > > > Seems that's a fairly easy to solve problem. Anyone could cobble this > together today, and there's no real reason why you couldn't do that in a > more integrated fashion if there is market demand. Obviously, you should file the patents now. You'll shortly be proven wrong, or become a very rich, and very famous man. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 17:09:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14508 for ; Wed, 6 Oct 2004 17:09:29 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJC0-0001sy-RW for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:19:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFIfg-0007ea-IA; Wed, 06 Oct 2004 16:46:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFHxE-0005dh-8o for manet@megatron.ietf.org; Wed, 06 Oct 2004 16:00:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00773 for ; Wed, 6 Oct 2004 16:00:01 -0400 (EDT) Received: from web61109.mail.yahoo.com ([216.155.196.111]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFI6a-0002jp-JB for manet@ietf.org; Wed, 06 Oct 2004 16:09:57 -0400 Message-ID: <20041006195920.53815.qmail@web61109.mail.yahoo.com> Received: from [66.208.44.5] by web61109.mail.yahoo.com via HTTP; Wed, 06 Oct 2004 12:59:20 PDT Date: Wed, 6 Oct 2004 12:59:20 -0700 (PDT) From: manet user Subject: RE: [manet] AODV : receiving and forwarding route replies To: John Mullen , Raphael-a.MASSIN@fr.thalesgroup.com In-Reply-To: <001f01c4abb9$bae6e4d0$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1172657542==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6 --===============1172657542== Content-Type: multipart/alternative; boundary="0-1321878175-1097092760=:52693" --0-1321878175-1097092760=:52693 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA00773 Content-Transfer-Encoding: quoted-printable Check this link regarding Dest Seq Num update while sending RREP. Check t= he previous and follow up messages as well. =20 http://www1.ietf.org/mail-archive/web/manet/current/msg02593.html =20 -MU John Mullen wrote: Hi Raphael, What you say is true, but just before the destination generates a RREP, it will increment its sequence number. This would cause S2 to forward the RREP back to S1, since the RREP would indicate S2's current routing table entry is invalid, due to it having an older destination sequence number. I was just thinking. What we really need is a complete state diagram for AODV. :-) John Mullen -----Original Message----- From: Raphael-a.MASSIN@fr.thalesgroup.com [mailto:Raphael-a.MASSIN@fr.thalesgroup.com]=20 Sent: Wednesday, October 06, 2004 12:40 AM To: jomullen@nmsu.edu Cc: manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies John, Thank you for your comments. AODV must behave as you describe when intermediate node are allowed to reply to RREQ concerning destination they have a route "fresh enough" to. >From section 6.6 on p18 : A node generates a RREP if either (i) it is itself the destination or, (ii) it has an active route to the destination, the destination sequence number in the node's existing route table entry for the destination is valid and greater than or equal to the destination sequence number of the RREQ, and the "destination only" ('D') flag is NOT set So if the "destination only" flag is set in the RREQ, an intermediate node will not generate a RREP in response to any RREQ. I think that if the sequence number of station S4 is not modified, the case illustrated by the example below is incorrectly handled in RFC 3561. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. This means that either : - "destination only" flag in RREQs must never be set to 1 or, - a RREP is always forwarded, even if it does not cause an update to the route to the destination (opposite to what is written in RFC 3561, section 6.7 page 21) Rapha=EBl -----Message d'origine----- De : John Mullen [mailto:jomullen@nmsu.edu] Envoy=E9 : mardi 5 octobre 2004 20:06 =C0 : Raphael-a.MASSIN@fr.thalesgroup.com Cc : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hi Raphael, >From Section 2 on p. 3, As long as the endpoints of a communication connection have valid routes to each other, AODV does not play any role. When a route to a new destination is needed, the node broadcasts a RREQ to find a route to the destination. A route can be determined when the RREQ reaches either the destination itself, or an intermediate node with a 'fresh enough' route to the destination. A 'fresh enough' route is a valid route entry for the destination whose associated sequence number is at least as great as that contained in the RREQ. >From the last line, if the route is fresh enough, S2 sends a RREP back to S1. If not, when the RREQ propagation continues to S4, the destination sequence number will be higher (otherwise the route is fresh enough). From p. 12, one of the cases in which a node increments its sequence number is: - Immediately before a destination node originates a RREP in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. So, if the route is not "fresh enough," the destination will increment its own sequence number. (Otherwise it won't see the RREQ). This means that by the time you get to Section 6.7, either the RREP is simply confirming the known route, in which case S2 need not reply to S1 because it already did so earlier, or it is indicating some sort of better route from S2 to S4, in which case S2 will forward the RREP to S1 to correct its earlier misinformation.=20 At least, that is how I understand it. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Monday, October 04, 2004 11:22 PM To: yann_eads@hotmail.com; manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Hi, The destination sequence number of station D is only updated when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the D is broken increments the destination sequence number of D. Later, this node sends AODV messages with updated sequence number for destination D. In the example below, the sequence number of S4 is never updated. It is the reason why S3 never propagates the RREP message corresponding to the RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the RREP. In my mind, the sequence number received by S2 is greater than the one which created its route to S4. And if this route is updated, it fowards the RREP to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP=20 >forwarding when route reply by intermediate nodes is not activated.=20 >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage ! http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ 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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 --0-1321878175-1097092760=:52693 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA00773 Content-Transfer-Encoding: quoted-printable
Check this link regarding Dest Seq Num update while sending RREP. Ch= eck the previous and follow up messages as well.
 
 
-MU

John Mullen <jomullen@nmsu.edu> wrote= :
Hi Raphael,

What you say is true, = but just before the destination generates a RREP,
it will increment it= s sequence number. This would cause S2 to forward
the RREP back to S1,= since the RREP would indicate S2's current routing
table entry is inv= alid, due to it having an older destination sequence
number.

I = was just thinking. What we really need is a complete state diagram
for= AODV.

:-)

John Mullen

-----Original Message-----From: Raphael-a.MASSIN@fr.thalesgroup.com
[mailto:Raphael-a.MASSIN@fr= .thalesgroup.com]
Seent: Wednesday, October 06, 2004 12:40 AM
To: = jomullen@nmsu.edu
Cc: manet@ietf.org
Subject: RE: [manet] AODV : re= ceiving and forwarding route replies


John,

Thank you fo= r your comments.
AODV must behave as you describe when intermediate no= de are allowed to
reply to RREQ concerning destination they have a route "fresh enough"
to.

>From sect= ion 6.6 on p18 :
A node generates a RREP if either
(i) it is itself= the destination or,
(ii) it has an active route to the destination, t= he destination sequence
number in the node's existing route table entr= y for the destination is
valid and greater than or equal to the destin= ation sequence number of
the RREQ, and the "destination only" ('D') fl= ag is NOT set

So if the "destination only" flag is set in the RREQ= , an intermediate
node will not generate a RREP in response to any RRE= Q. I think that if
the sequence number of station S4 is not modified, = the case illustrated
by the example below is incorrectly handled in RF= C 3561.

>Let's consider the following network :
>
>= S1 --- S2 --- S3 --- S4
>
>First, S2 establishes a route to S= 4.
>Then S1 wants to do the same thing. If intermeediate node reply= is not
>activated, the route research reaches S4, that sends a RREP back to S1.

>Nevertheless, in se= ction 6.7 of RFC 3561 a node forwards a RREP only if

>a forward= route (to the destination) has been updated (or created). As
>thi= s is not the case here, the RREP is not forwarded and the route to
&g= t;S4 is never established on S1.

This means that either :
- "de= stination only" flag in RREQs must never be set to 1 or,
- a RREP is a= lways forwarded, even if it does not cause an update to the
route to t= he destination (opposite to what is written in RFC 3561,
section 6.7 p= age 21)


Rapha=EBl

-----Message d'origine-----
De : J= ohn Mullen [mailto:jomullen@nmsu.edu]
Envoy=E9 : mardi 5 octobre 2004 = 20:06
=C0 : Raphaael-a.MASSIN@fr.thalesgroup.com
Cc : manet@ietf.or= g
Objet : RE: [manet] AODV : receiving and forwarding route replies

Hi Raphael,

>From Section 2 on p. 3,

As long as= the endpoints of a communication connection have valid
routes to each other, AODV does not play any role. When a route= to a
new destination is needed, the node broadcasts a RREQ to find a = route
to the destination. A route can be determined when the RREQ reac= hes
either the destination itself, or an intermediate node with a 'fre= sh
enough' route to the destination. A 'fresh enough' route is a valid=
route entry for the destination whose associated sequence number isat least as great as that contained in the RREQ.

>From the la= st line, if the route is fresh enough, S2 sends a RREP back
to S1. If = not, when the RREQ propagation continues to S4, the
destination sequen= ce number will be higher (otherwise the route is fresh
enough). From p= . 12, one of the cases in which a node increments its
sequence number = is:

- Immediately before a destination node originates a RREP inresponse to a RREQ, it MUST update its own sequence number to the
ma= ximum of its current sequence number and the destination
sequence number in the RREQ packet.

So, if the rou= te is not "fresh enough," the destination will increment
its own seque= nce number. (Otherwise it won't see the RREQ). This means
that by the = time you get to Section 6.7, either the RREP is simply
confirming the = known route, in which case S2 need not reply to S1
because it already = did so earlier, or it is indicating some sort of
better route from S2 = to S4, in which case S2 will forward the RREP to S1
to correct its ear= lier misinformation.

At least, that is how I understand it.
John Mullen

-----Original Message-----
From: manet-bounces@ie= tf.org [mailto:manet-bounces@ietf.org] On Behalf
Of Raphael-a.MASSIN@f= rr.thalesgroup.com
Sent: Monday, October 04, 2004 11:22 PM
To: yann= _eads@hotmail.com; manet@ietf.org
Subject: RE: [manet] AODV : receivin= g and forwarding route replies


Hi,

The destination sequ= ence number of station D is only updated when :
- the station D itself sends a RREQ
- a route to the D is broken= . In that case, the node whose link to the D
is broken increments the = destination sequence number of D. Later, this
node sends AODV messages= with updated sequence number for destination D.

In the example be= low, the sequence number of S4 is never updated. It is
the reason why = S3 never propagates the RREP message corresponding to the
RREQ origina= ted at S1.

Anyhow, it is the way I have understood RFC 3561. If I = am wrong, I would
like somebody to tell me what is not correct in my u= nderstanding.

Rapha=EBl


-----Message d'origine-----
= De : Yann -EADS- [mailto:yann_eads@hotmail.com]
Envoy=E9 : lundi 4 oct= obre 2004 18:02
=C0 : mmanet@ietf.org
Objet : RE: [manet] AODV : re= ceiving and forwarding route replies


Hello,

I guess tha= t the forward route is actually updated upon receiving the
RREP. In my= mind, the sequence number received by S2 is greater than the
one which

created its route to S4. And if this route = is updated, it fowards the
RREP to S1.

Am I wrong ?


= >From: Raphael-a.MASSIN@fr.thalesgroup.com
>To: manet@ietf.org>Subject: [manet] AODV : receiving and forwarding route replies
&= gt;Date: Mon, 4 Oct 2004 17:18:18 +0200
>
>Hi all,
>>As it is described in RFC 3561, AODV incorrectly handles RREP
&g= t;forwarding when route reply by intermediate nodes is not activated. >Let's consider the following network :
>
>S1 --- S2 --- = S3 --- S4
>
>First, S2 establishes a route to S4.
>Then= S1 wants to do the same thing. If intermeediate node reply is not
&g= t;activated, the route research reaches S4, that sends a RREP back to S1.=

>Nevertheless, in section 6.7 of RFC 3561 a node forwards a RR= EP only if

>a forward route (to the destination) has been updat= ed (or created). As
>this is not the case here, the RREP is not forwarded and the route to
>S4 is never est= ablished on S1.
>
>Any comment ?
>
> Rapha=EBl>
>
>_______________________________________________
&= gt;manet mailing list
>manet@ietf.org
>https://www1.ietf.org/= mailman/listinfo/manet

___________________________________________= ______________________
Hotmail : bient=F4t 250 Mo de stockage !
htt= p://www.imagine-msn.com/hotmail/fr-fr/


_______________________= ________________________
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

________________= __________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection arou= nd
http://mail.yahoo.com=20 --0-1321878175-1097092760=:52693-- --===============1172657542== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1172657542==-- From manet-bounces@ietf.org Wed Oct 6 17:15:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15484 for ; Wed, 6 Oct 2004 17:15:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJI3-0002J9-6R for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:25:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFIh4-0000X0-6O; Wed, 06 Oct 2004 16:47:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFI9F-0003hI-Li for manet@megatron.ietf.org; Wed, 06 Oct 2004 16:12:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02907 for ; Wed, 6 Oct 2004 16:12:27 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFIIn-00045D-Ex for manet@ietf.org; Wed, 06 Oct 2004 16:22:22 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 7F00C2025; Wed, 6 Oct 2004 14:12:22 -0600 (MDT) From: "John Mullen" To: "'Jim Thompson'" Subject: RE: [manet] Is it difficult to receive simultaneously over multiplechannels? Date: Wed, 6 Oct 2004 14:12:22 -0600 Message-ID: <000201c4abe0$ca5664a0$67f57b80@engr.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: <41644E84.1030900@netgate.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit Cc: "'IETF manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit -----Original Message----- From: Jim Thompson [mailto:jim@netgate.com] Sent: Wednesday, October 06, 2004 12:59 PM To: Christian Kuhtz Cc: John Mullen; 'David Young'; IETF manet Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? Christian Kuhtz wrote: > > > On 10/6/04 11:12 AM, "John Mullen" wrote: > > >>If you want to receive on two or more channels that are simultaneously >>active, you must have dedicated circuitry for each channel. >>Otherwise, the RF signals will mix and interfere with each other, >>causing data collisions, rather than distinct data streams. > > > Seems that's a fairly easy to solve problem. Anyone could cobble this > together today, and there's no real reason why you couldn't do that in > a more integrated fashion if there is market demand. Obviously, you should file the patents now. You'll shortly be proven wrong, or become a very rich, and very famous man. Well, filing patents is no guarantee. http://www.inventions.org/culture/female/lamarr.html :-) John Mullen _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 17:18:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15941 for ; Wed, 6 Oct 2004 17:18:11 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJKR-0002Y6-Oy for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:28:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFItn-0006mw-CI; Wed, 06 Oct 2004 17:00:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFIbv-0004z3-1G for manet@megatron.ietf.org; Wed, 06 Oct 2004 16:42:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09361 for ; Wed, 6 Oct 2004 16:42:03 -0400 (EDT) Received: from mail.netgate.com ([192.207.126.2] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFIlQ-0007cg-KY for manet@ietf.org; Wed, 06 Oct 2004 16:51:59 -0400 Received: by netgate.com (Postfix, from userid 45) id 457C1F404E; Wed, 6 Oct 2004 13:42:01 -0700 (PDT) Received: from [192.168.1.2] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 644E9F4020; Wed, 6 Oct 2004 13:41:51 -0700 (PDT) Message-ID: <4164588F.9010808@netgate.com> Date: Wed, 06 Oct 2004 10:41:51 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 0.8 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Mullen Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? References: <001d01c4abb6$ea261b60$67f57b80@engr.ad.nmsu.edu> In-Reply-To: <001d01c4abb6$ea261b60$67f57b80@engr.ad.nmsu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, "'David Young'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit > Actually, it is the other way around. High selectivity would reduce the > number of channels that can be simultaneously received. What I described, and the statement I made are accurate. > If you want to receive on two or more channels that are simultaneously > active, you must have dedicated circuitry for each channel. Otherwise, > the RF signals will mix and interfere with each other, causing data > collisions, rather than distinct data streams. I've already mentioned Engim. Note that GNUradio can receive two FM stations simultaneously. http://www.gnu.org/software/gnuradio/examples.html Extending this to 802.11 is left as an exercise for the reader. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 17:28:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17379 for ; Wed, 6 Oct 2004 17:28:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJUN-00038S-So for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:38:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFJ9k-0005Y1-Dz; Wed, 06 Oct 2004 17:17:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFIma-0002BC-5V for manet@megatron.ietf.org; Wed, 06 Oct 2004 16:53:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11171 for ; Wed, 6 Oct 2004 16:53:05 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFIw5-0000B8-Oc for manet@ietf.org; Wed, 06 Oct 2004 17:03:01 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 98DEB2003; Wed, 6 Oct 2004 14:53:01 -0600 (MDT) From: "John Mullen" To: "'manet user'" , Subject: RE: [manet] AODV : receiving and forwarding route replies Date: Wed, 6 Oct 2004 14:53:02 -0600 Message-ID: <000201c4abe6$787f4150$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <20041006195920.53815.qmail@web61109.mail.yahoo.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.1 (/) X-Scan-Signature: 4da339c42fe5be09fa120bb0fcc4a575 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1157133776==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: c3d1fcc6feccbcc611b6c309986f05f7 This is a multi-part message in MIME format. --===============1157133776== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C4ABB4.2DE4D150" This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C4ABB4.2DE4D150 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hmm, =20 Seems there *is* a problem. =20 :-) =20 We can't just say never set the destination only flag, because that is used to force a search through to the destination when the originator suspects that a "valid" sub route is actually invalid. I think a cleaner solution is to say "always forward the RREP back towards the originator if the destination only flag is set." This condition could be kept in the table entry, but a cleaner approach would be to add a flag to the RREP packet, perhaps using one of the reserved bits, or simply call such a RREP packet one of Type 5. =20 John Mullen -----Original Message----- From: manet user [mailto:manet_user@yahoo.com]=20 Sent: Wednesday, October 06, 2004 12:59 PM To: John Mullen; Raphael-a.MASSIN@fr.thalesgroup.com Cc: manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Check this link regarding Dest Seq Num update while sending RREP. Check the previous and follow up messages as well. =20 http://www1.ietf.org/mail-archive/web/manet/current/msg02593.html =20 -MU John Mullen wrote: Hi Raphael, What you say is true, but just before the destination generates a RREP, it will increment its sequence number. This would cause S2 to forward the RREP back to S1, since the RREP would indicate S2's current routing table entry is invalid, due to it having an older destination sequence number. I was just thinking. What we really need is a complete state diagram for AODV. :-) John Mullen -----Original Message----- From: Raphael-a.MASSIN@fr.thalesgroup.com [mailto:Raphael-a.MASSIN@fr.thalesgroup.com]=20 Sent: Wednesday, October 06, 2004 12:40 AM To: jomullen@nmsu.edu Cc: manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies John, Thank you for your comments. AODV must behave as you describe when intermediate node are allowed to reply to RREQ concerning destination they have a route "fresh enough" to. >From section 6.6 on p18 : A node generates a RREP if either (i) it is itself the destination or, (ii) it has an active route to the destination, the destination sequence number in the node's existing route table entry for the destination is valid and greater than or equal to the destination sequence number of the RREQ, and the "destination only" ('D') flag is NOT set So if the "destination only" flag is set in the RREQ, an intermediate node will not generate a RREP in response to any RREQ. I think that if the sequence number of station S4 is not modified, the case illustrated by the example below is incorrectly handled in RFC 3561. >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route rese! arch reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not the case here, the RREP is not forwarded and the route to=20 >S4 is never established on S1. This means that either : - "destination only" flag in RREQs must never be set to 1 or, - a RREP is always forwarded, even if it does not cause an update to the route to the destination (opposite to what is written in RFC 3561, section 6.7 page 21) Rapha=EBl -----Message d'origine----- De : John Mullen [mailto:jomullen@nmsu.edu] Envoy=E9 : mardi 5 octobre 2004 20:06 =C0 : Raphael-a.MASSIN@fr.thalesgroup.com Cc : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hi Raphael, >From Section 2 on p. 3, As long as the endpoints of a communication connection ha! ve valid routes to each other, AODV does not play any role. When a route to a new destination is needed, the node broadcasts a RREQ to find a route to the destination. A route can be determined when the RREQ reaches either the destination itself, or an intermediate node with a 'fresh enough' route to the destination. A 'fresh enough' route is a valid route entry for the destination whose associated sequence number is at least as great as that contained in the RREQ. >From the last line, if the route is fresh enough, S2 sends a RREP back to S1. If not, when the RREQ propagation continues to S4, the destination sequence number will be higher (otherwise the route is fresh enough). From p. 12, one of the cases in which a node increments its sequence number is: - Immediately before a destination node originates a RREP in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and! the destination sequence number in the RREQ packet. So, if the route is not "fresh enough," the destination will increment its own sequence number. (Otherwise it won't see the RREQ). This means that by the time you get to Section 6.7, either the RREP is simply confirming the known route, in which case S2 need not reply to S1 because it already did so earlier, or it is indicating some sort of better route from S2 to S4, in which case S2 will forward the RREP to S1 to correct its earlier misinformation.=20 At least, that is how I understand it. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Raphael-a.MASSIN@fr.thalesgroup.com Sent: Monday, October 04, 2004 11:22 PM To: yann_eads@hotmail.com; manet@ietf.org Subject: RE: [manet] AODV : receiving and forwarding route replies Hi, The destination sequence number of station D is only updated ! when : - the station D itself sends a RREQ - a route to the D is broken. In that case, the node whose link to the D is broken increments the destination sequence number of D. Later, this node sends AODV messages with updated sequence number for destination D. In the example below, the sequence number of S4 is never updated. It is the reason why S3 never propagates the RREP message corresponding to the RREQ originated at S1. Anyhow, it is the way I have understood RFC 3561. If I am wrong, I would like somebody to tell me what is not correct in my understanding. Rapha=EBl -----Message d'origine----- De : Yann -EADS- [mailto:yann_eads@hotmail.com] Envoy=E9 : lundi 4 octobre 2004 18:02 =C0 : manet@ietf.org Objet : RE: [manet] AODV : receiving and forwarding route replies Hello, I guess that the forward route is actually updated upon receiving the RREP. In my mind, the sequence number received by S2 is gr! eater than the one which created its route to S4. And if this route is updated, it fowards the RREP to S1. Am I wrong ? >From: Raphael-a.MASSIN@fr.thalesgroup.com >To: manet@ietf.org >Subject: [manet] AODV : receiving and forwarding route replies >Date: Mon, 4 Oct 2004 17:18:18 +0200 > >Hi all, > >As it is described in RFC 3561, AODV incorrectly handles RREP=20 >forwarding when route reply by intermediate nodes is not activated.=20 >Let's consider the following network : > >S1 --- S2 --- S3 --- S4 > >First, S2 establishes a route to S4. >Then S1 wants to do the same thing. If intermediate node reply is not=20 >activated, the route research reaches S4, that sends a RREP back to S1. >Nevertheless, in section 6.7 of RFC 3561 a node forwards a RREP only if >a forward route (to the destination) has been updated (or created). As=20 >this is not t! he case here, the RREP is not forwarded and the route to >S4 is never established on S1. > >Any comment ? > > Rapha=EBl > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Hotmail : bient=F4t 250 Mo de stockage ! http://www.imagine-msn.com/hotmail/fr-fr/ _______________________________________________ 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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 ------=_NextPart_000_0003_01C4ABB4.2DE4D150 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message

Hmm,
 
Seems=20 there *is* a problem.
 
:-)
 
We=20 can't just say never set the destination only flag, because that is used = to=20 force a search through to the destination when the originator suspects = that a=20 "valid" sub route is actually invalid.  I think a cleaner solution = is to=20 say "always forward the RREP back towards the originator if the = destination only=20 flag is set."  This condition could be kept in the table entry, but = a=20 cleaner approach would be to add a flag to the RREP packet, perhaps = using one of=20 the reserved bits, or simply call such a RREP packet one of Type=20 5.
 
John=20 Mullen
-----Original Message-----
From: = manet user=20 [mailto:manet_user@yahoo.com]
Sent: Wednesday, October 06, = 2004=20 12:59 PM
To: John Mullen;=20 Raphael-a.MASSIN@fr.thalesgroup.com
Cc:=20 manet@ietf.org
Subject: RE: [manet] AODV : receiving and = forwarding=20 route replies

Check this link regarding Dest Seq Num update while sending RREP. = Check=20 the previous and follow up messages as well.
 
http://www1.ietf.org/mail-archive/web/manet/current/msg02593.html
 
-MU

John Mullen <jomullen@nmsu.edu>=20 wrote:
Hi=20 Raphael,

What you say is true, but just before the = destination=20 generates a RREP,
it will increment its sequence number. This = would cause=20 S2 to forward
the RREP back to S1, since the RREP would indicate = S2's=20 current routing
table entry is invalid, due to it having an older = destination sequence
number.

I was just thinking. What we = really=20 need is a complete state diagram
for AODV.

:-)

John = Mullen

-----Original Message-----
From:=20 = Raphael-a.MASSIN@fr.thalesgroup.com
[mailto:Raphael-a.MASSIN@fr.thales= group.com]=20
Sent: Wednesday, October 06, 2004 12:40 AM
To:=20 jomullen@nmsu.edu
Cc: manet@ietf.org
Subject: RE: [manet] AODV = :=20 receiving and forwarding route replies


John,

Thank = you for=20 your comments.
AODV must behave as you describe when intermediate = node=20 are allowed to
reply to RREQ concerning destination they have a = route=20 "fresh enough"
to.

>From section 6.6 on p18 :
A node = generates a RREP if either
(i) it is itself the destination = or,
(ii)=20 it has an active route to the destination, the destination=20 sequence
number in the node's existing route table entry for the=20 destination is
valid and greater than or equal to the destination = sequence number of
the RREQ, and the "destination only" ('D') = flag is NOT=20 set

So if the "destination only" flag is set in the RREQ, an=20 intermediate
node will not generate a RREP in response to any = RREQ. I=20 think that if
the sequence number of station S4 is not modified, = the case=20 illustrated
by the example below is incorrectly handled in RFC=20 3561.

>Let's consider the following network = :
>
>S1=20 --- S2 --- S3 --- S4
>
>First, S2 establishes a route to = S4.
>Then S1 wants to do the same thing. If intermediate node = reply is=20 not
>activated, the route rese! arch reaches S4, that sends a = RREP=20 back to S1.

>Nevertheless, in section 6.7 of RFC 3561 a = node=20 forwards a RREP only if

>a forward route (to the = destination) has=20 been updated (or created). As
>this is not the case here, the = RREP is=20 not forwarded and the route to
>S4 is never established on=20 S1.

This means that either :
- "destination only" flag in = RREQs=20 must never be set to 1 or,
- a RREP is always forwarded, even if = it does=20 not cause an update to the
route to the destination (opposite to = what is=20 written in RFC 3561,
section 6.7 page=20 21)


Rapha=EBl

-----Message d'origine-----
De : = John=20 Mullen [mailto:jomullen@nmsu.edu]
Envoy=E9 : mardi 5 octobre 2004 = 20:06
=C0 : Raphael-a.MASSIN@fr.thalesgroup.com
Cc :=20 manet@ietf.org
Objet : RE: [manet] AODV : receiving and = forwarding route=20 replies


Hi Raphael,

>From Section 2 on p. = 3,

As=20 long as the endpoints of a communication connection ha! ve = valid
routes=20 to each other, AODV does not play any role. When a route to a
new = destination is needed, the node broadcasts a RREQ to find a = route
to the=20 destination. A route can be determined when the RREQ = reaches
either the=20 destination itself, or an intermediate node with a 'fresh
enough' = route=20 to the destination. A 'fresh enough' route is a valid
route entry = for the=20 destination whose associated sequence number is
at least as great = as that=20 contained in the RREQ.

>From the last line, if the route = is fresh=20 enough, S2 sends a RREP back
to S1. If not, when the RREQ = propagation=20 continues to S4, the
destination sequence number will be higher=20 (otherwise the route is fresh
enough). From p. 12, one of the = cases in=20 which a node increments its
sequence number is:

- = Immediately=20 before a destination node originates a RREP in
response to a = RREQ, it=20 MUST update its own sequence number to the
maximum of its current = sequence number and! the destination
sequence number in the RREQ=20 packet.

So, if the route is not "fresh enough," the = destination will=20 increment
its own sequence number. (Otherwise it won't see the = RREQ).=20 This means
that by the time you get to Section 6.7, either the = RREP is=20 simply
confirming the known route, in which case S2 need not = reply to=20 S1
because it already did so earlier, or it is indicating some = sort=20 of
better route from S2 to S4, in which case S2 will forward the = RREP to=20 S1
to correct its earlier misinformation.

At least, that = is how I=20 understand it.

John Mullen

-----Original = Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On = Behalf
Of=20 Raphael-a.MASSIN@fr.thalesgroup.com
Sent: Monday, October 04, = 2004 11:22=20 PM
To: yann_eads@hotmail.com; manet@ietf.org
Subject: RE: = [manet] AODV=20 : receiving and forwarding route replies


Hi,

The=20 destination sequence number of station D is only updated ! when = :
- the=20 station D itself sends a RREQ
- a route to the D is broken. In = that case,=20 the node whose link to the D
is broken increments the destination = sequence number of D. Later, this
node sends AODV messages with = updated=20 sequence number for destination D.

In the example below, the = sequence=20 number of S4 is never updated. It is
the reason why S3 never = propagates=20 the RREP message corresponding to the
RREQ originated at=20 S1.

Anyhow, it is the way I have understood RFC 3561. If I am = wrong,=20 I would
like somebody to tell me what is not correct in my=20 understanding.

Rapha=EBl


-----Message = d'origine-----
De :=20 Yann -EADS- [mailto:yann_eads@hotmail.com]
Envoy=E9 : lundi 4 = octobre 2004=20 18:02
=C0 : manet@ietf.org
Objet : RE: [manet] AODV : = receiving and=20 forwarding route replies


Hello,

I guess that the = forward=20 route is actually updated upon receiving the
RREP. In my mind, = the=20 sequence number received by S2 is gr! eater than the
one=20 which

created its route to S4. And if this route is updated, = it=20 fowards the
RREP to S1.

Am I wrong ?


>From:=20 Raphael-a.MASSIN@fr.thalesgroup.com
>To:=20 manet@ietf.org
>Subject: [manet] AODV : receiving and = forwarding route=20 replies
>Date: Mon, 4 Oct 2004 17:18:18 = +0200
>
>Hi=20 all,
>
>As it is described in RFC 3561, AODV incorrectly = handles=20 RREP
>forwarding when route reply by intermediate nodes is = not=20 activated.
>Let's consider the following network = :
>
>S1=20 --- S2 --- S3 --- S4
>
>First, S2 establishes a route to = S4.
>Then S1 wants to do the same thing. If intermediate node = reply is=20 not
>activated, the route research reaches S4, that sends a = RREP back=20 to S1.

>Nevertheless, in section 6.7 of RFC 3561 a node = forwards a=20 RREP only if

>a forward route (to the destination) has = been=20 updated (or created). As
>this is not t! he case here, the = RREP is=20 not forwarded and the route to
>S4 is never established on=20 S1.
>
>Any comment ?
>
>=20 = Rapha=EBl
>
>
>________________________________________= _______
>manet=20 mailing=20 = list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/= manet

____________________________________________________________= _____
Hotmail=20 : bient=F4t 250 Mo de stockage=20 = !
http://www.imagine-msn.com/hotmail/fr-fr/


_______________= ________________________________
manet=20 mailing=20 = list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet=20 mailing=20 = list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet

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

__________________________________________________
Do You=20 Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection = around=20
http://mail.yahoo.com

------=_NextPart_000_0003_01C4ABB4.2DE4D150-- --===============1157133776== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1157133776==-- From manet-bounces@ietf.org Wed Oct 6 17:36:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18293 for ; Wed, 6 Oct 2004 17:36:59 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJcd-0003wO-KH for manet-web-archive@ietf.org; Wed, 06 Oct 2004 17:46:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFJCZ-0007qf-Fy; Wed, 06 Oct 2004 17:19:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFJ2K-0002Yi-3Z for manet@megatron.ietf.org; Wed, 06 Oct 2004 17:09:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14471 for ; Wed, 6 Oct 2004 17:09:21 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJBs-0001s6-0a for manet@ietf.org; Wed, 06 Oct 2004 17:19:17 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 90B172007; Wed, 6 Oct 2004 15:09:19 -0600 (MDT) From: "John Mullen" To: "'Jim Thompson'" Subject: RE: [manet] Is it difficult to receive simultaneously over multiplechannels? Date: Wed, 6 Oct 2004 15:09:18 -0600 Message-ID: <000901c4abe8$be42d5b0$67f57b80@engr.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: <4164588F.9010808@netgate.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: 7bit Hi Jim, Well, not exactly. The code you refer to acts on the IF signal, which is extracted from the media by means of a RF front end. http://comsec.com/wiki?RfFrontEnd This would mean that for this code to work, the two radio channels would have to share a common RF frequency channel. This is a common technique in FM, allowing the transmission of stereo as a sum and a difference signal, but is essentially the result of combining the signals at the transmitter for this purpose. I assume that the signals being decoded in the ad hoc net would be from two different transmitters, in which case, such a technique would not work. There are sophisticated techniques that involve FFTs and such, but the radios that use them are not cheap at all. I was not able to find the detail in the link you supplied, but from its description, it is referring to two channels in a cable modem. Such channels are generally multiplexed and the problem of pulling out two or more channels from a multiplexed signal is completely different than that of receiving two different radio channels that originate from two different transmitters. John Mullen -----Original Message----- From: Jim Thompson [mailto:jim@netgate.com] Sent: Wednesday, October 06, 2004 1:42 PM To: John Mullen Cc: 'David Young'; manet@ietf.org Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? > Actually, it is the other way around. High selectivity would reduce > the number of channels that can be simultaneously received. What I described, and the statement I made are accurate. > If you want to receive on two or more channels that are simultaneously > active, you must have dedicated circuitry for each channel. > Otherwise, the RF signals will mix and interfere with each other, > causing data collisions, rather than distinct data streams. I've already mentioned Engim. Note that GNUradio can receive two FM stations simultaneously. http://www.gnu.org/software/gnuradio/examples.html Extending this to 802.11 is left as an exercise for the reader. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 19:50:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00772 for ; Wed, 6 Oct 2004 19:50:00 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLhO-0004aI-7N for manet-web-archive@ietf.org; Wed, 06 Oct 2004 19:59:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLT9-0005et-FC; Wed, 06 Oct 2004 19:45:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLON-0004ib-70 for manet@megatron.ietf.org; Wed, 06 Oct 2004 19:40:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29994 for ; Wed, 6 Oct 2004 19:40:15 -0400 (EDT) Received: from 209-254-158-42.ip.mcleodusa.net ([209.254.158.42] helo=che.ojctech.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLXx-000416-BU for manet@ietf.org; Wed, 06 Oct 2004 19:50:14 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id i96NdlKb005697; Wed, 6 Oct 2004 18:39:47 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id i96Ndk3h005695; Wed, 6 Oct 2004 18:39:46 -0500 Date: Wed, 6 Oct 2004 18:39:46 -0500 From: David Young To: joerg.habetha@philips.com Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? Message-ID: <20041006233946.GE654@che.ojctech.com> Mail-Followup-To: joerg.habetha@philips.com, manet@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a On Wed, Oct 06, 2004 at 11:26:02AM +0200, joerg.habetha@philips.com wrote: > Hi, > > if you do not double your oscillator or even the complete tranceiver you > can assume a channel switching time of about 1ms. > We have developed forwarding schemes that are based on frequency > switching. You use one frequency on the incoming hop and a different one > on the outgoing hop. The forwarder switches in-between the channels. Some > overhead is unavoidable due to the switching times. > Joerg, In your opinion, where lies the bottleneck in channel-switching speed? Are you working with the Philips SA2400, by chance? Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 6 21:04:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05932 for ; Wed, 6 Oct 2004 21:04:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFMrm-0000nu-QU for manet-web-archive@ietf.org; Wed, 06 Oct 2004 21:14:47 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFMgR-00041X-1B; Wed, 06 Oct 2004 21:03:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFMcr-0003O0-7O for manet@megatron.ietf.org; Wed, 06 Oct 2004 20:59:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05557 for ; Wed, 6 Oct 2004 20:59:19 -0400 (EDT) Received: from web21121.mail.yahoo.com ([216.136.227.168]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFMmR-0000SU-Ef for manet@ietf.org; Wed, 06 Oct 2004 21:09:16 -0400 Message-ID: <20041007005918.41861.qmail@web21121.mail.yahoo.com> Received: from [24.60.185.56] by web21121.mail.yahoo.com via HTTP; Wed, 06 Oct 2004 17:59:18 PDT Date: Wed, 6 Oct 2004 17:59:18 -0700 (PDT) From: Vinod To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] Which Simulator can do per-packet power control? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Hi All. I was hoping to do some simulation work on topology control in manet's. could anyone advise me what simulator is able to do per-packet power control? I had a look at ns-2 and it seems the power for nodes are set at the beginning and can't be changed later (correct me if i am wrong.would be very helpful if 'how' can also be explained). I haven't looked at glomosim or opnet. I would prefer NS2, but if i have to, i am willing to put the effort in for the other two. p.s: I was under the impression that lot of power control work that has been published was done on ns2.however, i see no contributed code or extensions for power control in ns2. Any pointers to implementations on ns2 are most welcome Thanks, Vinod __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 7 03:00:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15978 for ; Thu, 7 Oct 2004 03:00:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFSQ9-0005dG-ES for manet-web-archive@ietf.org; Thu, 07 Oct 2004 03:10:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFSE7-00032F-W1; Thu, 07 Oct 2004 02:58:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFS9f-0002IE-DX for manet@megatron.ietf.org; Thu, 07 Oct 2004 02:53:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15617 for ; Thu, 7 Oct 2004 02:53:33 -0400 (EDT) Received: from postfix.iai.uni-bonn.de ([131.220.8.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFSJJ-000503-8G for manet@ietf.org; Thu, 07 Oct 2004 03:03:33 -0400 X-IAI-Env-From: : [131.220.242.116] Received: from [131.220.242.116] (apu.informatik.uni-bonn.de [131.220.242.116]) by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 57E3D5C82A; Thu, 7 Oct 2004 08:53:02 +0200 (MEST) (envelope-from dewaal@cs.uni-bonn.de) (envelope-to VARIOUS) (2) (internal use: ta=0, tu=1, te=0, am=-, au=-) Message-ID: <4164E7CE.700@cs.uni-bonn.de> Date: Thu, 07 Oct 2004 08:53:02 +0200 From: Christian de Waal User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod , manet@ietf.org Subject: Re: [manet] Which Simulator can do per-packet power control? References: <20041007005918.41861.qmail@web21121.mail.yahoo.com> In-Reply-To: <20041007005918.41861.qmail@web21121.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: 7bit Hi Vinod, indeed it is possible to control the tx power of a mobile node in ns-2. You can get the WirelessPhy of a node at runtime with the following expression: (WirelessPhy*)(Node::get_node_by_address(here_.addr_))->ifhead().lh_first; This is what we use in our ns-2 implementation of the "Cooperative Nearest Neighbours Topology Control" (which is not "per packet", put "per node"). Unfortunately, the code is not yet in state to be publicly released, but we might do so soon. Best regards, Christian de Waal Vinod wrote: > Hi All. I was hoping to do some simulation work on > topology control in manet's. could anyone advise me > what simulator is able to do per-packet power control? > I had a look at ns-2 and it seems the power for nodes > are set at the beginning and can't be changed later > (correct me if i am wrong.would be very helpful if > 'how' can also be explained). I haven't looked at > glomosim or opnet. I would prefer NS2, but if i have > to, i am willing to put the effort in for the other > two. > p.s: I was under the impression that lot of power > control work that has been published was done on > ns2.however, i see no contributed code or extensions > for power control in ns2. Any pointers to > implementations on ns2 are most welcome > Thanks, > Vinod > > > > __________________________________ > Do you Yahoo!? > Take Yahoo! Mail with you! Get it on your mobile phone. > http://mobile.yahoo.com/maildemo > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- ____________________________________________________________________ Christian de Waal University of Bonn Phone: +49 228 73-4548 Institute of Computer Science IV Fax: +49 228 73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de 53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 7 10:29:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20294 for ; Thu, 7 Oct 2004 10:29:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFZQQ-0008Qs-Nf for manet-web-archive@ietf.org; Thu, 07 Oct 2004 10:39:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZ8w-0002Id-1m; Thu, 07 Oct 2004 10:21:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZ1q-0007zH-2G for manet@megatron.ietf.org; Thu, 07 Oct 2004 10:13:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18591 for ; Thu, 7 Oct 2004 10:13:55 -0400 (EDT) Received: from web8403.mail.in.yahoo.com ([202.43.219.151]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFZBG-0007Lv-6Y for manet@ietf.org; Thu, 07 Oct 2004 10:24:00 -0400 Message-ID: <20041007141038.73446.qmail@web8403.mail.in.yahoo.com> Received: from [202.141.29.35] by web8403.mail.in.yahoo.com via HTTP; Thu, 07 Oct 2004 15:10:38 BST Date: Thu, 7 Oct 2004 15:10:38 +0100 (BST) From: MUTHU KRISHNAN To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.2 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [manet] header intact X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1014913244==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d --===============1014913244== Content-Type: multipart/alternative; boundary="0-379837137-1097158238=:72040" --0-379837137-1097158238=:72040 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit hi i wish to subscribe my mail id in your group... thank u Yahoo! India Matrimony: Find your life partneronline. --0-379837137-1097158238=:72040 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
hi
 i wish to subscribe my mail id in your group...
thank u

Yahoo! India Matrimony: Find your life partner online. --0-379837137-1097158238=:72040-- --===============1014913244== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1014913244==-- From manet-bounces@ietf.org Thu Oct 7 10:35:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21480 for ; Thu, 7 Oct 2004 10:35:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFZWc-0000c1-Lx for manet-web-archive@ietf.org; Thu, 07 Oct 2004 10:46:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZ9r-0002qY-KW; Thu, 07 Oct 2004 10:22:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZ75-0001TZ-J4 for manet@megatron.ietf.org; Thu, 07 Oct 2004 10:19:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19200 for ; Thu, 7 Oct 2004 10:19:21 -0400 (EDT) Received: from web8408.mail.in.yahoo.com ([202.43.219.156]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFZGX-0007iN-Qu for manet@ietf.org; Thu, 07 Oct 2004 10:29:26 -0400 Message-ID: <20041007141548.97637.qmail@web8408.mail.in.yahoo.com> Received: from [202.141.29.35] by web8408.mail.in.yahoo.com via HTTP; Thu, 07 Oct 2004 15:15:48 BST Date: Thu, 7 Oct 2004 15:15:48 +0100 (BST) From: MUTHU KRISHNAN To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] reg-flooding control X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1979807599==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 --===============1979807599== Content-Type: multipart/alternative; boundary="0-902967547-1097158548=:97602" --0-902967547-1097158548=:97602 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit hi how to identify one hop nodes using AODV protocol in glomosim tool.. expecting any kind of suggesion bye Yahoo! India Matrimony: Find your life partneronline. --0-902967547-1097158548=:97602 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

hi
how to identify one hop nodes using AODV protocol
in glomosim tool..
expecting any kind of suggesion
bye

Yahoo! India Matrimony: Find your life partner online. --0-902967547-1097158548=:97602-- --===============1979807599== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1979807599==-- From manet-bounces@ietf.org Thu Oct 7 11:11:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25436 for ; Thu, 7 Oct 2004 11:11:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFa4x-0002xW-Ua for manet-web-archive@ietf.org; Thu, 07 Oct 2004 11:21:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZl2-0003qS-Bz; Thu, 07 Oct 2004 11:00:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZdP-00022m-Va for manet@megatron.ietf.org; Thu, 07 Oct 2004 10:52:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23762 for ; Thu, 7 Oct 2004 10:52:45 -0400 (EDT) Received: from smtp12.clb.oleane.net ([213.56.31.47]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFZn7-0001iW-CU for manet@ietf.org; Thu, 07 Oct 2004 11:02:51 -0400 Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be forged)) by smtp12.clb.oleane.net with ESMTP id i97EqBPv027958 for ; Thu, 7 Oct 2004 16:52:13 +0200 Message-Id: <200410071452.i97EqBPv027958@smtp12.clb.oleane.net> From: "Peter" To: Date: Thu, 7 Oct 2004 16:52:08 +0200 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcSsfTgU6VdOv1sQTzesZZ+4szdACQ== X-Spam-Score: 0.2 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Subject: [manet] WiMAX Summit 05: Call for proposals X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1200195683==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff This is a multi-part message in MIME format. --===============1200195683== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0106_01C4AC8D.FBEC4C70" This is a multi-part message in MIME format. ------=_NextPart_000_0106_01C4AC8D.FBEC4C70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit . What is the business model for WiMAX? . What do we learn from earlier deployments? . What about the future extensions of the standard? . How is addressed the interoperability challenge? These questions, among others, will be addressed during the WiMAX Summit to be held in Paris next 5-8 April, 2005. A call for papers has been launched online, effective until October 29. Get all details at: http://www.upperside.fr/wimax05/wimax2005intro.htm ------=_NextPart_000_0106_01C4AC8D.FBEC4C70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

• = What is the business model for WiMAX?
• = What do we learn from earlier deployments?
• = What about the future extensions of the standard?
• = How is addressed the interoperability challenge?

These questions, among others, will be addressed during the WiMAX Summit = to be held in Paris next 5-8 April, 2005.

A call for papers has = been launched online, effective until October = 29.

 

Get all details = at:

http://www.upperside.fr/wimax05/wimax2005intro.htm

 

------=_NextPart_000_0106_01C4AC8D.FBEC4C70-- --===============1200195683== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1200195683==-- From manet-bounces@ietf.org Thu Oct 7 11:37:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27416 for ; Thu, 7 Oct 2004 11:37:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFaUC-0004K3-FX for manet-web-archive@ietf.org; Thu, 07 Oct 2004 11:47:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFa1h-0007wv-TW; Thu, 07 Oct 2004 11:17:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFZt6-0005a9-2N for manet@megatron.ietf.org; Thu, 07 Oct 2004 11:09:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24985 for ; Thu, 7 Oct 2004 11:08:57 -0400 (EDT) From: joerg.habetha@philips.com Received: from gw-eur4.philips.com ([161.85.125.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFa2o-0002tj-OG for manet@ietf.org; Thu, 07 Oct 2004 11:19:03 -0400 Received: from smtpscan-eur5.philips.com (smtpscan-eur5.mail.philips.com [130.144.57.168]) by gw-eur4.philips.com (Postfix) with ESMTP id 5402B49A69; Thu, 7 Oct 2004 15:08:25 +0000 (UTC) Received: from smtpscan-eur5.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 617B35A8; Thu, 7 Oct 2004 15:08:24 +0000 (GMT) Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com [130.144.57.171]) by smtpscan-eur5.philips.com (Postfix) with ESMTP id B046B5A3; Thu, 7 Oct 2004 15:08:23 +0000 (GMT) Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) by smtprelay-eur2.philips.com (8.9.3p3/8.9.3-1.2.2m-20040401) with ESMTP id PAA17257; Thu, 7 Oct 2004 15:08:22 GMT To: David Young Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.9a January 7, 2002 Message-ID: Date: Thu, 7 Oct 2004 17:01:52 +0200 X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.0.2CF1HF706 | September 14, 2004) at 07/10/2004 17:07:12, Serialize complete at 07/10/2004 17:07:12 X-Spam-Score: 0.8 (/) X-Scan-Signature: 2086112c730e13d5955355df27e3074b Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0998449697==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d This is a multipart message in MIME format. --===============0998449697== Content-Type: multipart/alternative; boundary="=_alternative 0052AD01C1256F26_=" This is a multipart message in MIME format. --=_alternative 0052AD01C1256F26_= Content-Type: text/plain; charset="us-ascii" > Joerg, > > In your opinion, where lies the bottleneck in channel-switching speed? > > Are you working with the Philips SA2400, by chance? > > Dave David, I am with research not with our design team, also more on the protocol than the RF side. The bottleneck is definitely the RF-side (on baseband-side you could do the switching very fast). In my understanding the problem is the VCO (synchronization to the new frequency, etc.). Regards, Joerg David Young Sent by: manet-bounces@ietf.org 07.10.2004 01:39 To: Joerg Habetha/ACN/RESEARCH/PHILIPS@PHILIPS cc: manet@ietf.org Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? Classification: On Wed, Oct 06, 2004 at 11:26:02AM +0200, joerg.habetha@philips.com wrote: > Hi, > > if you do not double your oscillator or even the complete tranceiver you > can assume a channel switching time of about 1ms. > We have developed forwarding schemes that are based on frequency > switching. You use one frequency on the incoming hop and a different one > on the outgoing hop. The forwarder switches in-between the channels. Some > overhead is unavoidable due to the switching times. > --=_alternative 0052AD01C1256F26_= Content-Type: text/html; charset="us-ascii"
> Joerg,
>
> In your opinion, where lies the bottleneck in channel-switching speed?
>
> Are you working with the Philips SA2400, by chance?
>
> Dave
David,

I am with research not with our design team, also more on the protocol than the RF side.
The bottleneck is definitely the RF-side (on baseband-side you could do the switching very fast). In my understanding the problem is the VCO (synchronization to the new frequency, etc.).

Regards,
Joerg









David Young <dyoung@pobox.com>

Sent by:
manet-bounces@ietf.org

07.10.2004 01:39

       
        To:        Joerg Habetha/ACN/RESEARCH/PHILIPS@PHILIPS
        cc:        manet@ietf.org
        Subject:        Re: [manet] Is it difficult to receive simultaneously over         multiplechannels?

        Classification:        




On Wed, Oct 06, 2004 at 11:26:02AM +0200, joerg.habetha@philips.com wrote:
> Hi,
>
> if you do not double your oscillator or even the complete tranceiver you
> can assume a channel switching time of about 1ms.
> We have developed forwarding schemes that are based on frequency
> switching. You use one frequency on the incoming hop and a different one
> on the outgoing hop. The forwarder switches in-between the channels. Some
> overhead is unavoidable due to the switching times.
>


--=_alternative 0052AD01C1256F26_=-- --===============0998449697== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0998449697==-- From manet-bounces@ietf.org Thu Oct 7 12:07:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00226 for ; Thu, 7 Oct 2004 12:07:13 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFaxE-0006IK-1v for manet-web-archive@ietf.org; Thu, 07 Oct 2004 12:17:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFaOW-0004aA-B2; Thu, 07 Oct 2004 11:41:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFaM5-0003h1-Mn for manet@megatron.ietf.org; Thu, 07 Oct 2004 11:38:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27615 for ; Thu, 7 Oct 2004 11:38:54 -0400 (EDT) From: jasteven@rockwellcollins.com Received: from fw01.rockwellcollins.com ([205.175.225.1] ident=firewall-user) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFaVo-0004U7-MO for manet@ietf.org; Thu, 07 Oct 2004 11:49:01 -0400 Received: by fw01.rockwellcollins.com; id KAA17465; Thu, 7 Oct 2004 10:38:54 -0500 (CDT) Received: from nodnsquery(131.198.169.132) by fw01.rockwellcollins.com via smap (V5.5) id xma017350; Thu, 7 Oct 04 10:38:06 -0500 Received: from smtpgw02.rockwellcollins.com (localhost [127.0.0.1]) by vs02.rockwellcollins.com (8.11.7+Sun/8.11.7) with ESMTP id i97Fc7J26988 for ; Thu, 7 Oct 2004 10:38:07 -0500 (CDT) Received: from crnotes2.rockwellcollins.com (unverified) by smtpgw02.rockwellcollins.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 7 Oct 2004 10:38:05 -0500 Subject: Re: [manet] Is it difficult to receive simultaneously over multiple channels? To: manet@ietf.org X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: Date: Thu, 7 Oct 2004 10:38:01 -0500 X-MIMETrack: Serialize by Router on CollinsCRSMTP02/CedarRapids/RockwellCollins(Release 6.5.2|June 01, 2004) at 10/07/2004 10:38:05 AM MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" X-Spam-Score: 0.3 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Is it possible to receive simultaneously over multiple channels? - Obviously yes when you think about cellular base stations that are receiving multiple channels simultaneously. By-the-way, I believe that the first digital network that received simultaneously over multiple channels, where all nodes were mobile (as compared to cellular systems where the base stations are stationary), was an experimental system demonstrated at sea for the Navy in 1958 or 1959 using a variant of the Collins Radio Kineplex data communications system ( http://www.collinsradio.org/Collins_1959_Kineplex.pdf). I believe that this experimental system was also the first to use automatic power control to mitigate against near/far problems when receiving multiple channels simultaneously (http://www.stormingmedia.us/89/8987/A898791.html). Also interesting to note is that Kineplex modulation appears to also be the first multi-carrier modulation (i.e. OFDM modulation) and was used to improve performance against multipath ( http://www.engr.colostate.edu/ece/pages/Research/rawcom/paper63.pdf). Is it difficult to receive simultaneously over multiple channels? - Yes, but it is getting easier every year, especially with modern software defined radio (SDR) technology. Of course even through the hardware and computing costs are dropping, you still have to worry about physical and data link layer issues like near/far problems, transmit/receive coordination (depending upon half/full dux capabilities), etc. Jim Stevens _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 8 06:52:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13228 for ; Fri, 8 Oct 2004 06:52:55 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFsWl-0003iQ-Dq for manet-web-archive@ietf.org; Fri, 08 Oct 2004 07:03:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFsKY-00024u-Ly; Fri, 08 Oct 2004 06:50:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFsFa-0000wA-PY for manet@megatron.ietf.org; Fri, 08 Oct 2004 06:45:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12619 for ; Fri, 8 Oct 2004 06:45:25 -0400 (EDT) Received: from jpnmailout02.yamato.ibm.com ([203.141.80.82]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFsPU-0003Wa-15 for manet@ietf.org; Fri, 08 Oct 2004 06:55:41 -0400 Received: from e19f2n15.jp.ibm.com (d19relay01.sagamino.japan.ibm.com [203.141.80.90] (may be forged)) by jpnmailout02.yamato.ibm.com (8.12.11/8.12.11) with ESMTP id i98AiYTt025908; Fri, 8 Oct 2004 19:44:34 +0900 Received: from D19ML114.sagamino.japan.ibm.com (d19av04.sagamino.japan.ibm.com [9.189.5.112]) by e19f2n15.jp.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i98AiXQw167914; Fri, 8 Oct 2004 19:44:34 +0900 To: manet@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 From: Akihiko Mizutani Message-ID: Date: Fri, 8 Oct 2004 19:44:32 +0900 X-MIMETrack: Serialize by Router on D19ML114/19/M/IBM(Release 6.0.2CF2|July 23, 2003) at 2004/10/08 19:44:33, Serialize complete at 2004/10/08 19:44:33 X-Spam-Score: 0.0 (/) X-Scan-Signature: 872695ea777a517bf5717e5acc69f8be Cc: icmu2005-hq@ishilab.net Subject: [manet] IPSJ ICMU 2005 -- Call for Papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1642412748==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4c358d334afcd91b425d436ca5722f22 This is a multipart message in MIME format. --===============1642412748== Content-Type: multipart/alternative; boundary="=_alternative 003B021549256F27_=" This is a multipart message in MIME format. --=_alternative 003B021549256F27_= Content-Type: text/plain; charset="ISO-2022-JP" CALL FOR PAPERS Second International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2005) April 13 through 15, 2005 Osaka University Convention Center, Osaka, Japan http://www.ipsj.or.jp/sig/mbl/icmu2005/ IMPORTANT DATES Deadline for submissions: November 15, 2004 Notification of acceptance: January 15, 2005 Camera ready due: February 15, 2005 Sponsored by IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing) Will be also supported by IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems) IPSJ SIG-UBI (Ubiquitous Computing System) Financial support by The Telecommunications Advancement Foundation ------------------------------------------------------------------------------- Scope ~~~~~ Mobile computing aims at ubiquitous user access to computer application. To make it possible, networking technology which enables Internet access anytime and everywhere, i.e. ubiquitous networking is necessary. It is obvious that with the accelerating trends towards mobile networks, ad hoc networks, and wireless networks, mobile computing and ubiquitous networking will play an important role in future network. This conference is aimed at providing researchers and practitioners in this hot research area a forum for discussion and collaboration. Authors are invited to submit papers addressing, but not limited to, the following topics: * Applications and services for mobile computing * Network management for ubiquitous networking * Data management for mobile computing * Wireless and mobile communications * Performance evaluation for mobile computing and ubiquitous networking systems * Broadcast communication * Network architectures, protocols, or service models for ubiquitous networking * Security in mobile computing and ubiquitous networking * Nomadic computing * Mobile Internetworking * Ad hoc networks * Sensor networks * Location-based Service Submission Instructions ~~~~~~~~~~~~~~~~~~~~~~~ Papers are solicited as full papers of no more than 6 pages, each of which will be subject to a full review process. Submission should already follow the author guidelines as specified in the web site below. An electronic, PDF-based submission of papers is mandatory. Please check the web site of the conference http://www.ishilab.net/icmu2005/ http://www.ipsj.or.jp/sig/mbl/icmu2005/ for further submission instructions. After the conference, a selected number of papers will be published as special issues in IPSJ journal. Committees ~~~~~~~~~~ General Chair Yasuo Hirata (KDDI R&D Laboratories, Japan) Executive Committee General Co-Chairs: Tadanori Mizuno (Shizuoka University, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Technical Program Committee Chair: Takashi Watanabe (Shizuoka University, Japan) Publication Chair Hidetoshi Yokota (KDDI R&D Laboratories, Japan) Publicity Chair Akihiko Mizutani (IBM Japan, Japan) Local Arrangement Masahiko Tsukamoto (Kobe University, Japan) Treasurer Hirozumi Yamaguchi (Osaka University, Japan) Technical Program Committee Mohammed Atiquzzaman (University of Oklahoma, USA) Biplab Sikdar (Rensselaer Polytechnic Institute, USA) Tatsuya Suda (University of California at Irvine$B!$(BUSA) Winston Seah (Institute for Infocomm Research, Singapore) Masahiko Tsukamoto (Kobe University, Japan) Hirozumi Yamaguchi (Osaka University, Japan) Akihiko Mizutani (IBM Japan, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Ken Ohta (NTT DoCoMo, Japan) Nobuo Kawaguchi (Nagoya University, Japan) Nobutsugu Fujino (Fujitsu Laboratories, Japan) Fumiyuki Iizuka (Fujitsu Laboratories, Japan) Susumu Ishihara (Shizuoka University, Japan) Masahiro Ishiyama (Toshiba Corporation, Japan) Tomoko Itao (NTT, Japan) Tetsuo Ideguchi (Aichi Prefectural University, Japan) Akino Inoue (Matsushita Electric Industrial, Japan) Masugi Inoue (National Institute of Information and Communications Technology, Japan) Minoru Okada (Nara Institute of Science and Technology, Japan) Kouji Okamura (Kyushu University, Japan) Akiyoshi Ogawa (Vodafone, Japan) Ryouji Ono (Mitsubishi Electric, Japan) Yuko Onoe (NTT DoCoMo, Japan) Shuichi Karino (NEC, Japan) Gen Kitagata (Tohoku University, Japan) Keizo Saisho (Kagawa University, Japan) Ichiro Satoh (National Institute of Informatics, Japan) Hiroshi Shigeno (Keio University, Japan) Akio Shinohara (NTT, Japan) Shinta Sugimoto (Nippon Ericsson, Japan) Keisuke Suwa (Musashi Institute of Technology, Japan) Kazunori Takashio (Keio University, Japan) Kastumi Takahashi (NTT, Japan) Takamichi Tateoka (University of Electro-Communications, Japan) Junya Nakata (Japan Advanced Institute of Science and Technology, Japan $B!K(B Yasuto Nakanishi (Tokyo University of Agriculture and Technology, Japan) Masahiro Nishi (Hiroshima City University, Japan) Mitsuji Matshumoto(Waseda University, Japan) Masateru Minami (Shibaura Institute of Technology, Japan) Masahiko Mizutani (IBM Japan, Japan) Mori Eigo (Nokia Japan, Japan) Hiroyuki Morikawa (University of Tokyo, Japan) Masashi Yano (Hitachi Ltd., Japan) Hirofumi Yamaki (Kyoto University, Japan) Nagatsugu Yamanouchi (Toho University, Japan) Miki Yamamoto (Osaka University, Japan) Takashi Yoshino (Wakayama University, Japan) Masaki Bandai (Shizuoka University, Japan) --=_alternative 003B021549256F27_= Content-Type: text/html; charset="ISO-2022-JP"
                           CALL FOR PAPERS

                Second International Conference on
       Mobile Computing and Ubiquitous Networking (ICMU 2005)

                    April 13 through 15, 2005
          Osaka University Convention Center, Osaka, Japan
             http://www.ipsj.or.jp/sig/mbl/icmu2005/

                         IMPORTANT DATES

           Deadline for submissions: November 15, 2004
            Notification of acceptance: January 15, 2005
            Camera ready due: February 15, 2005

Sponsored by

 IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest
               Group of Mobile Computing and Ubiquitous Networking)
IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing)

Will be also supported by

 IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems)
IPSJ SIG-UBI (Ubiquitous Computing System)
Financial support by

 The Telecommunications Advancement Foundation
<Please forgive us if you receive this information from multiple sources>
-------------------------------------------------------------------------------

Scope
~~~~~
Mobile computing aims at ubiquitous user access to computer application.
To make it possible, networking technology
which enables Internet access anytime and everywhere,
i.e. ubiquitous networking is necessary. It is obvious that with the
accelerating trends towards mobile networks, ad hoc networks,
and wireless networks, mobile computing and ubiquitous
networking will play an important role in future network.
This conference is aimed at providing researchers and practitioners
in this hot research area a forum for discussion and collaboration.
Authors are invited to submit papers addressing, but not
limited to, the following topics:

* Applications and services for mobile computing
* Network management for ubiquitous networking
* Data management for mobile computing
* Wireless and mobile communications
* Performance evaluation for mobile computing and
 ubiquitous networking systems
* Broadcast communication
* Network architectures, protocols, or service models
 for ubiquitous networking
* Security in mobile computing and ubiquitous networking
* Nomadic computing
* Mobile Internetworking
* Ad hoc networks
* Sensor networks
* Location-based Service


Submission Instructions
~~~~~~~~~~~~~~~~~~~~~~~
Papers are solicited as full papers of no more than 6 pages,
each of which will be subject to a full review process.
Submission should already follow the author guidelines as
specified in the web site below.
An electronic, PDF-based submission of papers is mandatory.

Please check the web site of the conference

http://www.ishilab.net/icmu2005/
http://www.ipsj.or.jp/sig/mbl/icmu2005/

for further submission instructions.

After the conference, a selected number of papers will
be published as special issues in IPSJ journal.


Committees
~~~~~~~~~~
General Chair
Yasuo Hirata (KDDI R&D Laboratories, Japan)

Executive Committee
General Co-Chairs:
Tadanori Mizuno (Shizuoka University, Japan)
Osamu Takahashi (Future University-Hakodate, Japan)

Technical Program Committee Chair:
Takashi Watanabe (Shizuoka University, Japan)

Publication Chair
Hidetoshi Yokota (KDDI R&D Laboratories, Japan)

Publicity Chair
Akihiko Mizutani (IBM Japan, Japan)

Local Arrangement
Masahiko Tsukamoto (Kobe University, Japan)

Treasurer
Hirozumi Yamaguchi (Osaka University, Japan)

Technical Program Committee
Mohammed Atiquzzaman (University of Oklahoma, USA)
Biplab Sikdar (Rensselaer Polytechnic Institute, USA)
Tatsuya Suda (University of California at Irvine$B!$(BUSA)
Winston Seah (Institute for Infocomm Research, Singapore)
Masahiko Tsukamoto (Kobe University, Japan)
Hirozumi Yamaguchi (Osaka University, Japan)
Akihiko Mizutani (IBM Japan, Japan)
Osamu Takahashi (Future University-Hakodate, Japan)
Ken Ohta (NTT DoCoMo, Japan)
Nobuo Kawaguchi (Nagoya University, Japan)
Nobutsugu Fujino (Fujitsu Laboratories, Japan)
Fumiyuki Iizuka (Fujitsu Laboratories, Japan)
Susumu Ishihara (Shizuoka University, Japan)
Masahiro Ishiyama (Toshiba Corporation, Japan)
Tomoko Itao (NTT, Japan)
Tetsuo Ideguchi (Aichi Prefectural University, Japan)
Akino Inoue (Matsushita Electric Industrial, Japan)
Masugi Inoue (National Institute of Information and Communications
  Technology, Japan)
Minoru Okada (Nara Institute of Science and Technology, Japan)
Kouji Okamura (Kyushu University, Japan)
Akiyoshi Ogawa (Vodafone, Japan)
Ryouji Ono (Mitsubishi Electric, Japan)
Yuko Onoe (NTT DoCoMo, Japan)
Shuichi Karino (NEC, Japan)
Gen Kitagata (Tohoku University, Japan)
Keizo Saisho (Kagawa University, Japan)
Ichiro Satoh (National Institute of Informatics, Japan)
Hiroshi Shigeno (Keio University, Japan)
Akio Shinohara (NTT, Japan)
Shinta Sugimoto (Nippon Ericsson, Japan)
Keisuke Suwa (Musashi Institute of Technology, Japan)
Kazunori Takashio (Keio University, Japan)
Kastumi Takahashi (NTT, Japan)
Takamichi Tateoka (University of Electro-Communications, Japan)
Junya Nakata  (Japan Advanced Institute of Science and Technology, Japan$B!K(B
Yasuto Nakanishi (Tokyo University of Agriculture and Technology,  Japan)
Masahiro Nishi (Hiroshima City University, Japan)
Mitsuji Matshumoto(Waseda University, Japan)
Masateru Minami (Shibaura Institute of Technology, Japan)
Masahiko Mizutani (IBM Japan, Japan)
Mori Eigo (Nokia Japan, Japan)
Hiroyuki Morikawa (University of Tokyo, Japan)
Masashi Yano (Hitachi Ltd., Japan)
Hirofumi Yamaki (Kyoto University, Japan)
Nagatsugu Yamanouchi (Toho University, Japan)
Miki Yamamoto (Osaka University, Japan)
Takashi Yoshino (Wakayama University, Japan)
Masaki Bandai (Shizuoka University, Japan)
 --=_alternative 003B021549256F27_=-- --===============1642412748== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1642412748==-- From manet-bounces@ietf.org Fri Oct 8 14:09:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17116 for ; Fri, 8 Oct 2004 14:09:11 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzKy-0004k7-PB for manet-web-archive@ietf.org; Fri, 08 Oct 2004 14:19:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFz3C-0004Nw-Mi; Fri, 08 Oct 2004 14:01:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFywd-0002o9-2Y for manet@megatron.ietf.org; Fri, 08 Oct 2004 13:54:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15734 for ; Fri, 8 Oct 2004 13:54:19 -0400 (EDT) Received: from aismtp3g.bellsouth.com ([139.76.165.193]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFz6c-0004Np-6C for manet@ietf.org; Fri, 08 Oct 2004 14:04:38 -0400 Received: from 01al10015010118.ad.bls.com ([90.152.52.46] [90.152.52.46]) by aismtp3g.bellsouth.com with ESMTP; Fri, 8 Oct 2004 13:47:52 -0400 thread-index: AcStXu8/BjVmU58JQ3aXnfjqxTO9/w== Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Received: from 01al10015010131.ad.bls.com ([90.152.5.15]) by 01al10015010118.ad.bls.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 8 Oct 2004 12:47:51 -0500 Received: e2k.bls.com 90.152.5.15 from 90.152.5.141 90.152.5.141 via HTTP with MS-WebStorage 6.0.6249 Received: 90.152.5.141 90.152.5.141 from via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Fri, 08 Oct 2004 13:47:49 -0400 Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? From: "Christian Kuhtz" To: "Jim Thompson" Message-Id: In-Reply-To: <41644E84.1030900@netgate.com> X-Entourage-Rocks: Got Mac? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 08 Oct 2004 17:47:51.0116 (UTC) FILETIME=[EE6230C0:01C4AD5E] X-Spam-Score: 0.2 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: quoted-printable Cc: IETF manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: quoted-printable Why? There's nothing preventing you from assembling a system, with = several 802.11b or 802.11a cards, for example, and using them simultaneously (as long as you use channels which don't interfere). I think it all depends on the specifics of what is attempted. But thanks for the flame anyway. Cheers, Christian On 10/6/04 3:59 PM, "Jim Thompson" wrote: > Christian Kuhtz wrote: >>=20 >>=20 >> On 10/6/04 11:12 AM, "John Mullen" wrote: >>=20 >>=20 >>> If you want to receive on two or more channels that are = simultaneously >>> active, you must have dedicated circuitry for each channel. = Otherwise, >>> the RF signals will mix and interfere with each other, causing data >>> collisions, rather than distinct data streams. >>=20 >>=20 >> Seems that's a fairly easy to solve problem. Anyone could cobble = this >> together today, and there's no real reason why you couldn't do that = in a >> more integrated fashion if there is market demand. >=20 > Obviously, you should file the patents now. You'll shortly be proven > wrong, or become a very rich, and very famous man. ***** "The information transmitted is intended only for the person or entity = to which it is addressed and may contain confidential, proprietary, = and/or privileged material. Any review, retransmission, dissemination = or other use of, or taking of any action in reliance upon, this = information by persons or entities other than the intended recipient is = prohibited. If you received this in error, please contact the sender = and delete the material from all computers." 118 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 8 14:20:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18046 for ; Fri, 8 Oct 2004 14:20:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzWF-00051v-Ey for manet-web-archive@ietf.org; Fri, 08 Oct 2004 14:31:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFzGj-0001BM-F3; Fri, 08 Oct 2004 14:15:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFz4e-0004kw-9H for manet@megatron.ietf.org; Fri, 08 Oct 2004 14:02:36 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16472 for ; Fri, 8 Oct 2004 14:02:34 -0400 (EDT) Received: from mail.netgate.com ([192.207.126.2] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzEZ-0004Zp-Ch for manet@ietf.org; Fri, 08 Oct 2004 14:12:53 -0400 Received: by netgate.com (Postfix, from userid 45) id F3451F405E; Fri, 8 Oct 2004 11:02:28 -0700 (PDT) Received: from [192.168.1.2] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id A3339F4016; Fri, 8 Oct 2004 11:02:24 -0700 (PDT) Message-ID: <4166D62F.7080806@netgate.com> Date: Fri, 08 Oct 2004 08:02:23 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 0.8 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Kuhtz Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Score: 0.2 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: 7bit Cc: IETF manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: 7bit Christian Kuhtz wrote: > Why? There's nothing preventing you from assembling a system, with several > 802.11b or 802.11a cards, for example, and using them simultaneously (as > long as you use channels which don't interfere). > > I think it all depends on the specifics of what is attempted. OK, just for the sake of discussion. Lets put two 802.11b or 802.11g cards in the system, fit them both with the antenna(s) of your choosing, and locate those antennas 1m apart. Please let me know which two channels you pick. Be sure to also specify the transmit power of the cards, your intended modulation rate, etc. Jim > But thanks for the flame anyway. > > Cheers, > Christian > > On 10/6/04 3:59 PM, "Jim Thompson" wrote: > > >>Christian Kuhtz wrote: >> >>> >>>On 10/6/04 11:12 AM, "John Mullen" wrote: >>> >>> >>> >>>>If you want to receive on two or more channels that are simultaneously >>>>active, you must have dedicated circuitry for each channel. Otherwise, >>>>the RF signals will mix and interfere with each other, causing data >>>>collisions, rather than distinct data streams. >>> >>> >>>Seems that's a fairly easy to solve problem. Anyone could cobble this >>>together today, and there's no real reason why you couldn't do that in a >>>more integrated fashion if there is market demand. >> >>Obviously, you should file the patents now. You'll shortly be proven >>wrong, or become a very rich, and very famous man. > > > > ***** > "The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers." 118 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 8 14:34:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19414 for ; Fri, 8 Oct 2004 14:34:05 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzj5-0005PU-7y for manet-web-archive@ietf.org; Fri, 08 Oct 2004 14:44:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFzTf-00048b-BH; Fri, 08 Oct 2004 14:28:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFzHZ-0001aQ-Oq for manet@megatron.ietf.org; Fri, 08 Oct 2004 14:15:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17812 for ; Fri, 8 Oct 2004 14:15:58 -0400 (EDT) Received: from aismtp2g.bellsouth.com ([139.76.165.197]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzRY-0004vM-GF for manet@ietf.org; Fri, 08 Oct 2004 14:26:17 -0400 Received: from 01al10015010113.ad.bls.com ([90.152.52.35] [90.152.52.35]) by aismtp2g.bellsouth.com with ESMTP; Fri, 8 Oct 2004 14:15:27 -0400 Thread-Index: AcStYsmsjNKhhKl+Td+zJoZESrUkqg== Received: from 01al10015010131.ad.bls.com ([90.152.5.15]) by 01al10015010113.ad.bls.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 8 Oct 2004 13:15:27 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 content-class: urn:content-classes:message Importance: normal Priority: normal Received: e2k.bls.com 90.152.5.15 from 90.152.5.141 90.152.5.141 via HTTP with MS-WebStorage 6.0.6249 Received: 90.152.5.141 90.152.5.141 from via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Fri, 08 Oct 2004 14:15:25 -0400 Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? From: "Christian Kuhtz" To: "Jim Thompson" Message-Id: In-Reply-To: <4166D62F.7080806@netgate.com> X-Entourage-Rocks: Got Mac? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 08 Oct 2004 18:15:27.0049 (UTC) FILETIME=[C9658390:01C4AD62] X-Spam-Score: 0.2 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Content-Transfer-Encoding: quoted-printable Cc: IETF manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Content-Transfer-Encoding: quoted-printable Jim, Assuming it's 802.11b and you're in the U.S., why couldn't you have = three separate WLANs on channels 1, 6, and 11? Thanks, Christian On 10/8/04 2:02 PM, "Jim Thompson" wrote: > Christian Kuhtz wrote: >> Why? There's nothing preventing you from assembling a system, with = several >> 802.11b or 802.11a cards, for example, and using them simultaneously = (as >> long as you use channels which don't interfere). >>=20 >> I think it all depends on the specifics of what is attempted. >=20 > OK, just for the sake of discussion. Lets put two 802.11b or 802.11g > cards in the system, fit them both with the antenna(s) of your = choosing, > and locate those antennas 1m apart. >=20 > Please let me know which two channels you pick. Be sure to also = specify > the transmit power of the cards, your intended modulation rate, etc. >=20 > Jim >=20 >> But thanks for the flame anyway. >>=20 >> Cheers, >> Christian >>=20 >> On 10/6/04 3:59 PM, "Jim Thompson" wrote: >>=20 >>=20 >>> Christian Kuhtz wrote: >>>=20 >>>>=20 >>>> On 10/6/04 11:12 AM, "John Mullen" wrote: >>>>=20 >>>>=20 >>>>=20 >>>>> If you want to receive on two or more channels that are = simultaneously >>>>> active, you must have dedicated circuitry for each channel. = Otherwise, >>>>> the RF signals will mix and interfere with each other, causing = data >>>>> collisions, rather than distinct data streams. >>>>=20 >>>>=20 >>>> Seems that's a fairly easy to solve problem. Anyone could cobble = this >>>> together today, and there's no real reason why you couldn't do that = in a >>>> more integrated fashion if there is market demand. >>>=20 >>> Obviously, you should file the patents now. You'll shortly be = proven >>> wrong, or become a very rich, and very famous man. >>=20 >>=20 >>=20 >> ***** >> "The information transmitted is intended only for the person or = entity to >> which it is addressed and may contain confidential, proprietary, = and/or >> privileged material. Any review, retransmission, dissemination or = other use >> of, or taking of any action in reliance upon, this information by = persons or >> entities other than the intended recipient is prohibited. If you = received >> this in error, please contact the sender and delete the material from = all >> computers." 118 >=20 ***** The information transmitted is intended only for the person or entity to = which it is addressed and may contain confidential, proprietary, and/or = privileged material. Any review, retransmission, dissemination or other = use of, or taking of any action in reliance upon, this information by = persons or entities other than the intended recipient is prohibited. If = you received this in error, please contact the sender and delete the = material from all computers. 113 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 8 14:54:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22594 for ; Fri, 8 Oct 2004 14:54:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG033-00061W-18 for manet-web-archive@ietf.org; Fri, 08 Oct 2004 15:05:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFzjC-00008J-LZ; Fri, 08 Oct 2004 14:44:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFzcC-0006wS-5c for manet@megatron.ietf.org; Fri, 08 Oct 2004 14:37:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19809 for ; Fri, 8 Oct 2004 14:37:16 -0400 (EDT) Received: from mail.netgate.com ([192.207.126.2] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFzmB-0005Uy-PW for manet@ietf.org; Fri, 08 Oct 2004 14:47:36 -0400 Received: by netgate.com (Postfix, from userid 45) id C2969F405E; Fri, 8 Oct 2004 11:37:16 -0700 (PDT) Received: from [192.168.1.2] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 9C676F4016; Fri, 8 Oct 2004 11:37:12 -0700 (PDT) Message-ID: <4166DE57.1040802@netgate.com> Date: Fri, 08 Oct 2004 08:37:11 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 0.8 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Kuhtz Subject: Re: [manet] Is it difficult to receive simultaneously over multiplechannels? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Score: 0.2 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: 7bit Cc: IETF manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Content-Transfer-Encoding: 7bit First, I wasn't flaming, though I admit it was a "trick question". Its true that the transmit masks of the "non-overlapping channels" (1, 6, 11) don't overlap. But none of the radios on the market have enough selectivity to eliminate in-band signals from an adjacent (25Mhz away) or alternate (50MHz away) channel. Minimum IEEE specs for a 11b receiver is 35dB of adjacent (25MHz away) channel rejection. IEEE doesn't publish specs for alternate channel rejection, but I can tell you that the best designs (in terms of ACR) are the "old" super-het receivers. Intersil (now Connextant)'s Prism2/2.5 is good for about 41dB of ACR. Alternate channel rejection is perhaps 20dB more with this chipset. That means that if you're operating (your Prism 2/2.5 chipset radio) on channel 11, a signal on channel 1 will be 60dB down from where it would be if your radio was on channel 1. Path loss in the first meter @ 2.4GHz is 41dB. Lets say you've got a garden-variety radio that puts up 32mW (15dBm) of tx power, and ignore antenna gain for now (so 0 dBi antennas on both radios). 15dBm - 41dB - 60dB = -86dBm This is the in-channel 'noise power' of the alternate channel radio. Notice that it is at least 15dB above the thermal noise floor. Translated: you've lowered your SINR. Thus, even if you pick "1 and 11", you're going to end up with significant in-channel power from any operate on the alternate channel by a close-by transmitter. Now, if you add any antenna gain to the equation, then, unless you manage to find really special antennas, (or use channel filters, etc) then the gain of both antennas affects the above in a negative way. The situation is (much) worse with 11g. Due to their (quite common, but non universal) direct conversion archectures, and some interesting properties of OFDM, most 802.11g receivers can't muster even the 35dB of ACR that the IEEE specifies when operating in the 802.11g modes. It varies by modulation rate, but the minimum ACR for 802.11g at 6Mbps is 16dB (alternate is 16dB more, for 32dB). This goes down to -1dB (yes, -1dB) ACR @ 54Mbps (with alternate channel rejection at 54Mbps down to 15dB.) If you try the obvious experiment, be sure to make sure that you've got the same "range" from both cards operating as from one card operating. 1) establish range for first card with no second card operations 2) enable 2nd card 3) re-check range of 1st card while 2nd card is under full operation (passing a lot of traffic) You'll find it appears to work if the clients are at close range. 11a isn't immune either. Jim > Jim, > > Assuming it's 802.11b and you're in the U.S., why couldn't you have three > separate WLANs on channels 1, 6, and 11? > > Thanks, > Christian > > > On 10/8/04 2:02 PM, "Jim Thompson" wrote: > > >>Christian Kuhtz wrote: >> >>>Why? There's nothing preventing you from assembling a system, with several >>>802.11b or 802.11a cards, for example, and using them simultaneously (as >>>long as you use channels which don't interfere). >>> >>>I think it all depends on the specifics of what is attempted. >> >>OK, just for the sake of discussion. Lets put two 802.11b or 802.11g >>cards in the system, fit them both with the antenna(s) of your choosing, >>and locate those antennas 1m apart. >> >>Please let me know which two channels you pick. Be sure to also specify >>the transmit power of the cards, your intended modulation rate, etc. >> >>Jim >> >> >>>But thanks for the flame anyway. >>> >>>Cheers, >>>Christian >>> >>>On 10/6/04 3:59 PM, "Jim Thompson" wrote: >>> >>> >>> >>>>Christian Kuhtz wrote: >>>> >>>> >>>>>On 10/6/04 11:12 AM, "John Mullen" wrote: >>>>> >>>>> >>>>> >>>>> >>>>>>If you want to receive on two or more channels that are simultaneously >>>>>>active, you must have dedicated circuitry for each channel. Otherwise, >>>>>>the RF signals will mix and interfere with each other, causing data >>>>>>collisions, rather than distinct data streams. >>>>> >>>>> >>>>>Seems that's a fairly easy to solve problem. Anyone could cobble this >>>>>together today, and there's no real reason why you couldn't do that in a >>>>>more integrated fashion if there is market demand. >>>> >>>>Obviously, you should file the patents now. You'll shortly be proven >>>>wrong, or become a very rich, and very famous man. >>> >>> >>> >>>***** >>>"The information transmitted is intended only for the person or entity to >>>which it is addressed and may contain confidential, proprietary, and/or >>>privileged material. Any review, retransmission, dissemination or other use >>>of, or taking of any action in reliance upon, this information by persons or >>>entities other than the intended recipient is prohibited. If you received >>>this in error, please contact the sender and delete the material from all >>>computers." 118 >> > > > ***** > The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. 113 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Oct 9 01:56:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02831 for ; Sat, 9 Oct 2004 01:56:38 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGANj-0006fr-AH for manet-web-archive@ietf.org; Sat, 09 Oct 2004 02:07:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGABX-0007pA-9t; Sat, 09 Oct 2004 01:54:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGA8r-0007Lq-Mt for manet@megatron.ietf.org; Sat, 09 Oct 2004 01:51:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02621 for ; Sat, 9 Oct 2004 01:51:40 -0400 (EDT) Received: from web20925.mail.yahoo.com ([216.136.224.142]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CGAIu-0006bE-90 for manet@ietf.org; Sat, 09 Oct 2004 02:02:05 -0400 Message-ID: <20041009055136.32380.qmail@web20925.mail.yahoo.com> Received: from [203.208.193.230] by web20925.mail.yahoo.com via HTTP; Fri, 08 Oct 2004 22:51:36 PDT Date: Fri, 8 Oct 2004 22:51:36 -0700 (PDT) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [manet] Sensor Network X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1066067959==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 --===============1066067959== Content-Type: multipart/alternative; boundary="0-857640556-1097301096=:32108" --0-857640556-1097301096=:32108 Content-Type: text/plain; charset=us-ascii Hi, I want to make some adaptions to 802.11 to meet the requirements of a Sensor Network. Our network is a single hop network and is used for automatic tracking of workers and equipment in underground mines. This sensor network would require a communication network to relay the answers to the central system. Let us consider a simpler situation. Suppose we would like to Establish wireless data and voice connectivity in a hostel like environment quickly. A simple way is to set up a backbone on the main corridor, and then, set up towers ( 5 - 6 feet high antennas that are almost in vision range of the wings). A similar design ought to work in mines. I request Members and Scientists to give me some references and Suggestions. Sincerely, Praveen. --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-857640556-1097301096=:32108 Content-Type: text/html; charset=us-ascii
Hi,
  I want to make some adaptions to 802.11 to meet the requirements of a Sensor Network. Our network is a single hop network and is used for automatic tracking of workers and equipment in underground mines. This sensor network would require a communication network to relay the answers to the central system.
 
Let us consider a simpler situation. Suppose we would like to Establish wireless data and voice connectivity in a hostel like environment quickly. A simple way is to set up a backbone on the main corridor, and then, set up towers ( 5 - 6 feet high antennas that are almost in vision range of the wings). A similar design ought to work in mines.
 
I request Members and Scientists to give me some references and Suggestions.
 
Sincerely,
Praveen.

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-857640556-1097301096=:32108-- --===============1066067959== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1066067959==-- From manet-bounces@ietf.org Sun Oct 10 07:21:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02912 for ; Sun, 10 Oct 2004 07:21:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGbvo-0005WQ-6J for manet-web-archive@ietf.org; Sun, 10 Oct 2004 07:32:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGbiA-0001n0-55; Sun, 10 Oct 2004 07:17:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGbgA-0001OT-Aw for manet@megatron.ietf.org; Sun, 10 Oct 2004 07:15:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02730 for ; Sun, 10 Oct 2004 07:15:50 -0400 (EDT) Received: from [203.199.83.38] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CGbqI-0005S2-Ql for manet@ietf.org; Sun, 10 Oct 2004 07:26:34 -0400 Received: (qmail 5443 invoked by uid 510); 10 Oct 2004 11:15:22 -0000 Date: 10 Oct 2004 11:15:22 -0000 Message-ID: <20041010111522.5441.qmail@webmail28.rediffmail.com> Received: from unknown (203.94.195.239) by rediffmail.com via HTTP; 10 oct 2004 11:15:22 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 2.1 (++) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [manet] plz help me X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1656568703==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 This is a multipart mime message --===============1656568703== Content-type: multipart/alternative; boundary="Next_1097406922---0-203.199.83.38-5435" This is a multipart mime message --Next_1097406922---0-203.199.83.38-5435 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0Ahaiii
=0A
=0Aseveral times iasked for help but no one in this g= roup to help me in my project.can any one plz plz tell me how to use glomos= im for ad hoc network simulation.i know about glomosim but dont know in whi= ch folder i need to make my code so that i can run it using  config fi= le.
=0A
=0Aplz some one help me.i m not getting enough help manuals f= or it.can anyone send me some links from where i can get help documents to = use glomosim
=0Aanjali
=0A
=0A
=0A=0A

=0A

=0A=0A --Next_1097406922---0-203.199.83.38-5435 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable haiii=0A=0Aseveral times iasked for help but no one in this group to help m= e in my project.can any one plz plz tell me how to use glomosim for ad hoc = network simulation.i know about glomosim but dont know in which folder i ne= ed to make my code so that i can run it using config file.=0A=0Aplz some o= ne help me.i m not getting enough help manuals for it.can anyone send me so= me links from where i can get help documents to use glomosim=0Aanjali=0A=0A= =0A --Next_1097406922---0-203.199.83.38-5435-- --===============1656568703== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1656568703==-- From manet-bounces@ietf.org Sun Oct 10 21:45:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01521 for ; Sun, 10 Oct 2004 21:45:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGpPz-0003b6-9T for manet-web-archive@ietf.org; Sun, 10 Oct 2004 21:56:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGpDZ-00004w-Tr; Sun, 10 Oct 2004 21:43:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGp3E-0007lC-Jg for manet@megatron.ietf.org; Sun, 10 Oct 2004 21:32:36 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00802 for ; Sun, 10 Oct 2004 21:32:34 -0400 (EDT) Received: from bay4-f4.bay4.hotmail.com ([65.54.171.4] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGpDc-0003Ot-UX for manet@ietf.org; Sun, 10 Oct 2004 21:43:24 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 10 Oct 2004 18:32:01 -0700 Received: from 202.141.24.2 by by4fd.bay4.hotmail.msn.com with HTTP; Mon, 11 Oct 2004 01:31:10 GMT X-Originating-IP: [202.141.24.2] X-Originating-Email: [sriram1raghavan@msn.com] X-Sender: sriram1raghavan@msn.com From: "Sriram Raghavan" To: manet@ietf.org Date: Mon, 11 Oct 2004 07:01:10 +0530 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 11 Oct 2004 01:32:01.0538 (UTC) FILETIME=[1B5AD620:01C4AF32] X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id VAA00802 Subject: [manet] RE: manet Digest, Vol 6, Issue 13 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable Hi, Its fairly simple...All the layers are defined are distinct programs. Sav= e a=20 copy of the existing as ".old" (say) and modify the layers you require af= ter=20 renaming. You just have to tune it to your Networks characteristics (Powe= r=20 levels, Transmission range, Number of hops, Number of Neighbors, etc...) = and=20 modify the configuration file accordingly (link the programs according to= =20 the names under which you have saved them) and run it. Then you are=20 done...... Anything is possible..........Impossible just takes longer............. sriram _________________________________________________________________ Messenger=A0 - =A0Wer in Echtzeit kommunizieren will, l=E4dt den MSN Mess= enger.=20 Cool, kostenlos und mit 3D Emoticons: http://messenger.msn.de _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 04:26:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13120 for ; Mon, 11 Oct 2004 04:26:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGvg7-0002BF-FQ for manet-web-archive@ietf.org; Mon, 11 Oct 2004 04:37:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGvTC-0001Ku-A5; Mon, 11 Oct 2004 04:23:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGvQC-0000vb-H6 for manet@megatron.ietf.org; Mon, 11 Oct 2004 04:20:44 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12695 for ; Mon, 11 Oct 2004 04:20:42 -0400 (EDT) Received: from web13204.mail.yahoo.com ([216.136.174.189]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CGvah-000253-7Y for manet@ietf.org; Mon, 11 Oct 2004 04:31:35 -0400 Message-ID: <20041011082040.55626.qmail@web13204.mail.yahoo.com> Received: from [67.64.26.100] by web13204.mail.yahoo.com via HTTP; Mon, 11 Oct 2004 01:20:40 PDT Date: Mon, 11 Oct 2004 01:20:40 -0700 (PDT) From: sumanth sarma Subject: RE: [manet] Help choose manet simulation tools To: John Mullen In-Reply-To: <001901c4a4ad$3835e490$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.1 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Hi, I need some information about the protocols in sensor networks, which aids in broadcasting for flooding in wireless sensor networks. Any kind help is appreciated. thanks, Sumanth _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 05:10:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15799 for ; Mon, 11 Oct 2004 05:10:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGwMT-00032f-Ir for manet-web-archive@ietf.org; Mon, 11 Oct 2004 05:20:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGw9X-0001e3-Rw; Mon, 11 Oct 2004 05:07:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGw2Z-0000E0-5p for manet@megatron.ietf.org; Mon, 11 Oct 2004 05:00:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15239 for ; Mon, 11 Oct 2004 05:00:20 -0400 (EDT) Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGwD4-0002qZ-2J for manet@ietf.org; Mon, 11 Oct 2004 05:11:14 -0400 Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6] helo=spamhost.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10) id 1CGw2V-0000vi-00 for ; Mon, 11 Oct 2004 11:00:19 +0200 Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3) id 1CGw2V-0005Gs-00 for ; Mon, 11 Oct 2004 11:00:19 +0200 Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by spamhost.ira.uka.de with esmtp (Exim 3.30 #3) id 1CGw29-0005FY-00 for ; Mon, 11 Oct 2004 10:59:57 +0200 Received: from i72tribble.tm.uni-karlsruhe.de ([141.3.71.8]) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 ) for id 1CGw29-0005yP-00; Mon, 11 Oct 2004 10:59:57 +0200 From: Kilian Weniger Organization: University of Karlsruhe To: manet@ietf.org Date: Mon, 11 Oct 2004 10:59:56 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200410111059.56677.weniger@tm.uka.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit Subject: [manet] Announcement: Implementation of PACMAN: Passive Autoconfiguration for MANETs X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 7bit Hi all, we would like to announce the first public release of a "Passive Autoconfiguration for MANETs (PACMAN)"-implementation for Linux. PACMAN is is an efficient and robust distributed solution for assigning and maintaining unique IP addresses in a MANET (see "K. Weniger: PACMAN: Passive Autoconfiguration for Mobile Ad hoc Networks", to appear in IEEE JSAC, March 2005). To the best of our knowledge, this is the first publicly available implementation of an address autoconfiguration protocol for MANETs. The implementation was demonstrated at the ACM Mobicom 2004. PACMAN heavily uses cross-layer information from ongoing routing protocol traffic: The maintenance of an address allocation table as well as the Duplicate Address Detection (DAD) are performed in a passive manner and therefore generate no additional communication overhead. The Passive DAD (PDAD) component is able to detect address conflicts whenever they occur (e.g. after network mergers) based on anomalies in the routing protocol traffic. Different routing protocols are supported by PACMAN. However, a modification of the message format or the implementation of the routing protocol is not necessary. Thus, existing routing protocol implementation as, e.g., the UniK OLSR implementation, can be used. support for OLSR and FSR is implemented. Due to a modular architecture, new protocols can easily be added. The source code as well as related publications, links, a GUI and some tools for tests and demonstrations are available for download at http://pacman-autoconf.sourceforge.net http://sourceforge.net/projects/pacman-autoconf/ Both the implementation as well as the concepts were developed within the project IPonAir by members of the Institute of Telematics, University of Karlsruhe, Germany. (http://www.iponair.de), (http://www.tm.uka.de/itm-zitterbart.html) Regards, Kilian Weniger -- Dr.-Ing. Kilian Weniger Institute of Telematics, Universitaet Karlsruhe (TH) Zirkel 2, 76128 Karlsruhe, Germany Phone: +49 721 608 6415, Fax: +49 721 388097 Email: weniger@tm.uka.de, HP: http://www.tm.uka.de/~weniger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 05:36:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17762 for ; Mon, 11 Oct 2004 05:36:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGwli-0003V5-8G for manet-web-archive@ietf.org; Mon, 11 Oct 2004 05:47:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGwZ9-00061G-0v; Mon, 11 Oct 2004 05:34:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGwXq-0005oJ-BK for manet@megatron.ietf.org; Mon, 11 Oct 2004 05:32:42 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17498 for ; Mon, 11 Oct 2004 05:32:40 -0400 (EDT) Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.24] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGwiL-0003Rf-Vj for manet@ietf.org; Mon, 11 Oct 2004 05:43:34 -0400 Received: From neo ([129.94.173.78] == sitcrc.cse.unsw.EDU.AU) By note With Smtp ; Mon, 11 Oct 2004 19:32:36 +1000 From: Justin Lipman To: manet@ietf.org Date: Mon, 11 Oct 2004 19:32:34 +1000 Organization: CRC-SIT Subject: Re: [manet] Optimised flooding (was: Help choose manet simulation tools) User-Agent: KMail/1.7 References: <20041011082040.55626.qmail@web13204.mail.yahoo.com> In-Reply-To: <20041011082040.55626.qmail@web13204.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410111932.34395.justin@titr.uow.edu.au> X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Cc: sumanth sarma X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: justin@titr.uow.edu.au List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Hi, On Monday 11 October 2004 18:20, sumanth sarma wrote: > Hi, > I need some information about the protocols in > sensor networks, which aids in broadcasting for > flooding in wireless sensor networks. Any kind help is > appreciated. > thanks, > Sumanth You may look at my webpage http://www.cse.unsw.edu.au/~justinl or follow up with some of the following authors: Ivan Stojmenovic Julien Cartigny David Simplot-Ryl Jie Wu The above have written some significant papers related to optimised flooding in ad hoc networks and sensor networks. Much of the ad hoc network literature is equally relevant to sensor networks. You may also use google and search for "optimised flooding" "optimized flooding" "optimised broadcasting" ... etc... etc... Kind regards, Justin -- Smart Internet Technology Cooperative Research Centre University of New South Wales, Sydney, Australia http://www.cse.unsw.edu.au/~justinl _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 11:37:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15542 for ; Mon, 11 Oct 2004 11:37:38 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH2Pb-0001i6-KK for manet-web-archive@ietf.org; Mon, 11 Oct 2004 11:48:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH29a-0003yB-Ab; Mon, 11 Oct 2004 11:32:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH297-0003kA-2w for manet@megatron.ietf.org; Mon, 11 Oct 2004 11:31:33 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14886 for ; Mon, 11 Oct 2004 11:31:30 -0400 (EDT) Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH2Jf-0001aZ-GH for manet@ietf.org; Mon, 11 Oct 2004 11:42:28 -0400 Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6] helo=spamhost.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10) id 1CH294-0003Fz-00; Mon, 11 Oct 2004 17:31:30 +0200 Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3) id 1CH291-00059r-00; Mon, 11 Oct 2004 17:31:27 +0200 Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by spamhost.ira.uka.de with esmtp (Exim 3.30 #3) id 1CH253-0004Ed-00; Mon, 11 Oct 2004 17:27:21 +0200 Received: from i72tribble.tm.uni-karlsruhe.de ([141.3.71.8]) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 ) id 1CH252-0001xw-00; Mon, 11 Oct 2004 17:27:20 +0200 From: Kilian Weniger Organization: University of Karlsruhe Subject: Re: [manet] Announcement: Implementation of PACMAN: =?utf-8?q?Passive=09Autoconfiguration_for?= MANETs Date: Mon, 11 Oct 2004 17:27:19 +0200 User-Agent: KMail/1.6.2 To: Christophe Jelger MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200410111727.19382.weniger@tm.uka.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit Hello Christophe, yes, n won't be a leader. Instead, n would be an isolated node and thus would use the "Isolated Node"-Flag to join a nearby subnet. A node recognizes that it is isolated, when it does not receive any RA messages from leaders and is not a leader itself (see paper). However, we do not follow this approach anymore and developed PACMAN instead, since we found out how significant the improvements in efficiency and robustness are that can be achieved by using information from on-going routing protocol traffic. Regards, Kilian Am Montag, 11. Oktober 2004 15:29 schrieben Sie: > Hello, > > I have a question regarding your "old" paper published in 2002 (IPv6 > Autoconfiguration in Large Scale Mobile Ad-Hoc Networks). The question > is related to the leader election algorithm. If I remember, a node > elects itself as a leader if it is the node that has the highest degree > in a radius of size rs around itself. > > I attached an eps figure that shows a problematic case ... If say E(n) > is the set of nodes within radius rs of node n. On the figure there is a > node k and a node l (L). Say node l is the leader of E(k) and E(l)--> > i.e. l is the node with highest degree in E(k) and E(l). Say now that k > is the node with highest degree in E(n). That means n won't be a leader > > : it will think k is the leader in E(n). The problem is that k does not > > decide to be a leader because l is the leader in E(k). If a similar > situation occurs for all nodes "k" in E(n) there won't be a leader in E(n). > > Is this a problem ? Did I miss something ? > > Regards, > Christophe > > Kilian Weniger wrote: > >Hi all, > > > >we would like to announce the first public release of a "Passive > >Autoconfiguration for MANETs (PACMAN)"-implementation for Linux. > >PACMAN is is an efficient and robust distributed solution for > >assigning and maintaining unique IP addresses in a MANET > >(see "K. Weniger: PACMAN: Passive Autoconfiguration for Mobile Ad hoc > >Networks", to appear in IEEE JSAC, March 2005). > >To the best of our knowledge, this is the first publicly available > >implementation of an address autoconfiguration protocol for MANETs. > >The implementation was demonstrated at the ACM Mobicom 2004. > > > >PACMAN heavily uses cross-layer information from ongoing routing protocol > >traffic: The maintenance of an address allocation table as well as the > >Duplicate Address Detection (DAD) are performed in a passive manner > >and therefore generate no additional communication overhead. > >The Passive DAD (PDAD) component is able to detect address conflicts > >whenever they occur (e.g. after network mergers) based on anomalies in the > >routing protocol traffic. Different routing protocols are supported by > > PACMAN. However, a modification of the message format or the > > implementation of the routing protocol is not necessary. Thus, existing > > routing protocol implementation as, e.g., the UniK OLSR implementation, > > can be used. support for OLSR and FSR is implemented. Due to a modular > > architecture, new protocols can easily be added. > > > >The source code as well as related publications, links, a GUI and some > > tools for tests and demonstrations are available for download at > > > > http://pacman-autoconf.sourceforge.net > > http://sourceforge.net/projects/pacman-autoconf/ > > > >Both the implementation as well as the concepts were developed within the > >project IPonAir by members of the Institute of Telematics, University of > >Karlsruhe, Germany. > >(http://www.iponair.de), (http://www.tm.uka.de/itm-zitterbart.html) > > > > > >Regards, > > > >Kilian Weniger -- Dr.-Ing. Kilian Weniger Institute of Telematics, Universitaet Karlsruhe (TH) Zirkel 2, 76128 Karlsruhe, Germany Phone: +49 721 608 6415, Fax: +49 721 388097 Email: weniger@tm.uka.de, HP: http://www.tm.uka.de/~weniger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 17:49:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02133 for ; Mon, 11 Oct 2004 17:49:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH8Dk-00063H-Fv for manet-web-archive@ietf.org; Mon, 11 Oct 2004 18:00:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH7vq-0000C8-Fg; Mon, 11 Oct 2004 17:42:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH7ok-0005OE-Sm for manet@megatron.ietf.org; Mon, 11 Oct 2004 17:34:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01183 for ; Mon, 11 Oct 2004 17:34:51 -0400 (EDT) Received: from taurus.cs.albany.edu ([169.226.2.109] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH7zM-0005kG-4l for manet@ietf.org; Mon, 11 Oct 2004 17:45:52 -0400 Received: from broomstick.cs.albany.edu (ravi@broomstick.cs.albany.edu [169.226.2.89]) by taurus.cs.albany.edu (8.12.8p1-20030918/8.12.8) with ESMTP id i9BLYbuX024291 for ; Mon, 11 Oct 2004 17:34:37 -0400 (EDT) Received: (from ravi@localhost) by broomstick.cs.albany.edu (8.12.8p1-20030918/8.12.8/Submit) id i9BLYZiw011179 for manet@ietf.org; Mon, 11 Oct 2004 17:34:35 -0400 (EDT) Date: Mon, 11 Oct 2004 17:34:35 -0400 (EDT) From: "S.S.Ravi" Message-Id: <200410112134.i9BLYZiw011179@broomstick.cs.albany.edu> To: manet@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Subject: [manet] Call for Papers -- WiMob 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES Call for Papers -- WiMob'2005 International Conference on Wireless and Mobile Computing, Networking and Communications Conference dates: August 22-24, 2005 Location: Hotel Delta Centre-Ville Montreal, Canada Website: http://congresbcu.com/wimob2005/ Important Dates: Submissions due: December 21, 2004 Notification of acceptance: February 21, 2005 Tutorial and special session proposals due: March 21, 2005 Final manuscripts due: April 21, 2005 Registration and full payment due: April 30, 2005 Topics of Interest: WiMob'2005 addresses three main areas: Wireless Communications, Mobile Networking, Ubiquitous Computing and Applications. This conference aims to stimulate interactions between participants through them by exchanging new ideas and practical experience in these areas. The conference offers opportunities for in-depth exploration of the most recent research and results in these fields. The conference will be comprised of the following three symposia: Symposium 1: Wireless Communications Symposium 2: Mobile Networking Symposium 3: Ubiquitous Computing, Services and Applications Please see the conference website for the list of topics for each of the above symposia as well as for information regarding Tutorials, Special Sessions and Industrial Exhibits. Proceedings: To be published by Springer-Verlag, as part of the Lecture Notes in Computer Science (LNCS) series. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 11 18:35:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06248 for ; Mon, 11 Oct 2004 18:35:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH8wT-0006pF-IV for manet-web-archive@ietf.org; Mon, 11 Oct 2004 18:46:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH8eH-0000aq-My; Mon, 11 Oct 2004 18:28:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CH8TU-0000oF-7h for manet@megatron.ietf.org; Mon, 11 Oct 2004 18:17:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04921 for ; Mon, 11 Oct 2004 18:16:57 -0400 (EDT) Received: from outbound-mail.lax.untd.com ([64.136.28.164]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CH8dw-0006VV-31 for manet@ietf.org; Mon, 11 Oct 2004 18:27:58 -0400 Received: from outbound28-2.lax.untd.com (smtp04.lax.untd.com [10.130.24.124]) by smtpout06.lax.untd.com with SMTP id AABAYYBRTA4NX6B2 for (sender ); Mon, 11 Oct 2004 15:15:13 -0700 (PDT) Received: (qmail 21410 invoked from network); 11 Oct 2004 22:15:13 -0000 Received: from unknown (HELO utdallas.edu) (cobbtx@netzero.net@129.110.90.216) by smtp04.lax.untd.com with SMTP; 11 Oct 2004 22:15:13 -0000 Message-ID: <416B05F1.10309@utdallas.edu> Date: Mon, 11 Oct 2004 17:15:13 -0500 From: Jorge Cobb User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ContentStamp: 11:5:2577452393 X-MAIL-INFO: 1dba5a3ea7833e4a3f333baabb9f87cf07874f135e77c7 X-UNTD-OriginStamp: reyva3a81tRumyBHF+9yP51pGNv2I6UdvkVsFGoHRdytZ76jRwbcCQ== X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 7bit Subject: [manet] CF Participation, QSHine '04, less than a week left! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cobb@utdallas.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: 7bit (* our apologies if you receive multiple copies *) ----------------------------------------------------------------------------- Call for Participation QShine 2004 ----------------------------------------------------------------------------- First International Conference on Quality of Service in Heterogeneous Wired/Wireless Networks October 18-20, 2004 Dallas, Texas, USA Wyndham Hotel, Dallas ----------------------------------------------------------------------------- http://www.qshine.org/ ----------------------------------------------------------------------------- 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. Held in the Dallas, TX, home of the Telecomm Corridor, this conference focuses on all aspects of QoS support for heterogeneous wired and wireless networks. It serves 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. Please join us in Dallas for QShine 2004! This year, QShine include - 2 prominent Keynote Speakers: * Dr. Sanjoy Paul Director of Wireless Networking Research Bell Laboratories * Prof Sajal K. Das, Director, Center for Research in Wireless Mobility and Networking (CReWMaN), The University of Texas at Arlington - 10 Technical sessions which include: * Admission Control and Resource Allocation * Ad-hoc and sensor networks * QoS and Multimedia Support * QoS Routing * Wired-Wireless Networks and Hybrid Networks * Voice and Multi-Media Protocols * Reliability and Resource Management * Advanced Routing Techniques - 3 Panel sessions: * Can WiFi hotspots survive without QoS ? * QoS in the Internet: How strong is the need ? * QoS for sensor networks: is it an overkill? - A Poster Session with works in progress Please consult www.qshine.org for further details regarding the Technical Program, Hotel, and Registration. Organizing Committee: General Chair: Azzedine Boukerche, University of Ottawa, Canada Vice Chair: Michael Fang, University of Florida, USA Technical Program Co-Chairs Jorge Cobb, University of Texas at Dallas, USA Shigang Chen, University of Florida, USA Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas, USA -- Jorge A. Cobb Assistant Professor Erik Jonsson School of Engineering and Computer Science The University of Texas at Dallas PO Box 830688, Mail Station EC 31 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 From manet-bounces@ietf.org Tue Oct 12 06:03:09 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04856 for ; Tue, 12 Oct 2004 06:03:09 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHJfc-0001QP-6O for manet-web-archive@ietf.org; Tue, 12 Oct 2004 06:14:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHJS6-0006UT-Na; Tue, 12 Oct 2004 06:00:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHJNX-00045o-Lk for manet@megatron.ietf.org; Tue, 12 Oct 2004 05:55:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04338 for ; Tue, 12 Oct 2004 05:55:33 -0400 (EDT) Received: from bay8-f88.bay8.hotmail.com ([64.4.27.88] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHJYE-0001Gy-R3 for manet@ietf.org; Tue, 12 Oct 2004 06:06:40 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 12 Oct 2004 02:55:02 -0700 Received: from 203.197.138.163 by by8fd.bay8.hotmail.msn.com with HTTP; Tue, 12 Oct 2004 09:54:59 GMT X-Originating-IP: [203.197.138.163] X-Originating-Email: [muthu_india@hotmail.com] X-Sender: muthu_india@hotmail.com From: "Muthukumar Subramaniyam" To: manet@ietf.org Date: Tue, 12 Oct 2004 09:54:59 +0000 Mime-Version: 1.0 Message-ID: X-OriginalArrivalTime: 12 Oct 2004 09:55:02.0300 (UTC) FILETIME=[8AE765C0:01C4B041] X-Spam-Score: 1.3 (+) X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574 Subject: [manet] Energy aware Dsr details X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1042181528==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.5 (+) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 --===============1042181528== Content-Type: text/html



hi,
If any one know about energy aware DSR  protocol / any modifications to study the energy related characteristics .Please help me

The new MSN toolbar! Your shortcut to the internet! Access a world of convenience! --===============1042181528== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1042181528==-- From manet-bounces@ietf.org Tue Oct 12 08:27:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14243 for ; Tue, 12 Oct 2004 08:27:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHLvY-0003y6-6b for manet-web-archive@ietf.org; Tue, 12 Oct 2004 08:38:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHLZs-0005aF-Pb; Tue, 12 Oct 2004 08:16:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHLQc-0003Li-S8 for manet@megatron.ietf.org; Tue, 12 Oct 2004 08:06:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12222 for ; Tue, 12 Oct 2004 08:06:53 -0400 (EDT) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHLbL-0003ZD-LS for manet@ietf.org; Tue, 12 Oct 2004 08:18:00 -0400 Received: (qmail 20939 invoked for bounce); 12 Oct 2004 12:07:01 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (jelger@unknown) by unknown with SMTP; 12 Oct 2004 12:07:01 -0000 Message-ID: <416BC8DC.1070003@dpt-info.u-strasbg.fr> Date: Tue, 12 Oct 2004 14:06:52 +0200 From: Christophe Jelger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040530 Debian/1.6-6.backports.org.1 X-Accept-Language: en MIME-Version: 1.0 To: Kilian Weniger Subject: Re: [manet] Announcement: Implementation of PACMAN: Passive Autoconfiguration for MANETs References: <200410111059.56677.weniger@tm.uka.de> In-Reply-To: <200410111059.56677.weniger@tm.uka.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: 7bit Hello all, There is also some developments (OLSR with autoconfiguration, MLD Proxying and Multicast Forwarder) from the Network and Protocols Research Team of the LSIIT (Louis Pasteur University, Strasbourg, France). Everything is for IP version 6. Everything can be found here : http://clarinet.u-strasbg.fr/~frey/safari/autoconf.html All comments and bug reports are welcome ! We of course tested all these things and they worked fine with our testbed, but there might still be some bugs. Regards, Christophe Kilian Weniger wrote: >Hi all, > >we would like to announce the first public release of a "Passive >Autoconfiguration for MANETs (PACMAN)"-implementation for Linux. >PACMAN is is an efficient and robust distributed solution for >assigning and maintaining unique IP addresses in a MANET >(see "K. Weniger: PACMAN: Passive Autoconfiguration for Mobile Ad hoc >Networks", to appear in IEEE JSAC, March 2005). >To the best of our knowledge, this is the first publicly available >implementation of an address autoconfiguration protocol for MANETs. >The implementation was demonstrated at the ACM Mobicom 2004. > >PACMAN heavily uses cross-layer information from ongoing routing protocol >traffic: The maintenance of an address allocation table as well as the >Duplicate Address Detection (DAD) are performed in a passive manner >and therefore generate no additional communication overhead. >The Passive DAD (PDAD) component is able to detect address conflicts >whenever they occur (e.g. after network mergers) based on anomalies in the >routing protocol traffic. Different routing protocols are supported by PACMAN. >However, a modification of the message format or the implementation of the >routing protocol is not necessary. Thus, existing routing protocol >implementation as, e.g., the UniK OLSR implementation, can be used. support >for OLSR and FSR is implemented. Due to a modular architecture, new protocols >can easily be added. > >The source code as well as related publications, links, a GUI and some tools >for tests and demonstrations are available for download at > > http://pacman-autoconf.sourceforge.net > http://sourceforge.net/projects/pacman-autoconf/ > >Both the implementation as well as the concepts were developed within the >project IPonAir by members of the Institute of Telematics, University of >Karlsruhe, Germany. >(http://www.iponair.de), (http://www.tm.uka.de/itm-zitterbart.html) > > >Regards, > >Kilian Weniger > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 11:20:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00107 for ; Tue, 12 Oct 2004 11:20:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHOd3-0007ZM-N5 for manet-web-archive@ietf.org; Tue, 12 Oct 2004 11:31:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHOKo-0006GW-Lh; Tue, 12 Oct 2004 11:13:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHO7e-0002Mm-5c for manet@megatron.ietf.org; Tue, 12 Oct 2004 10:59:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27626 for ; Tue, 12 Oct 2004 10:59:28 -0400 (EDT) Received: from [203.199.83.32] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHOIN-00075I-RL for manet@ietf.org; Tue, 12 Oct 2004 11:10:37 -0400 Received: (qmail 23758 invoked by uid 510); 12 Oct 2004 12:25:04 -0000 Date: 12 Oct 2004 12:25:04 -0000 Message-ID: <20041012122504.23757.qmail@webmail32.rediffmail.com> Received: from unknown (203.94.197.234) by rediffmail.com via HTTP; 12 oct 2004 12:25:04 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Subject: [manet] dsdv in glomosim X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1310207580==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab This is a multipart mime message --===============1310207580== Content-type: multipart/alternative; boundary="Next_1097583904---0-203.199.83.32-23733" This is a multipart mime message --Next_1097583904---0-203.199.83.32-23733 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0Ahii
=0A
=0Athanks a lot for every one who replied to my mail.i = want to use glomosim to see the effects of mobility models on ad hoc networ= ks.for this i need to work on dsdv algorithm.i want to see the impact of mo= bility on dsdv algorithm.is there any one of this group who is working on d= sdv algorithm and is ready to share with me.or some one has the code of dsd= v for glomosim.i am writing algorithm for mobility models then want to run = them on dsdv and want to see how the various models effects the dsdv algori= thm.can any one help me in this.
=0A
=0Aanjali  =0A

=0A
=0A=0A --Next_1097583904---0-203.199.83.32-23733 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hii=0A=0Athanks a lot for every one who replied to my mail.i want to use gl= omosim to see the effects of mobility models on ad hoc networks.for this i = need to work on dsdv algorithm.i want to see the impact of mobility on dsdv= algorithm.is there any one of this group who is working on dsdv algorithm = and is ready to share with me.or some one has the code of dsdv for glomosim= .i am writing algorithm for mobility models then want to run them on dsdv a= nd want to see how the various models effects the dsdv algorithm.can any on= e help me in this.=0A=0Aanjali =20 --Next_1097583904---0-203.199.83.32-23733-- --===============1310207580== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1310207580==-- From manet-bounces@ietf.org Tue Oct 12 12:04:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03626 for ; Tue, 12 Oct 2004 12:04:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHP91-0008IK-JI for manet-web-archive@ietf.org; Tue, 12 Oct 2004 12:04:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHOnj-0004pc-Us; Tue, 12 Oct 2004 11:42:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHOgv-0003Iw-Jc for manet@megatron.ietf.org; Tue, 12 Oct 2004 11:35:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01701 for ; Tue, 12 Oct 2004 11:35:55 -0400 (EDT) Received: from farley3.colorado.edu ([128.138.129.104]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHOrf-0007tb-4z for manet@ietf.org; Tue, 12 Oct 2004 11:47:05 -0400 Received: (from nobody@localhost) by farley3.Colorado.EDU (8.12.10/8.12.10/ITS-6.0/test-webmail) id i9CFZpua010503 for manet@ietf.org; Tue, 12 Oct 2004 09:35:51 -0600 (MDT) Received: from smct43-141-dhcp.resnet.colorado.edu (smct43-141-dhcp.resnet.colorado.edu [128.138.43.141]) by webmail.colorado.edu (IMP) with HTTP for ; Tue, 12 Oct 2004 09:35:50 -0600 Message-ID: <1097595350.416bf9d6dab60@webmail.colorado.edu> Date: Tue, 12 Oct 2004 09:35:50 -0600 From: Sheetalkumar Doshi To: manet@ietf.org Subject: [manet] Energy aware Dsr details MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 8bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 8bit Hi Muthukumar We at the University of Colorado at Boulder have been looking at Energy Aware DSR for sometime. You can find papers and implementation source code at http://pecolab.colorado.edu . Regards -- Sheetalkumar Doshi PhD Student/Research Assistant Dept. Of Electrical and Computer Engineering University of Colorado at Boulder http://ucsub.colorado.edu/~doshi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 13:37:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12178 for ; Tue, 12 Oct 2004 13:37:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHQln-0002zo-NG for manet-web-archive@ietf.org; Tue, 12 Oct 2004 13:49:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHQQE-0006PD-EP; Tue, 12 Oct 2004 13:26:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHQHC-0004DV-1q for manet@megatron.ietf.org; Tue, 12 Oct 2004 13:17:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10198 for ; Tue, 12 Oct 2004 13:17:27 -0400 (EDT) Received: from imap.telefonica.net ([213.4.129.150] helo=telesmtp3.mail.isp) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHQRo-0002a8-JU for manet@ietf.org; Tue, 12 Oct 2004 13:28:39 -0400 Received: from [192.168.1.10] ([80.38.46.159]) by telesmtp3.mail.isp (terra.es) with ESMTP id I5HEOS00.LAR for ; Tue, 12 Oct 2004 19:17:16 +0200 From: "Xavier M." To: manet@ietf.org Date: Tue, 12 Oct 2004 19:17:24 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200410121917.24405.xaviermm3@telefonica.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Subject: [manet] How to change de Active Route Timeout in AODV X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hi all, I would like to know how to change the ACTIVE ROUTE TIMEOUT parameter in the tcl script for using it in a ns-2 simulation. I am using the AODV routing protocol. What is the default value? is it 3? what other values can be set? I am using the ns-allinone2.27 package and I don't know whether it can be done directly with tcl or not. thank you for your help Xavier M. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 16:06:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27675 for ; Tue, 12 Oct 2004 16:06:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHT56-0006ki-LM for manet-web-archive@ietf.org; Tue, 12 Oct 2004 16:17:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSm7-0004PK-I1; Tue, 12 Oct 2004 15:57:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSaA-0006OL-KB for manet@megatron.ietf.org; Tue, 12 Oct 2004 15:45:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24731 for ; Tue, 12 Oct 2004 15:45:13 -0400 (EDT) Received: from web52509.mail.yahoo.com ([206.190.39.134]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHSkx-0005sp-LX for manet@ietf.org; Tue, 12 Oct 2004 15:56:24 -0400 Message-ID: <20041012194441.82660.qmail@web52509.mail.yahoo.com> Received: from [128.4.130.33] by web52509.mail.yahoo.com via HTTP; Tue, 12 Oct 2004 12:44:41 PDT Date: Tue, 12 Oct 2004 12:44:41 -0700 (PDT) From: Leon Martin To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] carrier frequency X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Hi, I was just wondering if someone could give me some hint on the following questions. 1. There are several channels defined in 802.11. When different channels are used, are the carrier frequencies the same? 2. Is it possible to design a receiver that does not need to know the carrier frequency in advance? Thanks. - Leon _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 17:51:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18705 for ; Tue, 12 Oct 2004 17:51:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHUiu-0004dS-TS for manet-web-archive@ietf.org; Tue, 12 Oct 2004 18:02:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHUKY-0003F1-93; Tue, 12 Oct 2004 17:37:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHTl9-0001bb-UL for manet@megatron.ietf.org; Tue, 12 Oct 2004 17:00:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08701 for ; Tue, 12 Oct 2004 17:00:38 -0400 (EDT) Received: from smtp1.utdallas.edu ([129.110.10.12]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHTvy-0001d1-Mk for manet@ietf.org; Tue, 12 Oct 2004 17:11:51 -0400 Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9]) by smtp1.utdallas.edu (Postfix) with ESMTP id 49835389994 for ; Tue, 12 Oct 2004 15:50:38 -0500 (CDT) Received: by apache.utdallas.edu (Postfix, from userid 30625) id 1BC3F1777D; Tue, 12 Oct 2004 15:50:38 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by apache.utdallas.edu (Postfix) with ESMTP id 0AA0D17581 for ; Tue, 12 Oct 2004 15:50:38 -0500 (CDT) Date: Tue, 12 Oct 2004 15:50:37 -0500 (CDT) From: Ming Li To: manet@ietf.org In-Reply-To: <20041012194441.82660.qmail@web52509.mail.yahoo.com> Message-ID: References: <20041012194441.82660.qmail@web52509.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Subject: [manet] information sharing in MANET X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Hi, I am wondering that what kind of information can be shared between nodes in a MANET. It is quite common that MAC-level information is shared among neighbors. But can user-level information such as node location be shared so that improvement can be made based on these information? Thanks a lot! ming _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 18:50:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24792 for ; Tue, 12 Oct 2004 18:50:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHVeV-0005qB-JR for manet-web-archive@ietf.org; Tue, 12 Oct 2004 19:01:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHVLj-0002uL-TA; Tue, 12 Oct 2004 18:42:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHVIZ-0001tD-VL for manet@megatron.ietf.org; Tue, 12 Oct 2004 18:39:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24081 for ; Tue, 12 Oct 2004 18:39:14 -0400 (EDT) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHVTM-0005cX-0M for manet@ietf.org; Tue, 12 Oct 2004 18:50:28 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id D90CD19EBEC for ; Tue, 12 Oct 2004 23:18:11 +0200 (CEST) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01907-06 for ; Tue, 12 Oct 2004 23:18:11 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id BE4FC19EA34 for ; Tue, 12 Oct 2004 23:18:11 +0200 (CEST) Received: from afontenayssb-152-1-47-146.w83-114.abo.wanadoo.fr ([83.114.189.146]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Tue, 12 Oct 2004 23:18:11 +0200 (CEST) Message-ID: <4292.83.114.189.146.1097615891.squirrel@www.lri.fr> Date: Tue, 12 Oct 2004 23:18:11 +0200 (CEST) To: manet@ietf.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 8bit Subject: [manet] Draft submission X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 8bit Hi all, I have submitted an individual draft, which focuses on QoS in ad hoc networks using OLSR (QOLSR). This draft presents a simple version of QOLSR. Admission control and reservation mechanisms under multiple interfaces will be integrated in next versions. Any comments on the subject are welcome. draft URL: http://www.ietf.org/internet-drafts/draft-badis-manet-qolsr-00.txt Hakim. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 20:09:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00296 for ; Tue, 12 Oct 2004 20:09:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHWse-0007E7-Gx for manet-web-archive@ietf.org; Tue, 12 Oct 2004 20:20:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHWfl-0001EC-SD; Tue, 12 Oct 2004 20:07:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHWbb-0000BV-GK for manet@megatron.ietf.org; Tue, 12 Oct 2004 20:02:59 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29635 for ; Tue, 12 Oct 2004 20:02:58 -0400 (EDT) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHWmQ-00075q-HY for manet@ietf.org; Tue, 12 Oct 2004 20:14:11 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id E530D19EC1A for ; Wed, 13 Oct 2004 00:08:14 +0200 (CEST) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05990-05 for ; Wed, 13 Oct 2004 00:08:14 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id CC02319EC19 for ; Wed, 13 Oct 2004 00:08:14 +0200 (CEST) Received: from afontenayssb-152-1-47-146.w83-114.abo.wanadoo.fr ([83.114.189.146]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Wed, 13 Oct 2004 00:08:14 +0200 (CEST) Message-ID: <4455.83.114.189.146.1097618894.squirrel@www.lri.fr> In-Reply-To: References: <20041012194441.82660.qmail@web52509.mail.yahoo.com> Date: Wed, 13 Oct 2004 00:08:14 +0200 (CEST) Subject: [manet] Draft submission To: manet@ietf.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 8bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 8bit Hi all, I have submitted an individual draft, which focuses on QoS in ad hoc networks using OLSR (QOLSR). This draft presents a simple version of QOLSR. Admission control and reservation mechanisms under multiple interfaces will be integrated in next versions. Any comments on the subject are welcome. draft URL: http://www.ietf.org/internet-drafts/draft-badis-manet-qolsr-00.txt Hakim. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 12 23:49:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15920 for ; Tue, 12 Oct 2004 23:49:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHaK7-0002ur-AD for manet-web-archive@ietf.org; Wed, 13 Oct 2004 00:01:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHa5c-0008B3-NO; Tue, 12 Oct 2004 23:46:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHa1k-0007JE-Hb for manet@megatron.ietf.org; Tue, 12 Oct 2004 23:42:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15440 for ; Tue, 12 Oct 2004 23:42:08 -0400 (EDT) Received: from web20927.mail.yahoo.com ([216.136.224.145]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHaCZ-0002eP-Ur for manet@ietf.org; Tue, 12 Oct 2004 23:53:25 -0400 Message-ID: <20041013034207.24071.qmail@web20927.mail.yahoo.com> Received: from [203.208.193.230] by web20927.mail.yahoo.com via HTTP; Tue, 12 Oct 2004 20:42:07 PDT Date: Tue, 12 Oct 2004 20:42:07 -0700 (PDT) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] Research in Sensor Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0077078164==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 --===============0077078164== Content-Type: multipart/alternative; boundary="0-1096222293-1097638927=:22550" --0-1096222293-1097638927=:22550 Content-Type: text/plain; charset=us-ascii Hi, I am Praveen from India. I am doing research in routing aspects of Sensor Networks. I have developed an idea for energy efficient broadcasting in Sensor Networks. My algorithm requires only one-hop neighbourhood information. I am considering energy as a parameter in algorithm. I want to refine my algorithm and go for major Publication. Can anyone of you tell me. if I can consider more parameters other than energy to decide the route. If there are any such parameters that I can consider, what are those parameters or atleast give some references where I can get an idea. Kindly tell me what are the simulation softwares available freely where I can simulate my algorithm and evaluate its performance. I am doing research Independently. Many members of this group may be working in the routing aspects of Sensor Networks or Wireless Adhoc Networks. I want to know, if anyone of you is interested in my research. I want to collaborate with you and involve in your research. I look forward, for suggestions from members and if anybody can come forward and help me in Research by giving me guidance. Sincerely, Praveen. --------------------------------- Do you Yahoo!? vote.yahoo.com - Register online to vote today! --0-1096222293-1097638927=:22550 Content-Type: text/html; charset=us-ascii
Hi,
 I am Praveen from India. I am doing research in routing aspects of Sensor Networks. I have developed an idea for energy efficient broadcasting in Sensor Networks. My algorithm requires only one-hop neighbourhood information. I am considering energy as a parameter in algorithm. I want to refine my algorithm and go for major Publication. Can anyone of you tell me. if I can consider more parameters other than energy to decide the route. If there are any such parameters that I can consider, what are those parameters or atleast give some references where I can get an idea. Kindly tell me what are the simulation softwares available freely where I can simulate my algorithm and evaluate its performance.
 I am doing research Independently. Many members of this group may be working in the routing aspects of Sensor Networks or Wireless Adhoc Networks. I want to know, if anyone of you is interested in my research. I want to collaborate with you and involve in your research.
 I look forward, for suggestions from members and if anybody can come forward and help me in Research by giving me guidance.
 
Sincerely,
Praveen.
 

Do you Yahoo!?
vote.yahoo.com - Register online to vote today! --0-1096222293-1097638927=:22550-- --===============0077078164== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0077078164==-- From manet-bounces@ietf.org Wed Oct 13 05:12:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04842 for ; Wed, 13 Oct 2004 05:12:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHfMG-0008No-US for manet-web-archive@ietf.org; Wed, 13 Oct 2004 05:23:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHf8d-0003K1-VP; Wed, 13 Oct 2004 05:09:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHf4F-0001o8-OT for manet@megatron.ietf.org; Wed, 13 Oct 2004 05:05:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04326 for ; Wed, 13 Oct 2004 05:05:03 -0400 (EDT) Received: from [203.199.83.38] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHfEv-0008DU-9x for manet@ietf.org; Wed, 13 Oct 2004 05:16:20 -0400 Received: (qmail 32154 invoked by uid 510); 13 Oct 2004 09:04:29 -0000 Date: 13 Oct 2004 09:04:29 -0000 Message-ID: <20041013090429.32153.qmail@webmail28.rediffmail.com> Received: from unknown (202.141.140.161) by rediffmail.com via HTTP; 13 oct 2004 09:04:29 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 1.8 (+) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Subject: [manet] dsdv + mobility in glomosim X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0767237157==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 This is a multipart mime message --===============0767237157== Content-type: multipart/alternative; boundary="Next_1097658269---0-203.199.83.38-32147" This is a multipart mime message --Next_1097658269---0-203.199.83.38-32147 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahi every one
=0A
=0Athanks for ur replies.as i di= scussed  before regarding my project now i want to tell u all in detai= l wat i want to do.i want to use dsdv algorithm and want to see the impact = of mobility models on the algorithm.the problem is that dsdv is not present= in glomosim so dont even know how to proceed.i read  manuals but that= didnt given full guidance to me.can any one help me i this to how to add m= obility models file so that i can see the impact of them.plz send me more h= elp material on this.one thing more  i insatlled glomosim in linux but= that contains red hat 6.0 whereas my system has linux(red hat 9.2).due to = this it is not running.wat to do.
=0A
=0Aplz reply.
=0Aanjali=0A<= /P>=0A

=0A=0A --Next_1097658269---0-203.199.83.38-32147 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahi every one=0A=0Athanks for ur replies.as i discussed before regar= ding my project now i want to tell u all in detail wat i want to do.i want = to use dsdv algorithm and want to see the impact of mobility models on the = algorithm.the problem is that dsdv is not present in glomosim so dont even = know how to proceed.i read manuals but that didnt given full guidance to m= e.can any one help me i this to how to add mobility models file so that i c= an see the impact of them.plz send me more help material on this.one thing = more i insatlled glomosim in linux but that contains red hat 6.0 whereas m= y system has linux(red hat 9.2).due to this it is not running.wat to do. = =0A=0Aplz reply.=0Aanjali --Next_1097658269---0-203.199.83.38-32147-- --===============0767237157== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0767237157==-- From manet-bounces@ietf.org Wed Oct 13 07:21:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14897 for ; Wed, 13 Oct 2004 07:21:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHhNK-0002An-N2 for manet-web-archive@ietf.org; Wed, 13 Oct 2004 07:32:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHh7u-0007gF-7q; Wed, 13 Oct 2004 07:17:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHh5H-0006BK-Mb for manet@megatron.ietf.org; Wed, 13 Oct 2004 07:14:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13904 for ; Wed, 13 Oct 2004 07:14:13 -0400 (EDT) Received: from [203.199.83.39] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHhFo-0001zv-9p for manet@ietf.org; Wed, 13 Oct 2004 07:25:33 -0400 Received: (qmail 10434 invoked by uid 510); 13 Oct 2004 11:13:31 -0000 Date: 13 Oct 2004 11:13:31 -0000 Message-ID: <20041013111331.10433.qmail@webmail29.rediffmail.com> Received: from unknown (202.141.140.161) by rediffmail.com via HTTP; 13 oct 2004 11:13:31 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 2.8 (++) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [manet] parsec X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1658568977==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 This is a multipart mime message --===============1658568977== Content-type: multipart/alternative; boundary="Next_1097666011---0-203.199.83.39-10427" This is a multipart mime message --Next_1097666011---0-203.199.83.39-10427 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahaiii every one
=0A
=0Acan any one send me parse= c folder containg red hat 7.2 of glomosim (2.03) for linux plz
=0A
= =0Athanks
=0A
=0A=0A

=0A

=0A=0A --Next_1097666011---0-203.199.83.39-10427 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahaiii every one =0A=0Acan any one send me parsec folder containg red= hat 7.2 of glomosim (2.03) for linux plz=0A=0Athanks=0A=0A --Next_1097666011---0-203.199.83.39-10427-- --===============1658568977== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1658568977==-- From manet-bounces@ietf.org Wed Oct 13 07:24:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15064 for ; Wed, 13 Oct 2004 07:24:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHhPm-0002E8-0R for manet-web-archive@ietf.org; Wed, 13 Oct 2004 07:35:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHh7w-0007jd-3t; Wed, 13 Oct 2004 07:17:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHh5m-0006BP-SR for manet@megatron.ietf.org; Wed, 13 Oct 2004 07:14:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13944 for ; Wed, 13 Oct 2004 07:14:45 -0400 (EDT) Received: from [203.199.83.31] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHhGd-00020w-94 for manet@ietf.org; Wed, 13 Oct 2004 07:26:04 -0400 Received: (qmail 14588 invoked by uid 510); 13 Oct 2004 11:14:17 -0000 Date: 13 Oct 2004 11:14:17 -0000 Message-ID: <20041013111417.14587.qmail@webmail46.rediffmail.com> Received: from unknown (202.141.140.161) by rediffmail.com via HTTP; 13 oct 2004 11:14:17 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 2.8 (++) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [manet] parsec X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0539847713==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 This is a multipart mime message --===============0539847713== Content-type: multipart/alternative; boundary="Next_1097666057---0-203.199.83.31-14571" This is a multipart mime message --Next_1097666057---0-203.199.83.31-14571 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahaiii every one
=0A
=0Acan any one send me parse= c folder containg red hat 7.2 of glomosim (2.03) for linux plz
=0A
= =0Athanks
=0A
=0A=0A

=0A

=0A=0A --Next_1097666057---0-203.199.83.31-14571 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahaiii every one =0A=0Acan any one send me parsec folder containg red= hat 7.2 of glomosim (2.03) for linux plz=0A=0Athanks=0A=0A --Next_1097666057---0-203.199.83.31-14571-- --===============0539847713== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0539847713==-- From manet-bounces@ietf.org Wed Oct 13 07:27:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15672 for ; Wed, 13 Oct 2004 07:27:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHhTK-0002NH-3B for manet-web-archive@ietf.org; Wed, 13 Oct 2004 07:39:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHhA8-0008Is-NK; Wed, 13 Oct 2004 07:19:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHh6F-00074r-TB for manet@megatron.ietf.org; Wed, 13 Oct 2004 07:15:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14050 for ; Wed, 13 Oct 2004 07:15:14 -0400 (EDT) Received: from [203.199.83.39] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHhH6-00021m-GJ for manet@ietf.org; Wed, 13 Oct 2004 07:26:33 -0400 Received: (qmail 13037 invoked by uid 510); 13 Oct 2004 11:14:53 -0000 Date: 13 Oct 2004 11:14:53 -0000 Message-ID: <20041013111453.13030.qmail@webmail29.rediffmail.com> Received: from unknown (202.141.140.161) by rediffmail.com via HTTP; 13 oct 2004 11:14:53 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 2.8 (++) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [manet] parsec X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0030813760==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 This is a multipart mime message --===============0030813760== Content-type: multipart/alternative; boundary="Next_1097666093---0-203.199.83.39-13018" This is a multipart mime message --Next_1097666093---0-203.199.83.39-13018 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahaiii every one
=0A
=0Acan any one send me parse= c folder containg red hat 7.2 of glomosim (2.03) for linux plz
=0A
= =0Athanks
=0A
=0A=0A

=0A

=0A=0A --Next_1097666093---0-203.199.83.39-13018 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahaiii every one =0A=0Acan any one send me parsec folder containg red= hat 7.2 of glomosim (2.03) for linux plz=0A=0Athanks=0A=0A --Next_1097666093---0-203.199.83.39-13018-- --===============0030813760== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0030813760==-- From manet-bounces@ietf.org Wed Oct 13 08:03:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18633 for ; Wed, 13 Oct 2004 08:03:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHi1l-0003Ek-4F for manet-web-archive@ietf.org; Wed, 13 Oct 2004 08:14:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHhlq-0001hz-Nx; Wed, 13 Oct 2004 07:58:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHhl2-0001QM-RE for manet@megatron.ietf.org; Wed, 13 Oct 2004 07:57:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18322 for ; Wed, 13 Oct 2004 07:57:24 -0400 (EDT) Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHhvq-00039y-2D for manet@ietf.org; Wed, 13 Oct 2004 08:08:42 -0400 Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6] helo=spamhost.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10) id 1CHhkq-0007FD-00 for ; Wed, 13 Oct 2004 13:57:16 +0200 Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3) id 1CHhkp-00022D-00 for ; Wed, 13 Oct 2004 13:57:15 +0200 Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by spamhost.ira.uka.de with esmtp (Exim 3.30 #3) id 1CHhkl-000224-00 for ; Wed, 13 Oct 2004 13:57:11 +0200 Received: from i72tribble.tm.uni-karlsruhe.de ([141.3.71.8]) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 ) for id 1CHhkl-0005gq-00; Wed, 13 Oct 2004 13:57:11 +0200 From: Kilian Weniger Organization: University of Karlsruhe To: manet@ietf.org Subject: Re: [manet] Announcement: Implementation of PACMAN: =?iso-8859-1?q?Passive=09Autoconfiguration_for?= MANETs Date: Wed, 13 Oct 2004 13:57:10 +0200 User-Agent: KMail/1.6.2 References: <200410111059.56677.weniger@tm.uka.de> <416BC8DC.1070003@dpt-info.u-strasbg.fr> In-Reply-To: <416BC8DC.1070003@dpt-info.u-strasbg.fr> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410131357.10380.weniger@tm.uka.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Content-Transfer-Encoding: 7bit Hello, maybe I should mention that PACMAN aims at autoconfiguring stand-alone ad hoc networks with MANET-local-prefixed addresses and that the PACMAN concept can be applied to both IPv4 or IPv6. However, the linux implementation announced in the last mail is designed for IPv4. Christophe, your implementation seems to aim at providing global routable addresses in MANET with Internet connectivity. Thus, stand-alone MANETs cannot be configured with this implementation. Is this correct? Regards, Kilian Am Dienstag, 12. Oktober 2004 14:06 schrieb Christophe Jelger: > Hello all, > > There is also some developments (OLSR with autoconfiguration, MLD > Proxying and Multicast Forwarder) from the Network and Protocols > Research Team of the LSIIT (Louis Pasteur University, Strasbourg, > France). Everything is for IP version 6. > > Everything can be found here : > > http://clarinet.u-strasbg.fr/~frey/safari/autoconf.html > > All comments and bug reports are welcome ! We of course tested all these > things and they worked fine with our testbed, but there might still be > some bugs. > > Regards, > Christophe > > Kilian Weniger wrote: > >Hi all, > > > >we would like to announce the first public release of a "Passive > >Autoconfiguration for MANETs (PACMAN)"-implementation for Linux. > >PACMAN is is an efficient and robust distributed solution for > >assigning and maintaining unique IP addresses in a MANET > >(see "K. Weniger: PACMAN: Passive Autoconfiguration for Mobile Ad hoc > >Networks", to appear in IEEE JSAC, March 2005). > >To the best of our knowledge, this is the first publicly available > >implementation of an address autoconfiguration protocol for MANETs. > >The implementation was demonstrated at the ACM Mobicom 2004. > > > >PACMAN heavily uses cross-layer information from ongoing routing protocol > >traffic: The maintenance of an address allocation table as well as the > >Duplicate Address Detection (DAD) are performed in a passive manner > >and therefore generate no additional communication overhead. > >The Passive DAD (PDAD) component is able to detect address conflicts > >whenever they occur (e.g. after network mergers) based on anomalies in the > >routing protocol traffic. Different routing protocols are supported by > > PACMAN. However, a modification of the message format or the > > implementation of the routing protocol is not necessary. Thus, existing > > routing protocol implementation as, e.g., the UniK OLSR implementation, > > can be used. support for OLSR and FSR is implemented. Due to a modular > > architecture, new protocols can easily be added. > > > >The source code as well as related publications, links, a GUI and some > > tools for tests and demonstrations are available for download at > > > > http://pacman-autoconf.sourceforge.net > > http://sourceforge.net/projects/pacman-autoconf/ > > > >Both the implementation as well as the concepts were developed within the > >project IPonAir by members of the Institute of Telematics, University of > >Karlsruhe, Germany. > >(http://www.iponair.de), (http://www.tm.uka.de/itm-zitterbart.html) > > > > > >Regards, > > > >Kilian Weniger > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Dr.-Ing. Kilian Weniger Institute of Telematics, Universitaet Karlsruhe (TH) Zirkel 2, 76128 Karlsruhe, Germany Phone: +49 721 608 6415, Fax: +49 721 388097 Email: weniger@tm.uka.de, HP: http://www.tm.uka.de/~weniger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 13 08:31:52 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21664 for ; Wed, 13 Oct 2004 08:31:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHiTG-000409-Ot for manet-web-archive@ietf.org; Wed, 13 Oct 2004 08:43:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHiE8-0000kV-3l; Wed, 13 Oct 2004 08:27:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHi98-0007uU-LK for manet@megatron.ietf.org; Wed, 13 Oct 2004 08:22:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21076 for ; Wed, 13 Oct 2004 08:22:18 -0400 (EDT) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHiJw-0003pu-Qu for manet@ietf.org; Wed, 13 Oct 2004 08:33:36 -0400 Received: (qmail 930 invoked for bounce); 13 Oct 2004 12:15:32 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (jelger@unknown) by unknown with SMTP; 13 Oct 2004 12:15:32 -0000 Message-ID: <416D1C5E.7010408@dpt-info.u-strasbg.fr> Date: Wed, 13 Oct 2004 14:15:26 +0200 From: Christophe Jelger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040530 Debian/1.6-6.backports.org.1 X-Accept-Language: en MIME-Version: 1.0 To: Kilian Weniger Subject: Re: [manet] Announcement: Implementation of PACMAN: Passive Autoconfiguration for MANETs References: <200410111059.56677.weniger@tm.uka.de> <416BC8DC.1070003@dpt-info.u-strasbg.fr> <200410131357.10380.weniger@tm.uka.de> In-Reply-To: <200410131357.10380.weniger@tm.uka.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Content-Transfer-Encoding: 7bit Hi Kilian, You are right. Our solution has indeed been proposed to connect an ad hoc network to the Internet. We do not support autoconfiguration of a "stand-alone" ad hoc network (unless if one ad hoc node is chosen as gateway). Actually our proposal and develoment were driven by a project in which the ad hoc network is connected to the Internet via a gateway. That's why we also propose a multicast gateway (MLD Proxy) and a simple multicast forwarder (based on flooding). Actually the forwarder could quite easily been upgraded to do real multicast routing, maybe in a few weeks I'll try to add such a feature. I hope to be able to get a closer look at PACMAN some day. I'm quite busy at the moment but I will try to take some time next month to see how it works. ;-) Regards, Christophe Kilian Weniger wrote: >Hello, > >maybe I should mention that PACMAN aims at autoconfiguring stand-alone ad hoc >networks with MANET-local-prefixed addresses and that the PACMAN concept can >be applied to both IPv4 or IPv6. However, the linux implementation announced >in the last mail is designed for IPv4. > >Christophe, your implementation seems to aim at providing global routable >addresses in MANET with Internet connectivity. Thus, stand-alone MANETs cannot >be configured with this implementation. Is this correct? > >Regards, > >Kilian > >Am Dienstag, 12. Oktober 2004 14:06 schrieb Christophe Jelger: > > >>Hello all, >> >>There is also some developments (OLSR with autoconfiguration, MLD >>Proxying and Multicast Forwarder) from the Network and Protocols >>Research Team of the LSIIT (Louis Pasteur University, Strasbourg, >>France). Everything is for IP version 6. >> >>Everything can be found here : >> >>http://clarinet.u-strasbg.fr/~frey/safari/autoconf.html >> >>All comments and bug reports are welcome ! We of course tested all these >>things and they worked fine with our testbed, but there might still be >>some bugs. >> >>Regards, >>Christophe >> >>Kilian Weniger wrote: >> >> >>>Hi all, >>> >>>we would like to announce the first public release of a "Passive >>>Autoconfiguration for MANETs (PACMAN)"-implementation for Linux. >>>PACMAN is is an efficient and robust distributed solution for >>>assigning and maintaining unique IP addresses in a MANET >>>(see "K. Weniger: PACMAN: Passive Autoconfiguration for Mobile Ad hoc >>>Networks", to appear in IEEE JSAC, March 2005). >>>To the best of our knowledge, this is the first publicly available >>>implementation of an address autoconfiguration protocol for MANETs. >>>The implementation was demonstrated at the ACM Mobicom 2004. >>> >>>PACMAN heavily uses cross-layer information from ongoing routing protocol >>>traffic: The maintenance of an address allocation table as well as the >>>Duplicate Address Detection (DAD) are performed in a passive manner >>>and therefore generate no additional communication overhead. >>>The Passive DAD (PDAD) component is able to detect address conflicts >>>whenever they occur (e.g. after network mergers) based on anomalies in the >>>routing protocol traffic. Different routing protocols are supported by >>>PACMAN. However, a modification of the message format or the >>>implementation of the routing protocol is not necessary. Thus, existing >>>routing protocol implementation as, e.g., the UniK OLSR implementation, >>>can be used. support for OLSR and FSR is implemented. Due to a modular >>>architecture, new protocols can easily be added. >>> >>>The source code as well as related publications, links, a GUI and some >>>tools for tests and demonstrations are available for download at >>> >>> http://pacman-autoconf.sourceforge.net >>> http://sourceforge.net/projects/pacman-autoconf/ >>> >>>Both the implementation as well as the concepts were developed within the >>>project IPonAir by members of the Institute of Telematics, University of >>>Karlsruhe, Germany. >>>(http://www.iponair.de), (http://www.tm.uka.de/itm-zitterbart.html) >>> >>> >>>Regards, >>> >>>Kilian Weniger >>> >>> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 13 11:07:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05908 for ; Wed, 13 Oct 2004 11:07:19 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHktj-0006zA-B7 for manet-web-archive@ietf.org; Wed, 13 Oct 2004 11:18:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHkUF-0003PB-IU; Wed, 13 Oct 2004 10:52:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHkRa-0002L9-QP for manet@megatron.ietf.org; Wed, 13 Oct 2004 10:49:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04598 for ; Wed, 13 Oct 2004 10:49:28 -0400 (EDT) Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHkcR-0006dA-TJ for manet@ietf.org; Wed, 13 Oct 2004 11:00:48 -0400 Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C180A30988 for ; Wed, 13 Oct 2004 16:48:51 +0200 (CEST) Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253]) by smtp.um.es (Postfix) with SMTP id 9A6E230983 for ; Wed, 13 Oct 2004 16:48:51 +0200 (CEST) Received: (qmail 18975 invoked from network); 13 Oct 2004 14:48:33 -0000 Received: from vpnsg2.dif.um.es (HELO pepito) (155.54.210.49) by aries.dif.um.es with SMTP; 13 Oct 2004 14:48:33 -0000 Message-ID: <007c01c4b133$c0ba9bc0$31d2369b@pepito> From: =?iso-8859-1?Q?Carmen_M_Yago_S=E1nchez?= To: Date: Wed, 13 Oct 2004 16:48:50 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.8 (/) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Subject: [manet] MAC filtering and multicast X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0370039615==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c This is a multi-part message in MIME format. --===============0370039615== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01C4B144.8440FAC0" This is a multi-part message in MIME format. ------=_NextPart_000_0079_01C4B144.8440FAC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all, I am working with IPv6 ad-hoc networks and I am testing a new multicast = protocol. To do this, I need to filter packets on the MAC level. I am using Mandrake 10.0 with kernel 2.6.3-7 and, to filter the packets, = first I tried mackill 0.1 and 0.2 but I couldn't compile them because of = the kernel, then I tried iptables/iptables-ipv6 1.2.9-7mdk but these = didn't seem to work either. With iptables, first I tried these rules: ip6tables -i eth1 -A INPUT -m mac --mac-source 00:02:2D:01:02:03 -j = DROP ip6tables -i eth1 -A FORWARD -m mac --mac-source 00:02:2D:01:02:03 -j = DROP These rules blocked unicast traffic but they DID NOT block multicast = traffic, then I flushed all the rules and I established the DROP policy = in all chains and all tables but multicast traffic was accepted. Could someone tell me where the problem is, or indicate me a mac-filter = tool working with multicast, please? Thanks in advance. Best Regards,=20 Carmen=20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004 ------=_NextPart_000_0079_01C4B144.8440FAC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello all,
I am working with IPv6 ad-hoc networks = and I am=20 testing a new multicast protocol. To do this, I need to filter packets = on the=20 MAC level.
I am using Mandrake 10.0 with kernel 2.6.3-7 = and, to=20 filter the packets, first I tried mackill 0.1 and 0.2 but I = couldn't=20 compile them because of the kernel, then I tried = iptables/iptables-ipv6 1.2.9-7mdk but these didn't seem to work = either.
 
With iptables, first I tried these=20 rules:
ip6tables -i eth1 -A INPUT -m mac=20 --mac-source 00:02:2D:01:02:03  -j DROP
ip6tables -i eth1 -A FORWARD -m = mac=20 --mac-source 00:02:2D:01:02:03  -j = DROP
 
These rules blocked unicast traffic but = they DID NOT block multicast traffic, then I flushed all = the=20 rules and I established the DROP policy in all chains and all = tables=20 but multicast traffic was accepted.
 
Could someone tell me where the = problem is, or=20 indicate me a mac-filter tool working with multicast, please?
 
Thanks in advance.
 
Best Regards,
Carmen
 

---
Outgoing mail is certified = Virus=20 Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: = 6.0.775 /=20 Virus Database: 522 - Release Date:=20 08/10/2004
------=_NextPart_000_0079_01C4B144.8440FAC0-- --===============0370039615== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0370039615==-- From manet-bounces@ietf.org Wed Oct 13 18:09:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18210 for ; Wed, 13 Oct 2004 18:09:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHrUR-0001Sa-P0 for manet-web-archive@ietf.org; Wed, 13 Oct 2004 18:21:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHqwW-00089e-A7; Wed, 13 Oct 2004 17:45:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHqap-0001mX-D1 for manet@megatron.ietf.org; Wed, 13 Oct 2004 17:23:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12124 for ; Wed, 13 Oct 2004 17:23:31 -0400 (EDT) Received: from web61102.mail.yahoo.com ([216.155.196.104]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHqlg-00080h-H4 for manet@ietf.org; Wed, 13 Oct 2004 17:34:55 -0400 Message-ID: <20041013212244.28387.qmail@web61102.mail.yahoo.com> Received: from [66.208.44.5] by web61102.mail.yahoo.com via HTTP; Wed, 13 Oct 2004 14:22:44 PDT Date: Wed, 13 Oct 2004 14:22:44 -0700 (PDT) From: manet user To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] AODV v6 compatibility X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0456774542==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 --===============0456774542== Content-Type: multipart/alternative; boundary="0-1429376613-1097702564=:27990" --0-1429376613-1097702564=:27990 Content-Type: text/plain; charset=us-ascii Hi, draft-perkins-manet-aodv6 refers to AODV support for IPv6. After reading it, i guess that AODV can support only one family at a time. Is AODV capable of supporting IPV4 and IPv6 together in a network. For example, a network having mixure of nodes (running IPv4 and IPv6) or some nodes with interfaces capabale of both IPv4 and IPv6 addressing. In a case of mixed families, how a "Hello" message will be sent out? Draft does not talk about it. Since, "Hello" message is a broadcast, if a node supports both address families, node will send out two kinds of hello pkts (one for v4 bcast and one for v6 bcast)? Any help in this matter will be greatly appreicated. Thanks in advance, -MU --------------------------------- Do you Yahoo!? vote.yahoo.com - Register online to vote today! --0-1429376613-1097702564=:27990 Content-Type: text/html; charset=us-ascii
Hi,
 
draft-perkins-manet-aodv6 refers to AODV support for IPv6. After reading it, i guess that AODV can support only one family at a time. Is AODV capable of supporting IPV4 and IPv6 together in a network. For example, a network having mixure of nodes (running IPv4 and IPv6) or some nodes with interfaces capabale of both IPv4 and IPv6 addressing. In a case of mixed families, how a "Hello" message will be sent out? Draft does not talk about it. Since, "Hello" message is a broadcast, if a node supports both address families, node will send out two kinds of hello pkts (one for v4 bcast and one for v6 bcast)?
 
Any help in this matter will be greatly appreicated.
 
Thanks in advance,
-MU

Do you Yahoo!?
vote.yahoo.com - Register online to vote today! --0-1429376613-1097702564=:27990-- --===============0456774542== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0456774542==-- From manet-bounces@ietf.org Wed Oct 13 18:33:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21135 for ; Wed, 13 Oct 2004 18:33:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHrrW-000251-P1 for manet-web-archive@ietf.org; Wed, 13 Oct 2004 18:44:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHraO-00070C-Lr; Wed, 13 Oct 2004 18:27:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHrS6-0002NI-41 for manet@megatron.ietf.org; Wed, 13 Oct 2004 18:18:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19505 for ; Wed, 13 Oct 2004 18:18:33 -0400 (EDT) Received: from [170.210.239.2] (helo=gtwing.efn.uncor.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHrce-0001gs-NO for manet@ietf.org; Wed, 13 Oct 2004 18:29:58 -0400 Received: from localhost (localhost [127.0.0.1]) by gtwing.efn.uncor.edu (Postfix) with ESMTP id AF354CB448 for ; Wed, 13 Oct 2004 19:19:09 -0300 (ART) Received: from gtwing.efn.uncor.edu ([127.0.0.1]) by localhost (gtwing.efn.uncor.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26604-03 for ; Wed, 13 Oct 2004 19:19:09 -0300 (ART) Received: from mendieta.lcd.efn.uncor.edu (lcd.efn.uncor.edu [200.16.19.5]) by gtwing.efn.uncor.edu (Postfix) with ESMTP id 62131CB446 for ; Wed, 13 Oct 2004 19:19:09 -0300 (ART) Date: Wed, 13 Oct 2004 19:17:25 -0300 (ART) From: Maximiliano Eschoyez X-X-Sender: meschoyez@mendieta.lcd.efn.uncor.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="-1463811071-1799151258-1097253270=:27022" Content-ID: X-Virus-Scanned: by amavisd-new at efn.uncor.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [manet] Which simulator is better to use? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463811071-1799151258-1097253270=:27022 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; FORMAT=flowed Content-ID: Content-Transfer-Encoding: QUOTED-PRINTABLE Dear all, I'm starting my Ph.D studies in ad hoc routing and I'm wondering which netw= ork=20 simulator is good enough to test and develop protocols. I've started to use NS2 because is widely known and used as reference. But,= =20 those bugs related with the 802.11 MAC code (thread of August) disapponted = me a=20 litle bit. Also, I've been using GloMoSim 2.03, but this release is a little bit older= =20 (2000) and not so well documented. As I have seen, there is a lot of contributed routing code made for OPNet, = but=20 I didn't tried it yet. So, my question is which of these (or other) simulator could you recommend = me?=20 I want to hear experiencies, pros and cons, etc. Thanks in advance! Regards, Maximiliano Eschoyez Ing. en Telecomunicaciones +-------------------------------------------+ | Laboratorio de Comunicaciones Digitales | | http://lcd.efn.uncor.edu/ | | | | Universidad Nacional de C=F3rdoba | | C=F3rdoba - Argentina | +-------------------------------------------+ ---1463811071-1799151258-1097253270=:27022 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ---1463811071-1799151258-1097253270=:27022-- From manet-bounces@ietf.org Wed Oct 13 21:22:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01865 for ; Wed, 13 Oct 2004 21:22:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHuUj-00055W-JV for manet-web-archive@ietf.org; Wed, 13 Oct 2004 21:33:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHuBt-0005Z0-K8; Wed, 13 Oct 2004 21:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHu7l-0004Dj-EW for manet@megatron.ietf.org; Wed, 13 Oct 2004 21:09:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00998 for ; Wed, 13 Oct 2004 21:09:45 -0400 (EDT) Received: from mailoff.mtu.edu ([141.219.70.111]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHuIp-0004tX-0M for manet@ietf.org; Wed, 13 Oct 2004 21:21:11 -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 i9E19hl12920 for ; Wed, 13 Oct 2004 21:09:43 -0400 (EDT) Received: from node34.edge.dcsint.mtu.edu (node34.mtu.edu [141.219.69.34]) by node5.services.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id i9E19gX9003509 for ; Wed, 13 Oct 2004 21:09:42 -0400 Received: from mail.mtu.edu (campus4.mtu.edu [141.219.70.7]) by node34.edge.dcsint.mtu.edu (8.12.11/8.12.11) with ESMTP id i9E19fYM022227 for ; Wed, 13 Oct 2004 21:09:42 -0400 (envelope-from leli@mtu.edu) Received: from node6.services.dcsint.mtu.edu (node6.mtu.edu [141.219.69.6]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id i9E19fF05224 for ; Wed, 13 Oct 2004 21:09:41 -0400 (EDT) Received: from ccgradpc3 (ccgrad-pc3.cecn.sabo.mtu.edu [141.219.193.32]) by node6.services.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with SMTP id i9E19fwT001886 for ; Wed, 13 Oct 2004 21:09:41 -0400 Message-ID: <01d201c4b18a$7bf65180$20c1db8d@ccgradpc3> From: "Leiyuan Li" To: Date: Wed, 13 Oct 2004 21:09:41 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.10.13.3 X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 0.0 (/) X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593 Content-Transfer-Encoding: 7bit Subject: [manet] [CFP] 2005 Applied Telecommunication Symposium (ATS'05) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc Content-Transfer-Encoding: 7bit Sorry if you received multiple copies of this CFP. ======================================================== Call for Papers 2005 Applied Telecommunication Symposium (ATS'05) "Modeling and Simulation Challenges in Telecommunication Systems" Part of the 2005 Spring Simulation Multiconference (SpringSim'05) Sponsored by: The Society for Modeling and Simulation International (SCS) April 2 - 8, 2005 Hilton Mission Valley Hotel San Diego, CA The Applied Telecommunication Symposium (ATS) is an international forum for exchange of technical knowledge and presentation of original papers on the analysis of telecommunication systems and technologies. It is intended for professionals, engineers, software developers, managers, and others interested in cellular and packet traffic characteristics, analysis of telecommunication networks, and practitioners operating telecommunication networks. We are looking for innovative technical papers describing projects, applications, and research and development work pertinent to telecommunication. This year's Symposium is particularly seeking papers in the following tracks: Wireless Chairs: Hassan Rajaei, Bowling Green State University, USA Axel Lehmann, Universitaet der Bundeswehr Muenchen, Germany Topics: UMTS GSM / CDMA 2.5G/3G Wireless Mobile Internet and Wireless Multimedia Cell Traffic Network Performance and Engineering Measurements SPECIAL SESSION: WLAN research with particular emphasis on QoS, routing, reliability, overload/congestion control, and interworking with 2.5/3G systems. Telecommunications Business and Regulation Chair: George Kraft, Stuart School of Business, Illinois Institute of Technology, USA Topics: Cost modeling Call center operations Billing models E-commerce Network Security and Management Chairs: Susan Lincke-Salecker, University of Wisconsin-Parkside, USA John Laskar, Mitretek Systems, USA Topics: Innovative Network Security methods WLAN Security Influence of security measures on network performance Operations, Administration, Maintenance Overload/congestion control Load balancing Networks and Multimedia Chairs: Aftab Ahmad, Norfolk State University, USA Wolfang Haidegger, Siemens, Austria Topics: Internet QoS Architectures Network performance - analysis and simulation Traffic characterization Packet switch architecture evaluation Modeling Techniques and V&V Chairs: Axel Lehmann, Universitaet der Bundeswehr Muenchen, Germany Shakil Akhtar, UAE University, Al-Ain, United Arab Emirates Topics: Simulation techniques Acceleration methods Distributed Simulation Simulation Tools for Modeling and V & V traffic measurements, analysis and synthesis Combined simulation/analytic procedures Metro area design and modeling Traffic Engineering with Protocols and Devices Chairs: Junaid Zubairi, SUNY at Fredonia, USA Chia J. Liu, AT&T Labs, USA Topics: Traffic Management and control Traffic engineering architectures Bandwidth management GMPLS VPN (Virtual Private Network) Performance Issues General Chair: Bohdan Bodnar Motorola, Inc. Co-Chair: Hassan Rajaei Bowling Green State University, USA Program Chair: George Kraft Stuart School of Business, Illinois Institute of Technology, USA Draft Paper / Extended Abstract Submission Deadline: November 1, 2004. Draft paper or extended abstract should be submitted to http://scs.proceedingscentral.com Deadlines Abstract/Draft paper due - November 1, 2004 Notification of acceptance sent - November 30, 2004 Camera-ready paper due - January 31, 2005 Please indicate in the abstract for which track(s) you wish to have your paper considered; note that the final track selection will be at the discretion of the ATS organizers. The abstract must include the author(s), e-mail address(es), and affiliation. Sponsored by The Society for Modeling and Simulation International P.O. Box 17900 San Diego, California 92177 Phone 858-277-3888 Fax 858-277-3930 E-mail scs@scs.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 01:44:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22807 for ; Thu, 14 Oct 2004 01:44:50 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHyb6-0001SK-44 for manet-web-archive@ietf.org; Thu, 14 Oct 2004 01:56:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHyO4-0006oA-1t; Thu, 14 Oct 2004 01:42:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHyMO-0006SC-H1 for manet@megatron.ietf.org; Thu, 14 Oct 2004 01:41:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22629 for ; Thu, 14 Oct 2004 01:41:07 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.202] helo=mproxy.gmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHyXU-0001OK-RA for manet@ietf.org; Thu, 14 Oct 2004 01:52:37 -0400 Received: by mproxy.gmail.com with SMTP id 75so637626rnk for ; Wed, 13 Oct 2004 22:41:05 -0700 (PDT) Received: by 10.38.24.78 with SMTP id 78mr2822409rnx; Wed, 13 Oct 2004 22:41:05 -0700 (PDT) Received: by 10.38.165.49 with HTTP; Wed, 13 Oct 2004 22:41:05 -0700 (PDT) Message-ID: Date: Thu, 14 Oct 2004 00:41:05 -0500 From: satyavalli vejendla To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] Multi Channels in Ad hoc Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: satyavalli vejendla List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit I would like to know if any one is working in Ad hoc networks using Multi Channels in Glomosim. I have few questions. Please let me know. Thanks Satya -- The secret of life is honesty and fair dealing. If you can fake that, you've got it made. -Groucho Marx _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 05:12:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21099 for ; Thu, 14 Oct 2004 05:12:28 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI1q3-00052u-Qb for manet-web-archive@ietf.org; Thu, 14 Oct 2004 05:24:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI1ZQ-0006hL-O8; Thu, 14 Oct 2004 05:06:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI1Y1-0006Ot-B1 for manet@megatron.ietf.org; Thu, 14 Oct 2004 05:05:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20684 for ; Thu, 14 Oct 2004 05:05:19 -0400 (EDT) Received: from mix.hive.no ([128.39.114.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI1j9-0004vA-4p for manet@ietf.org; Thu, 14 Oct 2004 05:16:51 -0400 Received: from [128.39.116.77] (HVE6824.hive.no [128.39.116.77]) by mix.hive.no (8.12.11/8.12.11) with ESMTP id i9E95C0x005014; Thu, 14 Oct 2004 11:05:12 +0200 From: Thomas Nordli To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1097744723.1458.8.camel@hve6824> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 14 Oct 2004 11:05:23 +0200 X-Spam-Status: No, score=-5.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on mix.hive.no Received-SPF: fail (mix.hive.no: domain of thomas.nordli@hive.no does not designate 128.39.116.77 as permitted sender) Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mix.hive.no id i9E95C0x005014 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: quoted-printable Subject: [manet] What happens with the MPRF-draft? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: quoted-printable The ietf-draft "Multipoint relay flooding for manets" (draft-perkin-manet-mprf.txt) has expired. What does it mean? Was the ideas in it no good, have someone come up with something better, or is someone working on a newer version?=20 I was thinking about implementing a MPR-mechanism, as a part of my master thesis, and found the ideas in the draft interesting. --=20 Thomas Nordli Lecturer Vestfold University College Faculty of Social Sciences P.O.Box 2243, N-3103 T=F8nsberg B.Card: http://www.hive.no/telefon/viskort.php?&pers_id=3Dtn W.Phone: (+47) 33 03 12 09 GSM: (+47) 932 97 065 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 05:58:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24807 for ; Thu, 14 Oct 2004 05:58:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI2YU-00061L-JG for manet-web-archive@ietf.org; Thu, 14 Oct 2004 06:09:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI2LU-0000qm-Sl; Thu, 14 Oct 2004 05:56:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI2HS-0008T1-FJ for manet@megatron.ietf.org; Thu, 14 Oct 2004 05:52:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24461 for ; Thu, 14 Oct 2004 05:52:15 -0400 (EDT) Received: from cheviot5.ncl.ac.uk ([128.240.233.122] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI2Sa-0005vO-Ro for manet@ietf.org; Thu, 14 Oct 2004 06:03:49 -0400 Received: from [128.240.149.114] (deerbook.ncl.ac.uk [128.240.149.114]) by cheviot5.ncl.ac.uk (8.12.11/8.12.10) with ESMTP id i9E9peA3005268; Thu, 14 Oct 2004 10:51:41 +0100 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Einar Vollset Subject: Re: [manet] Which simulator is better to use? Date: Thu, 14 Oct 2004 10:52:01 +0100 To: Maximiliano Eschoyez X-Mailer: Apple Mail (2.619) X-Newcastle-MailScanner-Information: Please contact Postmaster@newcastle.ac.uk for more information X-Newcastle-MailScanner: Found to be clean X-Newcastle-MailScanner-From: einar.vollset@ncl.ac.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Content-Transfer-Encoding: quoted-printable Hello Maximiliano, I would strongly recommend taking a look at SWANS developed by Rimon =20 Barr at Cornell. Impressive performance in terms of possible simulation sizes, =20= and also allows you to develop in Java (a bonus to me at least) and harness =20 "real" java applications to simulate. The one downside is that it's not widely used (yet), and thus has a =20 limited amount of "standard" protocols available (particularly w.r.t multicast). http://jist.ece.cornell.edu/index.html Cheers, Einar On 13 Oct 2004, at 23:17, Maximiliano Eschoyez wrote: > Dear all, > > I'm starting my Ph.D studies in ad hoc routing and I'm wondering which = =20 > network simulator is good enough to test and develop protocols. > > I've started to use NS2 because is widely known and used as reference. = =20 > But, those bugs related with the 802.11 MAC code (thread of August) =20= > disapponted me a litle bit. > > Also, I've been using GloMoSim 2.03, but this release is a little bit =20= > older (2000) and not so well documented. > > As I have seen, there is a lot of contributed routing code made for =20= > OPNet, but I didn't tried it yet. > > So, my question is which of these (or other) simulator could you =20 > recommend me? I want to hear experiencies, pros and cons, etc. > > Thanks in advance! > > Regards, > > Maximiliano Eschoyez > Ing. en Telecomunicaciones > > +-------------------------------------------+ > | Laboratorio de Comunicaciones Digitales | > | http://lcd.efn.uncor.edu/ | > | | > | Universidad Nacional de C=F3rdoba | > | C=F3rdoba - Argentina | > =20 > +-------------------------------------------=20 > +_______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 06:38:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27780 for ; Thu, 14 Oct 2004 06:38:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI3BS-0006gH-7t for manet-web-archive@ietf.org; Thu, 14 Oct 2004 06:50:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI2vB-0000X9-8R; Thu, 14 Oct 2004 06:33:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI2mM-0007Ui-EP for manet@megatron.ietf.org; Thu, 14 Oct 2004 06:24:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26604 for ; Thu, 14 Oct 2004 06:24:11 -0400 (EDT) Received: from dadar.upf.edu ([193.145.39.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI2xL-0006SC-2C for manet@ietf.org; Thu, 14 Oct 2004 06:35:45 -0400 Received: from dadar.upf.edu (localhost [127.0.0.1]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id i9EANV1g027952 for ; Thu, 14 Oct 2004 12:23:31 +0200 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186]) by dadar.upf.edu (8.12.10/8.12.10) with ESMTP id i9EANUXF027948 for ; Thu, 14 Oct 2004 12:23:31 +0200 Message-ID: <416E53D5.8010804@upf.edu> Date: Thu, 14 Oct 2004 12:24:21 +0200 From: Manel Guerrero User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] How to change de Active Route Timeout in AODV Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Hi Xavier :) Xavier M. wrote: > Hi all, > > I would like to know how to change the ACTIVE ROUTE TIMEOUT parameter in the tcl script for using it in a ns-2 simulation. I am using the AODV routing protocol. What is the default value? is it 3? what other values can be set? In the file 'ns-2.27/aodv/aodv.h' line 79 you have the '#define': 8<-------- #define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds -------->8 So the default value is 10 seconds (ignore the comment at the end of the line). You can set a different value just by replacing the '10' for whatever number of seconds you preffer. (And then recompile the thing). I don't know if there is a way to do it without changing the source code. A fast search sugests that there is no other way: 8<-------- foobar/ns-2.27/aodv$ fgrep "ACTIVE_ROUTE_TIMEOUT" * aodv.cc: // Set expiry time to CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT aodv.cc: rt0->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; aodv.cc: rt->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; aodv.h:#define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds foobar/ns-2.27/aodv$ -------->8 Hope this helps ;) Manel P.D.: I didn't know telefonica was working on this ;) > I am using the ns-allinone2.27 package and I don't know whether it can be done directly with tcl or not. > > > > thank you for your help > > Xavier M. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 09:12:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11990 for ; Thu, 14 Oct 2004 09:12:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI5a4-0001dK-Gx for manet-web-archive@ietf.org; Thu, 14 Oct 2004 09:23:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI5Ld-000173-65; Thu, 14 Oct 2004 09:08:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI5Hw-00004y-Ig for manet@megatron.ietf.org; Thu, 14 Oct 2004 09:05:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11374 for ; Thu, 14 Oct 2004 09:04:58 -0400 (EDT) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI5T5-0001Tj-DQ for manet@ietf.org; Thu, 14 Oct 2004 09:16:33 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i9ECbK513171; Thu, 14 Oct 2004 05:37:20 -0700 X-mProtect: <200410141237> Nokia Silicon Valley Messaging Protection Received: from danira-pool049137.americas.nokia.com (10.241.49.137, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdfUReI2; Thu, 14 Oct 2004 05:37:18 PDT Message-ID: <416E7949.9060206@iprg.nokia.com> Date: Thu, 14 Oct 2004 06:04:09 -0700 From: "Charles E. Perkins" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Nordli Subject: Re: [manet] What happens with the MPRF-draft? References: <1097744723.1458.8.camel@hve6824> In-Reply-To: <1097744723.1458.8.camel@hve6824> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: 7bit Hello Thomas, We intend to have a a much improved draft out soon. Regards, Charlie P. Thomas Nordli wrote: >The ietf-draft "Multipoint relay flooding for manets" >(draft-perkin-manet-mprf.txt) has expired. What does it mean? Was the >ideas in it no good, have someone come up with something better, or is >someone working on a newer version? > >I was thinking about implementing a MPR-mechanism, as a part of my >master thesis, and found the ideas in the draft interesting. > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 11:17:03 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29294 for ; Thu, 14 Oct 2004 11:17:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7Ww-0004Ue-4u for manet-web-archive@ietf.org; Thu, 14 Oct 2004 11:28:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI7Au-00012j-AN; Thu, 14 Oct 2004 11:05:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI79V-0000Ti-A8 for manet@megatron.ietf.org; Thu, 14 Oct 2004 11:04:25 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28015 for ; Thu, 14 Oct 2004 11:04:22 -0400 (EDT) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7Kf-0004G2-1s for manet@ietf.org; Thu, 14 Oct 2004 11:15:58 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i9EEaYe18312; Thu, 14 Oct 2004 07:36:34 -0700 X-mProtect: <200410141436> Nokia Silicon Valley Messaging Protection Received: from danira-pool049137.americas.nokia.com (10.241.49.137, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdtFVg7j; Thu, 14 Oct 2004 07:36:32 PDT Message-ID: <416E953B.1060007@iprg.nokia.com> Date: Thu, 14 Oct 2004 08:03:23 -0700 From: "Charles E. Perkins" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Einar Vollset , Maximiliano Eschoyez Subject: Re: [manet] Which simulator is better to use? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: 8bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 8bit Hello folks, I would recommend looking at SNS-2, also from Cornell. It is NS-2 souped up with some performance enhancements that allow large-scale simulations in much reduced time. We use it and like it. Is anyone working on improving the previously noted deficiencies of the NS-2 802.11 models (sorry I don't remember the specifics)? Regards, Charlie P. Einar Vollset wrote: > > Hello Maximiliano, > > I would strongly recommend taking a look at SWANS developed by Rimon > Barr at > Cornell. Impressive performance in terms of possible simulation > sizes, and also > allows you to develop in Java (a bonus to me at least) and harness > "real" java > applications to simulate. > The one downside is that it's not widely used (yet), and thus has a > limited amount > of "standard" protocols available (particularly w.r.t multicast). > > http://jist.ece.cornell.edu/index.html > > Cheers, > > Einar > > > On 13 Oct 2004, at 23:17, Maximiliano Eschoyez wrote: > >> Dear all, >> >> I'm starting my Ph.D studies in ad hoc routing and I'm wondering >> which network simulator is good enough to test and develop protocols. >> >> I've started to use NS2 because is widely known and used as >> reference. But, those bugs related with the 802.11 MAC code (thread >> of August) disapponted me a litle bit. >> >> Also, I've been using GloMoSim 2.03, but this release is a little >> bit older (2000) and not so well documented. >> >> As I have seen, there is a lot of contributed routing code made for >> OPNet, but I didn't tried it yet. >> >> So, my question is which of these (or other) simulator could you >> recommend me? I want to hear experiencies, pros and cons, etc. >> >> Thanks in advance! >> >> Regards, >> >> Maximiliano Eschoyez >> Ing. en Telecomunicaciones >> >> +-------------------------------------------+ >> | Laboratorio de Comunicaciones Digitales | >> | http://lcd.efn.uncor.edu/ | >> | | >> | Universidad Nacional de Csrdoba | >> | Csrdoba - Argentina | >> +------------------------------------------- >> +_______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 12:52:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06658 for ; Thu, 14 Oct 2004 12:52:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI91G-0006Zy-MQ for manet-web-archive@ietf.org; Thu, 14 Oct 2004 13:04:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI8du-0002ec-KJ; Thu, 14 Oct 2004 12:39:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI8XA-0000rF-IU for manet@megatron.ietf.org; Thu, 14 Oct 2004 12:32:56 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05287 for ; Thu, 14 Oct 2004 12:32:54 -0400 (EDT) From: kvadde@asu.edu Received: from post5.inre.asu.edu ([129.219.110.120]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI8iM-00069r-Su for manet@ietf.org; Thu, 14 Oct 2004 12:44:31 -0400 Received: from conversion.post5.inre.asu.edu by asu.edu (PMDF V6.1-1X6 #30769) id <0I5L000011SVSP@asu.edu> for manet@ietf.org; Thu, 14 Oct 2004 09:29:19 -0700 (MST) Received: from smtp.asu.edu (smtp.asu.edu [129.219.110.107]) by asu.edu (PMDF V6.1-1X6 #30769) with ESMTP id <0I5L0006L1STJ8@asu.edu>; Thu, 14 Oct 2004 09:29:17 -0700 (MST) Received: from general3.asu.edu (general3.asu.edu [129.219.10.243]) by smtp.asu.edu (8.12.10/8.12.10/asu_smtp_relay, nullclient, tcp_wrapped) with ESMTP id i9EGTG72001016; Thu, 14 Oct 2004 09:29:17 -0700 (MST) Date: Thu, 14 Oct 2004 09:29:16 -0700 (MST) Subject: Re: [manet] How to change de Active Route Timeout in AODV In-reply-to: <416E53D5.8010804@upf.edu> X-Sender: kvadde@general3.asu.edu To: Manel Guerrero Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.3 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Hi, You can change it in the tcl script too. In AODV.cc, bind the variable using bind("actrttout",&ACTIVE_ROUTE_TIMEOUT); and in the tcl file use Agent/AODV set actrttout $opt(val) where $opt(val) is the actual value. Hope this helps Thanks Kiran Vadde On Thu, 14 Oct 2004, Manel Guerrero wrote: > Hi Xavier :) > > Xavier M. wrote: > > > Hi all, > > > > I would like to know how to change the ACTIVE ROUTE TIMEOUT parameter in the tcl script for using it in a ns-2 simulation. I am using the AODV routing protocol. What is the default value? is it 3? what other values can be set? > > > In the file 'ns-2.27/aodv/aodv.h' > line 79 you have the '#define': > > 8<-------- > #define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > -------->8 > > So the default value is 10 seconds (ignore the comment at the end of the line). > > You can set a different value just by replacing the '10' for whatever number > of seconds you preffer. (And then recompile the thing). > > I don't know if there is a way to do it without changing the source code. > A fast search sugests that there is no other way: > > 8<-------- > foobar/ns-2.27/aodv$ fgrep "ACTIVE_ROUTE_TIMEOUT" * > aodv.cc: // Set expiry time to CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT > aodv.cc: rt0->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > aodv.cc: rt->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > aodv.h:#define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > foobar/ns-2.27/aodv$ > -------->8 > > Hope this helps ;) > > Manel > > P.D.: I didn't know telefonica was working on this ;) > > > I am using the ns-allinone2.27 package and I don't know whether it can be done directly with tcl or not. > > > > > > > > thank you for your help > > > > Xavier M. > > > > _______________________________________________ > > 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 > Kiran Vadde Graduate Research Associate Dept. of Computer Science and Eng. Arizona State University _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 14 15:39:52 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20521 for ; Thu, 14 Oct 2004 15:39:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIBdJ-0001Zu-CQ for manet-web-archive@ietf.org; Thu, 14 Oct 2004 15:51:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIBPP-0004zl-M7; Thu, 14 Oct 2004 15:37:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIBLv-0003Fq-7r for manet@megatron.ietf.org; Thu, 14 Oct 2004 15:33:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19119 for ; Thu, 14 Oct 2004 15:33:29 -0400 (EDT) Received: from [203.199.83.31] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIBX8-0001JH-41 for manet@ietf.org; Thu, 14 Oct 2004 15:45:07 -0400 Received: (qmail 14589 invoked by uid 510); 14 Oct 2004 19:32:59 -0000 Date: 14 Oct 2004 19:32:59 -0000 Message-ID: <20041014193259.14588.qmail@webmail46.rediffmail.com> Received: from unknown (203.94.197.115) by rediffmail.com via HTTP; 14 oct 2004 19:32:59 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Subject: [manet] prob in 'make' X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0198140149==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c This is a multipart mime message --===============0198140149== Content-type: multipart/alternative; boundary="Next_1097782379---0-203.199.83.31-14585" This is a multipart mime message --Next_1097782379---0-203.199.83.31-14585 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahi every one
=0Ai am trying to install glomosim in = linux but facing prob at the time of make can any one help:
=0A
=0Ai = have installed glomosim in root folder and parsec red hat 7.2 in \usr\local= folder.after this i have set path export PCC_DIRECTORY=3D/usr/local/parsec= .then went to glomosim main n then did  make but sfter this its gettin= g this error:
=0A
=0A
=0A[root@localhost main]# make
=0Apcc -g = -O3 -I../include/ -I../transport -I../transport/tcp -I../application -I../m= ac -I../main -I../network -I../radio -clock longlong -lm -c ../main/glomo.p= c
=0Amake: pcc: Command not found
=0Amake: *** [../main/glomo.o] Erro= r 127
=0A[root@localhost main]#
=0A
=0Acan u plz suggest why i am = unable to make.i have installed linux red hat 9.0.
=0A
=0Acan any one= help.
=0A
=0A =0A

=0A

=0A=0A --Next_1097782379---0-203.199.83.31-14585 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahi every one =0Ai am trying to install glomosim in linux but facing = prob at the time of make can any one help:=0A=0Ai have installed glomosim i= n root folder and parsec red hat 7.2 in \usr\local folder.after this i have= set path export PCC_DIRECTORY=3D/usr/local/parsec.then went to glomosim ma= in n then did make but sfter this its getting this error:=0A=0A=0A[root@lo= calhost main]# make=0Apcc -g -O3 -I../include/ -I../transport -I../transpor= t/tcp -I../application -I../mac -I../main -I../network -I../radio -clock lo= nglong -lm -c ../main/glomo.pc=0Amake: pcc: Command not found=0Amake: *** [= ../main/glomo.o] Error 127=0A[root@localhost main]#=0A=0Acan u plz suggest = why i am unable to make.i have installed linux red hat 9.0.=0A=0Acan any on= e help.=0A=0A=20 --Next_1097782379---0-203.199.83.31-14585-- --===============0198140149== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0198140149==-- From manet-bounces@ietf.org Thu Oct 14 18:17:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13514 for ; Thu, 14 Oct 2004 18:17:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIE5Q-0007YP-M6 for manet-web-archive@ietf.org; Thu, 14 Oct 2004 18:28:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIDn0-0003mA-Bw; Thu, 14 Oct 2004 18:09:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIDg5-0000F1-CG for manet@megatron.ietf.org; Thu, 14 Oct 2004 18:02:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11475 for ; Thu, 14 Oct 2004 18:02:26 -0400 (EDT) Received: from smtp.telefonica.net ([213.4.129.135] helo=tnetsmtp1.mail.isp) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIDr9-0007FC-V5 for manet@ietf.org; Thu, 14 Oct 2004 18:14:06 -0400 Received: from workspace ([80.38.46.159]) by tnetsmtp1.mail.isp (terra.es) with ESMTP id I5LH7L01.VE6; Fri, 15 Oct 2004 00:02:11 +0200 Message-ID: <001701c4b239$7f0f36c0$0301a8c0@workspace> From: "Xavier Marchador" To: , "Manel Guerrero" References: Subject: Re: [manet] How to change de Active Route Timeout in AODV Date: Fri, 15 Oct 2004 00:02:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.0 (/) X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Content-Transfer-Encoding: 7bit Hi all, I'll try this too. By the way, what is bind? it's a function? a C++ command? I've never used it before. thanks Xavi ----- Original Message ----- From: To: "Manel Guerrero" Cc: Sent: Thursday, October 14, 2004 6:29 PM Subject: Re: [manet] How to change de Active Route Timeout in AODV > Hi, > > You can change it in the tcl script too. > In AODV.cc, bind the variable using > bind("actrttout",&ACTIVE_ROUTE_TIMEOUT); > and in the tcl file use > > Agent/AODV set actrttout $opt(val) > > where $opt(val) is the actual value. > > Hope this helps > > Thanks > Kiran Vadde > > > On Thu, 14 Oct 2004, Manel Guerrero wrote: > > > Hi Xavier :) > > > > Xavier M. wrote: > > > > > Hi all, > > > > > > I would like to know how to change the ACTIVE ROUTE TIMEOUT parameter in the tcl script for using it in a ns-2 simulation. I am using the AODV routing protocol. What is the default value? is it 3? what other values can be set? > > > > > > In the file 'ns-2.27/aodv/aodv.h' > > line 79 you have the '#define': > > > > 8<-------- > > #define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > > -------->8 > > > > So the default value is 10 seconds (ignore the comment at the end of the line). > > > > You can set a different value just by replacing the '10' for whatever number > > of seconds you preffer. (And then recompile the thing). > > > > I don't know if there is a way to do it without changing the source code. > > A fast search sugests that there is no other way: > > > > 8<-------- > > foobar/ns-2.27/aodv$ fgrep "ACTIVE_ROUTE_TIMEOUT" * > > aodv.cc: // Set expiry time to CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT > > aodv.cc: rt0->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > > aodv.cc: rt->rt_expire = CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > > aodv.h:#define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > > foobar/ns-2.27/aodv$ > > -------->8 > > > > Hope this helps ;) > > > > Manel > > > > P.D.: I didn't know telefonica was working on this ;) > > > > > I am using the ns-allinone2.27 package and I don't know whether it can be done directly with tcl or not. > > > > > > > > > > > > thank you for your help > > > > > > Xavier M. > > > > > > _______________________________________________ > > > 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 > > > > Kiran Vadde > Graduate Research Associate > Dept. of Computer Science and Eng. > Arizona State University > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 15 10:20:42 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04747 for ; Fri, 15 Oct 2004 10:20:42 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIT8A-0000CB-9X for manet-web-archive@ietf.org; Fri, 15 Oct 2004 10:32:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIStU-0003S3-VP; Fri, 15 Oct 2004 10:17:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CISr8-0002xZ-HR for manet@megatron.ietf.org; Fri, 15 Oct 2004 10:14:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03750 for ; Fri, 15 Oct 2004 10:14:51 -0400 (EDT) Received: from smtp25.singnet.com.sg ([165.21.101.224]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIT2T-0008UU-RW for manet@ietf.org; Fri, 15 Oct 2004 10:26:40 -0400 Received: from bearty1 (qtas0139.singnet.com.sg [165.21.56.49]) by smtp25.singnet.com.sg (8.13.1/8.13.1) with SMTP id i9FEEcbd017753 for ; Fri, 15 Oct 2004 22:14:39 +0800 Message-ID: <005401c4b2c1$53031640$313815a5@bearty1> From: "Boon Yeo" To: Subject: [manet] WOCN 2005 CFP Date: Fri, 15 Oct 2004 22:14:39 +0800 MIME-Version: 1.0 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-Spam-Score: 0.1 (/) X-Scan-Signature: 5d99cba2a085c3987933aa34e30e85ab X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1846901449==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 2af167865907217f0b49c659e31a77f7 This is a multi-part message in MIME format. --===============1846901449== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0051_01C4B304.5D2392B0" This is a multi-part message in MIME format. ------=_NextPart_000_0051_01C4B304.5D2392B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable **Apologies for multiple copies** Call for Papers=20 Second IFIP International Conference on Wireless and Optical = Communications Networks WOCN 2005 =20 March 6 - 9, 2005, Dubai, United Arab Emirates UAE Paper Submission=20 http://www.wocn2005.org=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Sponsored by IFIPTC6 WG6.8 (Mobile and Wireless Communications),=20 WG6.6 (Management of Networks and Distributed Systems), WG6.10 (Photonic = Networking) Technically sponsored by IEEE Communication Society Endorsed by: IEEE ComSoc Technical Committee on Information Infrastructure (TCII),=20 IEEE ComSoc Technical Committee on Personal Communications (TCPC) =20 =20 The Second IFIP International Conference on wireless and Optical = Communications Networks (WOCN 2005) invites high-quality recent research = results in the areas of Mobile and Wireless Communications, optical = communications and networking, architectures, protocols, planning and = design, management and operation. The main goal of the conference is to = bring together scientists and engineers who work on wireless and optical = communications networks. The Second IEEE and IFIP International = Conference on Wireless and Optical Communications Networks (WOCN 2005) = will be held in Dubai, United Arab Emirates March 2005. WOCN 2005 is the = second conference in its series aimed at stimulating technical exchange = in the emerging and important field of mobile, wireless and Optical = communications networks. WOCN 2005 seeks to address and capture highly = innovative and state of the art research and work in the wireless and = Optical industries. The scope of the conference includes a wide range of = techni....... as optic al amplifier, tunable filters, transceivers, termination devices and = add-drop multi-plexers are becoming more affordable and reliable. Access = and metropolitan area networks are increasingly built with optical = technologies to overcome the electronic bottleneck at network edges. New = components and subsystems for high-speed optical networks offer new = design options. The objective of this event is therefore to foster the = exchange of information among researchers in this fast-moving field. The = authors can present their finding on new Fibers, optical fiber gratings = and devices, optical amplifiers, optical sensing and medical application = of fiber optics and opto-electronics.=20 Important Dates=20 Paper Submissions Deadline: December 15, 2004=20 Notification of Acceptance: January 1, 2005=20 Camera Ready Versions Due: January 15, 2005=20 Information for Contributors=20 Contributions are invited on all topics concerning wireless and optical = communications networks and components. We are soliciting original = papers describing the state-of-the-art research and development in the = areas of wireless and Optical Communication and Networks, including, but = not limited to the following topics:=20 Topics of Interest=20 1. Optical Networking Technologies=20 * Optical network planning, design and modelling =20 * Optical access/metro networks =20 * IP over optical networks =20 * Network protection/restoration =20 * Generalised multi-protocol label switching (GMPLS) =20 * Planning and design tools for optical networks =20 * QoS issues in optical networks =20 * Routing and wavelength assignment =20 * Multiple access technique and fairness control in optical LANs and = MANs =20 2. Optical Switching and Network Elements=20 * Photonic switching system architectures =20 * Optical cross-connects and add-drop multiplexers =20 * Optical IP routers =20 * Photonic packet switching =20 * Network signalling and monitoring techniques =20 * Optical signal processing =20 * Wavelength conversion techniques =20 3. Optical Transmission Technologies=20 * WDM Ultra-long haul transmission systems =20 * OTDM transmission systems =20 * Soliton transmission systems =20 * Transmission system experiments =20 * Radio over fibre-optics =20 * Optical interconnections =20 * Optical interfaces and terminals =20 4. Optical Passive Components=20 * Fiber-Bragg-grating-based devices =20 * Fiber-grating dispersion compensators =20 * Optical circulators and isolators =20 * Optical waveguide-based devices =20 * Fiber and waveguide filters =20 * Microstructured waveguides and devices =20 * Arrayed waveguide devices =20 * Optical splitting and directional couplers =20 5. Optical Active Components and Modules=20 * Optical modulators and switches =20 * Semiconductor optical amplifiers =20 * Semiconductor lasers and detectors =20 * Fibre amplifiers and lasers =20 * Raman and Brillouin amplifiers =20 * Automatic gain control of optical amplifiers =20 * Optical MEMS =20 * Photonic integrated circuits/modules =20 * Optical tunable filters =20 * Optical logics and memories =20 Mobile and Wireless Communications topics of interest include but are = not limited to the following: =20 1. Management Resource and Information Management =20 * Pricing and Billing Issues =20 2. Architecture=20 * Convergence of Fixed and Mobile =20 * Hybrid Communications System =20 3. Devices=20 * Low-Power End-Devices and Wireless Communications =20 4. Security=20 * Security in Mobile and Wireless Networks =20 5. QoS=20 * Adaptive Quality of Service Provisioning =20 * End-to-end Quality of Service =20 6. Mobility Support=20 * Handoff Algorithms =20 * IP and Mobility =20 * Mobility and Connection Management in Heterogeneous Wireless = Networks =20 * Policy-based Mobility Management =20 7. Applications=20 * Personal Communications =20 * Location and Context Management =20 * Smart Media =20 * Mobile Code =20 * Mobile Ad-Hoc Networks Applications =20 8. Access=20 * Wireless IP =20 * Wireless Multimedia Services =20 * Wireless Local Loop (WLL) =20 * Multiple Access Technology =20 * Broadband Wireless Access =20 9. Networking=20 * Wireless Personal Area Networks =20 * Wireless Local Area Networks =20 * Mobility and Nomadic Computing =20 * Analysis and Simulation of Mobile Network Protocols =20 * Home Networking =20 * Mobile Ad-hoc Networks and the Internet =20 * Mobile Ad-Hoc Networking Routing =20 * Satellite Networks =20 Paper Submission Guidelines=20 Authors are requested to submit electronically a PDF or Word file to Dr. = Boon Sain Yeo, yeobs@i2r.a-star.edu.sg . = Papers should be written in English and should preferably follow the = instructions in . Preferred maximum paper length is 5 = printed pages (10-point font) including figures. IEEE will accept papers = for review up to 7 pages in length. Accepted papers that are longer than = 5 pages will be charged an over length fee of $100 USD for 6 pages and = $200 USD for 7 pages. Under no circumstances may any submission should = exceed 7 pages. Papers in excess of 7 pages shall not be considered for = review or publication. The cover page is not included in the page count. = The title of the paper, author's name, affiliation, complete return = address, telephone number, facsimile number and e-mail address should = appear at the top of the first page followed by an abstract with a = maximum of 100 words. Authors must state that their paper has neither = been pu..... Please contact: Dr. Boon Sain Yeo @ yeobs@i2r.a-star.edu.sg Panels and Tutorials=20 For information on submitting proposals for Panels and Tutorials,=20 Please contact: nazar@squ.edu.om or guy.omidyar@ieee.org=20 Organising Committee=20 General Chair: Professor Guy Omidyar, USA=20 General co-chairs: Dr. Eesa M. Bastaki, IEEE UAE Section chair: Abdullah I. Lootah, Vice Chairman Lootah Group=20 General Vice Chair: Abdumunam Lootah, UAE=20 Program co-Chairs:=20 Dr. Boon Sain Yeo, I2R Singapore Professor Maurice Gagnaire, ENST, France=20 Tutorials Chairs: Dr. Nazar Elfadil=20 Treasurer: Dr. Naser Nick Manochehri =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Please visit the WOCN 2005 home page http://www.wocn2005.org for more = information about the conference.=20 =20 ------=_NextPart_000_0051_01C4B304.5D2392B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
**Apologies for multiple = copies**
 
Call for Papers
 
Second IFIP International Conference = on =20 Wireless and Optical Communications Networks WOCN 2005 
March 6 = - 9,=20 2005, Dubai, United Arab Emirates UAE  Paper Submission =
 
http://www.wocn2005.org=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /FONT>
 
Sponsored by IFIPTC6 WG6.8 (Mobile and = Wireless=20 Communications),
WG6.6 (Management of Networks and Distributed = Systems),=20 WG6.10 (Photonic Networking)
 
Technically sponsored by IEEE = Communication=20 Society
 
Endorsed by:
IEEE ComSoc Technical = Committee on=20 Information Infrastructure (TCII),
IEEE ComSoc Technical Committee = on=20 Personal Communications (TCPC)  
 
          &nbs= p;    =20
The Second IFIP International Conference on wireless and Optical=20 Communications Networks (WOCN 2005) invites high-quality recent research = results=20 in the areas of Mobile and Wireless Communications, optical = communications and=20 networking, architectures, protocols, planning and design, management = and=20 operation. The main goal of the conference is to bring together = scientists and=20 engineers who work on wireless and optical communications networks. The = Second=20 IEEE and IFIP International Conference on Wireless and Optical = Communications=20 Networks (WOCN 2005) will be held in Dubai, United Arab Emirates March = 2005.=20 WOCN 2005 is the second conference in its series aimed at stimulating = technical=20 exchange in the emerging and important field of mobile, wireless and = Optical=20 communications networks. WOCN 2005 seeks to address and capture highly=20 innovative and state of the art research and work in the wireless and = Optical=20 industries. The scope of the conference includes a wide range of=20 techni.......
 as optic
al amplifier, tunable filters, = transceivers,=20 termination devices and add-drop multi-plexers are becoming more = affordable and=20 reliable. Access and metropolitan area networks are increasingly built = with=20 optical technologies to overcome the electronic bottleneck at network = edges. New=20 components and subsystems for high-speed optical networks offer new = design=20 options. The objective of this event is therefore to foster the exchange = of=20 information among researchers in this fast-moving field. The authors can = present=20 their finding on new Fibers, optical fiber gratings and devices, optical = amplifiers, optical sensing and medical application of fiber optics and=20 opto-electronics.
 

Important Dates
 
Paper Submissions Deadline: December 15, 2004
Notification of=20 Acceptance: January 1, 2005
Camera Ready Versions Due: January 15, = 2005=20
 

Information for Contributors
 
Contributions are invited on all topics concerning wireless and = optical=20 communications networks and components. We are soliciting original = papers=20 describing the state-of-the-art research and development in the areas of = wireless and Optical Communication and Networks, including, but not = limited to=20 the following topics:
 
Topics of Interest
 
    1. Optical Networking Technologies=20
    * Optical network planning, design and = modelling =20
    * Optical access/metro networks =20
    * IP over optical networks  =
    *=20 Network protection/restoration 
    * = Generalised=20 multi-protocol label switching (GMPLS) 
    * = Planning=20 and design tools for optical networks 
    * QoS = issues=20 in optical networks 
    * Routing and = wavelength=20 assignment 
    * Multiple access technique and = fairness=20 control in optical LANs and MANs 
 
    2. Optical Switching and Network Elements=20
    * Photonic switching system architectures =20
    * Optical cross-connects and add-drop = multiplexers =20
    * Optical IP routers 
    = *=20 Photonic packet switching 
    * Network = signalling and=20 monitoring techniques 
    * Optical signal=20 processing 
    * Wavelength conversion = techniques =20
 
    3. Optical Transmission Technologies=20
    * WDM Ultra-long haul transmission systems =20
    * OTDM transmission systems  =
   =20 * Soliton transmission systems 
    * = Transmission=20 system experiments 
    * Radio over = fibre-optics =20
    * Optical interconnections  =
    *=20 Optical interfaces and terminals 
 
    4. Optical Passive Components =
    *=20 Fiber-Bragg-grating-based devices 
    * = Fiber-grating=20 dispersion compensators 
    * Optical = circulators and=20 isolators 
    * Optical waveguide-based = devices =20
    * Fiber and waveguide filters =20
    * Microstructured waveguides and devices =20
    * Arrayed waveguide devices  =
   =20 * Optical splitting and directional couplers 
 
    5. Optical Active Components and Modules=20
    * Optical modulators and switches =20
    * Semiconductor optical amplifiers =20
    * Semiconductor lasers and detectors =20
    * Fibre amplifiers and lasers =20
    * Raman and Brillouin amplifiers =20
    * Automatic gain control of optical = amplifiers =20
    * Optical MEMS 
    * = Photonic=20 integrated circuits/modules 
    * Optical = tunable=20 filters 
    * Optical logics and = memories  =20
 

Mobile and Wireless Communications topics of interest include = but are=20 not limited to the following: 
 
    1. Management Resource and Information = Management =20
    * Pricing and Billing Issues 
 
    2. Architecture
    * = Convergence of=20 Fixed and Mobile 
    * Hybrid Communications=20 System 
 
    3. Devices
    * Low-Power=20 End-Devices and Wireless Communications 
 
    4. Security
    * Security in = Mobile=20 and Wireless Networks 
 
    5. QoS
    * Adaptive Quality = of=20 Service Provisioning 
    * End-to-end Quality = of=20 Service 
 
    6. Mobility Support
    * = Handoff=20 Algorithms 
    * IP and Mobility =20
    * Mobility and Connection Management in = Heterogeneous=20 Wireless Networks 
    * Policy-based Mobility=20 Management 
 
    7. Applications
    * = Personal=20 Communications 
    * Location and Context=20 Management 
    * Smart Media =20
    * Mobile Code 
    * = Mobile=20 Ad-Hoc Networks Applications 
 
    8. Access
    * Wireless = IP =20
    * Wireless Multimedia Services =20
    * Wireless Local Loop (WLL)  =
   =20 * Multiple Access Technology 
    * Broadband = Wireless=20 Access 
 
    9. Networking
    * Wireless = Personal=20 Area Networks 
    * Wireless Local Area = Networks =20
    * Mobility and Nomadic Computing =20
    * Analysis and Simulation of Mobile Network=20 Protocols 
    * Home Networking =20
    * Mobile Ad-hoc Networks and the Internet =20
    * Mobile Ad-Hoc Networking Routing =20
    * Satellite Networks   
 
 
 
Paper Submission Guidelines
 
Authors are requested to submit electronically a PDF or Word file = to Dr.=20 Boon Sain Yeo, yeobs@i2r.a-star.edu.sg = <mailto:yeobs@i2r.a-star.edu.sg>.=20 Papers should be written in English and should preferably follow the=20 instructions in <Template.pdf>. Preferred maximum paper length is = 5=20 printed pages (10-point font) including figures. IEEE will accept papers = for=20 review up to 7 pages in length. Accepted papers that are longer than 5 = pages=20 will be charged an over length fee of $100 USD for 6 pages and $200 USD = for 7=20 pages. Under no circumstances may any submission should exceed 7 pages. = Papers=20 in excess of 7 pages shall not be considered for review or publication. = The=20 cover page is not included in the page count. The title of the paper, = author's=20 name, affiliation, complete return address, telephone number, facsimile = number=20 and e-mail address should appear at the top of the first page followed = by an=20 abstract with a maximum of 100 words. Authors must state that their = paper has=20 neither been pu.....
 
Please contact: Dr. Boon Sain Yeo @ yeobs@i2r.a-star.edu.sg
=
 

Panels and Tutorials
 
For information on submitting proposals for Panels and Tutorials,=20
Please contact: nazar@squ.edu.om or guy.omidyar@ieee.org
 

Organising Committee
 
General Chair: Professor Guy Omidyar, USA
General co-chairs: = Dr. Eesa=20 M. Bastaki, IEEE UAE
Section chair: Abdullah I. Lootah, Vice Chairman = Lootah=20 Group
General Vice Chair: Abdumunam Lootah, UAE
Program = co-Chairs:=20
Dr. Boon Sain Yeo, I2R Singapore
Professor Maurice Gagnaire, = ENST, France=20
Tutorials Chairs: Dr. Nazar Elfadil
Treasurer: Dr. Naser Nick=20 Manochehri
 
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /DIV>
 
Please visit the WOCN 2005 home page http://www.wocn2005.org for more = information=20 about the conference.
 

 
 
 
------=_NextPart_000_0051_01C4B304.5D2392B0-- --===============1846901449== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1846901449==-- From manet-bounces@ietf.org Sun Oct 17 18:43:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01603 for ; Sun, 17 Oct 2004 18:43:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJJwY-0000dF-90 for manet-web-archive@ietf.org; Sun, 17 Oct 2004 18:56:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJJgF-0005mq-4B; Sun, 17 Oct 2004 18:39:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJJeM-0005ct-MK for manet@megatron.ietf.org; Sun, 17 Oct 2004 18:37:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01391 for ; Sun, 17 Oct 2004 18:37:11 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.196] helo=mproxy.gmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJJqE-0000Xc-8Z for manet@ietf.org; Sun, 17 Oct 2004 18:49:30 -0400 Received: by mproxy.gmail.com with SMTP id 73so288189rnl for ; Sun, 17 Oct 2004 15:37:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=JAU19aGLdalTjPcHvL3xUhzXafUyXK5eQmp5eju4O+49hWih596aJrJhOeXGZh21nlwCmBarLXe2Ux2fwJz/q/eU6sFhwmlaLCQBVoADEgM3arYxp85lE4cowIamBdeq/gZvY/24UYiRHulhW7oTUpyULSXZoCdbVnf/lsE7lbI Received: by 10.38.22.51 with SMTP id 51mr1150822rnv; Sun, 17 Oct 2004 15:37:12 -0700 (PDT) Received: by 10.38.165.22 with HTTP; Sun, 17 Oct 2004 15:37:12 -0700 (PDT) Message-ID: <171bc3041017153757a99226@mail.gmail.com> Date: Sun, 17 Oct 2004 15:37:12 -0700 From: Chetan N To: manet@ietf.org In-Reply-To: <3139833628382544463@unknownmsgid> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable References: <3139833628382544463@unknownmsgid> X-Spam-Score: 0.0 (/) X-Scan-Signature: ebd5ffc455fd7bcccba963126e1cf1f5 Content-Transfer-Encoding: quoted-printable Subject: [manet] Re: manet Digest, Vol 6, Issue 19 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chetan N List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b271b9c4fc51b08326fa0949e61c0156 Content-Transfer-Encoding: quoted-printable Hi everyone, I am having a few problems configuring Swans, I compiled the code but got the this message when I tried to run it, thanks for the comments D:\others\chetan\adhoc\swans_src\src>jist jist.swans.Main Error: no `server' JVM at `C:\Program Files\Java\j2re1.5.0\bin\server\jvm.d= ll'. My jre is in d: drive but I have set the path to include this. Thanks, chetan On Fri Oct 15 07:26:06 PDT 2004, manet-request@ietf.org wrote: > Send manet mailing list submissions to > manet@ietf.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > https://www1.ietf.org/mailman/listinfo/manet > or, via email, send a message with subject or body 'help' to > manet-request@ietf.org >=20 > You can reach the person managing the list at > manet-owner@ietf.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of manet digest..." >=20 > Today's Topics: >=20 > 1. Re: How to change de Active Route Timeout in AODV (kvadde@asu.edu) > 2. prob in 'make' (anjali mihir) > 3. Re: How to change de Active Route Timeout in AODV > (Xavier Marchador) > 4. WOCN 2005 CFP (Boon Yeo) >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Thu, 14 Oct 2004 09:29:16 -0700 (MST) > From: kvadde@asu.edu > Subject: Re: [manet] How to change de Active Route Timeout in AODV > To: Manel Guerrero > Cc: manet@ietf.org > Message-ID: > > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII >=20 > Hi, >=20 > You can change it in the tcl script too. > In AODV.cc, bind the variable using > bind("actrttout",&ACTIVE_ROUTE_TIMEOUT); > and in the tcl file use >=20 > Agent/AODV set actrttout $opt(val) >=20 > where $opt(val) is the actual value. >=20 > Hope this helps >=20 > Thanks > Kiran Vadde >=20 > On Thu, 14 Oct 2004, Manel Guerrero wrote: >=20 > > Hi Xavier :) > > > > Xavier M. wrote: > > > > > Hi all, > > > > > > I would like to know how to change the ACTIVE ROUTE TIMEOUT paramete= r in the tcl script for using it in a ns-2 simulation. I am using the AODV = routing protocol. What is the default value? is it 3? what other values can= be set? > > > > > > In the file 'ns-2.27/aodv/aodv.h' > > line 79 you have the '#define': > > > > 8<-------- > > #define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > > -------->8 > > > > So the default value is 10 seconds (ignore the comment at the end of th= e line). > > > > You can set a different value just by replacing the '10' for whatever n= umber > > of seconds you preffer. (And then recompile the thing). > > > > I don't know if there is a way to do it without changing the source cod= e. > > A fast search sugests that there is no other way: > > > > 8<-------- > > foobar/ns-2.27/aodv$ fgrep "ACTIVE_ROUTE_TIMEOUT" * > > aodv.cc: // Set expiry time to CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT > > aodv.cc: rt0->rt_expire =3D CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > > aodv.cc: rt->rt_expire =3D CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > > aodv.h:#define ACTIVE_ROUTE_TIMEOUT 10 = // 50 seconds > > foobar/ns-2.27/aodv$ > > -------->8 > > > > Hope this helps ;) > > > > Manel > > > > P.D.: I didn't know telefonica was working on this ;) > > > > > I am using the ns-allinone2.27 package and I don't know whether it c= an be done directly with tcl or not. > > > > > > > > > > > > thank you for your help > > > > > > Xavier M. > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 > Kiran Vadde > Graduate Research Associate > Dept. of Computer Science and Eng. > Arizona State University >=20 > ------------------------------ >=20 > Message: 2 > Date: 14 Oct 2004 19:32:59 -0000 > From: "anjali mihir" > Subject: [manet] prob in 'make' > To: manet@ietf.org > Message-ID: <20041014193259.14588.qmail@webmail46.rediffmail.com> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > An HTML attachment was scrubbed... > URL: http://www1.ietf.org/pipermail/manet/attachments/20041014/09dd3c81/a= ttachment.htm > -------------- next part -------------- > =20 > hi every one > i am trying to install glomosim in linux but facing prob at the time of m= ake can any one help: >=20 > i have installed glomosim in root folder and parsec red hat 7.2 in \usr\l= ocal folder.after this i have set path export PCC_DIRECTORY=3D/usr/local/pa= rsec.then went to glomosim main n then did make but sfter this its getting= this error: >=20 > [root@localhost main]# make > pcc -g -O3 -I../include/ -I../transport -I../transport/tcp -I../applicati= on -I../mac -I../main -I../network -I../radio -clock longlong -lm -c ../mai= n/glomo.pc > make: pcc: Command not found > make: *** [../main/glomo.o] Error 127 > [root@localhost main]# >=20 > can u plz suggest why i am unable to make.i have installed linux red hat = 9.0. >=20 > can any one help. >=20 > ------------------------------ >=20 > Message: 3 > Date: Fri, 15 Oct 2004 00:02:25 +0200 > From: "Xavier Marchador" > Subject: Re: [manet] How to change de Active Route Timeout in AODV > To: , "Manel Guerrero" > Cc: manet@ietf.org > Message-ID: <001701c4b239$7f0f36c0$0301a8c0@workspace> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > Hi all, >=20 > I'll try this too. By the way, what is bind? it's a function? a C++ comma= nd? > I've never used it before. >=20 > thanks >=20 > Xavi >=20 > ----- Original Message ----- > From: > To: "Manel Guerrero" > Cc: > Sent: Thursday, October 14, 2004 6:29 PM > Subject: Re: [manet] How to change de Active Route Timeout in AODV >=20 > > Hi, > > > > You can change it in the tcl script too. > > In AODV.cc, bind the variable using > > bind("actrttout",&ACTIVE_ROUTE_TIMEOUT); > > and in the tcl file use > > > > Agent/AODV set actrttout $opt(val) > > > > where $opt(val) is the actual value. > > > > Hope this helps > > > > Thanks > > Kiran Vadde > > > > > > On Thu, 14 Oct 2004, Manel Guerrero wrote: > > > > > Hi Xavier :) > > > > > > Xavier M. wrote: > > > > > > > Hi all, > > > > > > > > I would like to know how to change the ACTIVE ROUTE TIMEOUT parame= ter > in the tcl script for using it in a ns-2 simulation. I am using the AODV > routing protocol. What is the default value? is it 3? what other values c= an > be set? > > > > > > > > > In the file 'ns-2.27/aodv/aodv.h' > > > line 79 you have the '#define': > > > > > > 8<-------- > > > #define ACTIVE_ROUTE_TIMEOUT 10 // 50 seconds > > > -------->8 > > > > > > So the default value is 10 seconds (ignore the comment at the end of = the > line). > > > > > > You can set a different value just by replacing the '10' for whatever > number > > > of seconds you preffer. (And then recompile the thing). > > > > > > I don't know if there is a way to do it without changing the source > code. > > > A fast search sugests that there is no other way: > > > > > > 8<-------- > > > foobar/ns-2.27/aodv$ fgrep "ACTIVE_ROUTE_TIMEOUT" * > > > aodv.cc: // Set expiry time to CURRENT_TIME + ACTIVE_ROUTE_TIMEOU= T > > > aodv.cc: rt0->rt_expire =3D CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT= ; > > > aodv.cc: rt->rt_expire =3D CURRENT_TIME + ACTIVE_ROUTE_TIMEOUT; > > > aodv.h:#define ACTIVE_ROUTE_TIMEOUT 10 > // 50 seconds > > > foobar/ns-2.27/aodv$ > > > -------->8 > > > > > > Hope this helps ;) > > > > > > Manel > > > > > > P.D.: I didn't know telefonica was working on this ;) > > > > > > > I am using the ns-allinone2.27 package and I don't know whether it > can be done directly with tcl or not. > > > > > > > > > > > > > > > > thank you for your help > > > > > > > > Xavier M. > > > > > > > > _______________________________________________ > > > > 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 > > > > > > > Kiran Vadde > > Graduate Research Associate > > Dept. of Computer Science and Eng. > > Arizona State University > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet >=20 > ------------------------------ >=20 > Message: 4 > Date: Fri, 15 Oct 2004 22:14:39 +0800 > From: "Boon Yeo" > Subject: [manet] WOCN 2005 CFP > To: > Message-ID: <005401c4b2c1$53031640$313815a5@bearty1> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > **Apologies for multiple copies** >=20 > Call for Papers >=20 > Second IFIP International Conference on Wireless and Optical Communicati= ons Networks WOCN 2005 > March 6 - 9, 2005, Dubai, United Arab Emirates UAE Paper Submission >=20 > http://www.wocn2005.org > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Sponsored by IFIPTC6 WG6.8 (Mobile and Wireless Communications), > WG6.6 (Management of Networks and Distributed Systems), WG6.10 (Photonic = Networking) >=20 > Technically sponsored by IEEE Communication Society >=20 > Endorsed by: > IEEE ComSoc Technical Committee on Information Infrastructure (TCII), > IEEE ComSoc Technical Committee on Personal Communications (TCPC) >=20 > The Second IFIP International Conference on wireless and Optical Communic= ations Networks (WOCN 2005) invites high-quality recent research results in= the areas of Mobile and Wireless Communications, optical communications an= d networking, architectures, protocols, planning and design, management and= operation. The main goal of the conference is to bring together scientists= and engineers who work on wireless and optical communications networks. Th= e Second IEEE and IFIP International Conference on Wireless and Optical Com= munications Networks (WOCN 2005) will be held in Dubai, United Arab Emirate= s March 2005. WOCN 2005 is the second conference in its series aimed at sti= mulating technical exchange in the emerging and important field of mobile, = wireless and Optical communications networks. WOCN 2005 seeks to address an= d capture highly innovative and state of the art research and work in the w= ireless and Optical industries. The scope of the conference includes a wide= range of techni....... > as optic > al amplifier, tunable filters, transceivers, termination devices and add-= drop multi-plexers are becoming more affordable and reliable. Access and me= tropolitan area networks are increasingly built with optical technologies t= o overcome the electronic bottleneck at network edges. New components and s= ubsystems for high-speed optical networks offer new design options. The obj= ective of this event is therefore to foster the exchange of information amo= ng researchers in this fast-moving field. The authors can present their fin= ding on new Fibers, optical fiber gratings and devices, optical amplifiers,= optical sensing and medical application of fiber optics and opto-electroni= cs. >=20 > Important Dates >=20 > Paper Submissions Deadline: December 15, 2004 > Notification of Acceptance: January 1, 2005 > Camera Ready Versions Due: January 15, 2005 >=20 > Information for Contributors >=20 > Contributions are invited on all topics concerning wireless and optical c= ommunications networks and components. We are soliciting original papers de= scribing the state-of-the-art research and development in the areas of wire= less and Optical Communication and Networks, including, but not limited to = the following topics: >=20 > Topics of Interest >=20 > 1. Optical Networking Technologies > * Optical network planning, design and modelling > * Optical access/metro networks > * IP over optical networks > * Network protection/restoration > * Generalised multi-protocol label switching (GMPLS) > * Planning and design tools for optical networks > * QoS issues in optical networks > * Routing and wavelength assignment > * Multiple access technique and fairness control in optical LANs and M= ANs >=20 > 2. Optical Switching and Network Elements > * Photonic switching system architectures > * Optical cross-connects and add-drop multiplexers > * Optical IP routers > * Photonic packet switching > * Network signalling and monitoring techniques > * Optical signal processing > * Wavelength conversion techniques >=20 > 3. Optical Transmission Technologies > * WDM Ultra-long haul transmission systems > * OTDM transmission systems > * Soliton transmission systems > * Transmission system experiments > * Radio over fibre-optics > * Optical interconnections > * Optical interfaces and terminals >=20 > 4. Optical Passive Components > * Fiber-Bragg-grating-based devices > * Fiber-grating dispersion compensators > * Optical circulators and isolators > * Optical waveguide-based devices > * Fiber and waveguide filters > * Microstructured waveguides and devices > * Arrayed waveguide devices > * Optical splitting and directional couplers >=20 > 5. Optical Active Components and Modules > * Optical modulators and switches > * Semiconductor optical amplifiers > * Semiconductor lasers and detectors > * Fibre amplifiers and lasers > * Raman and Brillouin amplifiers > * Automatic gain control of optical amplifiers > * Optical MEMS > * Photonic integrated circuits/modules > * Optical tunable filters > * Optical logics and memories >=20 > Mobile and Wireless Communications topics of interest include but are not= limited to the following: >=20 > 1. Management Resource and Information Management > * Pricing and Billing Issues >=20 > 2. Architecture > * Convergence of Fixed and Mobile > * Hybrid Communications System >=20 > 3. Devices > * Low-Power End-Devices and Wireless Communications >=20 > 4. Security > * Security in Mobile and Wireless Networks >=20 > 5. QoS > * Adaptive Quality of Service Provisioning > * End-to-end Quality of Service >=20 > 6. Mobility Support > * Handoff Algorithms > * IP and Mobility > * Mobility and Connection Management in Heterogeneous Wireless Network= s > * Policy-based Mobility Management >=20 > 7. Applications > * Personal Communications > * Location and Context Management > * Smart Media > * Mobile Code > * Mobile Ad-Hoc Networks Applications >=20 > 8. Access > * Wireless IP > * Wireless Multimedia Services > * Wireless Local Loop (WLL) > * Multiple Access Technology > * Broadband Wireless Access >=20 > 9. Networking > * Wireless Personal Area Networks > * Wireless Local Area Networks > * Mobility and Nomadic Computing > * Analysis and Simulation of Mobile Network Protocols > * Home Networking > * Mobile Ad-hoc Networks and the Internet > * Mobile Ad-Hoc Networking Routing > * Satellite Networks >=20 > Paper Submission Guidelines >=20 > Authors are requested to submit electronically a PDF or Word file to Dr. = Boon Sain Yeo, yeobs@i2r.a-star.edu.sg . Pa= pers should be written in English and should preferably follow the instruct= ions in . Preferred maximum paper length is 5 printed pages (= 10-point font) including figures. IEEE will accept papers for review up to = 7 pages in length. Accepted papers that are longer than 5 pages will be cha= rged an over length fee of $100 USD for 6 pages and $200 USD for 7 pages. U= nder no circumstances may any submission should exceed 7 pages. Papers in e= xcess of 7 pages shall not be considered for review or publication. The cov= er page is not included in the page count. The title of the paper, author's= name, affiliation, complete return address, telephone number, facsimile nu= mber and e-mail address should appear at the top of the first page followed= by an abstract with a maximum of 100 words. Authors must state that their = paper has neither been pu..... >=20 > Please contact: Dr. Boon Sain Yeo @ yeobs@i2r.a-star.edu.sg >=20 > Panels and Tutorials >=20 > For information on submitting proposals for Panels and Tutorials, > Please contact: nazar@squ.edu.om or guy.omidyar@ieee.org >=20 > Organising Committee >=20 > General Chair: Professor Guy Omidyar, USA > General co-chairs: Dr. Eesa M. Bastaki, IEEE UAE > Section chair: Abdullah I. Lootah, Vice Chairman Lootah Group > General Vice Chair: Abdumunam Lootah, UAE > Program co-Chairs: > Dr. Boon Sain Yeo, I2R Singapore > Professor Maurice Gagnaire, ENST, France > Tutorials Chairs: Dr. Nazar Elfadil > Treasurer: Dr. Naser Nick Manochehri >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Please visit the WOCN 2005 home page http://www.wocn2005.org for more inf= ormation about the conference. >=20 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://www1.ietf.org/pipermail/manet/attachments/20041015/a1023385/a= ttachment.htm >=20 > ------------------------------ >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 > End of manet Digest, Vol 6, Issue 19 > ************************************ > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Oct 17 19:38:09 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04678 for ; Sun, 17 Oct 2004 19:38:09 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJKnF-0001V3-Bh for manet-web-archive@ietf.org; Sun, 17 Oct 2004 19:50:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJKZV-00031c-MC; Sun, 17 Oct 2004 19:36:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJKVG-0002kD-IP for manet@megatron.ietf.org; Sun, 17 Oct 2004 19:31:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04095 for ; Sun, 17 Oct 2004 19:31:51 -0400 (EDT) Received: from web50610.mail.yahoo.com ([206.190.38.249]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJKgw-0001NO-4X for manet@ietf.org; Sun, 17 Oct 2004 19:44:11 -0400 Message-ID: <20041017233110.62412.qmail@web50610.mail.yahoo.com> Received: from [130.74.176.55] by web50610.mail.yahoo.com via HTTP; Sun, 17 Oct 2004 16:31:10 PDT Date: Sun, 17 Oct 2004 16:31:10 -0700 (PDT) From: Raja Sombhotla To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [manet] Help on simulating Ad-Hoc network! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0449734669==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 --===============0449734669== Content-Type: multipart/alternative; boundary="0-1773291457-1098055870=:60444" --0-1773291457-1098055870=:60444 Content-Type: text/plain; charset=us-ascii Dear all, I have a request for you all regarding simulating Mobile Ad-Hoc networks. Please let me tell you what i want to do and then probably you can guide me. Actually i want to analyze the service carrying capacity of an Ad-Hoc network as a function of mobility and path loss. First, i would like to analyze the capacity (call carrying)of the network with static nodes and then with mobile nodes to see the effect of mobility on the service carrying capacity of the network. When it comes to path loss, since the radio links between the nodes depend on different parameters like frequency band, modulation type, transmitter power,, distance and antenna direction; i would like to vary each parameter and then see the capacity of the network. Now i have two questions: 1) Is my problem definition ok, or in what way i need to define it. Please comment on this. 2) I wish to use OPNET to do this. But i could not figure out how i can generate a mobile Ad-Hoc network say with 50 or 100 nodes and simulate it to estimate the required capacity. Can you please, in brief tell me how to do this using OPNET simulator? I would appreciate your time and patience in this regard. Regards, Raja. --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-1773291457-1098055870=:60444 Content-Type: text/html; charset=us-ascii
Dear all,
 
I have a request for you all regarding simulating Mobile Ad-Hoc networks. Please let me tell you what i want to do and then probably you can guide me.
 
Actually i want to analyze the service carrying capacity of an Ad-Hoc network as a function of mobility and path loss.
First, i would like to analyze the capacity (call carrying)of the network with static nodes and then with mobile nodes to see the effect of mobility on the service carrying capacity of the network.
When it comes to path loss, since the radio links between the nodes depend on different parameters like frequency band, modulation type, transmitter power,, distance and antenna direction; i would like to vary each parameter and then see the capacity of the network.
Now i have two questions:
1) Is my problem definition ok, or in what way i need to define it. Please comment on this.
2) I wish to use OPNET to do this. But i could not figure out how i can generate a mobile Ad-Hoc network say with 50 or 100 nodes and simulate it to estimate the required capacity. Can you please, in brief tell me how to do this using OPNET simulator?
 
I would appreciate your time and patience in this regard.
Regards,
Raja.

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-1773291457-1098055870=:60444-- --===============0449734669== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0449734669==-- From manet-bounces@ietf.org Mon Oct 18 13:07:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02346 for ; Mon, 18 Oct 2004 13:07:47 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJbB9-0004dB-2U for manet-web-archive@ietf.org; Mon, 18 Oct 2004 13:20:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJaUi-0005M1-GJ; Mon, 18 Oct 2004 12:36:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJaFy-0002qj-OM for manet@megatron.ietf.org; Mon, 18 Oct 2004 12:21:10 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25528 for ; Mon, 18 Oct 2004 11:26:46 -0400 (EDT) Received: from web21123.mail.yahoo.com ([216.136.227.188]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJZbL-0002dk-Vl for manet@ietf.org; Mon, 18 Oct 2004 11:39:13 -0400 Message-ID: <20041018152634.28086.qmail@web21123.mail.yahoo.com> Received: from [128.119.86.30] by web21123.mail.yahoo.com via HTTP; Mon, 18 Oct 2004 08:26:34 PDT Date: Mon, 18 Oct 2004 08:26:34 -0700 (PDT) From: Vinod To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [manet] Relation between range and battery power consumed X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Hi all. I am doing some simulation work with energy consumption in manet's. I have a question about the relation between transmit power which decides the range and the power taken up from the battery for communication. In what way are they related? For example, if my antenna transmits at E mW. Should the energy lost from battery be also E mW times packet transmit time? Or is the energy lost some function of the transmit power? The function could depend on some scaling done through resitors in the circuitry. Along similar lines, does the energy lost due to reception have anything to do with transmit power? I think it probably doesnt and is a constant for the hardware. I would appreciate if someone working on some real hardware could give some insight for the above points. Regards, Vinod _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Oct 18 14:44:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11487 for ; Mon, 18 Oct 2004 14:44:42 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJcgw-0006qk-2F for manet-web-archive@ietf.org; Mon, 18 Oct 2004 14:57:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJbzA-0001XA-Dt; Mon, 18 Oct 2004 14:11:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJbgQ-000787-FY for manet@megatron.ietf.org; Mon, 18 Oct 2004 13:52:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06369 for ; Mon, 18 Oct 2004 13:52:18 -0400 (EDT) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJbsC-0005eL-Pr for manet@ietf.org; Mon, 18 Oct 2004 14:04:46 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9IHqCkc027007 for ; Mon, 18 Oct 2004 13:52:14 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Mon, 18 Oct 2004 13:52:13 -0400 Message-ID: <000e01c4b53b$32d033e0$0600a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.3 (/) X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606 Subject: [manet] Assistance with Thesis Topics X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1897287402==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7 This is a multi-part message in MIME format. --===============1897287402== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01C4B519.ABBE93E0" This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C4B519.ABBE93E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, I am looking at doing Thesis CSC PhD work in MANETS in one of the following areas and would appreciate any suggestions on which are the most promising and any further suggestions in those areas: 1) Security 2) Cross Layer Architectures 3) QoS 4) Hybrid Architectures 5) Applications in Hospitals 6) Law Enforcement and EMS 7) Nomadic computing My website is http://www4.ncsu.edu/~crigano/cpr.htm Thanks in advance for your time and effort, Christopher ------=_NextPart_000_000F_01C4B519.ABBE93E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

 

I am looking at doing Thesis CSC PhD work in MANETS = in one of the following areas and would appreciate any suggestions on which are = the most promising and any further suggestions in those = areas:

1) Security

2) Cross Layer = Architectures

3) QoS

4) Hybrid Architectures

5) Applications in = Hospitals

6) Law Enforcement and EMS

7) Nomadic = computing

 

My website is http://www4.ncsu.edu/~crig= ano/cpr.htm

 

Thanks in advance for your time and = effort,

 

Christopher

 

 

 

------=_NextPart_000_000F_01C4B519.ABBE93E0-- --===============1897287402== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1897287402==-- From manet-bounces@ietf.org Tue Oct 19 05:00:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02877 for ; Tue, 19 Oct 2004 05:00:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJq2q-0007r8-H6 for manet-web-archive@ietf.org; Tue, 19 Oct 2004 05:12:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJpAR-0007ZL-T7; Tue, 19 Oct 2004 04:16:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJosb-00050v-Dr for manet@megatron.ietf.org; Tue, 19 Oct 2004 03:58:01 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28587 for ; Tue, 19 Oct 2004 03:57:49 -0400 (EDT) Received: from promet2.deis.unibo.it ([137.204.59.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJp4a-0006mm-Ql for manet@ietf.org; Tue, 19 Oct 2004 04:10:25 -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 i9J7vZFH024556; Tue, 19 Oct 2004 09:57:35 +0200 (MEST) Message-Id: <5.2.0.9.0.20041019093846.00b2b430@pop.deis.unibo.it> X-Sender: p30820@pop.deis.unibo.it X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 19 Oct 2004 09:57:39 +0200 To: Vinod , manet@ietf.org From: Dario Bottazzi Subject: Re: [manet] Relation between range and battery power consumed In-Reply-To: <20041018152634.28086.qmail@web21123.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Hi Vinod, I suggest you to read some papers by Laura Marie Feeney and Martin Nilsson. they model the energy consumption at the MAC layer as a linear. Energy = m * packet_size + b m = incremental cost b = channel allocation Energy is consumed both when a packet is sent and when a packet is received. In addition a fixed cost apply when the apparatus is in idle state. The energy consumption is determined by your network apparatus characteristics (Feeney and Nilsson measured energy consumption for 802.11b lucent lan cards). regards dario At 08:26 AM 10/18/2004 -0700, Vinod wrote: >Hi all. >I am doing some simulation work with energy >consumption in manet's. I have a question about the >relation between transmit power which decides the >range and the power taken up from the battery for >communication. In what way are they related? > >For example, if my antenna transmits at E mW. Should >the energy lost from battery be also E mW times packet >transmit time? > >Or is the energy lost some function of the transmit >power? The function could depend on some scaling done >through resitors in the circuitry. > >Along similar lines, does the energy lost due to >reception have anything to do with transmit power? I >think it probably doesnt and is a constant for the >hardware. >I would appreciate if someone working on some real >hardware could give some insight for the above points. > >Regards, >Vinod > > > > > >_______________________________ >Do you Yahoo!? >Declare Yourself - Register online to vote today! >http://vote.yahoo.com > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 19 21:22:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12453 for ; Tue, 19 Oct 2004 21:22:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CK5Nl-0002Du-JQ for manet-web-archive@ietf.org; Tue, 19 Oct 2004 21:35:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CK3fW-00078o-25; Tue, 19 Oct 2004 19:45:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJt71-0001TQ-Mp for manet@megatron.ietf.org; Tue, 19 Oct 2004 08:29:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18356 for ; Tue, 19 Oct 2004 08:29:05 -0400 (EDT) Received: from mx1.iit.cnr.it ([146.48.98.40] helo=mx.iit.cnr.it) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJtJ8-0003Rp-5W for manet@ietf.org; Tue, 19 Oct 2004 08:41:43 -0400 Received: from localhost (mx.iit.cnr.it [127.0.0.1]) by mx.iit.cnr.it (Postfix) with ESMTP id 84E3F2EED6 for ; Tue, 19 Oct 2004 14:28:31 +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 23516-20 for ; Tue, 19 Oct 2004 14:28:29 +0200 (CEST) Received: from delmastro1 (delmastrof.iit.cnr.it [146.48.98.74]) by mx.iit.cnr.it (Postfix) with ESMTP id B82322EE7E for ; Tue, 19 Oct 2004 14:28:28 +0200 (CEST) Message-ID: <01a501c4b5d7$239ca100$4a623092@delmastro1> From: "Franca Delmastro" To: Date: Tue, 19 Oct 2004 14:28:22 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by Content Checker at iit.cnr.it X-Spam-Score: 0.6 (/) X-Scan-Signature: f2a5dc784731617f446f668f2c529db6 Subject: [manet] [WoWMoM 2005] Cfp: IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0102843018==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: ee8eaa76ea6a4fb3ccc9059a3f656ffc This is a multi-part message in MIME format. --===============0102843018== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A2_01C4B5E7.E2D32DE0" This is a multi-part message in MIME format. ------=_NextPart_000_01A2_01C4B5E7.E2D32DE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= We apologize in advance if you receive multiple copies of this CFP. ************************************************************* CALL FOR PAPERS WoWMoM 2005 IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks http://cnd.iit.cnr.it/wowmom2005 Taormina, Italy, June 13-16, 2005 Sponsored by The IEEE Computer Society The University of Texas at Arlington Technical sponsored by IEEE TCCC **** Submission Deadline --- November 10, 2004 **** ************************************************************** Technology evolution is driving toward a world of wireless, mobile, and multimedia pervasive communications where users can seamlessly and ubiquitously accomplish their tasks, access information or communicate with other users all the anytime, everywhere, and from any device. Technologies include, among others, IEEE 802.11, 802.15, 802.16, Mobile IP, micro-mobility protocols, IP paging, wireless IP QOS, mobile ad hoc and sensor networks, and cellular networks. In addition to these, new and emerging technologies (e.g., UWB) need to be taken into account. The resulting networking environment will constitute the fourth generation wireless networks. 4G will integrate different types of wireless networks with wire-line backbone network seamlessly, and provide the convergence of voice, multimedia and data traffic over a single IP based core network. WoWMoM 2005 technical program committee is soliciting papers addressing the research challenges toward a world of wireless, mobile, and multimedia pervasive communications. Two types of contributions will be accepted: FULL PAPERS: Full Papers must present original, previously unpublished, complete works, validated by experimentation, simulation, or analysis. Practical experiences and experimental efforts are welcome. POSITION PAPERS: Papers in this category must be visionary, innovative and forward-looking. They must offer new perspectives opening future research directions, rather than by presenting mature work with quantitative results. Only a limited number of slots will be available for position papers that will be reviewed primarily for relevance and originality. Topics of interest for WOWMOM 2005 include, but are not limited to: - System prototypes and experiences - Software technologies and systems - QoS for real-time voice and video in wireless networks - Interactive broadband television, gaming, and video distribution - Middleware support for QoS provision - Caching and content management in WLANs and WMANs - Differentiated service in wireless multimedia networks - IP-based multimedia services over wireless networks - Networking services for ambient intelligent and pervasive environments - Multicasting and broadcasting problems and solutions - Handoff and mobility management - Seamless internetworking - IP-based mobile networks - Location mechanism and services - Wireless BAN, PAN, LAN, and MAN - Ad hoc and sensor networks - Vehicular wireless networks - Access technologies - Third and fourth generation systems - Energy-efficient protocols and power management - Wireless security and authentication - Pricing and billing - Modeling and Performance evaluation PAPER SUBMISSION AND PUBLICATION =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Papers should neither have been published elsewhere nor currently under review by another conference or journal. Guidelines on paper submission and formatting will be provided on the website. Accepted papers will appear in the symposium proceedings published by IEEE. IMPORTANT DATES =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Full papers due: November 10, 2004 Notification: January 20, 2005 Camera Ready due: February 15, 2005 ORGANIZING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D GENERAL Co-Chairs: Giuseppe Anastasi, University of Pisa, Italy Sajal K. Das, The University of Texas at Arlington, USA PROGRAM Co-Chairs: Marco Conti, IIT-CNR, Italy Dipankar Raychaudhuri WINLAB/Rutgers University, USA FINANCE & REGISTRATION Chair: Yonghe Liu, The University of Texas at Arlington, USA PUBLICITY Co-Chairs: Mainak Chatterjee, Univ. Central Florida, USA Sunghyun Choi, Seoul National University, Korea Franca Delmastro, IIT-CNR, Italy PUBLICATION Co-Chairs: Eleonora Borgia, IIT-CNR, Italy Luciana Pelusi, IIT-CNR, Italy SPONSORSHIP Chair Alessandro Genco, University of Palermo, Italy LOCAL ARRANGEMENTS Chair: Antonio Puliafito, University of Messina, Italy WEB DESIGNER & MANAGER: Patrizia Andronico, IIT-CNR, Italy STEERING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Marco Conti, IIT-CNR, Italy Sajal K. Das, The University of Texas at Arlington, USA (chair) Dipankar Raychaudhuri WINLAB/Rutgers University, USA Satish K. Tripathi, SUNY Buffalo, USA PROGRAM COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Arup Acharya, IBM T.J. Watson Research, USA Dharma P. Agrawal, University of Cincinnati, USA Kevin C. Almeroth, University of California at Santa Barbara, USA Christian Becker, University of Stuttgart, Germany Giuseppe Bianchi, University of Rome "Tor Vergata", Italy Chris Blondia, University of Antwerp, Belgium Azzedine Boukerche, University of Ottawa, Canada Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Chua Kee Chaing, National University of Singapore, Republic of Singapore Rajarathnam Chandramouili, Stevens Institute of Technology, USA Mainak Chatterjee, University of Central Florida, USA Carla-Fabiana Chiasserini, Polytechnic of Turin, Italy A. Chockalingam, Indian Institute of Science, Banglore, India Sunghyun Choi, Seoul National University, Korea Antonio Corradi, University of Bologna, Italy Antony Ephremides, University of Maryland, USA Gabor Fodor, Ericsson, Sweden Luigi Fratta, Polytechnic of Milan, Italy Marco Gruteser, Rutgers University, USA Paul J.M. Havinga, University of Twente, The Netherlands Kazuo Imai, NTT DoCoMo, Japan Holger Karl, Universtit=E4t Paderborn, Germany Anurag Kumar, Indian Inst of Science, Bangalore, India Mohan Kumar, The University of Texas at Arlington, USA P. R. Kumar, University of Illinois, USA Masahiro Kuroda, National Institute of Info. and Com. Tech., Japan Luciano Lenzini, University of Pisa, Italy K. Ben Letaief, Hong Kong Univ. Science & Technology, Hong Kong Victor Leung, The University of British Columbia, Canada Yonghe Liu, Univ. Texas at Arlington, USA Giri Mandyam, Nokia Research Center, USA Martin Mauve, University of Dusseldorf, Germany Archan Misra, IBM T.J. Watson Research, USA Refik Molva, Institut Eurecom, France Giacomo Morabito, University of Catania, Italy Hiroyuki Morikawa, , University of Tokyo, Japan Stephan Olariu, Old Dominion University, USA Maximilian Ott, Semandex Networks, USA Michael Paterakis, Technical University of Crete, Greece George C. Polyzos, Athens University of Economics and Business, Greece Antonio Puliafito, University of Messina, Italy Jochen H. Schiller, Freie Universit=E4t Berlin, Germany Henning Schulzrinne, Columbia University, USA Rajeev Shorey, IBM India Research Lab, India Ivan Stojmenovic, University of Ottawa, Canada Violet R. Syrotiuk, Arizona State University, USA Wade Trappe, Rutgers University, USA Ooi Wei Tsang, National University of Singapore, Singapore Christian Tschudin, Basel University, Switzerland Thierry Turletti, INRIA France Andras Valko, Ericsson, Hungary Bernard Walke, Aachen University of Technology, Germany Xingwei Wang, Northeastern Univ, China Jie Wu, Florida Atlantic University, USA Gergely Zaruba, The University of Texas at Arlington, USA Roger Zimmerman, University of Southern California, USA ************************************************************ Franca Delmastro Pervasive Computing & Networking Lab. (PerLab) IIT- National Research Council via G. Moruzzi,1 56124 Pisa, Italy ******************************************************** ------=_NextPart_000_01A2_01C4B5E7.E2D32DE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
----------------------------------------------------------------= ---------

We apologize in advance if you = receive multiple=20 copies of this=20 CFP.
*************************************************************

          &nbs= p;         &nbs= p;  =20 CALL FOR PAPERS

          &nbs= p;         &nbs= p;    =20 WoWMoM 2005
         IEEE=20 International Symposium on a World of=20 Wireless,
          =        =20 Mobile and Multimedia=20 Networks

         &nb= sp;      =20 http://cnd.iit.cnr.it/wowmom2005
      &= nbsp;        =20 Taormina, Italy, June 13-16,=20 2005

          &= nbsp;         &= nbsp;    =20 Sponsored=20 by
           <= SPAN>       =20 The IEEE Computer=20 Society
          &n= bsp; =20 The University of Texas at=20 Arlington
          =    =20 Technical sponsored by IEEE=20 TCCC

        **** Submission = Deadline=20 --- November 10, 2004=20 ****
**************************************************************

Technology=20 evolution is driving toward a world of wireless,
mobile, and = multimedia=20 pervasive communications where users can
seamlessly and ubiquitously=20 accomplish their tasks, access information
or communicate with other = users=20 all the anytime, everywhere, and from
any device. Technologies = include, among=20 others, IEEE 802.11,
802.15, 802.16, Mobile IP, micro-mobility = protocols, IP=20 paging,
wireless IP QOS, mobile ad hoc and sensor networks, and=20 cellular
networks.
In addition to these, new and emerging = technologies=20 (e.g., UWB) need to
be taken into account.  The resulting = networking=20 environment will
constitute the fourth generation wireless networks. = 4G will=20 integrate
different types of wireless networks with wire-line = backbone=20 network
seamlessly, and provide the convergence of voice, multimedia=20 and
data traffic over a single IP based core network.  WoWMoM = 2005=20 technical
program committee is soliciting papers addressing the=20 research
challenges
toward a world of wireless, mobile, and = multimedia=20 pervasive
communications.
Two types of contributions will be=20 accepted:

FULL PAPERS: Full Papers must present original, = previously=20 unpublished,
complete works, validated by experimentation, = simulation, or=20 analysis.
Practical experiences and experimental efforts are=20 welcome.

POSITION PAPERS: Papers in this category must be = visionary,=20 innovative
and forward-looking. They must offer new perspectives = opening=20 future
research directions, rather than by presenting mature work=20 with
quantitative results. Only a limited number of slots will be=20 available
for
position papers that will be reviewed primarily for=20 relevance and
originality.

Topics of interest for WOWMOM 2005 = include,=20 but are not limited to:
- System prototypes and experiences
- = Software=20 technologies and systems
- QoS for real-time voice and video in = wireless=20 networks
- Interactive broadband television, gaming, and video=20 distribution
- Middleware support for QoS provision
- Caching and = content=20 management in WLANs and WMANs
- Differentiated service in wireless = multimedia=20 networks
- IP-based multimedia services over wireless networks
-=20 Networking services for ambient intelligent and pervasive = environments
-=20 Multicasting and broadcasting problems and solutions
- Handoff and = mobility=20 management
- Seamless internetworking
- IP-based mobile=20 networks
- Location mechanism and = services
- Wireless=20 BAN, PAN, LAN, and MAN
- Ad hoc and sensor networks
- Vehicular = wireless=20 networks
- Access technologies
- Third and fourth generation = systems
-=20 Energy-efficient protocols and power management
- Wireless security = and=20 authentication
- Pricing and billing
- Modeling and Performance=20 evaluation

PAPER SUBMISSION AND=20 PUBLICATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Papers should neither have been = published=20 elsewhere nor currently
under review by another conference or = journal. =20 Guidelines on paper
submission and formatting will be = provided on=20 the website.
Accepted papers will appear in the symposium proceedings = published by
IEEE.


IMPORTANT = DATES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Full=20 papers due:        November 10,=20 2004
Notification:        &nb= sp; =20 January 20, 2005
Camera Ready = due:      =20 February 15, 2005


ORGANIZING COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
GENERAL=20 Co-Chairs:
        Giuseppe = Anastasi,=20 University of Pisa, Italy
        = Sajal K.=20 Das, The University of Texas at Arlington, USA

PROGRAM=20 Co-Chairs:
        Marco Conti, = IIT-CNR,=20 Italy
        Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA


FINANCE & REGISTRATION=20 Chair:
         Yonghe Liu, = The=20 University of Texas at Arlington, USA
PUBLICITY=20 Co-Chairs:
         Mainak=20 Chatterjee, Univ. Central Florida,=20 USA
         Sunghyun Choi, = Seoul=20 National University, Korea
        =20 Franca Delmastro, IIT-CNR, Italy


PUBLICATION Co-Chairs:
        =20 Eleonora Borgia, IIT-CNR, Italy
        =20 Luciana Pelusi, IIT-CNR, Italy


SPONSORSHIP Chair
        Alessandro = Genco,=20 University of Palermo, Italy


LOCAL ARRANGEMENTS=20 Chair:
        Antonio Puliafito,=20 University of Messina, Italy


WEB DESIGNER &=20 MANAGER:
        Patrizia = Andronico,=20 IIT-CNR, Italy



STEERING=20 COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Ma= rco Conti, IIT-CNR, Italy
Sajal K. Das,=20 The University of Texas at Arlington, USA (chair)
Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA
Satish K. Tripathi, SUNY Buffalo,=20 USA


PROGRAM = COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Arup = Acharya, IBM T.J.=20 Watson Research, USA
Dharma P. Agrawal, University of Cincinnati,=20 USA
Kevin C. Almeroth, University of California at Santa Barbara,=20 USA
Christian Becker, University of Stuttgart, Germany
Giuseppe = Bianchi,=20 University of Rome "Tor Vergata", Italy
Chris Blondia, University of = Antwerp,=20 Belgium
Azzedine  Boukerche, University of Ottawa, = Canada
Jiannong=20 Cao, Hong Kong Polytechnic University, Hong Kong
Chua Kee Chaing, = National=20 University of Singapore, Republic of Singapore
Rajarathnam = Chandramouili,=20 Stevens Institute of Technology, USA
Mainak Chatterjee, University of = Central=20 Florida, USA
Carla-Fabiana Chiasserini, Polytechnic of Turin, = Italy
A.=20 Chockalingam, Indian Institute of Science, Banglore, India
Sunghyun = Choi,=20 Seoul National University, Korea
Antonio Corradi, University of = Bologna,=20 Italy
Antony Ephremides, University of Maryland, USA
Gabor Fodor,=20 Ericsson, Sweden
Luigi Fratta, Polytechnic of Milan, Italy
Marco = Gruteser,=20 Rutgers University, USA
Paul J.M. Havinga, University of Twente, The=20 Netherlands
Kazuo Imai, NTT DoCoMo, Japan
Holger Karl, Universtit=E4t = Paderborn,=20 Germany
Anurag Kumar, Indian Inst of = Science, Bangalore,=20 India
Mohan Kumar, The University of Texas at Arlington, USA
P. R. = Kumar,=20 University of Illinois, USA
Masahiro Kuroda, National Institute of = Info. and=20 Com. Tech., Japan
Luciano Lenzini, University of Pisa, Italy
K. = Ben=20 Letaief, Hong Kong Univ. Science & Technology, Hong Kong
Victor = Leung,=20 The University of British Columbia, Canada
Yonghe Liu, Univ. Texas at = Arlington,=20 USA
Giri Mandyam, Nokia Research Center, = USA
Martin Mauve, University of Dusseldorf, Germany
Archan Misra, = IBM T.J.=20 Watson Research, USA
Refik Molva, Institut Eurecom, France
Giacomo = Morabito, University of Catania, Italy
Hiroyuki Morikawa, , = University of=20 Tokyo, Japan
Stephan Olariu, Old Dominion University, = USA
Maximilian Ott,=20 Semandex Networks, USA
Michael Paterakis, Technical University of = Crete,=20 Greece
George C. Polyzos, Athens University of Economics and = Business,=20 Greece
Antonio Puliafito, University of Messina, Italy
Jochen H. = Schiller,=20 Freie Universit=E4t Berlin, Germany
Henning Schulzrinne, Columbia = University,=20 USA
Rajeev Shorey, IBM India Research Lab, India
Ivan Stojmenovic, = University of Ottawa, Canada
Violet R. Syrotiuk, Arizona State = University,=20 USA
Wade Trappe, Rutgers University, USA
Ooi Wei Tsang, National=20 University of Singapore, Singapore
Christian Tschudin, Basel = University,=20 Switzerland
Thierry Turletti, INRIA France
Andras Valko, Ericsson, = Hungary
Bernard Walke, Aachen University of Technology, = Germany
Xingwei=20 Wang, Northeastern Univ, China
Jie Wu, Florida Atlantic University,=20 USA
Gergely Zaruba, The University of = Texas at=20 Arlington, USA
Roger Zimmerman, University of = Southern=20 California, USA
 
************************************************************
= Franca=20 Delmastro
Pervasive Computing & Networking Lab. = (PerLab)
 
IIT- National Research = Council
via G.=20 Moruzzi,1
56124 Pisa,=20 Italy
********************************************************<= /DIV> ------=_NextPart_000_01A2_01C4B5E7.E2D32DE0-- --===============0102843018== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0102843018==-- From manet-bounces@ietf.org Tue Oct 19 23:15:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20854 for ; Tue, 19 Oct 2004 23:15:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CK78y-0004gl-W9 for manet-web-archive@ietf.org; Tue, 19 Oct 2004 23:28:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CK4fa-0007L4-1m; Tue, 19 Oct 2004 20:49:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJyf4-0005UT-Af for manet@megatron.ietf.org; Tue, 19 Oct 2004 14:24:42 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25646 for ; Tue, 19 Oct 2004 14:24:10 -0400 (EDT) Received: from farley1.colorado.edu ([128.138.129.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJyqp-0005rm-AW for manet@ietf.org; Tue, 19 Oct 2004 14:36:51 -0400 Received: (from nobody@localhost) by farley1.Colorado.EDU (8.12.10/8.12.10/ITS-6.0/test-webmail) id i9JIO8UG025140; Tue, 19 Oct 2004 12:24:08 -0600 (MDT) Received: from smct43-141-dhcp.resnet.colorado.edu (smct43-141-dhcp.resnet.colorado.edu [128.138.43.141]) by webmail.colorado.edu (IMP) with HTTP for ; Tue, 19 Oct 2004 12:24:08 -0600 Message-ID: <1098210248.41755bc8b68d2@webmail.colorado.edu> Date: Tue, 19 Oct 2004 12:24:08 -0600 From: Sheetalkumar Doshi To: manet@ietf.org Subject: Re: [manet] Relation between range and battery power consumed (fwd) References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Content-Transfer-Encoding: 8bit Cc: Vinod X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: 8bit Hi Vinod Our group at the University of Colorado has been looking at battery consumption energy models and transmit power control as a part of our work on energy aware routing. Here is one paper from our group that could give you some insights: http://ece-www.colorado.edu/~timxb/timxb/publications/02MCCR.pdf You can find more information at http://pecolab.colorado.edu Regards Sheetal -- Sheetalkumar Doshi PhD Student/Research Assistant Dept. Of Electrical and Computer Engineering University of Colorado at Boulder http://ucsub.colorado.edu/~doshi > Date: Mon, 18 Oct 2004 08:26:34 -0700 (PDT) > From: Vinod > To: manet@ietf.org > Subject: [manet] Relation between range and battery power consumed > > Hi all. > I am doing some simulation work with energy > consumption in manet's. I have a question about the > relation between transmit power which decides the > range and the power taken up from the battery for > communication. In what way are they related? > > For example, if my antenna transmits at E mW. Should > the energy lost from battery be also E mW times packet > transmit time? > > Or is the energy lost some function of the transmit > power? The function could depend on some scaling done > through resitors in the circuitry. > > Along similar lines, does the energy lost due to > reception have anything to do with transmit power? I > think it probably doesnt and is a constant for the > hardware. > I would appreciate if someone working on some real > hardware could give some insight for the above points. > > Regards, > Vinod > > > > > > _______________________________ > Do you Yahoo!? > Declare Yourself - Register online to vote today! > http://vote.yahoo.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Oct 19 23:42:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22164 for ; Tue, 19 Oct 2004 23:42:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CK7ZI-00058P-6v for manet-web-archive@ietf.org; Tue, 19 Oct 2004 23:55:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CK4hG-0002G5-P0; Tue, 19 Oct 2004 20:51:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJzjU-0004sJ-KH for manet@megatron.ietf.org; Tue, 19 Oct 2004 15:33:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03534 for ; Tue, 19 Oct 2004 15:33:13 -0400 (EDT) Received: from web61101.mail.yahoo.com ([216.155.196.103]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJzvN-0007pV-Fv for manet@ietf.org; Tue, 19 Oct 2004 15:45:55 -0400 Message-ID: <20041019193224.71559.qmail@web61101.mail.yahoo.com> Received: from [66.208.44.5] by web61101.mail.yahoo.com via HTTP; Tue, 19 Oct 2004 12:32:24 PDT Date: Tue, 19 Oct 2004 12:32:24 -0700 (PDT) From: manet user To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] aodv v4/v6 compatibility X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1838018537==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 --===============1838018537== Content-Type: multipart/alternative; boundary="0-540827928-1098214344=:71286" --0-540827928-1098214344=:71286 Content-Type: text/plain; charset=us-ascii Hi, Can AODV support a mixed network having both IPv4 and IPV6 capable nodes? If a node is capable of supporting v4 & v6, will it broadcast "Hello" for both v4 & v6 ? Or a node should lock onto one type of addressing mode ? Any thoughts or comments will be helpful. Thanks in advance, -MU __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-540827928-1098214344=:71286 Content-Type: text/html; charset=us-ascii
Hi,
 
Can AODV support a mixed network having both IPv4 and IPV6 capable nodes? If a node is capable of supporting v4 & v6, will it broadcast "Hello" for both v4 & v6 ? Or a node should lock onto one type of addressing mode ?
 
Any thoughts or comments will be helpful. Thanks in advance,
-MU

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-540827928-1098214344=:71286-- --===============1838018537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1838018537==-- From manet-bounces@ietf.org Wed Oct 20 06:50:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20465 for ; Wed, 20 Oct 2004 06:50:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKEFt-0005ac-9Y for manet-web-archive@ietf.org; Wed, 20 Oct 2004 07:03:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKD7n-0008FF-To; Wed, 20 Oct 2004 05:51:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKC0P-0002nm-DX for manet@megatron.ietf.org; Wed, 20 Oct 2004 04:39:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11487 for ; Wed, 20 Oct 2004 04:39:29 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.194] helo=mproxy.gmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKCCg-0002wH-Ha for manet@ietf.org; Wed, 20 Oct 2004 04:52:19 -0400 Received: by mproxy.gmail.com with SMTP id 79so449821rnl for ; Wed, 20 Oct 2004 01:39:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=B64YMS3O5JDijvyBEsyfOI5Nujwdx2OG56g9YqsJFrSyy+C9hofroUSlUjSwsy8x+4Mw8YpjHFwFovsGk+Ecx3kaX1GJx6kwVk1OKhT6mIgWhn9LUQM9CPJOeSMLR9qP0o1KfotDuXFGh8rQBc/IAyXeXSpkox6wBAbPj3eH8o0 Received: by 10.38.65.16 with SMTP id n16mr498221rna; Wed, 20 Oct 2004 01:12:49 -0700 (PDT) Received: by 10.38.89.59 with HTTP; Wed, 20 Oct 2004 01:12:49 -0700 (PDT) Message-ID: <1a3ca34b04102001121a64e210@mail.gmail.com> Date: Wed, 20 Oct 2004 10:12:49 +0200 From: Abdalla Mahmoud To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Subject: [manet] Reputation mechanism X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Abdalla Mahmoud List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hello, I am reading different papers about the different MANETs reputation techniques and I just found one paper titled "On Using Reputations in Ad hoc Networks to counter Malicious Nodes" that deals with adding a reputation model to the AODV protocol, and I have two questions: 1) Does anyone have this paper code? 2) Can anyone refer me to more reputation models/papers for AODV, as I couldn't find any yet? Thanks, Abdalla Mahmoud _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 20 10:46:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11210 for ; Wed, 20 Oct 2004 10:46:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKHwA-0002EB-PR for manet-web-archive@ietf.org; Wed, 20 Oct 2004 10:59:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKGyX-0001Up-Tu; Wed, 20 Oct 2004 09:58:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKGOI-0001NN-7i for manet@megatron.ietf.org; Wed, 20 Oct 2004 09:20:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01564 for ; Wed, 20 Oct 2004 09:20:22 -0400 (EDT) Received: from ms-smtp-04-lbl.southeast.rr.com ([24.25.9.103] helo=ms-smtp-04-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKGaW-0000Mu-J0 for manet@ietf.org; Wed, 20 Oct 2004 09:33:14 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-04-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9KDKECh017285 for ; Wed, 20 Oct 2004 09:20:16 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Wed, 20 Oct 2004 09:20:14 -0400 Message-ID: <001e01c4b6a7$892abe50$0600a8c0@CPQ73745201364> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.2 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Subject: [manet] Newest topics/topics that need the most wrok X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0279854843==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 43317e64100dd4d87214c51822b582d1 This is a multi-part message in MIME format. --===============0279854843== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C4B686.02191E50" This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C4B686.02191E50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, I am looking for topics that aer the newest and would contribute the most to MANET research. I am a PhD student new to the field (Computer Science) and have finished 2 EE courses in wireless communications. In advance thanks for your time. I would really like to make a contribution in a new/needed area. Cheers, Christopher ------=_NextPart_000_001F_01C4B686.02191E50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings, I am looking for topics that aer the newest and would contribute the most to MANET research. I am a PhD = student new to the field (Computer Science) and have finished 2 EE courses in = wireless communications. In advance thanks for your time. I would really like to = make a contribution in a new/needed area.

 

Cheers,

 

Christopher

------=_NextPart_000_001F_01C4B686.02191E50-- --===============0279854843== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0279854843==-- From manet-bounces@ietf.org Thu Oct 21 10:31:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06102 for ; Thu, 21 Oct 2004 10:31:11 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKeAq-0004SS-Vi for manet-web-archive@ietf.org; Thu, 21 Oct 2004 10:44:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKdoS-0008Jn-Ca; Thu, 21 Oct 2004 10:21:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKdfq-0002nh-V7 for manet@megatron.ietf.org; Thu, 21 Oct 2004 10:12:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02962 for ; Thu, 21 Oct 2004 10:12:12 -0400 (EDT) Received: from web61005.mail.yahoo.com ([216.155.196.94]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKdsT-0003vK-O0 for manet@ietf.org; Thu, 21 Oct 2004 10:25:18 -0400 Message-ID: <20041021141142.93092.qmail@web61005.mail.yahoo.com> Received: from [192.93.2.12] by web61005.mail.yahoo.com via HTTP; Thu, 21 Oct 2004 07:11:42 PDT Date: Thu, 21 Oct 2004 07:11:42 -0700 (PDT) From: Jinshan To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: df9edf1223802dd4cf213867a3af6121 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA02962 Subject: [manet] CFP iTrust 2005 --3rd Int'l Conf. on Trust management X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d9238570526f12788af3d33c67f37625 Content-Transfer-Encoding: quoted-printable FYI, I think it might be interesting for the folks who work on trust management in MANET.=20 Sincere apologies if you receive multiple copies of this CFP. ------------------------------------------------------------------- ********************************************************************* Call for Papers ********************************************************************* 3rd International Conference on Trust Management (iTrust'2005) 23-26 May 2005, INRIA-Rocquencourt, France =20 http://www-rocq.inria.fr/arles/events/iTrust2005/ The iTrust international Conference looks at trust from multidisciplinary perspectives: economic, legal, pyschology, philosophy, sociology as well as information technology.=20 Building upon the work of the IST iTrust working group (http://www.itrust.uoc.gr) and the success of the two previous iTrust International conferences (http://www.trustmanagement.cclrc.ac.uk/), the aims=20 of iTrust'2005 are to attract a critical mass of experts from industry,=20 government and academia with a keen interest in the area of trust management.=20 The objectives of the Conference are:=20 - To facilitate the cross-disciplinary investigation of fundamental=20 issues underpinning computational trust models by bringing =20 together expertise from technology oriented sciences, law,=20 philosophy and social sciences.=20 - To facilitate the emergence of widely acceptable trust=20 management processes or dynamic open systems and=20 applications.=20 - To facilitate the development of new paradigms in the area of=20 dynamic open systems which effectively utilise computational=20 trust models.=20 - To facilitate the integration of new trust management paradigms=20 and emerging architectures for Grid computing and Virtual=20 Organisations.=20 - To help the incorporation of trust management elements in=20 existing standards. =20 Topics of Interest: Full technical papers contributing to the issue of trust management are solicited in the relevant areas, including but not limited to:=20 - The legal notion of trust in computer science and engineering - Requirements and methodologies to ensure that the user can=20 trust the functioning of software systems - Trust management frameworks for secure collaborations in =20 dynamic Virtual Organisations=20 - Design of trust based architectures and decision-making=20 mechanisms for e-community and e-service interactions - Trust specification, analysis and reasoning - Dynamics of trust dispositions and relations=20 - Realisation of prototypes of software architectures and=20 applications - Trust elements in contract negotiation, execution monitoring,=20 re-negotiation and arbitration - Legal contribution to trust in technological infrastructures and=20 interactions: the on-line identification of subjects, the evaluation of=20 their reliability, the data protection, privacy, confidentiality,=20 security, commercial transactions, the resolution of disputes, software agents, the access to source code - The conditions for the reliance in the artefact and the machine - Trust in the interaction and cooperation "mediated" through=20 computer and network, and the balance between control and=20 intervention.=20 - Research of on-line trust, the trust of the consumer towards the=20 web site of the distribution company - Analysis of the relationship between trust and such notions as=20 confidence, distrust, diffidence, expectation, risk and reliance. Important Dates:=20 Papers:=20 Submission of papers: November 25, 2004=20 Notification of paper acceptance: January 14, 2005 Submission of final camera ready version: February 25, 2005 How to Submit: Submissions must be original and must not have been submitted for publication elsewhere. =20 The proceedings of the Conference will be published by Springer in the Lecture Notes in Computer Science series. Submissions must be in English and authors should ensure that papers are formatted according to the LNCS format (see author's instructions given on the Conference Web site). Full technical papers should not exceed 15 pages in the abovementioned format.=20 Submissions should be made through the Conference Web Site. =20 Organization: General Chair:=20 Valerie Issarny (INRIA) Programme Co-Chairs: Peter Herrmann, University of Dortmund, Germany Simon Shiu, Hewlett Packard, UK Conference Committee: Demonstration Chair: Nikolaos Georgantas, INRIA, France Panel Chair: Paul Kearney, BTexact, UK Tutorial Chair: Yuecel Karabulut, SAP AG, Germany Publicity Chair: Jinshan Liu, INRIA, France Local Arrangement: Dominique Potherat, INRIA, France Programme Committee: =20 Eliza Bertino, University of Milano, Italy Jon Bing, NRCCL-University of Oslo, Norway Jeremy Bryans, University of Newcastle, UK Cristiano Castelfranchi, CNR, Italy David Chadwick, University of Salford, UK Andrew Charlesworth, University of Bristol, UK David Crocker, Brandenburg InternetWorking, USA Mark Roger Dibben, University of St. Andrews, UK Theo Dimitrakos, CCLRC, UK Rino Falcone, CNR, Italy Peter Herrmann, University of Dortmund, Germany Valerie Issarny, INRIA, France Keith Jeffery, CCLRC, UK Christian Jensen, DTU, Denmark Andrew Jones, King's College, UK Audun Josang, DSTC, Australia Yuecel Karabulut, SAP AG, Germany Paul Kearney, BTexact, UK Graham Klyne, Nine by Nine, UK Heiko Krumm, University of Dortmund, Germany Ninghui Li, Stanford University, USA Peter Linington, University of Kent at Canterbury, UK Stephane Lo Presti, University of Southampton, UK Fabio Martinelli, CNR, Italy Fabio Massacci, Universit=E0 di Trento, Italy Erich Neuhold, Darmstadt University of Technology and Fraunhofer IPSI, Germany Christos Nikolaou, University of Crete, Greece Paddy Nixon, University of Strathclyde, UK Stefan Poslad, Queen Mary Colledge, UK Jens Riegelsberger, University of Newcastle, UK Peter Ryan, University of Newcastle, UK Babak Sadighi, SICS, Sweden Simon Shiu, Hewlett Packard, UK Morris Sloman, Imperial College, UK Ketil Stoelen, SINTEF & University of Oslo, Norway Yao-Hua Tan, Free University of Amsterdam, Holland Sotirios Terzis, University of Strathclyde, UK Dimitris Tsigos, Virtual Trip Ltd, Greece Stavroula Tsinorema, University of Crete, Greece Andrew Twigg, University of Cambridge, UK Emily Weitzenboeck, NRCCL-University of Oslo, Norway Marianne Winslett, University of Illinois at Urbana-Champaign, USA =09 _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 22 07:44:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25419 for ; Fri, 22 Oct 2004 07:44:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKy32-0004Al-Kg for manet-web-archive@ietf.org; Fri, 22 Oct 2004 07:57:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKxna-0005NS-QV; Fri, 22 Oct 2004 07:41:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKxiq-0003vN-CY for manet@megatron.ietf.org; Fri, 22 Oct 2004 07:36:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25044 for ; Fri, 22 Oct 2004 07:36:38 -0400 (EDT) Received: from web60005.mail.yahoo.com ([216.109.116.228]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKxvb-00042q-S1 for manet@ietf.org; Fri, 22 Oct 2004 07:49:53 -0400 Message-ID: <20041022113605.19839.qmail@web60005.mail.yahoo.com> Received: from [195.229.241.183] by web60005.mail.yahoo.com via HTTP; Fri, 22 Oct 2004 04:36:05 PDT Date: Fri, 22 Oct 2004 04:36:05 -0700 (PDT) From: Hasan K To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 4.2 (++++) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [manet] Average Node Speed X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1203313676==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 4.2 (++++) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 --===============1203313676== Content-Type: multipart/alternative; boundary="0-1867688804-1098444965=:19522" --0-1867688804-1098444965=:19522 Content-Type: text/plain; charset=us-ascii Hello, Consider this simple mobility model: A node chooses a random coordinate (x, y) within a grid then move to it a speed uniformly selected on (0,V]. Then every T seconds, this process is repeated. The question is, what is the average nodal speed? It is not V/2 since we have the T factor. What do you think? HK --------------------------------- Do you Yahoo!? vote.yahoo.com - Register online to vote today! --0-1867688804-1098444965=:19522 Content-Type: text/html; charset=us-ascii
Hello,
 
Consider this simple mobility model: A node chooses a random coordinate (x, y) within a grid then move to it a speed uniformly selected on (0,V]. Then every T seconds, this process is repeated.
 
The question is, what is the average nodal speed? It is not V/2 since we have the T factor.
 
What do you think?
 
HK

Do you Yahoo!?
vote.yahoo.com - Register online to vote today! --0-1867688804-1098444965=:19522-- --===============1203313676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1203313676==-- From manet-bounces@ietf.org Fri Oct 22 08:58:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00166 for ; Fri, 22 Oct 2004 08:58:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKzCj-0005d5-3z for manet-web-archive@ietf.org; Fri, 22 Oct 2004 09:11:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKyna-0002Dr-Iz; Fri, 22 Oct 2004 08:45:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKyj3-0000Vk-1S for manet@megatron.ietf.org; Fri, 22 Oct 2004 08:40:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28727 for ; Fri, 22 Oct 2004 08:40:54 -0400 (EDT) Received: from agentesmith.cefriel.it ([131.175.55.145]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKyvo-0005Bc-O7 for manet@ietf.org; Fri, 22 Oct 2004 08:54:09 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by agentesmith.cefriel.it (8.12.11/8.12.11) with ESMTP id i9MCeKMT004927 for ; Fri, 22 Oct 2004 14:40:20 +0200 Message-ID: <4178FFB4.2070503@cefriel.it> Date: Fri, 22 Oct 2004 14:40:20 +0200 From: Alessandro La Piana User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] Average Node Speed References: <20041022113605.19839.qmail@web60005.mail.yahoo.com> In-Reply-To: <20041022113605.19839.qmail@web60005.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Hi, the average speed should always be V/2. Let's suppose we take N speed samples. The space traveled in N T seconds time will be Sum[V_i T] = T Sum[V_i] for i going from 1 to N. So the average speed will be Sum[V_i T] Sum[V_i] V_max ---------------- = ----------------- = (in the limit N->\infinity) ------------ N T N 2 Bye. Alessandro La Piana Hasan K wrote: > Hello, > > Consider this simple mobility model: A node chooses a random > coordinate (x, y) within a grid then move to it a speed uniformly > selected on (0,V]. Then every T seconds, this process is repeated. > > The question is, what is the average nodal speed? It is not V/2 since > we have the T factor. > > What do you think? > > HK > > ------------------------------------------------------------------------ > Do you Yahoo!? > vote.yahoo.com - Register online to vote today! > > >------------------------------------------------------------------------ > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 22 09:29:16 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02430 for ; Fri, 22 Oct 2004 09:29:16 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKzge-0006Bz-CY for manet-web-archive@ietf.org; Fri, 22 Oct 2004 09:42:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKzQZ-00086b-0J; Fri, 22 Oct 2004 09:25:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKzN9-0006aU-5t for manet@megatron.ietf.org; Fri, 22 Oct 2004 09:22:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02025 for ; Fri, 22 Oct 2004 09:22:20 -0400 (EDT) Received: from web60003.mail.yahoo.com ([216.109.116.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKzZv-000634-53 for manet@ietf.org; Fri, 22 Oct 2004 09:35:36 -0400 Message-ID: <20041022132148.12816.qmail@web60003.mail.yahoo.com> Received: from [213.42.2.27] by web60003.mail.yahoo.com via HTTP; Fri, 22 Oct 2004 06:21:48 PDT Date: Fri, 22 Oct 2004 06:21:48 -0700 (PDT) From: Hasan K Subject: Re: [manet] Average Node Speed To: Alessandro La Piana , manet@ietf.org In-Reply-To: <4178FFB4.2070503@cefriel.it> MIME-Version: 1.0 X-Spam-Score: 4.0 (++++) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1812431887==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 4.0 (++++) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a --===============1812431887== Content-Type: multipart/alternative; boundary="0-228054156-1098451308=:11866" --0-228054156-1098451308=:11866 Content-Type: text/plain; charset=us-ascii Thanks! That was fast! I agree with you if nodes continue to move till the next time they change speed. But in the model I am describing a node may may stop well before the expiry of T seconds because it reached its random coordinate. I am not sure whether the average (total distance travelled / total time) then will be V/2?! Thanks again! Alessandro La Piana wrote: Hi, the average speed should always be V/2. Let's suppose we take N speed samples. The space traveled in N T seconds time will be Sum[V_i T] = T Sum[V_i] for i going from 1 to N. So the average speed will be Sum[V_i T] Sum[V_i] V_max ---------------- = ----------------- = (in the limit N->\infinity) ------------ N T N 2 Bye. Alessandro La Piana Hasan K wrote: > Hello, > > Consider this simple mobility model: A node chooses a random > coordinate (x, y) within a grid then move to it a speed uniformly > selected on (0,V]. Then every T seconds, this process is repeated. > > The question is, what is the average nodal speed? It is not V/2 since > we have the T factor. > > What do you think? > > HK > > ------------------------------------------------------------------------ > Do you Yahoo!? > vote.yahoo.com - Register online to vote today! > > >------------------------------------------------------------------------ > >_______________________________________________ >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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-228054156-1098451308=:11866 Content-Type: text/html; charset=us-ascii
Thanks! That was fast!
 
I agree with you if nodes continue to move till the next time they change speed. But in the model I am describing a node may may stop well before the expiry of T seconds because it reached its random coordinate. I am not sure whether the average (total distance travelled / total time) then will be V/2?!
 
Thanks again!

Alessandro La Piana <lapiana@cefriel.it> wrote:
Hi,
the average speed should always be V/2.

Let's suppose we take N speed samples. The space traveled in N T seconds
time will be

Sum[V_i T] = T Sum[V_i] for i going from 1 to N.
So the average speed will be

Sum[V_i T] Sum[V_i] V_max
---------------- = ----------------- = (in the limit N->\infinity)
------------
N T N 2


Bye.
Alessandro La Piana

Hasan K wrote:

> Hello,
>
> Consider this simple mobility model: A node chooses a random
> coordinate (x, y) within a grid then move to it a speed uniformly
> selected on (0,V]. Then every T seconds, this process is repeated.
>
> The question is, what is the average nodal speed? It is not V/2 since
> we have the T factor.
>
> What do you think?
>
> HK
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> vote.yahoo.com - Register online to vote today!
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-228054156-1098451308=:11866-- --===============1812431887== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1812431887==-- From manet-bounces@ietf.org Fri Oct 22 12:12:30 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17280 for ; Fri, 22 Oct 2004 12:12:29 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2Ee-0001NX-FK for manet-web-archive@ietf.org; Fri, 22 Oct 2004 12:25:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL1yS-0004DT-P8; Fri, 22 Oct 2004 12:09:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL1xB-0003i1-IK for manet@megatron.ietf.org; Fri, 22 Oct 2004 12:07:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16907 for ; Fri, 22 Oct 2004 12:07:41 -0400 (EDT) Received: from web21324.mail.yahoo.com ([216.136.175.210]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CL29z-0001Fb-PC for manet@ietf.org; Fri, 22 Oct 2004 12:21:00 -0400 Message-ID: <20041022160738.30472.qmail@web21324.mail.yahoo.com> Received: from [193.205.203.3] by web21324.mail.yahoo.com via HTTP; Fri, 22 Oct 2004 18:07:38 CEST Date: Fri, 22 Oct 2004 18:07:38 +0200 (CEST) From: francesco caldonazzi To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.9 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA16907 Subject: [manet] request X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable Hi manet, i would like if you can remove my email by manet's list. Thank you for your service =09 ___________________________________=20 Nuovo Yahoo! Messenger: E' molto pi=F9 divertente: Audibles, Avatar, Webc= am, Giochi, Rubrica=85 Scaricalo ora!=20 http://it.messenger.yahoo.it _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 22 12:37:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18930 for ; Fri, 22 Oct 2004 12:37:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2cu-0001pC-Au for manet-web-archive@ietf.org; Fri, 22 Oct 2004 12:50:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2MO-0005BN-9i; Fri, 22 Oct 2004 12:33:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2Jf-0003wE-IM for manet@megatron.ietf.org; Fri, 22 Oct 2004 12:30:59 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18457 for ; Fri, 22 Oct 2004 12:30:55 -0400 (EDT) Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2WS-0001gN-Sz for manet@ietf.org; Fri, 22 Oct 2004 12:44:14 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id CECC9201E; Fri, 22 Oct 2004 10:30:53 -0600 (MDT) From: "John Mullen" To: "'Hasan K'" , Subject: RE: [manet] Average Node Speed Date: Fri, 22 Oct 2004 10:30:52 -0600 Message-ID: <000001c4b854$7fa12f50$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-Reply-To: <20041022113605.19839.qmail@web60005.mail.yahoo.com> X-Spam-Score: 0.9 (/) X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1519196990==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: b8f3559805f7873076212d6f63ee803e This is a multi-part message in MIME format. --===============1519196990== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4B822.3506BF50" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4B822.3506BF50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Hasan, The mean speed for nodes in motion will be V/2, but the mean speed over all nodes will be less. For nodes in motion, the speed is a random variable with an average of V/2. As long as a node has not reached its destination, it is moving at a speed randomly selected from a U(0,T) distribution. However, nodes that reach their destination before traveling T time units will stop and wait for the start of the next time interval. Therefore, the average speed is (V/2)Pr(Travel time is greater than or equal to T). The distribution of the distances between nodes uniformly distributed in a rectangular region is approximately bivariate Normal with a mean of (0,0), assuming your origin is in the center, and a standard deviation along each axis of W/12, where W is the width of the rectangle along that axis. Thus, depending on the ratio of V to Wx and Wy, you can calculate the probability that the selected travel distance is less than TV and from that, get your overall average. John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Hasan K Sent: Friday, October 22, 2004 4:36 AM To: manet@ietf.org Subject: [manet] Average Node Speed Hello, Consider this simple mobility model: A node chooses a random coordinate (x, y) within a grid then move to it a speed uniformly selected on (0,V]. Then every T seconds, this process is repeated. The question is, what is the average nodal speed? It is not V/2 since we have the T factor. What do you think? HK _____ Do you Yahoo!? vote.yahoo.com - Register online to vote today! ------=_NextPart_000_0001_01C4B822.3506BF50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hi=20 Hasan,
 
The=20 mean speed for nodes in motion will be V/2, but the mean speed over all = nodes=20 will be less.
 
For=20 nodes in motion, the speed is a random variable with an average of = V/2.  As=20 long as a node has not reached its destination, it is moving at a speed = randomly=20 selected from a U(0,T) distribution.
 
However, nodes that reach their destination before traveling T = time units=20 will stop and wait for the start of the next time interval.  = Therefore, the=20 average speed is
        (V/2)Pr(Travel time is = greater than=20 or equal to T).
 
The=20 distribution of the distances between nodes uniformly distributed in a=20 rectangular region is approximately bivariate Normal with a mean = of  (0,0),=20 assuming your origin is in the center, and a standard deviation along = each axis=20 of W/12, where W is the width of the rectangle along that axis.  = Thus,=20 depending on the ratio of V to Wx and Wy, you can calculate the = probability that=20 the selected travel distance is less than TV and from that, get your = overall=20 average.
 
John=20 Mullen
 
 
-----Original Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of = Hasan K
Sent: Friday, October 22, 2004 4:36 = AM
To:=20 manet@ietf.org
Subject: [manet] Average Node=20 Speed

Hello,
 
Consider this simple mobility model: A node chooses a random = coordinate=20 (x, y) within a grid then move to it a speed uniformly selected on = (0,V]. Then=20 every T seconds, this process is repeated.
 
The question is, what is the average nodal speed? It is not V/2 = since we=20 have the T factor.
 
What do you think?
 
HK

Do you Yahoo!?
vote.yahoo.com = -=20 Register online to vote today!
------=_NextPart_000_0001_01C4B822.3506BF50-- --===============1519196990== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1519196990==-- From manet-bounces@ietf.org Fri Oct 22 13:51:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24436 for ; Fri, 22 Oct 2004 13:51:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL3mG-00039w-Ms for manet-web-archive@ietf.org; Fri, 22 Oct 2004 14:04:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL3V8-0003Vo-Bz; Fri, 22 Oct 2004 13:46:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL3RM-00027J-CD for manet@megatron.ietf.org; Fri, 22 Oct 2004 13:43:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23775 for ; Fri, 22 Oct 2004 13:42:57 -0400 (EDT) Received: from mailg.surrey.ac.uk ([131.227.102.21]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CL3e8-0002zP-9n for manet@ietf.org; Fri, 22 Oct 2004 13:56:15 -0400 Received: from ads40.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP) with ESMTP; Fri, 22 Oct 2004 18:41:55 +0100 Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136]) by ads40.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Oct 2004 18:41:54 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 22 Oct 2004 18:37:44 +0100 Message-ID: Thread-Topic: Use of Planar Graphs Thread-Index: AcS4XYKLu8M0XMWNRtSpGBsP/CPxiAAAFP+F From: "Sivavakeesar S Mr (PG/R - Electronic Eng)" To: manet X-OriginalArrivalTime: 22 Oct 2004 17:41:54.0424 (UTC) FILETIME=[6B8FCF80:01C4B85E] X-Spam-Score: 0.8 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Subject: [manet] Use of Planar Graphs X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1584837880==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 This is a multi-part message in MIME format. --===============1584837880== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4B85E.6B62A190" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4B85E.6B62A190 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Collegues : =20 I am sure some of you can help me out. Can somebody tell me why we = always use planar graph in the case of finding shortests path within a = network OR perimeter OR face-routing in the case of geocasting in mobile = ad hoc networks. What happens if we opt for non-planerised graphs [ie: = graphs in which edges might cross each other]. =20 Since I am involved with routing in MANETs using graph theory = principles, can you please suggest me any book that deals with graph = theory in general OR preferably in the context of networking. =20 Your timely help would be greatly appreciated. =20 Thanks in advance. =20 Cheers =20 S. Siv =20 ------_=_NextPart_001_01C4B85E.6B62A190 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A=
=0A=
Dear = Collegues =0A= :
=0A=
=0A=
 
=0A=
I am sure some of you can help me out. = Can somebody =0A= tell me why we always use planar graph in the case of finding shortests = path =0A= within a network OR perimeter OR face-routing in the case of geocasting = in =0A= mobile ad hoc networks. What happens if we opt for non-planerised graphs = [ie: =0A= graphs in which edges might cross each other].
=0A=
 
=0A=
Since I am involved with routing = in MANETs =0A= using graph theory principles, can you please suggest me any book that = deals =0A= with graph theory in general OR preferably in the context of =0A= networking.
=0A=
 
=0A=
Your timely help would be greatly =0A= appreciated.
=0A=
 
=0A=
Thanks in advance.
=0A=
 
=0A=
Cheers
=0A=
 
=0A=
S. Siv
=0A=
 
------_=_NextPart_001_01C4B85E.6B62A190-- --===============1584837880== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1584837880==-- From manet-bounces@ietf.org Fri Oct 22 19:29:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13448 for ; Fri, 22 Oct 2004 19:29:31 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL93e-0000bd-Fo for manet-web-archive@ietf.org; Fri, 22 Oct 2004 19:42:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL8o6-0001Pz-24; Fri, 22 Oct 2004 19:26:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL8cD-0001BK-7X for manet@megatron.ietf.org; Fri, 22 Oct 2004 19:14:33 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12134 for ; Fri, 22 Oct 2004 19:14:31 -0400 (EDT) Received: from mail.villinski.com ([63.226.81.85] helo=villinski.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL8p7-0000Dv-AL for manet@ietf.org; Fri, 22 Oct 2004 19:27:54 -0400 Received: from onepostal.com not authenticated [63.230.21.107] by villinski.com with NetMail SMTP Agent $Revision: 3.89 $ on Novell NetWare; Fri, 22 Oct 2004 17:14:18 -0600 Received: from STENCH/SpoolDir by onepostal.com (Mercury 1.48); 22 Oct 04 17:14:13 -0700 Received: from SpoolDir by STENCH (Mercury 1.48); 22 Oct 04 17:13:43 -0700 Received: from NewCell (63.230.21.105) by onepostal.com (Mercury 1.48) with ESMTP; 22 Oct 04 17:13:39 -0700 From: "Scott C. Lemon" To: Date: Fri, 22 Oct 2004 17:13:30 -0600 Organization: HumanXtensions L.L.C. Message-ID: <01a801c4b88c$be9514f0$400a640a@NewCell> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 1.6 (+) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Subject: [manet] AODV and Internet Gateways ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0765726811==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f This is a multi-part message in MIME format. --===============0765726811== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A9_01C4B85A.73FAA4F0" This is a multi-part message in MIME format. ------=_NextPart_000_01A9_01C4B85A.73FAA4F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, =20 I am working on an embedded Linux system and implementing the AODV = protocol. As I have made some progress, I started to realize that there is no mechanism in AODV to do "discovery" of a "default gateway" or a route to = the Internet. (Not that it should!) =20 I am curious if there are suggested protocols or standards for discovery = of a gateway? =20 I know that I could look to use DHCP, however I am looking to use the Automatic Private IP Addressing for local assignment on the individual nodes, and then I want a node to be able to "query" for a gateway ... =20 Thoughts? =20 =20 Scott C. Lemon =20 =20 ------=_NextPart_000_01A9_01C4B85A.73FAA4F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hello,
 
I am = working on an=20 embedded Linux system and implementing the AODV protocol.  As I = have made=20 some progress, I started to realize that there is no mechanism in AODV = to do=20 "discovery" of a "default gateway" or a route to the Internet. (Not that = it=20 should!)
 
I am = curious if=20 there are suggested protocols or standards for discovery of a=20 gateway?
 
I know = that I could=20 look to use DHCP, however I am looking to use the Automatic Private IP=20 Addressing for local assignment on the individual nodes, and then I want = a node=20 to be able to "query" for a gateway ...
 
Thoughts?
 
 
Scott C. = Lemon
 
 
------=_NextPart_000_01A9_01C4B85A.73FAA4F0-- --===============0765726811== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0765726811==-- From manet-bounces@ietf.org Sat Oct 23 04:12:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07465 for ; Sat, 23 Oct 2004 04:12:50 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLHEB-0000Rl-06 for manet-web-archive@ietf.org; Sat, 23 Oct 2004 04:26:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLGyX-0001Oa-3Z; Sat, 23 Oct 2004 04:10:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLGuA-00083U-Ox for manet@megatron.ietf.org; Sat, 23 Oct 2004 04:05:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06675 for ; Sat, 23 Oct 2004 04:05:36 -0400 (EDT) Received: from 209-254-158-42.ip.mcleodusa.net ([209.254.158.42] helo=che.ojctech.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLH79-0000Fb-AK for manet@ietf.org; Sat, 23 Oct 2004 04:19:04 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id i9N8540O022816 for ; Sat, 23 Oct 2004 03:05:04 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id i9N854RL022814 for manet@ietf.org; Sat, 23 Oct 2004 03:05:04 -0500 Date: Sat, 23 Oct 2004 03:05:04 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] AODV and Internet Gateways ... Message-ID: <20041023080503.GG17288@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: <01a801c4b88c$be9514f0$400a640a@NewCell> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01a801c4b88c$be9514f0$400a640a@NewCell> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f On Fri, Oct 22, 2004 at 05:13:30PM -0600, Scott C. Lemon wrote: > Hello, > > I am working on an embedded Linux system and implementing the AODV protocol. > As I have made some progress, I started to realize that there is no > mechanism in AODV to do "discovery" of a "default gateway" or a route to the > Internet. (Not that it should!) I thought that AODV could advertise routes with any network mask length, thus advertising a 0/0 route was possible? In any event, that may not be sufficient. Is your network multi-homed? Based on (1) an illuminating discussion on this mailing list and (2) my project's desperate need and desire to route from nodes on our "rooftop" network to one or more IPv4 and IPv6 Internet gateways, while coping with NAT or 6to4 at each gateway. I motivated a gateway advertisement/negotiation protocol, , and wrote a "zeroth" draft of a protocol, . I haven't the time to implement. You may consider this enlistment for our open-source "rooftop" routing project, . :-) The protocol is stateful. I estimate that an implementation would be at least as complicated as Zeroconf, or a DHCP client---that is, quite possibly, way too complicated. Following one of the suggestions in the mailing list discussion, I break strict layering by using one-way tunnels; I know that offends purists, but I think that it is the right thing to do. Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Oct 24 02:46:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05563 for ; Sun, 24 Oct 2004 02:46:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLcME-00043g-IL for manet-web-archive@ietf.org; Sun, 24 Oct 2004 03:00:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLc2P-00051A-GB; Sun, 24 Oct 2004 02:39:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLbzn-0004io-4N for manet@megatron.ietf.org; Sun, 24 Oct 2004 02:36:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05027 for ; Sun, 24 Oct 2004 02:36:49 -0400 (EDT) Received: from [203.199.83.28] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLcCx-0003v4-Va for manet@ietf.org; Sun, 24 Oct 2004 02:50:29 -0400 Received: (qmail 20224 invoked by uid 510); 24 Oct 2004 06:36:22 -0000 Date: 24 Oct 2004 06:36:22 -0000 Message-ID: <20041024063622.20222.qmail@webmail18.rediffmail.com> Received: from unknown (202.159.211.160) by rediffmail.com via HTTP; 24 oct 2004 06:36:22 -0000 MIME-Version: 1.0 From: "anjali mihir" To: manet@ietf.org, glomosim-users-l@lists.ucla.edu X-Spam-Score: 3.1 (+++) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Subject: [manet] make clean in windows X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anjali mihir List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0880368628==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.8 (+) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 This is a multipart mime message --===============0880368628== Content-type: multipart/alternative; boundary="Next_1098599782---0-203.199.83.28-20217" This is a multipart mime message --Next_1098599782---0-203.199.83.28-20217 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0Ahiii
=0A
=0A
=0Ahow all r u.can any one plz te= ll me that as we use 'make clean' command in linux similary what command do= we use in 'windows XP',so that after adding r protocol we can clean and do= 'makent'
=0A=0A

=0A

=0A=0A --Next_1098599782---0-203.199.83.28-20217 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0Ahiii=0A=0A=0Ahow all r u.can any one plz tell me that as we use 'mak= e clean' command in linux similary what command do we use in 'windows XP',s= o that after adding r protocol we can clean and do 'makent'=0A --Next_1098599782---0-203.199.83.28-20217-- --===============0880368628== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0880368628==-- From manet-bounces@ietf.org Sun Oct 24 03:36:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08023 for ; Sun, 24 Oct 2004 03:36:50 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLd93-0004mB-Q2 for manet-web-archive@ietf.org; Sun, 24 Oct 2004 03:50:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLcp3-0003pS-EH; Sun, 24 Oct 2004 03:29:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLcl5-0003LH-Ns for manet@megatron.ietf.org; Sun, 24 Oct 2004 03:25:44 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07683 for ; Sun, 24 Oct 2004 03:25:42 -0400 (EDT) Received: from web60008.mail.yahoo.com ([216.109.116.246]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLcyG-0004d6-7A for manet@ietf.org; Sun, 24 Oct 2004 03:39:22 -0400 Message-ID: <20041024072510.9492.qmail@web60008.mail.yahoo.com> Received: from [194.170.95.22] by web60008.mail.yahoo.com via HTTP; Sun, 24 Oct 2004 00:25:10 PDT Date: Sun, 24 Oct 2004 00:25:10 -0700 (PDT) From: Hasan K Subject: RE: [manet] Average Node Speed To: manet@ietf.org In-Reply-To: <000001c4b854$7fa12f50$67f57b80@engr.ad.nmsu.edu> MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1344804617==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 --===============1344804617== Content-Type: multipart/alternative; boundary="0-639052796-1098602710=:6512" --0-639052796-1098602710=:6512 Content-Type: text/plain; charset=us-ascii Thank you all. HK --------------------------------- Do you Yahoo!? vote.yahoo.com - Register online to vote today! --0-639052796-1098602710=:6512 Content-Type: text/html; charset=us-ascii
Thank you all.

HK

Do you Yahoo!?
vote.yahoo.com - Register online to vote today! --0-639052796-1098602710=:6512-- --===============1344804617== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1344804617==-- From manet-bounces@ietf.org Tue Oct 26 13:24:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26060 for ; Tue, 26 Oct 2004 13:24:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMVGz-0008Vw-3n for manet-web-archive@ietf.org; Tue, 26 Oct 2004 13:38:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMUu2-0004Zd-Kc; Tue, 26 Oct 2004 13:14:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMUhT-0000PB-TC for manet@megatron.ietf.org; Tue, 26 Oct 2004 13:01:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22947 for ; Tue, 26 Oct 2004 13:01:33 -0400 (EDT) Received: from smtp1.clb.oleane.net ([213.56.31.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMUvA-0007Wu-IO for manet@ietf.org; Tue, 26 Oct 2004 13:15:45 -0400 Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be forged)) by smtp1.clb.oleane.net with ESMTP id i9QH128X006904 for ; Tue, 26 Oct 2004 19:01:03 +0200 Message-Id: <200410261701.i9QH128X006904@smtp1.clb.oleane.net> From: "peter" To: Date: Tue, 26 Oct 2004 19:00:59 +0200 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcS7fV3VIulYNz1XRyuL/E6Bh/5abA== X-Spam-Score: 0.2 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Subject: [manet] WiFi Voice Conference X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0697205061==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de This is a multi-part message in MIME format. --===============0697205061== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0061_01C4BB8E.21C75C00" This is a multi-part message in MIME format. ------=_NextPart_000_0061_01C4BB8E.21C75C00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - What are the market drivers for VoWLAN? - How will VoWLAN systems prioritize and deliver data packets? - What are the planning and engineering issues? - What about security and privacy? At the WiFi Voice Conference to be held in Paris on 10 to 13 May, 2005. distinguished experts and key players in the field will address these questions with detailed and technical explanations. A call for papers is online at: http://www.upperside.fr/wifi05/wifivoice2005intro.htm ------=_NextPart_000_0061_01C4BB8E.21C75C00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

- What are the market drivers for VoWLAN?
- How will VoWLAN systems prioritize and deliver data packets?
- What are the planning and engineering issues? 
- What about security and privacy? 

At the WiFi Voice Conference to be held in Paris on 10 to 13 = May, 2005. distinguished experts and key players in the field =

will address these questions with detailed and technical explanations.

A call for papers is = online at:

http://www.upperside.fr/wifi05/wifivoice2005intro.htm=

=

 

------=_NextPart_000_0061_01C4BB8E.21C75C00-- --===============0697205061== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0697205061==-- From manet-bounces@ietf.org Tue Oct 26 14:02:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29678 for ; Tue, 26 Oct 2004 14:02:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMVs6-00018Y-Pq for manet-web-archive@ietf.org; Tue, 26 Oct 2004 14:16:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMVbH-0002W1-Tv; Tue, 26 Oct 2004 13:59:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMVOI-0005Bz-PJ for manet@megatron.ietf.org; Tue, 26 Oct 2004 13:45:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27959 for ; Tue, 26 Oct 2004 13:45:48 -0400 (EDT) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMVby-0000bk-Ka for manet@ietf.org; Tue, 26 Oct 2004 14:00:00 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9QHjeKj024354 for ; Tue, 26 Oct 2004 13:45:45 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Tue, 26 Oct 2004 13:45:39 -0400 Message-ID: <000001c4bb83$9be59200$0600a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.2 (/) X-Scan-Signature: 43317e64100dd4d87214c51822b582d1 Subject: [manet] RE: MANET and WLAN Architectures to support Digital Video Command and Control X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0162663879==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c This is a multi-part message in MIME format. --===============0162663879== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4BB62.14D3F200" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4BB62.14D3F200 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, I am doing a short analysis of possible MANET and WLAN Architectures to support in-vehicle and man-pack Digital Video (MPEG4) to be used in Law Enforcement in support of incident response command and control. The solution could be IPV6 and something like a modified SIP at the higher layers with WLAN or infrastructure-like architectures. Any idea where to start? I am looking at Layer 1, MAC, Transport/P2P in such a way as to remain portable across MANET implementations. Thanks and regards, Chris ------=_NextPart_000_0001_01C4BB62.14D3F200 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

 

 

I am doing a short analysis of possible MANET and = WLAN Architectures to support in-vehicle and man-pack Digital Video (MPEG4) = to be used in Law Enforcement in support of incident response command and = control. The solution could be IPV6 and something like a modified SIP at the = higher layers with WLAN or infrastructure-like architectures. Any idea where to = start? I am looking at Layer 1, MAC, Transport/P2P = in such a way as to remain portable across MANET = implementations.

 

Thanks and regards,

 

Chris

------=_NextPart_000_0001_01C4BB62.14D3F200-- --===============0162663879== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0162663879==-- From manet-bounces@ietf.org Wed Oct 27 04:52:51 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17687 for ; Wed, 27 Oct 2004 04:52:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMjlv-0000Wa-I7 for manet-web-archive@ietf.org; Wed, 27 Oct 2004 05:07:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMjRL-0002XQ-OK; Wed, 27 Oct 2004 04:45:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMjQW-0002PN-Oo for manet@megatron.ietf.org; Wed, 27 Oct 2004 04:45:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17201 for ; Wed, 27 Oct 2004 04:45:02 -0400 (EDT) Received: from web90104.mail.scd.yahoo.com ([66.218.94.75]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMjeL-0000Nh-7w for manet@ietf.org; Wed, 27 Oct 2004 04:59:22 -0400 Message-ID: <20041027084431.51504.qmail@web90104.mail.scd.yahoo.com> Received: from [203.208.193.230] by web90104.mail.scd.yahoo.com via HTTP; Wed, 27 Oct 2004 01:44:31 PDT Date: Wed, 27 Oct 2004 01:44:31 -0700 (PDT) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 1.0 (+) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [manet] Wi Max? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1142464425==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa --===============1142464425== Content-Type: multipart/alternative; boundary="0-2143914522-1098866671=:50975" --0-2143914522-1098866671=:50975 Content-Type: text/plain; charset=us-ascii Dear All, If anybody tells me the major differences between Ad hoc networking and WiFi. As we know both are used for the communication between mobile nodes.Or is it the case that WiFi is also a part of Ad Hoc networking ? Best Regards, Parag Goswami http://www.geocities.com/paragboom2k --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-2143914522-1098866671=:50975 Content-Type: text/html; charset=us-ascii
Dear All,
If anybody tells me the major differences between Ad hoc networking and WiFi.
As we know both are used for the communication between mobile nodes.Or is it the case that WiFi is also a part of Ad Hoc networking ?
 
Best Regards,
Parag Goswami

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-2143914522-1098866671=:50975-- --===============1142464425== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1142464425==-- From manet-bounces@ietf.org Wed Oct 27 05:41:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20340 for ; Wed, 27 Oct 2004 05:41:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMkWr-0001KB-5e for manet-web-archive@ietf.org; Wed, 27 Oct 2004 05:55:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMkFC-0002yX-Ia; Wed, 27 Oct 2004 05:37:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMkE7-0002n5-SX for manet@megatron.ietf.org; Wed, 27 Oct 2004 05:36:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20147 for ; Wed, 27 Oct 2004 05:36:16 -0400 (EDT) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMkRx-0001Fh-4q for manet@ietf.org; Wed, 27 Oct 2004 05:50:37 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] Wi Max? Date: Wed, 27 Oct 2004 11:36:43 +0200 Message-ID: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> Thread-Topic: [manet] Wi Max? thread-index: AcS8AsglBX2N6GEuTV+eaywpqOIpjAABMybw From: "Giorgio Mulas" To: "Parag Goswami" , X-Spam-Score: 0.6 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1749819306==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407 This is a multi-part message in MIME format. --===============1749819306== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4BC08.7856450D" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4BC08.7856450D Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Parag, WiFi is a Layer 1 and 2 technology and it is not related with routing = issues. Ad hoc networking is a research topic considering routing issues (and, = of course, other important things) =20 The main relation between WiFi and Ad hoc networks is that cheap = WiFi-enabled devices are usually used to build up testbeds for MANETs... =20 BR. =20 Giorgio =20 =20 =20 =20 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of Parag Goswami Sent: mercoled=EC 27 ottobre 2004 10.45 To: manet@ietf.org Subject: [manet] Wi Max? Dear All, If anybody tells me the major differences between Ad hoc networking and = WiFi. As we know both are used for the communication between mobile nodes.Or = is it the case that WiFi is also a part of Ad Hoc networking ? =20 Best Regards, Parag Goswami http://www.geocities.com/paragboom2k _____ =20 Do you Yahoo!? Yahoo! = Mail Address AutoComplete - You start. We = finish. ------_=_NextPart_001_01C4BC08.7856450D Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Dear=20 Parag,
WiFi=20 is a Layer 1 and 2 technology and it is not related with routing=20 issues.
Ad hoc=20 networking is a research topic considering routing issues (and, of = course, other=20 important things)
 
The=20 main relation between WiFi and Ad hoc networks is that cheap = WiFi-enabled=20 devices are usually used to build up testbeds for = MANETs...
 
BR.
 
Giorgio
 
 
 
 
-----Original Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of = Parag Goswami
Sent: mercoled=EC 27 ottobre 2004=20 10.45
To: manet@ietf.org
Subject: [manet] Wi=20 Max?

Dear All,
If anybody tells me the major differences between Ad hoc = networking and=20 WiFi.
As we know both are used for the communication between mobile = nodes.Or is=20 it the case that WiFi is also a part of Ad Hoc networking ?
 
Best Regards,
Parag Goswami
http://www.geocities.com/pa= ragboom2k

Do you Yahoo!?
Yahoo!=20 Mail Address AutoComplete - You start. We = finish.
------_=_NextPart_001_01C4BC08.7856450D-- --===============1749819306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1749819306==-- From manet-bounces@ietf.org Wed Oct 27 10:19:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06748 for ; Wed, 27 Oct 2004 10:19:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMorj-00064A-Pc for manet-web-archive@ietf.org; Wed, 27 Oct 2004 10:33:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMoba-0000j2-NE; Wed, 27 Oct 2004 10:16:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMoaJ-0008NE-0y for manet@megatron.ietf.org; Wed, 27 Oct 2004 10:15:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06211 for ; Wed, 27 Oct 2004 10:15:28 -0400 (EDT) Message-Id: <200410271415.KAA06211@ietf.org> Received: from [218.22.21.7] (helo=ustc.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMon3-0005yG-L0 for manet@ietf.org; Wed, 27 Oct 2004 10:29:51 -0400 Received: (qmail 15389 invoked by uid 8021); 27 Oct 2004 13:42:03 -0000 Received: from kingpaul@ustc.edu by mail.ustc.edu by uid 0 with qmail-scanner-1.20 (hbedv: 6.28.0.7/6.28.0.38. Clear:RC:0(202.38.75.80):. Processed in 0.016061 secs); 27 Oct 2004 13:42:03 -0000 Received: from unknown (HELO jbhuang) (kingpaul@[202.38.75.80]) (envelope-sender ) by 0 (magicmail-2.1) with SMTP for ; 27 Oct 2004 13:42:03 -0000 Date: Wed, 27 Oct 2004 21:41:49 +0800 From: "kingpaul" To: "manet@ietf.org" Subject: [manet]AODV + ns2 help! X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Qmail-Scanner-Message-ID: <109888452391215384@mail.ustc.edu> X-Spam-Score: 2.9 (++) X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.7 (+++) X-Scan-Signature: 2086112c730e13d5955355df27e3074b Content-Transfer-Encoding: 7bit Dear All, I am a newer to AODV+ns2, I wrote a simple TCL file as follows: ################## example2.tcl start #################### set val(chan) Channel/WirelessChannel ;# channel type set val(prop) Propagation/TwoRayGround ;# radio-propagation model set val(netif) Phy/WirelessPhy ;# network interface type set val(mac) Mac/802_11 ;# MAC type set val(ifq) Queue/DropTail/PriQueue ;# interface queue type set val(ll) LL ;# link layer type set val(ant) Antenna/OmniAntenna ;# antenna model set val(ifqlen) 50 ;# max packet in ifq set val(nn) 2 ;# number of mobilenodes set val(rp) AODV ;# routing protocol set val(x) 500 ;# X dimension of the topography set val(y) 500 ;# Y dimension of the topography set ns [new Simulator] set tracefd [open example2.tr w] $ns trace-all $tracefd set namtracefd [open example2.nam w] $ns namtrace-all-wireless $namtracefd $val(x) $val(y) proc finish {} { global ns tracefd namtracefd $ns flush-trace close $tracefd close $namtracefd exec nam example2.nam & exit 0 } set topo [new Topography] $topo load_flatgrid $val(x) $val(y) create-god $val(nn) $ns node-config -addressType flat -adhocRouting $val(rp) \ -llType $val(ll) \ -macType $val(mac) \ -ifqType $val(ifq) \ -ifqLen $val(ifqlen) \ -antType $val(ant) \ -propType $val(prop) \ -phyType $val(netif) \ -channelType $val(chan) \ -topoInstance $topo \ -agentTrace ON \ -routerTrace ON \ -macTrace OFF \ -movementTrace OFF for {set i 0} {$i < $val(nn) } {incr i} { set node_($i) [$ns node] $node_($i) random-motion 0 ;# disable random motion } $node_(0) set X_ 5.0 $node_(0) set Y_ 2.0 $node_(0) set Z_ 0.0 $node_(1) set X_ 390.0 $node_(1) set Y_ 385.0 $node_(1) set Z_ 0.0 $ns at 10.0 "$node_(0) setdest 20.0 18.0 1.0" $ns at 50.0 "$node_(1) setdest 25.0 20.0 15.0" $ns at 100.0 "$node_(1) setdest 490.0 480.0 15.0" set tcp [new Agent/TCP] $tcp set class_ 2 set sink [new Agent/TCPSink] $ns attach-agent $node_(0) $tcp $ns attach-agent $node_(1) $sink $ns connect $tcp $sink set ftp [new Application/FTP] $ftp attach-agent $tcp $ns at 10.0 "$ftp start" for {set i 0} {$i < $val(nn) } {incr i} { $ns at 150.0 "$node_($i) reset"; } $ns at 150.0 "finish" $ns run ################## example2.tcl end #################### but I got the error: [root@jbhuangRH root]# ns example2.tcl num_nodes is set 2 ns-address.tcl:set-address-format: Unknown address format flat while executing "error "ns-address.tcl:set-address-format: Unknown address format $opt"" (procedure "_o3" line 20) (Simulator set-address-format line 20) invoked from within "$self set-address-format $addressType_ " (procedure "_o3" line 43) (Simulator node-config line 43) invoked from within "$ns node-config -addressType flat" (file "example2.tcl" line 37) [root@jbhuangRH root]# what is the problem with my TCL file? Best Regards, Kingpaul Huang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 27 13:55:52 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27151 for ; Wed, 27 Oct 2004 13:55:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMsFU-00030j-Cd for manet-web-archive@ietf.org; Wed, 27 Oct 2004 14:10:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMryG-0005X1-Tb; Wed, 27 Oct 2004 13:52:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMrvG-0004zR-LU for manet@megatron.ietf.org; Wed, 27 Oct 2004 13:49:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26846 for ; Wed, 27 Oct 2004 13:49:20 -0400 (EDT) Received: from ellis.ad.nps.navy.mil ([131.120.18.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMs98-0002ua-P1 for manet@ietf.org; Wed, 27 Oct 2004 14:03:45 -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, 27 Oct 2004 10:49:12 -0700 Subject: RE: [manet] Wi Max? From: Rex Buddenberg To: Giorgio Mulas In-Reply-To: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> References: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> Content-Type: text/plain; charset=UTF-8 Message-Id: <1098899352.17791.279.camel@antony> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 27 Oct 2004 10:49:12 -0700 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 27 Oct 2004 17:49:12.0880 (UTC) FILETIME=[44F7A300:01C4BC4D] X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Content-Transfer-Encoding: quoted-printable Parag, Giorgio is right. MANET is a layer 3 issue and both WiFi and WiMax are layer 1-2 technologies. That said ... Most experimental MANET stuff needs some kind of plumbing underneath and WiFi (IEEE 802.11) has been popular for that. And a lot of the experimentation has been done in 'ad hoc' or 'infrastructureless' mode where two subscriber nodes can connect with each other. In short, WiFi can be pretty promiscuous which happens to fit the MANET intentions. And it's d.c. -- dirt cheap. Wi-MAX (IEEE 802.16) changes the MAC algorithm from a carrier sense one used in WiFi (and it's antecedent, wired ethernet) to a scheduling algorithm. Scheduling MACs rely only on the assumption that everyone can hear the base station (BS); there's no requirement whatever that peers (SSs) hear each other so the hidden node problem goes away (so in=20 v1, SS-to-SS is not well supported). Many satellite comms algorithms (e.g. DAMA) fall in this general category, but are anemic by comparison to .16. Scheduling MACs can also provide stability under overload / oversubscription, bandwidth efficiency, and ability to control QoS to the extent that we can provide deterministic service at layer 2 ... all of which are important in many situations. ... but don't have much to do with MANET. What 802.16 does not do well yet is the Wi-Fi ad hoc mode. We may have to modify this statement soon as real compliant products start appearing in the marketplace (the 802.16-2004 standard was ratified in June and that seems to have uncorked a lot of development). There are two developments in IEEE 802 that are germane here: 1) there is 'mesh' work going on within 802.16 but it's acknowledged as not being mature in the -2004 version. =20 2) bit of bureaucratic dispute between 802.16, 802.20 and 802.22 about the terms 'fixed' and 'mobile' in the PARs (charters). All three committees (.20 and .22 are much less mature) have both MAC and PHY development in their charter docs. But it's not at all clear why either .20 or .22 need to develop a new MAC -- a little growth and maturity in the .16 MAC may be all that's needed.... but the 802.16 PAR has the term 'fixed' in it. These two committees do indeed need to develop new PHY standards for their particular purposes (cellphone --> packet switch and TV spectrum reuse for rural, respectively). =20 Wi-MAX is going to be interesting in the next few years. At least some in the industry are planning to put Wi-Max chipsets in your laptop like Wi-Fi ones are now. The shift from infrastructureless to a more hierarchical layer 2 structure does change some of the MANET tacit assumptions. Help? On Wed, 2004-10-27 at 02:36, Giorgio Mulas wrote: > Dear Parag, > WiFi is a Layer 1 and 2 technology and it is not related with routing > issues. > Ad hoc networking is a research topic considering routing issues (and, > of course, other important things) > =20 > The main relation between WiFi and Ad hoc networks is that cheap > WiFi-enabled devices are usually used to build up testbeds for > MANETs... > =20 > BR. > =20 > Giorgio > =20 > =20 > =20 > =20 > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > On Behalf Of Parag Goswami > Sent: mercoled=C3=AC 27 ottobre 2004 10.45 > To: manet@ietf.org > Subject: [manet] Wi Max? > =20 > =20 > Dear All, > If anybody tells me the major differences between Ad hoc > networking and WiFi. > As we know both are used for the communication between mobile > nodes.Or is it the case that WiFi is also a part of Ad Hoc > networking ? > =20 > Best Regards, > Parag Goswami > http://www.geocities.com/paragboom2k > =20 > =20 > ______________________________________________________________ > Do you Yahoo!? > Yahoo! Mail Address AutoComplete - You start. We finish. >=20 >=20 > ______________________________________________________________________ > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 b _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 27 14:18:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28925 for ; Wed, 27 Oct 2004 14:18:07 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMsb0-0003SH-Nm for manet-web-archive@ietf.org; Wed, 27 Oct 2004 14:32:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMsKy-0001NX-AU; Wed, 27 Oct 2004 14:15:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMsFq-00006G-6M for manet@megatron.ietf.org; Wed, 27 Oct 2004 14:10:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28402 for ; Wed, 27 Oct 2004 14:10:36 -0400 (EDT) Received: from asmtp-a063f29.pas.sa.earthlink.net ([207.217.120.131]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMsTZ-0003HI-KE for manet@ietf.org; Wed, 27 Oct 2004 14:25:01 -0400 Received: from [68.164.152.137] (helo=h-68-164-152-137.snvacaid.dynamic.covad.net) by asmtp-a063f29.pas.sa.earthlink.net with asmtp (Exim 4.34) id 1CMsF4-0004E1-As for manet@ietf.org; Wed, 27 Oct 2004 11:09:50 -0700 From: Jerry Toung To: manet@ietf.org Date: Wed, 27 Oct 2004 11:10:21 -0700 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410271110.21483.jtoung@arc.nasa.gov> X-ELNK-Trace: e66ec8515162d63394f5150ab1c16ac08f4233f47979de2600c82b53c8dcb6179ff5d87b10d7a4d1350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.164.152.137 X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Subject: [manet] MAC protocol for infrared L1 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jtoung@arc.nasa.gov List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Good morning List, I am looking for a MAC protocol that would be suitable for infrared signals in the MANET world. Any pointers and with possibly open source implementation or state diagrams in that direction will be great. I already know that IEEE 802.11 supports infrared at the physical layer. thanks a lot, Jerry _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 27 15:44:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06951 for ; Wed, 27 Oct 2004 15:44:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMtwN-0005R3-QG for manet-web-archive@ietf.org; Wed, 27 Oct 2004 15:58:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMtaC-0008Rq-HU; Wed, 27 Oct 2004 15:35:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMtV8-0004wh-Po for manet@megatron.ietf.org; Wed, 27 Oct 2004 15:30:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05685 for ; Wed, 27 Oct 2004 15:30:28 -0400 (EDT) Received: from web90101.mail.scd.yahoo.com ([66.218.94.72]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMtj2-0005A5-RI for manet@ietf.org; Wed, 27 Oct 2004 15:44:54 -0400 Message-ID: <20041027192955.74777.qmail@web90101.mail.scd.yahoo.com> Received: from [203.208.193.230] by web90101.mail.scd.yahoo.com via HTTP; Wed, 27 Oct 2004 12:29:55 PDT Date: Wed, 27 Oct 2004 12:29:55 -0700 (PDT) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 1.0 (+) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Subject: [manet] few questions about MAC protocol X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0419632209==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 --===============0419632209== Content-Type: multipart/alternative; boundary="0-732977678-1098905395=:73697" --0-732977678-1098905395=:73697 Content-Type: text/plain; charset=us-ascii Dear all, Could anybody please tell me the anwere to these questions ? Why does the complexity in MAC protocol design for wireless ad hoc networks arises due to : 1. node mobility 2. radio link vulnerability and 3. the lack of central coordination Thanks for the consideration. Regards, Parag Goswami http://www.geocities.com/paragboom2k --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. --0-732977678-1098905395=:73697 Content-Type: text/html; charset=us-ascii
Dear all,
Could anybody please tell me the anwere to these questions ?
Why does the complexity in MAC protocol design for wireless ad hoc networks arises due to  :
1.  node mobility
2. radio link vulnerability and
3. the lack of central coordination
 
Thanks for the consideration.
 
Regards,
Parag Goswami

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses. --0-732977678-1098905395=:73697-- --===============0419632209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0419632209==-- From manet-bounces@ietf.org Wed Oct 27 18:13:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21382 for ; Wed, 27 Oct 2004 18:13:20 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMwGi-0000cw-5C for manet-web-archive@ietf.org; Wed, 27 Oct 2004 18:27:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMvsK-00034l-By; Wed, 27 Oct 2004 18:02:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMvo6-0001GF-NX for manet@megatron.ietf.org; Wed, 27 Oct 2004 17:58:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19721 for ; Wed, 27 Oct 2004 17:58:11 -0400 (EDT) Received: from oak.research.panasonic.com ([150.169.1.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMw23-0000Jn-9D for manet@ietf.org; Wed, 27 Oct 2004 18:12:39 -0400 Received: from redwood.research.panasonic.com (redwood.research.panasonic.com [150.169.3.3]) by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id i9RLvhrG009281; Wed, 27 Oct 2004 17:57:43 -0400 Received: from redwood.research.panasonic.com (redwood.research.panasonic.com [150.169.3.3]) by testing.research.panasonic.com (Postfix) with ESMTP id 232763C80E2; Wed, 27 Oct 2004 17:55:51 -0400 (EDT) Received: from Brijesh2K (dhcp251.Research.Panasonic.COM [150.169.1.251])by redwood.research.panasonic.com (Postfix) with SMTP id 18A183C80E1; Wed, 27 Oct 2004 17:55:51 -0400 (EDT) From: "Brijesh Kumar" To: "Parag Goswami" , Subject: RE: [manet] few questions about MAC protocol Date: Wed, 27 Oct 2004 18:01:20 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <20041027192955.74777.qmail@web90101.mail.scd.yahoo.com> X-imss-version: 2.8 X-imss-result: Passed X-imss-scores: Clean:99.90000 C:22 M:2 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Parag: It is a big area to explain. Here are some short answers, and pointers for you to explore further. >>Could anybody please tell me the anwere to these questions ? >> Why does the complexity in MAC protocol design for wireless ad hoc networks arises due to : >>1. node mobility Node mobility affects how time slots get allocated to existing nodes in the network/ or how often the contention will occur for the control of the channel. This directly affects throughput and energy efficiency of MAC protocols. >> 2. radio link vulnerability and Radio link vulnerability needs to be dealt with additional security mechanisms. The more information you put in a control channel, less you are left for data transmission. It has direct impact on efficiency of the MAC protocols. >>3. the lack of central coordination It is hard to obtain energy efficiency without central co-ordination. If no node tells you when to sleep and wake up to listen for incoming transmission, then you may have to listen to every frame from every one. That's not you want for large ad-hoc networks. Cheers, --bk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 27 20:29:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01195 for ; Wed, 27 Oct 2004 20:29:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMyOv-0003Ij-JN for manet-web-archive@ietf.org; Wed, 27 Oct 2004 20:44:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMy7o-00065w-HH; Wed, 27 Oct 2004 20:26:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMy5I-0005pQ-TR for manet@megatron.ietf.org; Wed, 27 Oct 2004 20:24:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01009 for ; Wed, 27 Oct 2004 20:24:06 -0400 (EDT) Received: from ziz.its.uow.edu.au ([130.130.68.16]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMyJE-0003Dt-EH for manet@ietf.org; Wed, 27 Oct 2004 20:38:35 -0400 Received: from localhost ([127.0.0.1] helo=ziz) by ziz.its.uow.edu.au with esmtp (Exim 4.34) id 1CMy5B-0006nt-Uz; Thu, 28 Oct 2004 10:24:02 +1000 Received: from localhost ([127.0.0.1]) by ziz.its.uow.edu.au (MailMonitor for SMTP v1.2.2 ) ; Thu, 28 Oct 2004 10:01:29 +1000 (EST) Received: from eros.snrc.uow.edu.au ([130.130.10.74]) by ziz.its.uow.edu.au with esmtp (Exim 4.34) id 1CMxjL-0004iu-7a; Thu, 28 Oct 2004 10:01:27 +1000 From: Mehran Abolhasan To: manet@ietf.org Subject: Re: [manet] Wi Max? Date: Thu, 28 Oct 2004 10:01:25 +1000 User-Agent: KMail/1.7 References: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> In-Reply-To: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200410281001.25413.mehrana@uow.edu.au> X-Envelope-From: X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Content-Transfer-Encoding: quoted-printable Hi, The main difference between Ad hoc networks and current WiFi networks is th= at=20 Ad hoc networks do not rely on any existing infrastructure (such as base=20 station) in order to perform routing. The nodes in Ad hoc networks can all= =20 act as routers. In WiFi, however, nodes require a base station to=20 communicate. Even in "ad hoc mode", most current WiFi devices do not really= =20 function as an ad hoc node. Regards, =2D-=20 Mehran Abolhasan B.E Computer, PhD Research Fellow Telecommunications and IT Research Institute (TITR) University of Wollongong Northfields Avenue, NSW, 2522, Australia Phone: +61 2 4221 3347 =46ax: +61 2 4221 3277 http://www.titr.uow.edu.au/~mehran Email 1: mehrana@uow.edu.au Email 2: mehran@titr.uow.edu.au=20 On Wed, 27 Oct 2004 07:36 pm, Giorgio Mulas wrote: > Dear Parag, > WiFi is a Layer 1 and 2 technology and it is not related with routing > issues. Ad hoc networking is a research topic considering routing issues > (and, of course, other important things) > > The main relation between WiFi and Ad hoc networks is that cheap > WiFi-enabled devices are usually used to build up testbeds for MANETs... > > BR. > > Giorgio > > > > > > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > Parag Goswami Sent: mercoled=EC 27 ottobre 2004 10.45 > To: manet@ietf.org > Subject: [manet] Wi Max? > > > Dear All, > If anybody tells me the major differences between Ad hoc networking and > WiFi. As we know both are used for the communication between mobile > nodes.Or is it the case that WiFi is also a part of Ad Hoc networking ? > > Best Regards, > Parag Goswami > http://www.geocities.com/paragboom2k > > > > _____ > > Do you Yahoo!? > Yahoo!=20 > ew_mail/static/ease.html> Mail Address AutoComplete - You start. We finish. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Oct 27 23:06:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11331 for ; Wed, 27 Oct 2004 23:06:44 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN0qg-0005v4-M2 for manet-web-archive@ietf.org; Wed, 27 Oct 2004 23:21:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN0Zm-000352-S1; Wed, 27 Oct 2004 23:03:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN0Zd-0002zZ-Ei for manet@megatron.ietf.org; Wed, 27 Oct 2004 23:03:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11208 for ; Wed, 27 Oct 2004 23:03:33 -0400 (EDT) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN0nb-0005rX-MZ for manet@ietf.org; Wed, 27 Oct 2004 23:18:04 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9S33TKj010178 for ; Wed, 27 Oct 2004 23:03:32 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Wed, 27 Oct 2004 23:03:27 -0400 Message-ID: <000001c4bc9a$b2889ee0$0600a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e Subject: [manet] Do MANET-To - Centralized Hybrids make sense? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1388673274==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186 This is a multi-part message in MIME format. --===============1388673274== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4BC79.2B76FEE0" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4BC79.2B76FEE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings Does it make sense for a MANET to switch to a Base-Station Architecture and visa-versa dynamically to fit certain situations? What might those situations be? Thanks and regards, Christopher ------=_NextPart_000_0001_01C4BC79.2B76FEE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings

 

Does it make sense for a MANET to switch to a = Base-Station Architecture and visa-versa dynamically to fit certain situations? What = might those situations be?

 

Thanks and regards,

 

Christopher

 

 

------=_NextPart_000_0001_01C4BC79.2B76FEE0-- --===============1388673274== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1388673274==-- From manet-bounces@ietf.org Thu Oct 28 03:20:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12915 for ; Thu, 28 Oct 2004 03:20:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN4ny-0001sX-NB for manet-web-archive@ietf.org; Thu, 28 Oct 2004 03:34:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4Xn-0000yo-UQ; Thu, 28 Oct 2004 03:17:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4XD-0000rW-MQ for manet@megatron.ietf.org; Thu, 28 Oct 2004 03:17:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12664 for ; Thu, 28 Oct 2004 03:17:22 -0400 (EDT) Received: from avas3.olemiss.edu ([130.74.120.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN4lF-0001p9-0C for manet@ietf.org; Thu, 28 Oct 2004 03:31:53 -0400 Received: from sunset.backbone.olemiss.edu (sunset [172.16.1.8]) by avas3.olemiss.edu (8.12.11/8.12.11) with ESMTP id i9S7HApX002717 for ; Thu, 28 Oct 2004 02:17:11 -0500 (envelope-from srgopal@olemiss.edu) Received: from olemiss.edu (webmail.olemiss.edu [172.16.1.11]) by sunset.backbone.olemiss.edu (8.12.10+Sun/8.12.9) with ESMTP id i9S7HA1c008989 for ; Thu, 28 Oct 2004 02:17:10 -0500 (CDT) From: "srgopal" To: manet@ietf.org X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Thu, 28 Oct 2004 02:17:10 -0500 Message-id: <41809cf6.11.2a0.979336357@olemiss.edu> X-UofMississippi-MailScanner-Information: Please contact the ISP for more information X-UofMississippi-MailScanner: Found to be clean X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.10.27.5 X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [manet] Help needed! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Dear all, Did anyone work with packet voice transmission in mobile Ad-Hoc networks? If you have done or know of some published work please let me know. Is 2% packet loss and 200 ms one-way delay tolerable in Voice transmissions in analyzing the voice call carrying capacity performance of an Ad-Hoc network? Thanks for your time and patience. Regards, Rja. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 28 03:34:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14689 for ; Thu, 28 Oct 2004 03:34:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN51z-0002Bj-Bg for manet-web-archive@ietf.org; Thu, 28 Oct 2004 03:49:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4iX-0002bB-1L; Thu, 28 Oct 2004 03:29:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4eX-00020a-Nt for manet@megatron.ietf.org; Thu, 28 Oct 2004 03:24:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13539 for ; Thu, 28 Oct 2004 03:24:56 -0400 (EDT) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN4sY-0001xN-Bt for manet@ietf.org; Thu, 28 Oct 2004 03:39:27 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] Do MANET-To - Centralized Hybrids make sense? Date: Thu, 28 Oct 2004 09:25:21 +0200 Message-ID: <9F1223587A755D47805AECAB7ECAF5D901666403@swing.cefriel.it> Thread-Topic: [manet] Do MANET-To - Centralized Hybrids make sense? thread-index: AcS8m61x0bJzTvcCTiePTxkbTxPWawAI4D+w From: "Giorgio Mulas" To: "Christopher P. Rigano" , X-Spam-Score: 0.2 (/) X-Scan-Signature: 1094b1c84fa6e846d476f39271f5074f X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1026697119==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 4fc59e88b356924367ae169e6a06365d This is a multi-part message in MIME format. --===============1026697119== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4BCBF.48A98285" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4BCBF.48A98285 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Christopher, you hit a very important issue. IMHO MANETs are not alternative to = infrastructure-based architecture, but complementary. MANETs add flexibility to infrastructure-based architectures by = extending coverage where building infrastructure is not *economically* = feasible or possible, or enhancing capacity when needed (e.g. during = temporary, that is *ad hoc*, events like football matches or fairs or = conferences involving a concentration of *communicating people*, = infrastructure, usually sized on average traffic capacity, cannot manage = effectively peaks of traffic). Neverthless, actually infrastructure-based architectures have usually = better performances in particular for that it concerns real-time = applications and security issues. =20 So the answer is YES it does make sense. =20 For further information you can follow these links:=20 * = http://www.nortelnetworks.com/solutions/wrlsmesh/index.html# =20 * http://www.meshnetworks.com/ (in = partnership with Motorola) Google -> "Mesh networks" =20 They are related to state-of-the-art commercial meshnetworking (i.e. Ad = hoc + infrastructure) solutions. =20 Best Regards =20 Giorgio =20 =20 =20 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of Christopher P. Rigano Sent: gioved=EC 28 ottobre 2004 5.03 To: manet@ietf.org Subject: [manet] Do MANET-To - Centralized Hybrids make sense? Greetings =20 Does it make sense for a MANET to switch to a Base-Station Architecture = and visa-versa dynamically to fit certain situations? What might those = situations be?=20 =20 Thanks and regards, =20 Christopher =20 =20 ------_=_NextPart_001_01C4BCBF.48A98285 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Dear=20 Christopher,
you=20 hit a very important issue. IMHO MANETs are not = alternative to=20 infrastructure-based architecture, but = complementary.
MANETs=20 add flexibility to infrastructure-based architectures by extending = coverage=20 where building infrastructure is not *economically* feasible or = possible,=20 or enhancing capacity when needed (e.g. during temporary, that is = *ad hoc*,=20 events like football matches or fairs or conferences involving = a=20 concentration of *communicating people*, infrastructure, = usually sized on=20 average traffic capacity, cannot manage effectively peaks of=20 traffic).
Neverthless, = actually infrastructure-based=20 architectures have usually better performances in particular for that it = concerns real-time applications and security issues.
 
So the=20 answer is YES it does make sense.
 
For=20 further information you can follow these links: 
•http://www.nortelnetworks.com/solutions/wrlsmesh/index.ht= ml# 
•http://www.meshnetworks.com/ (in partnership with = Motorola)
Google=20 -> "Mesh networks"
 
They=20 are related to state-of-the-art commercial meshnetworking (i.e. Ad hoc + = infrastructure) solutions.
 
Best=20 Regards
 
Giorgio
=
 
 
 
-----Original Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of = Christopher P. Rigano
Sent: gioved=EC 28 ottobre 2004=20 5.03
To: manet@ietf.org
Subject: [manet] Do = MANET-To -=20 Centralized Hybrids make sense?

Greetings

 

Does it make sense for a = MANET to=20 switch to a Base-Station Architecture and visa-versa dynamically to = fit=20 certain situations? What might those situations be?=20

 

Thanks and=20 regards,

 

Christopher

 

 

------_=_NextPart_001_01C4BCBF.48A98285-- --===============1026697119== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1026697119==-- From manet-bounces@ietf.org Thu Oct 28 05:08:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21951 for ; Thu, 28 Oct 2004 05:08:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN6V7-0004Ei-Di for manet-web-archive@ietf.org; Thu, 28 Oct 2004 05:23:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN6E9-0007Mb-GH; Thu, 28 Oct 2004 05:05:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN6CA-0006rg-DB for manet@megatron.ietf.org; Thu, 28 Oct 2004 05:03:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21515 for ; Thu, 28 Oct 2004 05:03:44 -0400 (EDT) Received: from web20926.mail.yahoo.com ([216.136.224.143]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CN6QC-00048m-By for manet@ietf.org; Thu, 28 Oct 2004 05:18:16 -0400 Message-ID: <20041028090344.70402.qmail@web20926.mail.yahoo.com> Received: from [203.208.193.230] by web20926.mail.yahoo.com via HTTP; Thu, 28 Oct 2004 02:03:44 PDT Date: Thu, 28 Oct 2004 02:03:44 -0700 (PDT) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Subject: [manet] problem in sensor networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1551381929==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --===============1551381929== Content-Type: multipart/alternative; boundary="0-1657761502-1098954224=:68404" --0-1657761502-1098954224=:68404 Content-Type: text/plain; charset=us-ascii Hi, I am Praveen form India. I am building a system using RF-ID sensors for automatic tracking of workers in underground mines. I have read publications on Sensor Networks, especially the MAC protocol of 802.11 is in my interest. In the publications, they highlight the need to change the MAC protocol to meet the energy constraints on Sensor Networks. But in case of my application, energy is not a problem. The RF-ID readers are deployed at key points in the Mine. They are connected through a wired backbone to the base station. The RF-ID tags can be either passive or active. When the RF-ID tag comes in the range of RF-reader, the RF-reader detects the unique number embedded in the RF-ID tag, and sends the data to base station. The wireless part is the communication between the RF-reader and RF-ID tags. I think, if we use the RF-ID tags as it is, then we have to change the MAC protocol, because the RF-ID tag has no capability of sensing the medium. If this is the case, what kind of mechanism should be used. The RF-ID tags, in our case are installed in the helmet of the worker and it can get power supply for the battery of the Miner's cap lamp. Since, we can give power supply to the RF-ID tag, I want to know, is it advisable to add some hardware to the RF-ID tag so that we can directly use 802.11 without any modification. Members in this group might have knowledge in this area. Kindly let me know, what will be the best approach so that my system can be cost effective and robust. Please also let me know if any body in this group is working on a similiar kind of project and if there is any possibility in which I can collaborate with you. Looking forward for your reply, Praveen. --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-1657761502-1098954224=:68404 Content-Type: text/html; charset=us-ascii
Hi,
 I am Praveen form India. I am building a system using RF-ID sensors for automatic tracking of workers in underground mines. I have read publications on Sensor Networks, especially the MAC protocol of 802.11 is in my interest. In the publications, they highlight the need to change the MAC protocol to meet the energy constraints on Sensor Networks. But in case of my application, energy is not a problem.
 
 The RF-ID readers are deployed at key points in the Mine. They are connected through a wired backbone to the base station. The RF-ID tags can be either passive or active. When the RF-ID tag comes in the range of RF-reader, the RF-reader detects the unique number embedded in the RF-ID tag, and sends the data to base station. The wireless part is the communication between the RF-reader and RF-ID tags. I think, if we use the RF-ID tags as it is, then we have to change the MAC protocol, because the RF-ID tag has no capability of sensing the medium. If this is the case, what kind of mechanism should be used.
 
The RF-ID tags, in our case are installed in the helmet of the worker and it can get power supply for the battery of the Miner's cap lamp. Since, we can give power supply to the RF-ID tag, I want to know, is it advisable to add some hardware to the RF-ID tag so that we can directly use 802.11 without any modification.
 
Members in this group might have knowledge in this area. Kindly let me know, what will be the best approach so that my system can be cost effective and robust. Please also let me know if any body in this group is working on a similiar kind of project and if there is any possibility in which I can collaborate with you.
 
Looking forward for your reply,
Praveen.

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-1657761502-1098954224=:68404-- --===============1551381929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1551381929==-- From manet-bounces@ietf.org Thu Oct 28 08:57:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09246 for ; Thu, 28 Oct 2004 08:57:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNA4e-0000LT-Jt for manet-web-archive@ietf.org; Thu, 28 Oct 2004 09:12:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN9kr-0005C8-OK; Thu, 28 Oct 2004 08:51:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN9ju-0004pv-Tk for manet@megatron.ietf.org; Thu, 28 Oct 2004 08:50:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08531 for ; Thu, 28 Oct 2004 08:50:50 -0400 (EDT) Received: from sangam.sce.carleton.ca ([134.117.4.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN9xz-00009D-IR for manet@ietf.org; Thu, 28 Oct 2004 09:05:24 -0400 Received: from localhost (webmail.sce.carleton.ca [134.117.4.46]) by sangam.sce.carleton.ca (8.12.11/8.12.11) with ESMTP id i9SCojr6007756; Thu, 28 Oct 2004 08:50:45 -0400 Received: from wmc-06.sce.carleton.ca (wmc-06.sce.carleton.ca [134.117.60.231]) by webmail.sce.carleton.ca (IMP) with HTTP for ; Thu, 28 Oct 2004 08:50:45 -0400 Message-ID: <1098967845.4180eb25ae192@webmail.sce.carleton.ca> Date: Thu, 28 Oct 2004 08:50:45 -0400 From: "Carlos H. Rentel" To: Rex Buddenberg Subject: RE: [manet] Wi Max? References: <9F1223587A755D47805AECAB7ECAF5D9016662D1@swing.cefriel.it> <1098899352.17791.279.camel@antony> In-Reply-To: <1098899352.17791.279.camel@antony> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.5 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by sangam.sce.carleton.ca id i9SCojr6007756 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Content-Transfer-Encoding: quoted-printable Hello, In my humble opinion though to say MANET is a layer 3 issue is mainly ove= r simplistic. IEEE 802.11 ("WiFi") or 802.16 (ver. a adapts better to the c= oncept of MANET, although more accurately speaking is a mesh concept) can not be= the ultimate (particullarly MAC) approach. MANETs is an *all layer* issue (an= d I am not necessarily referring to cross-layer design :) ). Best Regards, Carlos Rentel Quoting Rex Buddenberg : > Parag, > > Giorgio is right. MANET is a layer 3 issue and both WiFi and WiMax are > layer 1-2 technologies. > > That said ... Most experimental MANET stuff needs some kind of plumbin= g > underneath and WiFi (IEEE 802.11) has been popular for that. And a lot > of the experimentation has been done in 'ad hoc' or 'infrastructureless= ' > mode where two subscriber nodes can connect with each other. In short, > WiFi can be pretty promiscuous which happens to fit the MANET > intentions. And it's d.c. -- dirt cheap. > > Wi-MAX (IEEE 802.16) changes the MAC algorithm from a carrier sense one > used in WiFi (and it's antecedent, wired ethernet) to a scheduling > algorithm. Scheduling MACs rely only on the assumption that everyone > can hear the base station (BS); there's no requirement whatever that > peers (SSs) hear each other so the hidden node problem goes away (so in > v1, SS-to-SS is not well supported). Many satellite comms algorithms > (e.g. DAMA) fall in this general category, but are anemic by comparison > to .16. Scheduling MACs can also provide stability under overload / > oversubscription, bandwidth efficiency, and ability to control QoS to > the extent that we can provide deterministic service at layer 2 ... all > of which are important in many situations. ... but don't have much to > do with MANET. > What 802.16 does not do well yet is the Wi-Fi ad hoc mode. We may hav= e > to modify this statement soon as real compliant products start appearin= g > in the marketplace (the 802.16-2004 standard was ratified in June and > that seems to have uncorked a lot of development). There are two > developments in IEEE 802 that are germane here: > 1) there is 'mesh' work going on within 802.16 but it's acknowledged a= s > not being mature in the -2004 version. > 2) bit of bureaucratic dispute between 802.16, 802.20 and 802.22 about > the terms 'fixed' and 'mobile' in the PARs (charters). All three > committees (.20 and .22 are much less mature) have both MAC and PHY > development in their charter docs. But it's not at all clear why eithe= r > .20 or .22 need to develop a new MAC -- a little growth and maturity in > the .16 MAC may be all that's needed.... but the 802.16 PAR has the ter= m > 'fixed' in it. These two committees do indeed need to develop new PHY > standards for their particular purposes (cellphone --> packet switch an= d > TV spectrum reuse for rural, respectively). > > Wi-MAX is going to be interesting in the next few years. At least some > in the industry are planning to put Wi-Max chipsets in your laptop like > Wi-Fi ones are now. The shift from infrastructureless to a more > hierarchical layer 2 structure does change some of the MANET tacit > assumptions. > > Help? > > > On Wed, 2004-10-27 at 02:36, Giorgio Mulas wrote: > > Dear Parag, > > WiFi is a Layer 1 and 2 technology and it is not related with routing > > issues. > > Ad hoc networking is a research topic considering routing issues (and= , > > of course, other important things) > > > > The main relation between WiFi and Ad hoc networks is that cheap > > WiFi-enabled devices are usually used to build up testbeds for > > MANETs... > > > > BR. > > > > Giorgio > > > > > > > > > > -----Original Message----- > > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > > On Behalf Of Parag Goswami > > Sent: mercoled=C3=AC 27 ottobre 2004 10.45 > > To: manet@ietf.org > > Subject: [manet] Wi Max? > > > > > > Dear All, > > If anybody tells me the major differences between Ad hoc > > networking and WiFi. > > As we know both are used for the communication between mobile > > nodes.Or is it the case that WiFi is also a part of Ad Hoc > > networking ? > > > > Best Regards, > > Parag Goswami > > http://www.geocities.com/paragboom2k > > > > > > _____________________________________________________________= _ > > Do you Yahoo!? > > Yahoo! Mail Address AutoComplete - You start. We finish. > > > > > > _____________________________________________________________________= _ > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > -- > > 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 manet-bounces@ietf.org Thu Oct 28 09:36:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12012 for ; Thu, 28 Oct 2004 09:36:19 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNAg1-0001AL-DZ for manet-web-archive@ietf.org; Thu, 28 Oct 2004 09:50:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNAN5-0004GF-U1; Thu, 28 Oct 2004 09:31:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNAK2-0003h9-EH for manet@megatron.ietf.org; Thu, 28 Oct 2004 09:28:10 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11346 for ; Thu, 28 Oct 2004 09:28:09 -0400 (EDT) Received: from relay-pt1.siemens.pt ([194.145.62.202] helo=relay2.siemens.pt) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNAY5-0000y0-Aq for manet@ietf.org; Thu, 28 Oct 2004 09:42:43 -0400 Received: from fw-mta1.siemens.pt (fw-mta1.siemens.pt [141.29.156.201]) by relay2.siemens.pt (8.12.8/8.12.9) with ESMTP id i9SDJNx0008572 for ; Thu, 28 Oct 2004 14:19:36 +0100 Received: from lisi053a.siemens.pt (lisi053a.siemens.pt [141.29.156.193]) by fw-mta1.siemens.pt (Hvm) with ESMTP id i9SDSuw20818 for ; Thu, 28 Oct 2004 14:28:56 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Wi Max? Date: Thu, 28 Oct 2004 14:26:49 +0100 Message-ID: <852246F66844CC41A5FE1EF659F98F90016E5C1F@lisi053a.siemens.pt> Thread-Topic: [manet] Wi Max? Thread-Index: AcS87gtZb0kF3QoWTwyaOBuQ8MxRAwAA7K0A From: "Vitor Silva (Ext)" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9 Content-Transfer-Encoding: quoted-printable Hi all, Exactly... I don't see where is the doubt. WiFi, Wimax, IrDA, ... are = the L1/L2 technology that "glues" the nodes together. MANET is the = *network*, with all its layers and planes. It's the same as discussing = what is the relation between Ethernet and Internet. Ethernet is, or can = be, an element of Internet. There's here a "include" relation -- and = nothing more. Actually, there's no reason, in theory, why you cannot build a MANET out = of wired ethernet. From my point of view, it's just a practical issue: = it would be silly to do it. Finally, and probably it's where the confusion comes from, most current = MANET approaches are trimmed to work with wireless RF and somehow (but = easily understood...) strongly associated to 802.11. For that reason, = all its proposed mechanisms are somewhat thought having 802.11 in mind, = although it should be as independent as possible of the underlaying = MAC/PHY technologies. But, then again, that's "only" a practical issue: = 802.11 is, at least for now, the top enabler for MANETs. --V=EDtor JS -----Original Message----- From: Carlos H. Rentel [mailto:crentel@sce.carleton.ca]=20 Sent: quinta-feira, 28 de Outubro de 2004 13:51 To: Rex Buddenberg Cc: manet@ietf.org Subject: RE: [manet] Wi Max? Hello, In my humble opinion though to say MANET is a layer 3 issue is mainly = over simplistic. IEEE 802.11 ("WiFi") or 802.16 (ver. a adapts better to the = concept of MANET, although more accurately speaking is a mesh concept) can not = be the ultimate (particullarly MAC) approach. MANETs is an *all layer* issue = (and I am not necessarily referring to cross-layer design :) ). Best Regards, Carlos Rentel Quoting Rex Buddenberg : > Parag, > > Giorgio is right. MANET is a layer 3 issue and both WiFi and WiMax = are > layer 1-2 technologies. > > That said ... Most experimental MANET stuff needs some kind of = plumbing > underneath and WiFi (IEEE 802.11) has been popular for that. And a = lot > of the experimentation has been done in 'ad hoc' or = 'infrastructureless' > mode where two subscriber nodes can connect with each other. In = short, > WiFi can be pretty promiscuous which happens to fit the MANET > intentions. And it's d.c. -- dirt cheap. > > Wi-MAX (IEEE 802.16) changes the MAC algorithm from a carrier sense = one > used in WiFi (and it's antecedent, wired ethernet) to a scheduling > algorithm. Scheduling MACs rely only on the assumption that everyone > can hear the base station (BS); there's no requirement whatever that > peers (SSs) hear each other so the hidden node problem goes away (so = in > v1, SS-to-SS is not well supported). Many satellite comms algorithms > (e.g. DAMA) fall in this general category, but are anemic by = comparison > to .16. Scheduling MACs can also provide stability under overload / > oversubscription, bandwidth efficiency, and ability to control QoS to > the extent that we can provide deterministic service at layer 2 ... = all > of which are important in many situations. ... but don't have much to > do with MANET. > What 802.16 does not do well yet is the Wi-Fi ad hoc mode. We may = have > to modify this statement soon as real compliant products start = appearing > in the marketplace (the 802.16-2004 standard was ratified in June and > that seems to have uncorked a lot of development). There are two > developments in IEEE 802 that are germane here: > 1) there is 'mesh' work going on within 802.16 but it's acknowledged = as > not being mature in the -2004 version. > 2) bit of bureaucratic dispute between 802.16, 802.20 and 802.22 = about > the terms 'fixed' and 'mobile' in the PARs (charters). All three > committees (.20 and .22 are much less mature) have both MAC and PHY > development in their charter docs. But it's not at all clear why = either > .20 or .22 need to develop a new MAC -- a little growth and maturity = in > the .16 MAC may be all that's needed.... but the 802.16 PAR has the = term > 'fixed' in it. These two committees do indeed need to develop new PHY > standards for their particular purposes (cellphone --> packet switch = and > TV spectrum reuse for rural, respectively). > > Wi-MAX is going to be interesting in the next few years. At least = some > in the industry are planning to put Wi-Max chipsets in your laptop = like > Wi-Fi ones are now. The shift from infrastructureless to a more > hierarchical layer 2 structure does change some of the MANET tacit > assumptions. > > Help? > > > On Wed, 2004-10-27 at 02:36, Giorgio Mulas wrote: > > Dear Parag, > > WiFi is a Layer 1 and 2 technology and it is not related with = routing > > issues. > > Ad hoc networking is a research topic considering routing issues = (and, > > of course, other important things) > > > > The main relation between WiFi and Ad hoc networks is that cheap > > WiFi-enabled devices are usually used to build up testbeds for > > MANETs... > > > > BR. > > > > Giorgio > > > > > > > > > > -----Original Message----- > > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > > On Behalf Of Parag Goswami > > Sent: mercoled=C3=AC 27 ottobre 2004 10.45 > > To: manet@ietf.org > > Subject: [manet] Wi Max? > > > > > > Dear All, > > If anybody tells me the major differences between Ad hoc > > networking and WiFi. > > As we know both are used for the communication between = mobile > > nodes.Or is it the case that WiFi is also a part of Ad Hoc > > networking ? > > > > Best Regards, > > Parag Goswami > > http://www.geocities.com/paragboom2k > > > > > > = ______________________________________________________________ > > Do you Yahoo!? > > Yahoo! Mail Address AutoComplete - You start. We finish. > > > > > > = ______________________________________________________________________ > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > -- > > 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 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 28 13:20:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24426 for ; Thu, 28 Oct 2004 13:20:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNEAv-0005Zr-1G for manet-web-archive@ietf.org; Thu, 28 Oct 2004 13:35:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNCfE-0006wa-08; Thu, 28 Oct 2004 11:58:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBgw-0004QT-Ui for manet@megatron.ietf.org; Thu, 28 Oct 2004 10:55:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20590 for ; Thu, 28 Oct 2004 10:55:54 -0400 (EDT) Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNBv2-00038X-Sm for manet@ietf.org; Thu, 28 Oct 2004 11:10:29 -0400 Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C66543083D; Thu, 28 Oct 2004 16:55:15 +0200 (CEST) Received: from correo.um.es (zape.um.es [155.54.212.102]) by smtp.um.es (Postfix) with ESMTP id A8CB63074A; Thu, 28 Oct 2004 16:55:15 +0200 (CEST) Received: from dif.um.es (dibulibu.um.es [155.54.1.250]) by correo.um.es (Postfix) with ESMTP id 8F8235CCA; Thu, 28 Oct 2004 16:55:13 +0200 (MEST) Message-ID: <418108E7.9030202@dif.um.es> Date: Thu, 28 Oct 2004 16:57:43 +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: srgopal@olemiss.edu Subject: Re: [manet] Help needed! References: <41809cf6.11.2a0.979336357@olemiss.edu> In-Reply-To: <41809cf6.11.2a0.979336357@olemiss.edu> 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 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Dear Rja, In my group we did some experiments with adaptive applications for videoconferencing over MANETs. In some of them we focus en maximizing the user-perceived QoS, and we measure the quality using the MOS from ITU. You can get some of those papers from http://ants.dif.um.es/staff/pedrom/publications.html In general, more than 450 ms of end-2-end delay is completely untolerable, and packet losses up to 10% (for voide, not audio tracks) can be easily tolerable. From 10 to 20% the quality severely degrades, and around 20% and beyond it is very bad and unacceptable quality. Please do not hesitate con contactme in case you need further information or some of the papers listed in my page but without the PDF file available. Regards, --Pedro srgopal wrote: >Dear all, > >Did anyone work with packet voice transmission in mobile >Ad-Hoc networks? If you have done or know of some published >work please let me know. >Is 2% packet loss and 200 ms one-way delay tolerable in >Voice transmissions in analyzing the voice call carrying >capacity performance of an Ad-Hoc network? > >Thanks for your time and patience. >Regards, >Rja. > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Oct 28 22:59:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29034 for ; Thu, 28 Oct 2004 22:59:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNND3-0001jL-Tl for manet-web-archive@ietf.org; Thu, 28 Oct 2004 23:13:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNMGH-0007ZW-OF; Thu, 28 Oct 2004 22:13:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJqZ-0002fe-2V for manet@megatron.ietf.org; Thu, 28 Oct 2004 19:38:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13731 for ; Thu, 28 Oct 2004 19:38:20 -0400 (EDT) Received: from wproxy.gmail.com ([64.233.184.197]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNK4i-0004S7-EK for manet@ietf.org; Thu, 28 Oct 2004 19:53:01 -0400 Received: by wproxy.gmail.com with SMTP id 55so561069wri for ; Thu, 28 Oct 2004 16:37:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=AhY7uOWita11XJeVxuWt3BWnA6ehAZ5ODPDsgRq+kvwapdSvtDX8i54B/ui5awWLuccKWZ+R/Biohlgd5FJdHRBXQsSmNBrX42XJxlKvewg84cc5lnZlvdm5mDmMm8bU+FU69ftg7agRat//6UOuHiN3UuygDhi8v8HvrXOjmwU= Received: by 10.38.76.16 with SMTP id y16mr1619806rna; Thu, 28 Oct 2004 16:37:25 -0700 (PDT) Received: by 10.38.152.32 with HTTP; Thu, 28 Oct 2004 16:37:25 -0700 (PDT) Message-ID: <645d37c5041028163761dba794@mail.gmail.com> Date: Thu, 28 Oct 2004 18:37:25 -0500 From: Vivek raghunathan To: srgopal@olemiss.edu Subject: Re: [manet] Help needed! In-Reply-To: <41809cf6.11.2a0.979336357@olemiss.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41809cf6.11.2a0.979336357@olemiss.edu> X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vivek raghunathan List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Rja, Yan Wu, a Masters student with Prof. P. R. Kumar's group at UIUC, had done a study of the voice call carrying capacity of wireless networks. You can contact Prof. P. R. Kumar (prkumar@uiuc.edu) for a copy of her Masters thesis. -Vivek On Thu, 28 Oct 2004 02:17:10 -0500, srgopal wrote: > Dear all, > > Did anyone work with packet voice transmission in mobile > Ad-Hoc networks? If you have done or know of some published > work please let me know. > Is 2% packet loss and 200 ms one-way delay tolerable in > Voice transmissions in analyzing the voice call carrying > capacity performance of an Ad-Hoc network? > > Thanks for your time and patience. > Regards, > Rja. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 00:22:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06908 for ; Fri, 29 Oct 2004 00:22:47 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNOVz-0004C0-NV for manet-web-archive@ietf.org; Fri, 29 Oct 2004 00:37:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNO1n-00025g-DO; Fri, 29 Oct 2004 00:06:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNNoY-00070e-QP for manet@megatron.ietf.org; Thu, 28 Oct 2004 23:52:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05363 for ; Thu, 28 Oct 2004 23:52:33 -0400 (EDT) Received: from green.its.bldrdoc.gov ([132.163.64.205] helo=its.bldrdoc.gov) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNO2l-0003hX-C4 for manet@ietf.org; Fri, 29 Oct 2004 00:07:16 -0400 Received: from its.bldrdoc.gov (localhost.0.0.127.in-addr.arpa [127.0.0.1] (may be forged)) by its.bldrdoc.gov (8.12.8p1/8.12.8) with SMTP id i9T3psJ9019864; Thu, 28 Oct 2004 21:51:54 -0600 (MDT) From: Andrew Thiessen Received: from 148-190-120-209.mesanetworks.net ([209.120.190.148]) (SquirrelMail authenticated user andrew) by www.its.bldrdoc.gov with HTTP; Thu, 28 Oct 2004 21:51:54 -0600 (MDT) Message-ID: <32790.209.120.190.148.1099021914.squirrel@www.its.bldrdoc.gov> Date: Thu, 28 Oct 2004 21:51:54 -0600 (MDT) Subject: Re: [manet] Help needed! To: In-Reply-To: <645d37c5041028163761dba794@mail.gmail.com> References: <41809cf6.11.2a0.979336357@olemiss.edu> <645d37c5041028163761dba794@mail.gmail.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 8bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 8bit Rja, You might also look into the work that Professor Tobagi at Stanford has done regarding multimedia (specifically voice) over wireless networks. Most of his work has been published in IEEE journals, but I think a good portion can be found on his website off the Stanford portal. Andy > Rja, > > Yan Wu, a Masters student with Prof. P. R. Kumar's group at UIUC, had > done a study of the voice call carrying capacity of wireless networks. > You can contact Prof. P. R. Kumar (prkumar@uiuc.edu) for a copy of her > Masters thesis. > > -Vivek > > > > On Thu, 28 Oct 2004 02:17:10 -0500, srgopal wrote: >> Dear all, >> >> Did anyone work with packet voice transmission in mobile >> Ad-Hoc networks? If you have done or know of some published >> work please let me know. >> Is 2% packet loss and 200 ms one-way delay tolerable in >> Voice transmissions in analyzing the voice call carrying >> capacity performance of an Ad-Hoc network? >> >> Thanks for your time and patience. >> Regards, >> Rja. >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 03:34:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02824 for ; Fri, 29 Oct 2004 03:34:35 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNRVf-0007ei-2w for manet-web-archive@ietf.org; Fri, 29 Oct 2004 03:49:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNR2s-0000UP-Cr; Fri, 29 Oct 2004 03:19:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNQuV-0003lF-3x for manet@megatron.ietf.org; Fri, 29 Oct 2004 03:10:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00897 for ; Fri, 29 Oct 2004 03:10:52 -0400 (EDT) Received: from xizor.is.scarlet.be ([193.74.71.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNR8h-00074U-U2 for manet@ietf.org; Fri, 29 Oct 2004 03:25:36 -0400 Received: from (u81-11-143-233.adsl.scarlet.be [81.11.143.233]) by xizor.is.scarlet.be with ESMTP id i9T7Ag514668 for ; Fri, 29 Oct 2004 09:10:42 +0200 From: Bart Braem To: manet@ietf.org Date: Fri, 29 Oct 2004 09:10:42 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410290910.42321.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Subject: [manet] AODV: Confusion about signed comparison sequence numbers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit I am having a problem understanding chapter 6.1 of the AODV RFC: how does the comparison of sequence numbers work: "This comparison MUST be done using signed 32-bit arithmetic, this is necessary to accomplish sequence number rollover. If the result of subtracting the currently stored sequence number from the value of the incoming sequence number is less than zero, then the information related to that destination in the AODV message MUST be discarded, since that information is stale compared to the node's currently stored information." Now I don't understand why it's not the other way round: when the value is larger than zero, then ... Because when I have to number that are smaller than 2^31-1 they have their most significant bit on 0. Then, according to what I know and can find, the unsigned and the signed integer value are the same. So what's written in the RFC is: if the currently stored sequence number is smaller then the incoming sequence number (their difference is negative), then the newer information MUST be discarded? I know there must be a mistake in my reasoning, but where? Thanks a lot for any information, Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 05:13:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10148 for ; Fri, 29 Oct 2004 05:13:28 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNT3N-0001VN-MC for manet-web-archive@ietf.org; Fri, 29 Oct 2004 05:28:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNSNk-0001UI-EG; Fri, 29 Oct 2004 04:45:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNS9n-0001iP-Ix for manet@megatron.ietf.org; Fri, 29 Oct 2004 04:30:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07423 for ; Fri, 29 Oct 2004 04:30:45 -0400 (EDT) Received: from xizor.is.scarlet.be ([193.74.71.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNSO1-0000ik-NC for manet@ietf.org; Fri, 29 Oct 2004 04:45:31 -0400 Received: from (u81-11-143-233.adsl.scarlet.be [81.11.143.233]) by xizor.is.scarlet.be with ESMTP id i9T8UQ500568; Fri, 29 Oct 2004 10:30:26 +0200 From: Bart Braem To: "Christian de Waal" Subject: Re: [manet] AODV: Confusion about signed comparison sequence numbers Date: Fri, 29 Oct 2004 10:30:26 +0200 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410291030.26918.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Op vrijdag 29 oktober 2004 10:23, schreef u: > "the result of subtracting the currently stored sequence number from the > value of the incoming sequence number" = "value of the incoming sequence > number" - "currently stored sequence number". > > This should solve your confusion. :) You are absolutely right, thanks a lot! Bart -- dwars, studentenblad van de UA www.dwars.ua.ac.be _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 09:59:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00910 for ; Fri, 29 Oct 2004 09:59:59 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXWh-0007jG-Gf for manet-web-archive@ietf.org; Fri, 29 Oct 2004 10:14:47 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXC9-0007VM-8y; Fri, 29 Oct 2004 09:53:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWnb-0002mK-0g for manet@megatron.ietf.org; Fri, 29 Oct 2004 09:28:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27965 for ; Fri, 29 Oct 2004 09:28:09 -0400 (EDT) Received: from [203.199.83.135] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNX1h-0006vJ-Td for manet@ietf.org; Fri, 29 Oct 2004 09:42:56 -0400 Received: (qmail 16190 invoked by uid 510); 29 Oct 2004 13:27:30 -0000 Date: 29 Oct 2004 13:27:30 -0000 Message-ID: <20041029132730.16189.qmail@webmail45.rediffmail.com> Received: from unknown (203.208.193.230) by rediffmail.com via HTTP; 29 oct 2004 13:27:30 -0000 MIME-Version: 1.0 From: "gokina " To: manet@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Subject: [manet] Research Ideas X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gokina List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1661835070==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 This is a multipart mime message --===============1661835070== Content-type: multipart/alternative; boundary="Next_1099056450---0-203.199.83.135-16153" This is a multipart mime message --Next_1099056450---0-203.199.83.135-16153 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0AHi,
=0A I am doing research Independently in Mobile = Ad-hoc Networks and in Sensor Networks. I have some doubts in some of the r= esearch topics in these fields.
=0A
=0A1. I have read some publicati= ons about trust management in Peer-to-Peer networks. The concept of trust h= as been extended to Mobile Ad-hoc Networks. In P2P networks the nodes are s= tationary where as in the second case the nodes can move. Assume that the t= rust management is not centralized but distributed across the network. Each= node maintains trust information about the nodes which are in it's interes= t. Now, suppose one node is found guilty. The nodes in its surroundings can= know about this. Immediately after the node is found guilty, this particul= ar node can travel long distance where the nodes are not aware of his behav= iour. I want to know if the existing publications take care of this kind of= situation.
=0A
=0A2.  Is it possible to extend the concept of = trust to Sensor Networks. Since, Security is also an aspect of Sensor Netwo= rks, Is there any mechanism so that one Sensor can choose the routing path = that has trusted Sensors.
=0A
=0A3. In Peer-to-Peer Networks there i= s a concept of Super Nodes. In this they exploit the property that some nod= es are more powerful than other nodes. To the best of my knowledge, that ma= in problem in Sensor Networks is energy. Is it realistic, if we assume that= some nodes in Sensor Networks are more powerful than others and handle mos= t of the traffic on the behalf other nodes which are less powerful. Will it= be realistic, if we assume that these powerful nodes have no energy constr= aints. I mean can there be a situation where some of the Sensors in the Sen= sor Network have continuous power supply.
=0A
=0AI think if these ass= umptions are realistic, then there is a possibiltiy of giving new direction= to research in Sensor Networks. I am not sure, if this can be done. I requ= est the members in this group to clarify my ideas and if possible, kindly g= ive me some references.
=0A
=0ALooking forward for your reply,
=0A= Gokina.=0A

=0A

=0A=0A --Next_1099056450---0-203.199.83.135-16153 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0AHi,=0A I am doing research Independently in Mobile Ad-hoc Networks a= nd in Sensor Networks. I have some doubts in some of the research topics in= these fields. =0A=0A1. I have read some publications about trust managemen= t in Peer-to-Peer networks. The concept of trust has been extended to Mobil= e Ad-hoc Networks. In P2P networks the nodes are stationary where as in the= second case the nodes can move. Assume that the trust management is not ce= ntralized but distributed across the network. Each node maintains trust inf= ormation about the nodes which are in it's interest. Now, suppose one node = is found guilty. The nodes in its surroundings can know about this. Immedia= tely after the node is found guilty, this particular node can travel long d= istance where the nodes are not aware of his behaviour. I want to know if t= he existing publications take care of this kind of situation. =0A=0A2. Is = it possible to extend the concept of trust to Sensor Networks. Since, Secur= ity is also an aspect of Sensor Networks, Is there any mechanism so that on= e Sensor can choose the routing path that has trusted Sensors. =0A=0A3. In = Peer-to-Peer Networks there is a concept of Super Nodes. In this they explo= it the property that some nodes are more powerful than other nodes. To the = best of my knowledge, that main problem in Sensor Networks is energy. Is it= realistic, if we assume that some nodes in Sensor Networks are more powerf= ul than others and handle most of the traffic on the behalf other nodes whi= ch are less powerful. Will it be realistic, if we assume that these powerfu= l nodes have no energy constraints. I mean can there be a situation where s= ome of the Sensors in the Sensor Network have continuous power supply.=0A= =0AI think if these assumptions are realistic, then there is a possibiltiy = of giving new direction to research in Sensor Networks. I am not sure, if t= his can be done. I request the members in this group to clarify my ideas an= d if possible, kindly give me some references.=0A=0ALooking forward for you= r reply,=0AGokina. --Next_1099056450---0-203.199.83.135-16153-- --===============1661835070== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1661835070==-- From manet-bounces@ietf.org Fri Oct 29 10:07:37 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01732 for ; Fri, 29 Oct 2004 10:07:37 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXe5-0007tn-N6 for manet-web-archive@ietf.org; Fri, 29 Oct 2004 10:22:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXCM-0007kz-JV; Fri, 29 Oct 2004 09:53:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWoE-0003NH-OT for manet@megatron.ietf.org; Fri, 29 Oct 2004 09:28:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28026 for ; Fri, 29 Oct 2004 09:28:48 -0400 (EDT) Received: from [203.199.83.147] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNX2V-0006wF-9c for manet@ietf.org; Fri, 29 Oct 2004 09:43:36 -0400 Received: (qmail 13634 invoked by uid 510); 29 Oct 2004 13:28:19 -0000 Date: 29 Oct 2004 13:28:19 -0000 Message-ID: <20041029132819.13633.qmail@webmail25.rediffmail.com> Received: from unknown (203.208.193.230) by rediffmail.com via HTTP; 29 oct 2004 13:28:19 -0000 MIME-Version: 1.0 From: "gokina " To: manet@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Subject: [manet] Research Ideas X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gokina List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0621668016==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 This is a multipart mime message --===============0621668016== Content-type: multipart/alternative; boundary="Next_1099056499---0-203.199.83.147-13554" This is a multipart mime message --Next_1099056499---0-203.199.83.147-13554 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0AHi,
=0A I am doing research Independently in Mobile = Ad-hoc Networks and in Sensor Networks. I have some doubts in some of the r= esearch topics in these fields.
=0A
=0A1. I have read some publicati= ons about trust management in Peer-to-Peer networks. The concept of trust h= as been extended to Mobile Ad-hoc Networks. In P2P networks the nodes are s= tationary where as in the second case the nodes can move. Assume that the t= rust management is not centralized but distributed across the network. Each= node maintains trust information about the nodes which are in it's interes= t. Now, suppose one node is found guilty. The nodes in its surroundings can= know about this. Immediately after the node is found guilty, this particul= ar node can travel long distance where the nodes are not aware of his behav= iour. I want to know if the existing publications take care of this kind of= situation.
=0A
=0A2.  Is it possible to extend the concept of = trust to Sensor Networks. Since, Security is also an aspect of Sensor Netwo= rks, Is there any mechanism so that one Sensor can choose the routing path = that has trusted Sensors.
=0A
=0A3. In Peer-to-Peer Networks there i= s a concept of Super Nodes. In this they exploit the property that some nod= es are more powerful than other nodes. To the best of my knowledge, that ma= in problem in Sensor Networks is energy. Is it realistic, if we assume that= some nodes in Sensor Networks are more powerful than others and handle mos= t of the traffic on the behalf other nodes which are less powerful. Will it= be realistic, if we assume that these powerful nodes have no energy constr= aints. I mean can there be a situation where some of the Sensors in the Sen= sor Network have continuous power supply.
=0A
=0AI think if these ass= umptions are realistic, then there is a possibiltiy of giving new direction= to research in Sensor Networks. I am not sure, if this can be done. I requ= est the members in this group to clarify my ideas and if possible, kindly g= ive me some references.
=0A
=0ALooking forward for your reply,
=0A= Gokina.=0A

=0A

=0A=0A --Next_1099056499---0-203.199.83.147-13554 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0AHi,=0A I am doing research Independently in Mobile Ad-hoc Networks a= nd in Sensor Networks. I have some doubts in some of the research topics in= these fields. =0A=0A1. I have read some publications about trust managemen= t in Peer-to-Peer networks. The concept of trust has been extended to Mobil= e Ad-hoc Networks. In P2P networks the nodes are stationary where as in the= second case the nodes can move. Assume that the trust management is not ce= ntralized but distributed across the network. Each node maintains trust inf= ormation about the nodes which are in it's interest. Now, suppose one node = is found guilty. The nodes in its surroundings can know about this. Immedia= tely after the node is found guilty, this particular node can travel long d= istance where the nodes are not aware of his behaviour. I want to know if t= he existing publications take care of this kind of situation. =0A=0A2. Is = it possible to extend the concept of trust to Sensor Networks. Since, Secur= ity is also an aspect of Sensor Networks, Is there any mechanism so that on= e Sensor can choose the routing path that has trusted Sensors. =0A=0A3. In = Peer-to-Peer Networks there is a concept of Super Nodes. In this they explo= it the property that some nodes are more powerful than other nodes. To the = best of my knowledge, that main problem in Sensor Networks is energy. Is it= realistic, if we assume that some nodes in Sensor Networks are more powerf= ul than others and handle most of the traffic on the behalf other nodes whi= ch are less powerful. Will it be realistic, if we assume that these powerfu= l nodes have no energy constraints. I mean can there be a situation where s= ome of the Sensors in the Sensor Network have continuous power supply.=0A= =0AI think if these assumptions are realistic, then there is a possibiltiy = of giving new direction to research in Sensor Networks. I am not sure, if t= his can be done. I request the members in this group to clarify my ideas an= d if possible, kindly give me some references.=0A=0ALooking forward for you= r reply,=0AGokina. --Next_1099056499---0-203.199.83.147-13554-- --===============0621668016== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0621668016==-- From manet-bounces@ietf.org Fri Oct 29 10:28:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04415 for ; Fri, 29 Oct 2004 10:28:38 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXyQ-0008WD-9a for manet-web-archive@ietf.org; Fri, 29 Oct 2004 10:43:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXbA-0006tO-Ep; Fri, 29 Oct 2004 10:19:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXLW-0006nL-Fb for manet@megatron.ietf.org; Fri, 29 Oct 2004 10:03:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01171 for ; Fri, 29 Oct 2004 10:03:12 -0400 (EDT) Received: from xizor.is.scarlet.be ([193.74.71.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXZl-0007nw-4N for manet@ietf.org; Fri, 29 Oct 2004 10:18:00 -0400 Received: from (u81-11-143-233.adsl.scarlet.be [81.11.143.233]) by xizor.is.scarlet.be with ESMTP id i9TE2u518942 for ; Fri, 29 Oct 2004 16:02:56 +0200 From: Bart Braem To: manet@ietf.org Date: Fri, 29 Oct 2004 16:02:56 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410291602.56149.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Subject: [manet] AODV: Gratuitous RREPs X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Hello, Another question regarding AODV: is there a rule in when to use the G flag and when not? I suspect that for TCP gratuitous RREPs are good and for UDP unnecessary, but I'm not really certain about that. Thanks for your replies, Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 10:30:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04580 for ; Fri, 29 Oct 2004 10:30:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNY09-000080-Oc for manet-web-archive@ietf.org; Fri, 29 Oct 2004 10:45:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXbC-0006vC-SC; Fri, 29 Oct 2004 10:19:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXOc-0000ip-59 for manet@megatron.ietf.org; Fri, 29 Oct 2004 10:06:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01552 for ; Fri, 29 Oct 2004 10:06:24 -0400 (EDT) Received: from oola.is.scarlet.be ([193.74.71.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXct-0007sI-2B for manet@ietf.org; Fri, 29 Oct 2004 10:21:12 -0400 Received: from (u81-11-143-233.adsl.scarlet.be [81.11.143.233]) by oola.is.scarlet.be with ESMTP id i9TE6NG28081 for ; Fri, 29 Oct 2004 16:06:23 +0200 From: Bart Braem To: manet@ietf.org Date: Fri, 29 Oct 2004 16:06:22 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410291606.23020.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] AODV: Very strange sentence in RFC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Hello, Chapter 6.6 reads, after the rules when generating RREPs: "When generating a RREP message, a node copies the Destination IP Address and the Originator Sequence Number from the RREQ message into the corresponding fields in the RREP message." Now that's strange: why the Originator Sequence Number, it's not really useful for the originator is it? There's no corresponding field for that one in the RREP either. Is this a mistake and should it be Destination Sequence Number? Greetings, Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 10:34:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05090 for ; Fri, 29 Oct 2004 10:34:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNY40-0000F2-DC for manet-web-archive@ietf.org; Fri, 29 Oct 2004 10:49:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXcw-0008Io-R7; Fri, 29 Oct 2004 10:21:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXQo-0003yh-Jh for manet@megatron.ietf.org; Fri, 29 Oct 2004 10:08:42 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01871 for ; Fri, 29 Oct 2004 10:08:40 -0400 (EDT) Received: from guri.is.scarlet.be ([193.74.71.22]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXf5-0007vG-Km for manet@ietf.org; Fri, 29 Oct 2004 10:23:29 -0400 Received: from (u81-11-143-233.adsl.scarlet.be [81.11.143.233]) by guri.is.scarlet.be with ESMTP id i9TE8dt21924 for ; Fri, 29 Oct 2004 16:08:39 +0200 From: Bart Braem To: manet@ietf.org Date: Fri, 29 Oct 2004 16:08:39 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410291608.39457.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Subject: [manet] AODV: previous hop for RREP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Hello, (This is my final question for today, sorry for the overload) Chapter 6.7 says to search for a route to the previous hop, which is that hop when considering RREPs? I can't really figure out wether it's the one on the forward route or the backward route... Thanks for your help, Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 11:02:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07160 for ; Fri, 29 Oct 2004 11:02:07 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNYUp-0000se-4I for manet-web-archive@ietf.org; Fri, 29 Oct 2004 11:16:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXvy-0003bW-Ns; Fri, 29 Oct 2004 10:40:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXdf-0000dA-Px for manet@megatron.ietf.org; Fri, 29 Oct 2004 10:21:59 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03908 for ; Fri, 29 Oct 2004 10:21:57 -0400 (EDT) Received: from zjuem.zju.edu.cn ([210.32.0.5] helo=eyou.net) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNXrv-0008LU-Sf for manet@ietf.org; Fri, 29 Oct 2004 10:36:46 -0400 Received: (eyou send program); Fri, 29 Oct 2004 22:20:41 +0800 Message-ID: <299059641.11047@eyou.net> X-EYOUMAIL-SMTPAUTH: jinxd@zju.edu.cn Received: from 10.13.72.25 by 10.10.2.41 with SMTP; Fri, 29 Oct 2004 22:20:40 +0800 Date: Fri, 29 Oct 2004 22:20:18 +0800 From: "Hang Su" To: "manet" X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.8 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Subject: [manet] Difference between wireless mesh networks and MANET X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Hi all, Can someone tell the differences between wireless mesh networks and wireless ad hoc networks. Is there any "include" relation between them? In the mesh networks, is the mobility of nodes important? Any suggestion would be appreciate. Cheers Hang Su _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 12:29:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13081 for ; Fri, 29 Oct 2004 12:29:55 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNZrp-0002ho-KC for manet-web-archive@ietf.org; Fri, 29 Oct 2004 12:44:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNZEf-0000eP-EM; Fri, 29 Oct 2004 12:04:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNZ8F-0004VB-3O for manet@megatron.ietf.org; Fri, 29 Oct 2004 11:57:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10883 for ; Fri, 29 Oct 2004 11:57:36 -0400 (EDT) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNZMX-00022d-3b for manet@ietf.org; Fri, 29 Oct 2004 12:12:26 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message Subject: RE: [manet] Difference between wireless mesh networks and MANET MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 29 Oct 2004 17:57:59 +0200 Message-ID: <9F1223587A755D47805AECAB7ECAF5D901666709@swing.cefriel.it> Thread-Topic: [manet] Difference between wireless mesh networks and MANET Thread-Index: AcS9zFvti+DOvI8ySYC2Zbyeq0wPSwAAEwWQ From: "Giorgio Mulas" To: "Hang Su" , "manet" X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: quoted-printable Hi Hang Su, Although these two expressions are usually used as synonims I think that = there could be a slight difference in the context you are using them.=20 I prefer to use the term *ad hoc* when I want to focus on the = self-organizing capability of nodes, while I prefer to use the term = *mesh* when I want to refer to the type of connections among nodes in = the network (that is every node can communicate in a distributed fashion = with all the nodes) Mobility is a particular characteristic of nodes and if you want to = highlight this characteristic as critical in the application you are = considering you could use the term MANETs (Mobile Ad hoc NETworks). This is just my opinion (de gustibus non est disputandum), the important = thing IMHO is to agree on a definition (chosen on an ad hoc basis :-) ) = if there are different points of view. Best Regards Giorgio =09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .=09 =09 =09 =09 Giorgio Mulas | Researcher=09 =09 CEFRIEL - Politecnico di Milano ICT Center of Excellence For Research, Innovation, Education & = industrial Labs partnership=20 Via Fucini, 2 =B7 20133 Milano (Italy) =09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .=09 [p. +39 02 23954 265 =B7 f. +39 02 23954 465 =B7 e. = giorgio.mulas@cefriel.it =B7 w. http://www.cefriel.it/~mulas =09 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of Hang Su Sent: venerd=EC 29 ottobre 2004 16.20 To: manet Subject: [manet] Difference between wireless mesh networks and MANET Hi all, Can someone tell the differences between wireless mesh networks and = wireless ad hoc networks. Is there any "include" relation between them? = In the mesh=20 networks, is the mobility of nodes important? Any suggestion would be appreciate. Cheers Hang Su _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 15:47:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29829 for ; Fri, 29 Oct 2004 15:47:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcwx-0007DZ-0D for manet-web-archive@ietf.org; Fri, 29 Oct 2004 16:02:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcM6-0000LZ-As; Fri, 29 Oct 2004 15:24:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcIS-0002NF-QT for manet@megatron.ietf.org; Fri, 29 Oct 2004 15:20:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27158 for ; Fri, 29 Oct 2004 15:20:22 -0400 (EDT) Received: from web21002.mail.yahoo.com ([216.136.227.56]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNcWd-0006UB-CO for manet@ietf.org; Fri, 29 Oct 2004 15:35:13 -0400 Message-ID: <20041029192012.54129.qmail@web21002.mail.yahoo.com> Received: from [141.225.9.226] by web21002.mail.yahoo.com via HTTP; Fri, 29 Oct 2004 12:20:12 PDT Date: Fri, 29 Oct 2004 12:20:12 -0700 (PDT) From: Yang Xiao To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA27158 Subject: [manet] Final Call -Journal Special issue of WCMC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: quoted-printable Journal of Wireless Communications and Mobile Computing=20 Special Issue Announcement=20 =20 Mobility, Paging and Quality of Service Management for Future Wireless Networks ---------------------------------------------------------------------- Guest Editors Yang Xiao, The University of Memphis, USA E-mail: yangxiao@memphis.edu =20 Yi Pan, Georgia State University, USA E-mail: pan@cs.gsu.edu =20 Kin K. Leung, Bell Labs, Lucent Technologies, USA E-mail: kin@bell-labs.com ---------------------------------------------------------------------- =20 Recently, the demand for wireless communications has grown tremendously. The need for "information anywhere anytime" has been a driving force for the increasing growth and advances in wireless communication and portable computing devices. The field of mobile computing and wireless computing is the merging place of these advances in information processing and communication with the aim of providing seamless and ubiquitous computing environment for mobile users. Location management, mobility management, and paging management are critical issues to provide "information anywhere anytime." Furthermore, requested information and services have to be delivered to mobile users with adequate quality of service (QoS). Ensuring expected QoS is still a big challenge, especially in light of user mobility and environments with heterogeneous wireless networks such as 3G/4G network, wireless LAN and ad hoc network. The purpose of the special issue is to focus on the novel ways in which location, mobility, paging and QoS management schemes for cellular networks, mobile IP, wireless LANs and ad hoc networks. Specific areas of interest include (but are not limited to): Location and mobility management for cellular networks, mobile IP, IEEE 802.11 wireless LANs, and mobile ad hoc networks.=20 Location and mobility models for future wireless networks=20 Paging management for cellular networks and mobile IP=20 Algorithms, designs and protocols for quality of service in future wireless networks=20 Integration of location management and quality of service for wireless networks=20 Integration of 3G and IEEE 802.11 wireless LANs=20 Resource management and control algorithms for multimedia applications=20 Performance model and analysis of management algorithms and protocols=20 =20 The manuscripts should be submitted as an e-mail attachment in PDF format to Yang Xiao at yangxiao@memphis.edu. If the file is larger than 1MB, the authors are encouraged to use WINZIP. Detailed instructions to authors can be found in: http://www3.interscience.wiley.com/cgi-bin/jabout/76507157/ForAuthors.htm= l =20 ---------------------------------------------------------------------- =20 Schedule: =B7 Submission deadline: November 1, 2004=20 =B7 Notification of acceptance: March 1, 2005 =B7 Submission of final version: April 15, 2005 =B7 Publication of special issue: Second half of 2005=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 17:18:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13713 for ; Fri, 29 Oct 2004 17:18:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNeNN-0002XR-HF for manet-web-archive@ietf.org; Fri, 29 Oct 2004 17:33:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNdhl-0003Pt-Fx; Fri, 29 Oct 2004 16:50:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcue-0004Mm-74 for manet@megatron.ietf.org; Fri, 29 Oct 2004 15:59:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01171 for ; Fri, 29 Oct 2004 15:59:49 -0400 (EDT) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNd8y-0007Z6-OV for manet@ietf.org; Fri, 29 Oct 2004 16:14:41 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9TJxZKj001643 for ; Fri, 29 Oct 2004 15:59:46 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Fri, 29 Oct 2004 15:59:34 -0400 Message-ID: <000001c4bdf1$d0aa82a0$0600a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 2.3 (++) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Subject: [manet] Are there protocols that are like SIP or H.323 that could provide session or peer-peer sceesions in MANETS for Voice or Multimedia? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0780866973==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407 This is a multi-part message in MIME format. --===============0780866973== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4BDD0.4998E2A0" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4BDD0.4998E2A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ------=_NextPart_000_0001_01C4BDD0.4998E2A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

------=_NextPart_000_0001_01C4BDD0.4998E2A0-- --===============0780866973== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0780866973==-- From manet-bounces@ietf.org Fri Oct 29 18:04:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18949 for ; Fri, 29 Oct 2004 18:04:19 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNf5T-0003tT-OL for manet-web-archive@ietf.org; Fri, 29 Oct 2004 18:19:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNea2-0005EW-M7; Fri, 29 Oct 2004 17:46:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNeAF-0007HQ-A7 for manet@megatron.ietf.org; Fri, 29 Oct 2004 17:20:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13930 for ; Fri, 29 Oct 2004 17:20:00 -0400 (EDT) Received: from web13201.mail.yahoo.com ([216.136.174.186]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNeOP-0002Zi-Oh for manet@ietf.org; Fri, 29 Oct 2004 17:34:53 -0400 Message-ID: <20041029211942.1691.qmail@web13201.mail.yahoo.com> Received: from [156.26.108.95] by web13201.mail.yahoo.com via HTTP; Fri, 29 Oct 2004 14:19:42 PDT Date: Fri, 29 Oct 2004 14:19:42 -0700 (PDT) From: sumanth sarma To: manet@ietf.org In-Reply-To: <200410291030.26918.bart.braem@ua.ac.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [manet] Mandrake 10.0/ns2 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Hello, I am using Mandrake 10.0 distro. I have problem installing ns2.27 on the machine. Did any of you had same kind of problem before?..If yes please let me know what is the fix. thanks, Sumanth __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 18:32:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21830 for ; Fri, 29 Oct 2004 18:32:56 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNfXC-0004Qy-LZ for manet-web-archive@ietf.org; Fri, 29 Oct 2004 18:47:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNf9V-0005Q5-HM; Fri, 29 Oct 2004 18:23:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNexv-0004EK-G8 for manet@megatron.ietf.org; Fri, 29 Oct 2004 18:11:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20071 for ; Fri, 29 Oct 2004 18:11:20 -0400 (EDT) Received: from wproxy.gmail.com ([64.233.184.196]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNfCE-00043z-Uq for manet@ietf.org; Fri, 29 Oct 2004 18:26:14 -0400 Received: by wproxy.gmail.com with SMTP id 44so522329wri for ; Fri, 29 Oct 2004 15:10:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=gQpex0BfWWKRyJI4iogk1ydLmzERWQKNe710v2s0WTvjb1ytB3lhUQzgTOXb8w5innLHU6+400KGFH8Ys9AY0/O4VLT3seJNOD7vVJRIMxP0Po8BYvPtH+sLs4lED0gvArhZXU86okd95jVBzFAU54Imtja0SWHk70n5sm5p7Sk= Received: by 10.38.15.20 with SMTP id 20mr1337304rno; Fri, 29 Oct 2004 15:10:44 -0700 (PDT) Received: by 10.38.15.65 with HTTP; Fri, 29 Oct 2004 15:10:44 -0700 (PDT) Message-ID: <78e4c4dc04102915102283266c@mail.gmail.com> Date: Fri, 29 Oct 2004 15:10:44 -0700 From: Pankaj Godbole To: Hang Su Subject: Re: [manet] Difference between wireless mesh networks and MANET In-Reply-To: <9F1223587A755D47805AECAB7ECAF5D901666709@swing.cefriel.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <9F1223587A755D47805AECAB7ECAF5D901666709@swing.cefriel.it> X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: quoted-printable Cc: manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pankaj Godbole List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: quoted-printable Hi Hang Su, Giorgio has explained the difference quite well. I'd just like to add a point to it. Essentially, MANETs are a type of mesh network, i.e. a subset of 'mesh' networks. Mesh networking to the mesh topology, which means that each node has a point-to-point and point-to-multipoint connectivity with other nodes, (thereby forming a mesh). Mobile ad-hoc networking, on the other hand, is networking among nodes that 1) form a network on the fly (ad-hoc manner), and 2) which could also be mobile. A mesh network can also be formed by wireless nodes that are static, e.g. mounted on lamp posts. That said, there are currently very few implementations of 'mesh networks' that are true MANETs. Regards, Pankaj. On Fri, 29 Oct 2004 17:57:59 +0200, Giorgio Mulas wrote: > Hi Hang Su, > Although these two expressions are usually used as synonims I think that = there could be a slight difference in the context you are using them. > I prefer to use the term *ad hoc* when I want to focus on the self-organi= zing capability of nodes, while I prefer to use the term *mesh* when I want= to refer to the type of connections among nodes in the network (that is ev= ery node can communicate in a distributed fashion with all the nodes) >=20 > Mobility is a particular characteristic of nodes and if you want to highl= ight this characteristic as critical in the application you are considerin= g you could use the term MANETs (Mobile Ad hoc NETworks). >=20 > This is just my opinion (de gustibus non est disputandum), the important = thing IMHO is to agree on a definition (chosen on an ad hoc basis :-) ) if = there are different points of view. >=20 > Best Regards >=20 > Giorgio >=20 > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . >=20 > Giorgio Mulas | Researcher >=20 > CEFRIEL - Politecnico di Milano > ICT Center of Excellence For Research, Innovation, Education & industrial= Labs partnership > Via Fucini, 2 =B7 20133 Milano (Italy) > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > [p. +39 02 23954 265 =B7 f. +39 02 23954 465 =B7 e. giorgio.mulas@cefri= el.it =B7 w. http://www.cefriel.it/~mulas >=20 >=20 >=20 >=20 > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of= Hang Su > Sent: venerd=EC 29 ottobre 2004 16.20 > To: manet > Subject: [manet] Difference between wireless mesh networks and MANET >=20 > Hi all, >=20 > Can someone tell the differences between wireless mesh networks and wirel= ess ad hoc networks. Is there any "include" relation between them? In the m= esh > networks, is the mobility of nodes important? >=20 > Any suggestion would be appreciate. >=20 > Cheers > Hang Su >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Oct 29 23:15:52 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07941 for ; Fri, 29 Oct 2004 23:15:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNjx0-0000cQ-OV for manet-web-archive@ietf.org; Fri, 29 Oct 2004 23:30:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNjRP-0005ds-6o; Fri, 29 Oct 2004 22:58:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNjIL-0002uL-DY for manet@megatron.ietf.org; Fri, 29 Oct 2004 22:48:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06312 for ; Fri, 29 Oct 2004 22:48:43 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.202]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNjWk-0000DU-ET for manet@ietf.org; Fri, 29 Oct 2004 23:03:38 -0400 Received: by rproxy.gmail.com with SMTP id 79so511rnl for ; Fri, 29 Oct 2004 19:48:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=KjhjbkKP9bIvgcR8XmNHEz7VNWyJAuDd/mYADc1ROBiKJM+VvI7mnWfflZ1YYDsmIBbeRpDUXKNzpUoIy2/qFaz0Ym0FNdpzB11ak8Bok+spZCx3fS4GY1qHaUBbp9aeaiM2I1qiYX/t/50ThZMAMTSX1aReGKwpCJgNSP0AyBs= Received: by 10.38.209.68 with SMTP id h68mr8022rng; Fri, 29 Oct 2004 19:48:35 -0700 (PDT) Received: by 10.38.15.65 with HTTP; Fri, 29 Oct 2004 19:48:35 -0700 (PDT) Message-ID: <78e4c4dc041029194821c4b9f4@mail.gmail.com> Date: Fri, 29 Oct 2004 19:48:35 -0700 From: Pankaj Godbole To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Subject: [manet] AODV kernel module problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pankaj Godbole List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Hi All, Has anybody tried to install and run the AODV kernel module from NIST ( kernel-aodv_v2.2.2)? I have successfully compiled this module, but when I try to run the script: start.sh, it returns an error saying "init_module: Operation not permitted" or "modprobe: Can't locate module" I have checked the paths to the module and also tried modifying the start.sh script but to no avail. If anyone has had success with this could you please guide me as to where I could be going wrong? Thanks in advance. Pankaj. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Oct 30 10:36:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26338 for ; Sat, 30 Oct 2004 10:36:07 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNuZQ-00033Q-5r for manet-web-archive@ietf.org; Sat, 30 Oct 2004 10:51:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNuB0-00080R-LG; Sat, 30 Oct 2004 10:25:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNu5z-00060y-U8 for manet@megatron.ietf.org; Sat, 30 Oct 2004 10:20:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25520 for ; Sat, 30 Oct 2004 10:20:41 -0400 (EDT) Received: from exch4.rhul.ac.uk ([134.219.201.11]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNuKU-0002oM-Vu for manet@ietf.org; Sat, 30 Oct 2004 10:35:43 -0400 Received: by exch4.rhul.ac.uk with Internet Mail Service (5.5.2656.59) id ; Sat, 30 Oct 2004 15:20:02 +0100 Message-ID: <74AB2EDFB513564CB272F5FF0E956CD20266AFAD@exch4.rhul.ac.uk> From: Yau P To: manet@ietf.org Subject: [manet] Another questions about MAC protocols Date: Sat, 30 Oct 2004 15:19:57 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Dear all, I was wondering if you help me answer a simple question. Assuming that 802.11 or some other similar MAC protocol is being used, and the ad hoc network in question is using AODV - does the broadcast of a RREQ undergo the same reliable delivery as with unicast packets (i.e. I think it is three attempts before 802.11 gives up)? Many thanks for your time in advance, Po _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Oct 30 10:51:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27105 for ; Sat, 30 Oct 2004 10:51:59 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNuom-0003Ks-8U for manet-web-archive@ietf.org; Sat, 30 Oct 2004 11:07:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNuOD-0004dY-0l; Sat, 30 Oct 2004 10:39:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNuCd-0008R4-8Q for manet@megatron.ietf.org; Sat, 30 Oct 2004 10:27:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25861 for ; Sat, 30 Oct 2004 10:27:32 -0400 (EDT) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNuR8-0002vf-EY for manet@ietf.org; Sat, 30 Oct 2004 10:42:34 -0400 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i9UERUkc027884 for ; Sat, 30 Oct 2004 10:27:31 -0400 (EDT) From: "Christopher P. Rigano" To: Date: Sat, 30 Oct 2004 10:27:26 -0400 Message-ID: <001301c4be8c$94a49750$0600a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Subject: [manet] Constant bit Rate (CBR) Traffic in MANET X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0118198131==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff This is a multi-part message in MIME format. --===============0118198131== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C4BE6B.0D960490" This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C4BE6B.0D960490 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit What is the best routing algorithm for CBR in MANETS? For example video streams to a central point form a mobile? Many thanks, Chris ------=_NextPart_000_0014_01C4BE6B.0D960490 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

What is the best routing algorithm for CBR in MANETS? = For example video streams to a central point form a = mobile?

 

Many thanks,

 

Chris

------=_NextPart_000_0014_01C4BE6B.0D960490-- --===============0118198131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0118198131==-- From manet-bounces@ietf.org Sat Oct 30 11:14:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27918 for ; Sat, 30 Oct 2004 11:14:55 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNvAy-0003eg-QK for manet-web-archive@ietf.org; Sat, 30 Oct 2004 11:29:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNugQ-0003kL-QF; Sat, 30 Oct 2004 10:58:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNuTG-0006B9-HR for manet@megatron.ietf.org; Sat, 30 Oct 2004 10:44:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26828 for ; Sat, 30 Oct 2004 10:44:44 -0400 (EDT) Received: from primary.vmtllc.com ([216.64.2.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNuhl-0003Cl-Vg for manet@ietf.org; Sat, 30 Oct 2004 10:59:46 -0400 Received: from amd2100 (localhost.localdomain [127.0.0.1]) by primary.vmtllc.com (8.11.6/8.11.6) with ESMTP id i9UEi8j28332; Sat, 30 Oct 2004 10:44:08 -0400 From: "Herbert Rubens" To: "'Yau P'" , Subject: RE: [manet] Another questions about MAC protocols Date: Sat, 30 Oct 2004 10:44:32 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <003c01c4be8e$f82b3070$6801a8c0@amd2100> 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.1441 In-Reply-To: <74AB2EDFB513564CB272F5FF0E956CD20266AFAD@exch4.rhul.ac.uk> X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: herb@cnds.jhu.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit This is no ACK or retransmission of broadcast packets, only unicast packets. So the RREQ will have no retransmissions by the lower layer but the RREP will since it is unicast back to the source. Hope this helps. -Herb -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Yau P Sent: Saturday, October 30, 2004 10:20 AM To: manet@ietf.org Subject: [manet] Another questions about MAC protocols Dear all, I was wondering if you help me answer a simple question. Assuming that 802.11 or some other similar MAC protocol is being used, and the ad hoc network in question is using AODV - does the broadcast of a RREQ undergo the same reliable delivery as with unicast packets (i.e. I think it is three attempts before 802.11 gives up)? Many thanks for your time in advance, Po _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Oct 30 11:31:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29286 for ; Sat, 30 Oct 2004 11:31:39 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNvRA-00042Y-S9 for manet-web-archive@ietf.org; Sat, 30 Oct 2004 11:46:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNv5J-0003ON-Uo; Sat, 30 Oct 2004 11:24:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNuw1-0000Oz-QY for manet@megatron.ietf.org; Sat, 30 Oct 2004 11:14:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27915 for ; Sat, 30 Oct 2004 11:14:27 -0400 (EDT) Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNvAU-0003dl-4s for manet@ietf.org; Sat, 30 Oct 2004 11:29:29 -0400 Received: (qmail 2480 invoked by uid 65534); 30 Oct 2004 15:13:48 -0000 Received: from unknown (EHLO 127.0.0.1) (67.176.36.236) by mail.gmx.net (mp010) with SMTP; 30 Oct 2004 17:13:48 +0200 X-Authenticated: #309278 Date: Sat, 30 Oct 2004 09:13:07 -0600 From: Daniel Henkel X-Mailer: The Bat! (v2.00.6) Business X-Priority: 3 (Normal) Message-ID: <104146498433.20041030091307@gmx.com> To: manet@ietf.org Subject: Re: [manet] Are there protocols that are like SIP or H.323 that could provide session or peer-peer sceesions in MANETS for Voice or Multimedia? In-Reply-To: <000001c4bdf1$d0aa82a0$0600a8c0@CPQ73745201364> References: <000001c4bdf1$d0aa82a0$0600a8c0@CPQ73745201364> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA27915 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Henkel List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable Hi Christopher, We have successfully used SIP to initiate VoIP sessions over several hops in our testbed. Using Linphone on both laptops and iPAQs we were able to have very reliable communication with our DSR implementation. You can possibly use a much more stripped down version of SIP and achieve same results if footprint is an issue; try oSIP: http://www.gnu.org/software/osip/osip.html Regards, Daniel Henkel University of Colorado at Boulder http://AUGNet.colorado.edu ---- Original Message ---- From: Christopher P. Rigano To: Subject: [manet] Are there protocols that are like SIP or H.323 that coul= d provide session or peer-peer sceesions in MANETS for Voice or Multimedi= a? Friday, October 29, 2004, 1:59:34 PM, you wrote: CPR> =A0 =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet