From manet-bounces@ietf.org Fri Apr 1 00:08:14 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20997 for ; Fri, 1 Apr 2005 00:08:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHEVX-00013y-4v for manet-web-archive@ietf.org; Fri, 01 Apr 2005 00:15:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHEN9-0005Ya-FV; Fri, 01 Apr 2005 00:07:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHEN7-0005YV-NM for manet@megatron.ietf.org; Fri, 01 Apr 2005 00:07:05 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20930 for ; Fri, 1 Apr 2005 00:07:03 -0500 (EST) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHEUN-0000zS-O2 for manet@ietf.org; Fri, 01 Apr 2005 00:14:36 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j31574tN005851 for ; Fri, 1 Apr 2005 00:07:04 -0500 (EST) Received: from gateway.ece.neu.edu ([129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005040100070330340 for ; Fri, 01 Apr 2005 00:07:03 -0500 Received: from localhost (basagni@localhost) by gateway.ece.neu.edu (8.9.3/8.9.3) with ESMTP id AAA22479 for ; Fri, 1 Apr 2005 00:07:03 -0500 (EST) X-Authentication-Warning: gateway.ece.neu.edu: basagni owned process doing -bs Date: Fri, 1 Apr 2005 00:07:02 -0500 (EST) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Subject: [manet] IEEE SECON 2005, Paper Registration Deadline is today! 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: a1852b4f554b02e7e4548cc7928acc1f We apologize if you receive multiple copies of this CfP ************************************************************* PAPER REGISTRATION IS NOW, APRIL 1st ************************************************************* Preliminary Announcement and Call for Papers *** IEEE SECON 2005 *** Second Annual IEEE Communications Society Conference on Sensor and Ad Hoc Communications and Networks Santa Clara, California, USA September 26-29, 2005 Paper Registration Deadline: April 1, 2005, by 5pm EST Paper Submission Deadline: April 6, 2005, by 5pm EDT http://www.ieee-secon.org/2005 ************************************************************ Building on the success of last year's inaugural conference, this new IEEE Communications Society conference will provide a forum to exchange ideas, techniques, and applications, discuss best practices, raise awareness and share experiences among researchers, practitioners, standard developers and policy makers in the field of sensor and ad hoc networks and systems. The conference will be organized to provide for a degree of collegiality and continuity in the discussions of the various topics among participants from the industrial, governmental and academic sectors. Original technical papers that address the communications, networking, systems and algorithmic aspects of ad hoc and sensor networks, as well as those that describe practical deployment and implementation experiences, are solicited for presentation at the conference and publication in the conference proceedings. Papers presenting novel contributions in such disciplines as communications, networking protocols and architectures, algorithms, embedded systems, middleware and information management, and novel applications are solicited. PAPERS: Full papers describing original, previously unpublished research work, experimental efforts, practical experiences, and industrial and commercial developments in sensor and ad hoc communications and networks. Papers with a deep focus on a specific discipline or stimulated by the synergistic interaction of diverse disciplines are encouraged. Particular topics of interest include, but are not limited to: * New architectures, protocols and access control to support communication, localization, time synchronization, routing and data dissemination in heterogeneous, large-scale distributed, ad hoc networks and sensor networks * Novel algorithms and theories for management, supervisory control and monitoring of distributed ad hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes * Modeling and performance evaluation of large-scale distributed and ad hoc sensor networks, practical implementations, and real-work experiences * Theories and models on fundamental information and communication aspects of wireless ad hoc and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and ad hoc networks * Integration of sensors into engineered systems, including novel techniques for sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing and efficient schemes to maximize accuracy and minimize false alarms * Chip-based systems incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware and tools for ad hoc and sensor network applications development, deployment and management * Mesh networking, mobile ad hoc peer-to-peer multipoint communications, applications and experiences TUTORIALS and PANELS: Proposals for tutorials and panels on current topics in the field of ad hoc and sensor networking and applications are solicited. Panels related to the commercial application and development of sensors and ad hoc networks are especially encouraged. DEMOS and EXPO: Demonstrations that showcases the practical implementations, industrial and commercial developments, and new applications for ad hoc and sensor networks are solicited. SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically through the EDAS system. Details regarding the paper format and the submission process will be posted at the conference web site. IMPORTANT DATES: April 6, 2005 Paper submission deadline May 1, 2005 Tutorial/Panel/Demo proposals deadline June 13, 2005 Notifications July 8, 2005 Camera-ready due date TPC Co-Chairs: Elizabeth Belding-Royer ebelding@cs.ucsb.edu Marwan Krunz krunz@ece.arizona.edu Thyaga Nandagopal thyaga@lucent.com General Chair: J.J. Garcia-Luna-Aceves jj@soe.ucsc.edu -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntington Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu *** http://www.ece.neu.edu/faculty/basagni/ *** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 1 10:47:23 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06192 for ; Fri, 1 Apr 2005 10:47:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHOU8-00075Y-UX for manet-web-archive@ietf.org; Fri, 01 Apr 2005 10:55:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOK8-0002u0-C8; Fri, 01 Apr 2005 10:44:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOK5-0002tv-Ob for manet@megatron.ietf.org; Fri, 01 Apr 2005 10:44:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06068 for ; Fri, 1 Apr 2005 10:44:35 -0500 (EST) Received: from wproxy.gmail.com ([64.233.184.197]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHORQ-0006z3-9v for manet@ietf.org; Fri, 01 Apr 2005 10:52:13 -0500 Received: by wproxy.gmail.com with SMTP id 71so1011888wri for ; Fri, 01 Apr 2005 07:44:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:reply-to:from:to:subject:date:mime-version:content-type:x-mailer:thread-index:x-mimeole:message-id; b=hdRJDGMAvT+rZdaTNjvpzIs6lv6wxeGz/VR1/FZ/gayuB4eKKoRvS/mV36+5XhXbwahKV/2bpsM4OHqAgKBIm8abAc6rsv7hKs3l9qjtkHp5/YTMQ7ShVhslSIUWpxurh/RNTTA3+p6O27UQk15lil8ysRRl7nOdyXfH62cODUs= Received: by 10.54.5.53 with SMTP id 53mr912841wre; Fri, 01 Apr 2005 07:44:27 -0800 (PST) Received: from laptop ([213.249.242.101]) by mx.gmail.com with ESMTP id d7sm689299wra.2005.04.01.07.44.26; Fri, 01 Apr 2005 07:44:27 -0800 (PST) From: "jason alcock" To: "manet" Subject: [manet] aodv query Date: Fri, 1 Apr 2005 16:44:31 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcU20bHE4SWV+ZtOQtON3eqXymueXA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: <424d6c5b.6f57ed49.0b5c.ffffc457@mx.gmail.com> X-Spam-Score: 1.1 (+) X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jason.alcock@gmail.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0193556960==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c This is a multi-part message in MIME format. --===============0193556960== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01C536DA.14FC32D0" This is a multi-part message in MIME format. ------=_NextPart_000_0004_01C536DA.14FC32D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi all Is their any point in implementing AODV unidirectional black list feature if I plan to use 802.11 at the link layer? Thanks in advance. Jason ------=_NextPart_000_0004_01C536DA.14FC32D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all

 

Is their any point in implementing AODV = unidirectional black list feature if I plan to use 802.11 at the link = layer?

 

Thanks in advance.

 

Jason

------=_NextPart_000_0004_01C536DA.14FC32D0-- --===============0193556960== 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 --===============0193556960==-- From manet-bounces@ietf.org Fri Apr 1 11:11:26 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08990 for ; Fri, 1 Apr 2005 11:11:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHOrQ-00084I-CX for manet-web-archive@ietf.org; Fri, 01 Apr 2005 11:19:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOh8-0006jJ-Dz; Fri, 01 Apr 2005 11:08:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOh4-0006jB-2N for manet@megatron.ietf.org; Fri, 01 Apr 2005 11:08:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08641 for ; Fri, 1 Apr 2005 11:08:19 -0500 (EST) Received: from web61105.mail.yahoo.com ([216.155.196.107]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DHOoP-0007wk-Mu for manet@ietf.org; Fri, 01 Apr 2005 11:15:58 -0500 Received: (qmail 50713 invoked by uid 60001); 1 Apr 2005 16:08:10 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ahOh1XCqO6822f8Fb5d/o19V1Uh0VWpSB/LV90RK1C7x2TfpDyWFi/zbDzz0Zz8kfvKyCXt/x+UAI0mRdSFygwLHl8BOcNkYqhBADN/b2OFZvG28xTx5ZA6UqKEmiWbSoUKgINW50DszWFZUURCRWuyZhtZFORBcgybw0hIJgrc= ; Message-ID: <20050401160810.50711.qmail@web61105.mail.yahoo.com> Received: from [66.208.44.5] by web61105.mail.yahoo.com via HTTP; Fri, 01 Apr 2005 08:08:09 PST Date: Fri, 1 Apr 2005 08:08:09 -0800 (PST) From: manet user Subject: Re: [MANET] AODV rfc query To: jason.alcock@gmail.com, manet In-Reply-To: <424c5d03.178c4ee1.54ae.239e@mx.gmail.com> MIME-Version: 1.0 X-Spam-Score: 0.2 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f 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="===============2019469170==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250 --===============2019469170== Content-Type: multipart/alternative; boundary="0-2003247112-1112371689=:50552" --0-2003247112-1112371689=:50552 Content-Type: text/plain; charset=us-ascii Hi Jason, The text in red explains the way forward route is created during a route discovery procedure. While receiving a RREP on an intermediate node, forward route is created by taking dest_addr as the address in "Destination IP Address" field of RREP message format and next_hop as the "Source Address" in IP header. Hope this helps. jason alcock wrote: st1\:*{behavior:url(#default#ieooui) } Hi all, I do not understand the bit about the next hop route entry (highlighted in red text below) from the AODV RFC 3561. Can anyone help please? 6.7. Receiving and Forwarding Route Replies If the route table entry to the destination is created or updated, then the following actions occur: - the route is marked as active, - the destination sequence number is marked as valid, - the next hop in the route entry is assigned to be the node from which the RREP is received, which is indicated by the source IP address field in the IP header, Thanks, Jason _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --------------------------------- Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. --0-2003247112-1112371689=:50552 Content-Type: text/html; charset=us-ascii
Hi Jason,
 
The text in red explains the way forward route is created during a route discovery procedure. While receiving a RREP on an intermediate node, forward route is created by taking dest_addr as the address in "Destination IP Address" field of RREP message format and next_hop as the "Source Address" in IP header.
 
Hope this helps.

jason alcock <jason.alcock@gmail.com> wrote:

Hi all,

 

I do not understand the bit about the next hop route entry (highlighted in red text below) from the AODV RFC 3561. Can anyone help please?

 

6.7. Receiving and Forwarding Route Replies

 

   If the route table entry to the destination is created or updated,

   then the following actions occur:

 

   -  the route is marked as active,

 

   -  the destination sequence number is marked as valid,

 

   -  the next hop in the route entry is assigned to be the node from

      which the RREP is received, which is indicated by the source IP

      address field in the IP header,

 

Thanks,

 

Jason

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

Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun. --0-2003247112-1112371689=:50552-- --===============2019469170== 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 --===============2019469170==-- From manet-bounces@ietf.org Fri Apr 1 11:23:06 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10207 for ; Fri, 1 Apr 2005 11:23:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHP2j-00008Y-AM for manet-web-archive@ietf.org; Fri, 01 Apr 2005 11:30:45 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOu2-0000e2-C1; Fri, 01 Apr 2005 11:21:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOtz-0000c0-OR for manet@megatron.ietf.org; Fri, 01 Apr 2005 11:21:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10090 for ; Fri, 1 Apr 2005 11:21:41 -0500 (EST) Received: from web61108.mail.yahoo.com ([216.155.196.110]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DHP1K-0008U9-V8 for manet@ietf.org; Fri, 01 Apr 2005 11:29:20 -0500 Received: (qmail 19407 invoked by uid 60001); 1 Apr 2005 16:21:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=un+ZboXcMgSEMBiLXzWvyHB6aulOhd55/26RRFpd4wsNj/BfLMZ6RRhR88XMN7Wq2uxcRNzPXBgXL5UnRIEVvPWxFDagrNOpGKgdDfaO0fzQerrwjxGzLDnInI0E3DmEYacchXvs+iyNWBqvDq7kAwWbdK3UWvOPCBbsdy8T5lk= ; Message-ID: <20050401162129.19405.qmail@web61108.mail.yahoo.com> Received: from [66.208.44.5] by web61108.mail.yahoo.com via HTTP; Fri, 01 Apr 2005 08:21:29 PST Date: Fri, 1 Apr 2005 08:21:29 -0800 (PST) From: manet user Subject: Re: [manet] aodv query To: jason.alcock@gmail.com, manet In-Reply-To: <424d6c5b.6f57ed49.0b5c.ffffc457@mx.gmail.com> MIME-Version: 1.0 X-Spam-Score: 0.2 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 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="===============1087060261==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a --===============1087060261== Content-Type: multipart/alternative; boundary="0-51654510-1112372489=:17283" --0-51654510-1112372489=:17283 Content-Type: text/plain; charset=us-ascii 802.11 uses broadcast mechanism to flood AODV RREQ. There is no backoff or acks related to broadcast transmissions. In AODV, a node acts on only the first RREQ with the same RREQ ID and ignores any subsequent RREQs. So if the first RREQ comes through unidirectional link, RREP will never make it to the SRC. Subsequent route discovery after timeouts will also fail unless black list feature is used to ignore this first RREQ (receieved through unicast link). jason alcock wrote: Hi all Is their any point in implementing AODV unidirectional black list feature if I plan to use 802.11 at the link layer? Thanks in advance. Jason _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --------------------------------- Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. --0-51654510-1112372489=:17283 Content-Type: text/html; charset=us-ascii
802.11 uses broadcast mechanism to flood AODV RREQ. There is no backoff or acks related to broadcast transmissions.  In  AODV, a node acts on only the first RREQ with the same RREQ ID and  ignores any subsequent RREQs. So if the first RREQ comes through unidirectional link, RREP will never make it to the SRC. Subsequent route discovery after timeouts will also fail unless black list feature is used to ignore this first RREQ (receieved through unicast link).
 

jason alcock <jason.alcock@gmail.com> wrote:

Hi all

 

Is their any point in implementing AODV unidirectional black list feature if I plan to use 802.11 at the link layer?

 

Thanks in advance.

 

Jason

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

Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard. --0-51654510-1112372489=:17283-- --===============1087060261== 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 --===============1087060261==-- From qzeisvqoji@yahoo.com Sat Apr 2 05:37:26 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12801; Sat, 2 Apr 2005 05:37:26 -0500 (EST) Received: from [218.52.12.105] (helo=KIM-VT4MIQFJL7F) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DHg7u-0001gc-Lo; Sat, 02 Apr 2005 05:45:15 -0500 Received: from [173.132.224.60] (helo=..dearriba.com) by smtp2.cistron.nl with esmtp ( 3.35 #1 ()) id 743LFL-0078PT-63 Message-ID: <69850953144732.R37498@.noc..gr> Sender: freeradius-devel-qzeisvqoji@yahoo.com X-Mailman-Version: 2.0.1 Date: Sat, 02 Apr 2005 03:36:07 -0700 From: "Tonia Howell" To: manet-admin@ietf.org Subject: Look...Here 51to1 X-Spam-Score: 14.6 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Look at this of-fers: V-codin - 225.00 (90 pi lls) Valliuum - 153.00 (90 pi lls) Vi graa - 270.00 (90 pi lls) Cai llis - 348.00 (90 pi lls) Codeinne - 126.00 (90 pi lls) X|a naax - 171.00 (90 pi lls) All orderrs are delivered by Fedex with full tracking 24/7. Satisfactiionnss guaaranteeed... http://www.ltxmeds.com to get rid of maiiling list: http://www.ltxmeds.com/removeme.asp From manet-bounces@ietf.org Sat Apr 2 09:29:35 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25067 for ; Sat, 2 Apr 2005 09:29:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHjkb-000399-N3 for manet-web-archive@ietf.org; Sat, 02 Apr 2005 09:37:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHjY0-0007y0-FQ; Sat, 02 Apr 2005 09:24:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHjXy-0007xv-9D for manet@megatron.ietf.org; Sat, 02 Apr 2005 09:24:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24793 for ; Sat, 2 Apr 2005 09:24:19 -0500 (EST) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHjfV-0002q0-UB for manet@IETF.ORG; Sat, 02 Apr 2005 09:32:10 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j32EOKtN009158 for ; Sat, 2 Apr 2005 09:24:20 -0500 (EST) Received: from gateway.ece.neu.edu ([129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005040209242003341 for ; Sat, 02 Apr 2005 09:24:20 -0500 Received: from localhost (basagni@localhost) by gateway.ece.neu.edu (8.9.3/8.9.3) with ESMTP id JAA05574 for ; Sat, 2 Apr 2005 09:24:20 -0500 (EST) X-Authentication-Warning: gateway.ece.neu.edu: basagni owned process doing -bs Date: Sat, 2 Apr 2005 09:24:20 -0500 (EST) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.6 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 Subject: [manet] IEEE SECON 2005, NEW SUBMISSION DEADLINES 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: b22590c27682ace61775ee7b453b40d3 We apologize if you receive multiple copies of this CfP ************************************************************* !!! NEW SUBMISSION DATES !!! Paper Registration Deadline: April 8, 2005, by 5pm EDT Paper Submission Deadline: April 10, 2005, by 5pm EDT ************************************************************* Announcement and Call for Papers *** IEEE SECON 2005 *** Second Annual IEEE Communications Society Conference on Sensor and Ad Hoc Communications and Networks Santa Clara, California, USA September 26-29, 2005 http://www.ieee-secon.org/2005 ************************************************************ Building on the success of last year's inaugural conference, this new IEEE Communications Society conference will provide a forum to exchange ideas, techniques, and applications, discuss best practices, raise awareness and share experiences among researchers, practitioners, standard developers and policy makers in the field of sensor and ad hoc networks and systems. The conference will be organized to provide for a degree of collegiality and continuity in the discussions of the various topics among participants from the industrial, governmental and academic sectors. Original technical papers that address the communications, networking, systems and algorithmic aspects of ad hoc and sensor networks, as well as those that describe practical deployment and implementation experiences, are solicited for presentation at the conference and publication in the conference proceedings. Papers presenting novel contributions in such disciplines as communications, networking protocols and architectures, algorithms, embedded systems, middleware and information management, and novel applications are solicited. PAPERS: Full papers describing original, previously unpublished research work, experimental efforts, practical experiences, and industrial and commercial developments in sensor and ad hoc communications and networks. Papers with a deep focus on a specific discipline or stimulated by the synergistic interaction of diverse disciplines are encouraged. Particular topics of interest include, but are not limited to: * New architectures, protocols and access control to support communication, localization, time synchronization, routing and data dissemination in heterogeneous, large-scale distributed, ad hoc networks and sensor networks * Novel algorithms and theories for management, supervisory control and monitoring of distributed ad hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes * Modeling and performance evaluation of large-scale distributed and ad hoc sensor networks, practical implementations, and real-work experiences * Theories and models on fundamental information and communication aspects of wireless ad hoc and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and ad hoc networks * Integration of sensors into engineered systems, including novel techniques for sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing and efficient schemes to maximize accuracy and minimize false alarms * Chip-based systems incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware and tools for ad hoc and sensor network applications development, deployment and management * Mesh networking, mobile ad hoc peer-to-peer multipoint communications, applications and experiences TUTORIALS and PANELS: Proposals for tutorials and panels on current topics in the field of ad hoc and sensor networking and applications are solicited. Panels related to the commercial application and development of sensors and ad hoc networks are especially encouraged. DEMOS and EXPO: Demonstrations that showcases the practical implementations, industrial and commercial developments, and new applications for ad hoc and sensor networks are solicited. SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically through the EDAS system. Details regarding the paper format and the submission process will be posted at the conference web site. IMPORTANT DATES: April 8, 2005: Paper registration deadline April 10, 2005: Paper submission deadline May 1, 2005: Tutorial/Panel/Demo proposals deadline June 13, 2005: Notifications July 8, 2005: Camera-ready due date TPC Co-Chairs: Elizabeth Belding-Royer ebelding@cs.ucsb.edu Marwan Krunz krunz@ece.arizona.edu Thyaga Nandagopal thyaga@lucent.com General Chair: J.J. Garcia-Luna-Aceves jj@soe.ucsc.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From WZWVRMU@msn.com Sun Apr 3 05:32:52 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07738; Sun, 3 Apr 2005 05:32:52 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DI1b9-0000EP-K5; Sun, 03 Apr 2005 05:40:51 -0400 Received: from [221.161.80.171] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1DI1TP-0005vu-Of; Sun, 03 Apr 2005 05:32:52 -0400 Received: from .anu..au ([140.157.250.164] helo=anu..au) by smtp5..co with esmtp id 1A5Ys6-942180-96 Message-ID: Sender: freeradius-devel-WZWVRMU@msn.com X-Mailman-Version: 2.0.1 Date: Sun, 03 Apr 2005 08:29:27 -0200 From: "Maggie Sheets" To: mailserv@ietf.org Subject: Everyone Need This Mailserv X-Spam-Score: 7.5 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Look at this of-fers: V-codin - 225.00 (90 pi lls) Valliuum - 153.00 (90 pi lls) Vi graa - 270.00 (90 pi lls) Cai llis - 348.00 (90 pi lls) Codeinne - 126.00 (90 pi lls) X|a naax - 171.00 (90 pi lls) All orderrs are delivered by Fedex with full tracking 24/7. Satisfactiionnss guaaranteeed... http://www.ltxmeds.com to get rid of maiiling list: http://www.ltxmeds.com/removeme.asp From manet-bounces@ietf.org Mon Apr 4 05:16:31 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09368 for ; Mon, 4 Apr 2005 05:16:31 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DINp5-0002KQ-9j for manet-web-archive@ietf.org; Mon, 04 Apr 2005 05:24:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DINZS-0004x8-Eq; Mon, 04 Apr 2005 05:08:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DINZQ-0004wU-4K for manet@megatron.ietf.org; Mon, 04 Apr 2005 05:08:32 -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 FAA08848 for ; Mon, 4 Apr 2005 05:08:29 -0400 (EDT) Received: from mailgate.cc.niigata-u.ac.jp ([133.35.14.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DINhI-0001zt-KP for manet@ietf.org; Mon, 04 Apr 2005 05:16:42 -0400 Received: from ms01.net.ie.niigata-u.ac.jp (mailgate.cc.niigata-u.ac.jp [127.0.0.1]) by mailgate.cc.niigata-u.ac.jp (8.11.6/8.11.6) with ESMTP id j34982L00561 for ; Mon, 4 Apr 2005 18:08:02 +0900 Received: from localhost (ms01 [127.0.0.1]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with ESMTP id 1C19412046 for ; Mon, 4 Apr 2005 18:07:36 +0900 (JST) Received: from ms01.net.ie.niigata-u.ac.jp ([127.0.0.1]) by localhost (ms01.net.ie.niigata-u.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14917-08 for ; Mon, 4 Apr 2005 18:07:26 +0900 (JST) Received: from localhost (ms02.net.ie.niigata-u.ac.jp [133.35.156.2]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with SMTP id 82C9B11DE6 for ; Mon, 4 Apr 2005 18:07:26 +0900 (JST) Date: Mon, 4 Apr 2005 18:11:29 +0900 From: wjf To: manet@ietf.org Message-Id: <20050404181129.17fb1a33.wjf@net.ie.niigata-u.ac.jp> X-Mailer: Sylpheed version 1.0.0beta1 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at net.ie.niigata-u.ac.jp X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] understanding of SYNC 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: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit hello All: i am puzzled about one concept of SYNC (referring to PHY layer's PLCP frame format in the MAC&PHY specifications). what is the substaintial meaning of the PLCP's Synchronization? whether the SYNC is simliar to a timer to wait until the SFD is detected at the receiver side? or the SYNC is reserved time for receiver's PHY to inform or sense the radio's change? or something else. thanks Wjf _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 4 09:38:26 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06594 for ; Mon, 4 Apr 2005 09:38:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIRua-0005EK-IM for manet-web-archive@ietf.org; Mon, 04 Apr 2005 09:46:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIRkh-00047E-Du; Mon, 04 Apr 2005 09:36:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIRke-00046v-UI for manet@megatron.ietf.org; Mon, 04 Apr 2005 09:36: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 JAA06334 for ; Mon, 4 Apr 2005 09:36:23 -0400 (EDT) Received: from morse.colorado.edu ([198.11.21.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIRsE-00053n-RV for manet@ietf.org; Mon, 04 Apr 2005 09:44:38 -0400 Received: from morse.Colorado.EDU (localhost [127.0.0.1]) by morse.Colorado.EDU (8.12.10/8.12.10/UnixOps+Hesiod) with ESMTP id j34Da0DZ014317; Mon, 4 Apr 2005 07:36:00 -0600 (MDT) Received: from localhost (timxb@localhost) by morse.Colorado.EDU (8.12.10/8.12.8/Submit) with ESMTP id j34DZxRT014314; Mon, 4 Apr 2005 07:36:00 -0600 (MDT) Date: Mon, 4 Apr 2005 07:35:59 -0600 (MDT) From: Brown Tim To: wjf Subject: Re: [manet] understanding of SYNC In-Reply-To: <20050404181129.17fb1a33.wjf@net.ie.niigata-u.ac.jp> Message-ID: References: <20050404181129.17fb1a33.wjf@net.ie.niigata-u.ac.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) 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.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb The SYNC is a known sequence of bits that the receiver can look for when trying to detect a packet. It also provides time for the transmitter to start up and the descrambler to be primed. Regards, Tim On Mon, 4 Apr 2005, wjf wrote: > hello All: > > i am puzzled about one concept of SYNC (referring to PHY layer's PLCP frame > format in the MAC&PHY specifications). what is the substaintial meaning of the > PLCP's Synchronization? whether the SYNC is simliar to a timer to wait until the > SFD is detected at the receiver side? or the SYNC is reserved time for receiver's > PHY to inform or sense the radio's change? or something else. > > thanks > > > Wjf > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > Timothy X Brown Interdisciplinary Telecommunications Electrical and Computer Engineering ECOT 256 Campus Box 530 University of Colorado Boulder, CO 80309 Tel: (303) 492-1630 Fax: (303) 492-1112 http://ece.colorado.edu/~timxb _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 4 13:35:18 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02842 for ; Mon, 4 Apr 2005 13:35:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIVbr-0001S8-Kq for manet-web-archive@ietf.org; Mon, 04 Apr 2005 13: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 1DIVSz-0005CL-Rg; Mon, 04 Apr 2005 13:34:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIVSx-0005AS-JS; Mon, 04 Apr 2005 13:34: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 NAA02755; Mon, 4 Apr 2005 13:34:20 -0400 (EDT) From: Claude.Castelluccia@inrialpes.fr Received: from mx-serv.inrialpes.fr ([194.199.18.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIVat-0001QF-A7; Mon, 04 Apr 2005 13:42:38 -0400 Received: from imap-serv.inrialpes.fr (imap-serv.inrialpes.fr [194.199.18.72]) by mx-serv.inrialpes.fr (8.13.0/8.13.0) with ESMTP id j34HXulC000558; Mon, 4 Apr 2005 19:33:56 +0200 (MEST) Received: (from nobody@localhost) by imap-serv.inrialpes.fr (8.11.6/8.11.3/ImagV2) id j34HXvu17255; Mon, 4 Apr 2005 19:33:57 +0200 (MEST) X-Authentication-Warning: imap-serv.inrialpes.fr: nobody set sender to ccastel@inrialpes.fr using -f Received: from 68.5.64.231 ( [68.5.64.231]) as user ccastel@imap-serv.inrialpes.fr by imap-serv.inrialpes.fr with HTTP; Mon, 4 Apr 2005 19:33:57 +0200 Message-ID: <1112636037.42517a853abc1@imap-serv.inrialpes.fr> Date: Mon, 4 Apr 2005 19:33:57 +0200 To: nemo@ietf.org, manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (mx-serv.inrialpes.fr [194.199.18.100]); Mon, 04 Apr 2005 19:33:56 +0200 (MEST) X-SMAUG-MailScanner: Found to be clean Envelope-From: ccastel@inrialpes.fr X-Spam-Score: 0.4 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 8bit Subject: [manet] -ESAS05 workshop- 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: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 8bit Dear all, FYI the submission deadline for ESAS05( 2nd European Workshop on Security and Privacy in Ad hoc and Sensor Networks) has been extended until April 18th. ESAS will be co-located with IEEE WICON (Wireless Internet Conference) in Budapest.... This is a great opportunity to present your work and to travel in a beautiful place ;-)... Don't miss it ! Cheers, Claude. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 4 16:30:17 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00987 for ; Mon, 4 Apr 2005 16:30:17 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIYLA-0005gN-SM for manet-web-archive@ietf.org; Mon, 04 Apr 2005 16:38:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIXvh-0000pM-Ol; Mon, 04 Apr 2005 16:12:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIXvf-0000os-H2 for manet@megatron.ietf.org; Mon, 04 Apr 2005 16:12: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 QAA26633 for ; Mon, 4 Apr 2005 16:12:09 -0400 (EDT) Received: from web31004.mail.mud.yahoo.com ([68.142.200.167]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DIY3d-0004BZ-6W for manet@ietf.org; Mon, 04 Apr 2005 16:20:28 -0400 Received: (qmail 87797 invoked by uid 60001); 4 Apr 2005 20:11:58 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=zSVvcuONKjnf9wTvHKLiy5vwzl/bSkRq4EoMx0BtjOTx0RgSxTPb2q3N0EtWHdrAD42vEp4e/0lXMqYbljbpeIt8sm+FDLEuGC6d8WUG8HWKOlhPlFVyt4bUJTvAR8UOgCVSGIVjGAMtWf3EErV0+bBRiTiNPYsXN777wfbl3gQ= ; Message-ID: <20050404201158.87795.qmail@web31004.mail.mud.yahoo.com> Received: from [156.26.108.50] by web31004.mail.mud.yahoo.com via HTTP; Mon, 04 Apr 2005 13:11:58 PDT Date: Mon, 4 Apr 2005 13:11:58 -0700 (PDT) From: sumanth sarma To: manet@ietf.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.5 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [manet] Fair MAC implementation X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Hello everyone, I need some help on Fair MAC. Did anyone implement any Fair MAC protocol till now. I need some suggestions and references. It would be great if I get any samples anywhere. Thanks Sumanth __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 5 07:22:15 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08064 for ; Tue, 5 Apr 2005 07:22:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DImGY-0004rg-LG for manet-web-archive@ietf.org; Tue, 05 Apr 2005 07:30:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIm5h-0003vl-7L; Tue, 05 Apr 2005 07:19:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIm5f-0003vg-1h for manet@megatron.ietf.org; Tue, 05 Apr 2005 07:19:27 -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 HAA07677 for ; Tue, 5 Apr 2005 07:19:19 -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 1DImDi-0004iq-LG for manet@ietf.org; Tue, 05 Apr 2005 07:27:47 -0400 Received: from localhost (mx.iit.cnr.it [127.0.0.1]) by mx.iit.cnr.it (Postfix) with ESMTP id 8327E2EE12 for ; Tue, 5 Apr 2005 13:19:07 +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 26580-14 for ; Tue, 5 Apr 2005 13:19:01 +0200 (CEST) Received: from [146.48.99.66] (dhcp3.iit.cnr.it [146.48.99.66]) by mx.iit.cnr.it (Postfix) with ESMTP id E5B902EE0C for ; Tue, 5 Apr 2005 13:19:00 +0200 (CEST) Mime-Version: 1.0 X-Sender: marco.conti@iit.cnr.it@mx.iit.cnr.it Message-Id: Date: Tue, 5 Apr 2005 13:20:39 +0200 To: manet@ietf.org From: Marco Conti X-Virus-Scanned: by Content Checker at iit.cnr.it X-Spam-Score: 0.1 (/) X-Scan-Signature: 2fe944273194be3112d13b31c91e6941 Subject: [manet] ACM MobiHoc 2005: Extended Dates for Posters and Demos Submissions 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="===============0688142942==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 9e1884bf469cda400682762c3e8d96c9 --===============0688142942== Content-Type: multipart/alternative; boundary="============_-1099422456==_ma============" --============_-1099422456==_ma============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" (Our apologies if you receive multiple copies of this document) ----------------------------------------------------------------------- Extended Dates for Posters and Demos Submissions MobiHoc 2005 6th ACM International Symposium on Mobile Ad Hoc Networking and Computing May 25-28, 2005, Urbana-Champaign, Illinois, USA http://www.sigmobile.org/mobihoc/2005/ Sponsored by ACM SIGMOBILE 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 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 . Analysis and design of transport, network and MAC protocols . Energy-efficient algorithms . Location discovery and management techniques . Network scaling and limits . Measurements and practical experience from experimental systems and testbeds . Cross layer design . Network resilience, fault-tolerance, and reliability . Security and defense issues . In-network processing, aggregation, and data dissemination . Distributed actuation, control, and coordination . Modeling, performance evaluation and QoS issues 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. Posters may not preclude concurrent submissions on the same topic in regular conferences and journals. Poster descriptions of no more than 3 pages (US letter size 8.5x11 inches) using font size 10 hould be submitted to the Poster Co-Chairs before April 8, 2005. Please include the words "Poster Abstract:" to precede the title on the cover page. A selected subset of the poster abstracts will be published in ACM Mobile Computing and Communications Review. DEMOS: Technical demonstration of experimental ad hoc networking and computing systems are solicited. One-page demo descriptions, including list of any required supporting equipment, should be sent to the Demo Chair before April 15, 2005. ORGANIZATION COMMITTEE: 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 Steering Committee Chair ------------------------ Nitin Vaidya Univ. of Illinois, Urbana-Champaign nhv@uiuc.edu Poster Co-Chairs ---------------- Saswati Sarkar University of Pennsylvania swati@seas.upenn.edu Songwu Lu University of California, Los Angeles slu@cs.ucla.edu Demo Chair ---------- Scott Graham Air Force Institute of Technology scott.graham@afit.edu Tutorial Co-Chairs ------------------ Richard Hyong-Jun La University of Maryland hyongla@eng.umd.edu Bhaskar Krishnamachari University of Southern California bkrishna@usc.edu Publicity Chairs ---------------- Sunghyun Choi Seoul National University schoi@snu.ac.kr Marco Conti Consiglio Nazionale delle Ricerche marco.conti@iit.cnr.it Robin Kravets Univ. of Illinois, Urbana-Champaign rhk@cs.uiuc.edu Finance Co-Chairs ----------------- Srikanth Krishnamurthy University of California, Riverside krish@cs.ucr.edu Raghupathy Sivakumar Georgia Institute of Technology siva@ece.gatech.edu Registration Chair ------------------ Prasun Sinha Ohio State University sinha.43@osu.edu Web Chair --------- Junshan Zhang Arizona State University junshan.zhang@asu.edu Publication Chair ----------------- Yongguang Zhang HRL Labs ygz@hrl.com Local Arrangements Co-Chairs ---------------------------- Xiang-Yang Li Illinois Institute of Technology xli@babbage2.cs.iit.edu Haiyun Luo Univ. of Illinois, Urbana-Champaign haiyun@cs.uiuc.edu Wai Gen Yee Illinois Institute of Technology yee@iit.edu ---------------------------------------------------------------------- For more information contact the General Chair P. R. Kumar or consult the symposium webpage http://www.sigmobile.org/mobihoc/2005/ --============_-1099422456==_ma============ Content-Type: text/html; charset="us-ascii" ACM MobiHoc 2005: Extended Dates for Posters and Demos Sub

(Our apologies if you receive multiple copies of this document)
-----------------------------------------------------------------------
                       
             Extended Dates for Posters and Demos Submissions

                         MobiHoc 2005

              6th ACM International Symposium on
            Mobile Ad Hoc Networking and Computing

       May 25-28, 2005, Urbana-Champaign, Illinois, USA

            http://www.sigmobile.org/mobihoc/2005/

                  Sponsored by ACM SIGMOBILE

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 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
.        Analysis and design of transport, network and MAC protocols
.        Energy-efficient algorithms
.        Location discovery and management techniques
.        Network scaling and limits
.        Measurements and practical experience from
         experimental systems and testbeds
.        Cross layer design
.        Network resilience, fault-tolerance, and reliability
.        Security and defense issues
.        In-network processing, aggregation, and data dissemination
.        Distributed actuation, control, and coordination
.        Modeling, performance evaluation and QoS issues

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. Posters may not preclude
concurrent submissions on the same topic in regular conferences and
journals. Poster descriptions of
no more than 3 pages (US letter size 8.5x11 inches) using font size 10
hould be submitted to the Poster Co-Chairs before April 8, 2005.
Please include the words "Poster Abstract:" to precede the title on
the cover page.
A selected subset of the poster abstracts will be published in ACM
Mobile Computing and Communications Review.

DEMOS: Technical demonstration of experimental ad hoc networking and
computing systems are solicited. One-page demo descriptions, including
list of any required supporting equipment, should be sent to the
Demo Chair before April 15, 2005.

ORGANIZATION COMMITTEE:

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

Steering Committee Chair
------------------------
Nitin Vaidya
Univ. of Illinois, Urbana-Champaign
nhv@uiuc.edu

Poster Co-Chairs
----------------
Saswati Sarkar
University of Pennsylvania
swati@seas.upenn.edu

Songwu Lu
University of California, Los Angeles
slu@cs.ucla.edu

Demo Chair
----------
Scott Graham
Air Force Institute of Technology
scott.graham@afit.edu

Tutorial Co-Chairs
------------------
Richard Hyong-Jun La
University of Maryland
hyongla@eng.umd.edu

Bhaskar Krishnamachari
University of Southern California
bkrishna@usc.edu

Publicity Chairs
----------------
Sunghyun  Choi
Seoul National University
schoi@snu.ac.kr

Marco Conti
Consiglio Nazionale delle Ricerche
marco.conti@iit.cnr.it

Robin Kravets
Univ. of Illinois, Urbana-Champaign
rhk@cs.uiuc.edu

Finance Co-Chairs
-----------------
Srikanth Krishnamurthy
University of California, Riverside
krish@cs.ucr.edu

Raghupathy Sivakumar
Georgia Institute of Technology
siva@ece.gatech.edu

Registration Chair
------------------
Prasun Sinha
Ohio State University
sinha.43@osu.edu

Web Chair
---------
Junshan  Zhang
Arizona State University
junshan.zhang@asu.edu

Publication Chair
-----------------
Yongguang Zhang
HRL Labs
ygz@hrl.com

Local Arrangements Co-Chairs
----------------------------
Xiang-Yang Li
Illinois Institute of Technology
xli@babbage2.cs.iit.edu

Haiyun Luo
Univ. of Illinois, Urbana-Champaign
haiyun@cs.uiuc.edu

Wai Gen Yee
Illinois Institute of Technology
yee@iit.edu

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

For more information contact the General Chair P. R. Kumar or consult
the symposium webpage http://www.sigmobile.org/mobihoc/2005/


--============_-1099422456==_ma============-- --===============0688142942== 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 --===============0688142942==-- From manet-bounces@ietf.org Tue Apr 5 19:12:25 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29143 for ; Tue, 5 Apr 2005 19:12:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIxLv-0002ef-KG for manet-web-archive@ietf.org; Tue, 05 Apr 2005 19:20:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIxBe-0003CD-Hc; Tue, 05 Apr 2005 19:10:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIxBd-0003C8-2p for manet@megatron.ietf.org; Tue, 05 Apr 2005 19:10: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 TAA28954 for ; Tue, 5 Apr 2005 19:10:17 -0400 (EDT) Received: from mail1.engr.ucsb.edu ([128.111.53.4] helo=smtp.engr.ucsb.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIxJq-0002bs-9A for manet@ietf.org; Tue, 05 Apr 2005 19:18:51 -0400 Received: from joshua.cs.ucsb.edu ([128.111.40.98]:56325) by smtp.engr.ucsb.edu with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1DIxBR-0005KF-QI; Tue, 05 Apr 2005 16:10:10 -0700 Mime-Version: 1.0 (Apple Message framework v619.2) Message-Id: <779d2660bedcad12ee9fdb88eb08d41d@cs.ucsb.edu> From: Ian Chakeres Date: Tue, 5 Apr 2005 16:10:11 -0700 To: manet X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: Determined clean by smtp.engr.ucsb.edu using clamd / ClamAV version 0.80 X-SA-Exim-Connect-IP: 128.111.40.98 X-SA-Exim-Mail-From: idc@cs.ucsb.edu Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on smtp.engr.ucsb.edu X-Spam-Status: No, score=-5.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-SA-Exim-Version: 4.1 (built Mon, 13 Dec 2004 10:51:27 -0800) X-SA-Exim-Scanned: Yes (on smtp.engr.ucsb.edu) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 7bit Subject: [manet] IETF 62 Minutes Presentations Available 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: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit For anyone who could not come to Minneapolis, the minutes and presentations for IETF 62 are available at https://datatracker.ietf.org/public/proceeding_interim.cgi? meeting_num=62. Ian Chakeres _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 05:13:25 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17744 for ; Wed, 6 Apr 2005 05:13:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ6jc-0005tn-0g for manet-web-archive@ietf.org; Wed, 06 Apr 2005 05:22:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ6Td-0006F2-KZ; Wed, 06 Apr 2005 05:05:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ6TR-0006EV-1l for manet@megatron.ietf.org; Wed, 06 Apr 2005 05:05: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 FAA16828 for ; Wed, 6 Apr 2005 05:05:17 -0400 (EDT) Received: from staff.cs.usyd.edu.au ([129.78.8.1]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJ6bi-0005YR-Qr for manet@ietf.org; Wed, 06 Apr 2005 05:13:56 -0400 Received: from staff.cs.usyd.edu.au. [129.78.8.1] by staff.cs.usyd.edu.au.; Wed, 06 Apr 2005 19:05:13 +1000 Date: Wed, 6 Apr 2005 19:05:13 +1000 (EST) From: "Corbett; Derek James" X-Sender: dcorbett@staff.cs.usyd.edu.au To: manet@ietf.org Subject: [manet] MAC Benchmarking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Hello, Is anyone aware of any work that has been done in an effort benchmark different MAC protocols for their suitability in MANETs. I know there are hundreds of papers out there that compare protocol A to protocol B and say A performs better in one field and B in another. But I was wondering if any effort has been undertaken to standardize this procedure? I am looking at comparing some MAC protocols I have been working on and if there is no benchmarking procedure available I am thinking about proposing my own. Derek "Who controls the past controls the future. Who controls the present controls the past. But who controls the spice controls the Universe!" --------------- Derek J Corbett PhD Student Smart Internet Technology Research Group The University of Sydney http://www.cs.usyd.edu.au/~dcorbett _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 06:58:04 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28222 for ; Wed, 6 Apr 2005 06:58:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ8Mu-0001Rk-DV for manet-web-archive@ietf.org; Wed, 06 Apr 2005 07:06:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ8D3-0004Cb-EJ; Wed, 06 Apr 2005 06:56:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ8D2-0004CW-4x for manet@megatron.ietf.org; Wed, 06 Apr 2005 06:56:32 -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 GAA27926 for ; Wed, 6 Apr 2005 06:56:29 -0400 (EDT) Received: from web54605.mail.yahoo.com ([68.142.225.189]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJ8LL-0001Lb-Cp for manet@ietf.org; Wed, 06 Apr 2005 07:05:08 -0400 Received: (qmail 50984 invoked by uid 60001); 6 Apr 2005 10:56:21 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=hIs38aI6YtMRKCQfl19SlubuGVOxKHMmWMAGRIlZB5/aIyPK3sFnBDHdTUj3SM9VJmXcw0X8mreXCBVMuXUmBNATQcZV86Zo882MjyMJ2IvbbUrWK5GfXElF7n+MO+UWj5XXbXoh4UDtvoCh3umjqEny7TOeJQFyT6vXW161ivA= ; Message-ID: <20050406105621.50982.qmail@web54605.mail.yahoo.com> Received: from [81.10.47.145] by web54605.mail.yahoo.com via HTTP; Wed, 06 Apr 2005 03:56:21 PDT Date: Wed, 6 Apr 2005 03:56:21 -0700 (PDT) From: amr hassan To: manet ietf MIME-Version: 1.0 X-Spam-Score: 2.2 (++) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [manet] Mobility Models 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="===============1100201596==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.2 (++) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 --===============1100201596== Content-Type: multipart/alternative; boundary="0-871656728-1112784981=:50519" --0-871656728-1112784981=:50519 Content-Type: text/plain; charset=us-ascii Hi everybody, I'm studying the mobility models in ad hoc networks using network simulator. I noticed that the only available model in network simulator is the random model. I was thinking to work on developing some sort of a deterministic or semi-deterministic model to simulate real life situations. So I was wondering if this is a new approach to go on with, or it has been studied & over. If anybody can help with this, it will be great to supply me with some pdfs. Thanks in advance Amr --------------------------------- Do you Yahoo!? Better first dates. More second dates. Yahoo! Personals --0-871656728-1112784981=:50519 Content-Type: text/html; charset=us-ascii
Hi everybody,
I'm studying the mobility models in ad hoc networks using network simulator. I noticed that the only available model in network simulator is the random model. I was thinking to work on developing some sort of a deterministic or semi-deterministic model to simulate real life situations.
So I was wondering if this is a new approach to go on with, or it has been studied & over.
If anybody can help with this, it will be great to supply me with some pdfs.
 
Thanks in advance
Amr

Do you Yahoo!?
Better first dates. More second dates. Yahoo! Personals --0-871656728-1112784981=:50519-- --===============1100201596== 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 --===============1100201596==-- From manet-bounces@ietf.org Wed Apr 6 07:46:22 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00943 for ; Wed, 6 Apr 2005 07:46:22 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ97b-0003iG-QO for manet-web-archive@ietf.org; Wed, 06 Apr 2005 07:55:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ8m2-0004Ez-7v; Wed, 06 Apr 2005 07:32:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ8lz-0004EB-N9 for manet@megatron.ietf.org; Wed, 06 Apr 2005 07:32: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 HAA29341 for ; Wed, 6 Apr 2005 07:32:37 -0400 (EDT) Received: from cliff.cs.toronto.edu ([128.100.3.120]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ8bG-000201-Ov for manet@ietf.org; Wed, 06 Apr 2005 07:21:36 -0400 Received: from berimbamaquina.cs.toronto.edu (qew.cs.toronto.edu [128.100.2.15]) by cliff.cs.toronto.edu (Postfix) with ESMTP id 38D035FD0A; Wed, 6 Apr 2005 07:12:56 -0400 (EDT) Message-Id: <6.2.1.2.0.20050406071315.02042800@pop.cs.toronto.edu> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 06 Apr 2005 07:15:01 -0400 To: amr hassan , manet ietf From: =?iso-8859-1?Q?Andr=E9s?= Lagar Cavilla Subject: Re: [manet] Mobility Models In-Reply-To: <20050406105621.50982.qmail@web54605.mail.yahoo.com> References: <20050406105621.50982.qmail@web54605.mail.yahoo.com> Mime-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 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="===============1866534734==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab --===============1866534734== Content-Type: text/html; charset="us-ascii" Hi Amr,
We researched this issue in our SECON'04 paper
"Simplified Simulation Models for Indoor MANET Evaluation are not Robust"
You'll find more details, citations and implementations at
http://www.cs.toronto.edu/~andreslc/publications/index.html
This question has been asked before and you can get plenty of pointers if you look into the mailing list archives
Good luck
Andres

At 06:56 AM 4/6/2005, amr hassan wrote:
Hi everybody,
I'm studying the mobility models in ad hoc networks using network simulator. I noticed that the only available model in network simulator is the random model. I was thinking to work on developing some sort of a deterministic or semi-deterministic model to simulate real life situations.
So I was wondering if this is a new approach to go on with, or it has been studied & over.
If anybody can help with this, it will be great to supply me with some pdfs.
 
Thanks in advance
Amr


Do you Yahoo!?
Better first dates. More second dates. Yahoo! Personals
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet
--===============1866534734== 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 --===============1866534734==-- From manet-bounces@ietf.org Wed Apr 6 08:56:49 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08148 for ; Wed, 6 Apr 2005 08:56:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJADo-0006fH-Fa for manet-web-archive@ietf.org; Wed, 06 Apr 2005 09:05:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJA37-0006Nv-Fo; Wed, 06 Apr 2005 08:54:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJA34-0006Nq-2W for manet@megatron.ietf.org; Wed, 06 Apr 2005 08:54: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 IAA08016 for ; Wed, 6 Apr 2005 08:54:20 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.192]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJABP-0006c9-6u for manet@ietf.org; Wed, 06 Apr 2005 09:03:00 -0400 Received: by rproxy.gmail.com with SMTP id a41so155760rng for ; Wed, 06 Apr 2005 05:54:20 -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=t6/E1t3qQhr+Hd0ElRQ8Uz9dk0xLNNziCNCHK6jSk+2+18fKzKmutsJOV++LftumQwYijRIJ+FEgpOJL7IBOkt/LBhK+IBtiRIFE2yw5wseEn7G0DNHQ1cbnbxo/QFfUEyIYXVHuyE4ehUoKTtVqE2q5BDhCngnucDi4mXu15bU= Received: by 10.38.155.3 with SMTP id c3mr734602rne; Wed, 06 Apr 2005 05:54:19 -0700 (PDT) Received: by 10.38.151.63 with HTTP; Wed, 6 Apr 2005 05:54:19 -0700 (PDT) Message-ID: <1bc0d2f40504060554ff9d0c@mail.gmail.com> Date: Wed, 6 Apr 2005 18:24:19 +0530 From: srikanth Thirmala To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Content-Transfer-Encoding: 7bit Subject: [manet] Request for mnet application X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srikanth Thirmala 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: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit hi, i am new to this group. currently i am project on mobile Ad-hoc networking. can any body suggest me the topic(related to the ad-hoc network application). pls i am so confusing to choose it. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 09:08:48 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09003 for ; Wed, 6 Apr 2005 09:08:48 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJAPP-0006z9-OA for manet-web-archive@ietf.org; Wed, 06 Apr 2005 09:17:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJAGI-0004rB-Ak; Wed, 06 Apr 2005 09:08:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJAGF-0004qS-Kj for manet@megatron.ietf.org; Wed, 06 Apr 2005 09:07: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 JAA08952 for ; Wed, 6 Apr 2005 09:07:57 -0400 (EDT) Received: from bells.cs.ucl.ac.uk ([128.16.5.31]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJAOa-0006yJ-DX for manet@ietf.org; Wed, 06 Apr 2005 09:16:37 -0400 Received: from basilico.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Apr 2005 14:07:50 +0100 Message-ID: <4253DF1C.1070809@cs.ucl.ac.uk> Date: Wed, 06 Apr 2005 14:07:40 +0100 From: Mirco Musolesi User-Agent: Mozilla Thunderbird 0.9 (X11/20041127) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amr hassan Subject: Re: [manet] Mobility Models References: <20050406105621.50982.qmail@web54605.mail.yahoo.com> In-Reply-To: <20050406105621.50982.qmail@web54605.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: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Cc: manet ietf X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Hi Amr, > I'm studying the mobility models in ad hoc networks using network simulator. I noticed that the only available model in network simulator is the random model. I was thinking to work on developing some sort of a deterministic or semi-deterministic model to simulate real life situations. > So I was wondering if this is a new approach to go on with, or it has been studied & over. > If anybody can help with this, it will be great to supply me with some pdfs. We are working on mobility models founded on social networks theory. You can find more information and papers at this address: http://www.cs.ucl.ac.uk/research/mobile/mobilitymodelsproject.html Best regards, Mirco -- Mirco Musolesi Department of Computer Science - University College London Gower Street London WC1E 6BT United Kingdom Email: m.musolesi@cs.ucl.ac.uk Phone: +44 20 7679 0391 Fax: +44 20 7387 1397 Web: http://www.cs.ucl.ac.uk/staff/m.musolesi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 12:37:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02419 for ; Wed, 6 Apr 2005 12:37:39 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJDfZ-0005co-1m for manet-web-archive@ietf.org; Wed, 06 Apr 2005 12:46:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJDPB-00076O-Nx; Wed, 06 Apr 2005 12:29:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJDP8-00076J-KL for manet@megatron.ietf.org; Wed, 06 Apr 2005 12:29: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 MAA01799 for ; Wed, 6 Apr 2005 12:29:19 -0400 (EDT) Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJDXV-0005RD-CY for manet@ietf.org; Wed, 06 Apr 2005 12:38:02 -0400 Received: from cypress.cs.ucsb.edu (cypress [128.111.40.165]) by letters.cs.ucsb.edu (8.13.1/8.13.1) with ESMTP id j36GWCUP005159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Apr 2005 09:32:12 -0700 Received: from cypress.cs.ucsb.edu (localhost [127.0.0.1]) by cypress.cs.ucsb.edu (8.12.8/8.12.8) with ESMTP id j36GTFFK010222; Wed, 6 Apr 2005 09:29:15 -0700 Received: from localhost (kimaya@localhost) by cypress.cs.ucsb.edu (8.12.8/8.12.8/Submit) with ESMTP id j36GTCiE010218; Wed, 6 Apr 2005 09:29:15 -0700 X-Authentication-Warning: cypress.cs.ucsb.edu: kimaya owned process doing -bs Date: Wed, 6 Apr 2005 09:29:12 -0700 (PDT) From: "Kimaya M. Sanzgiri" X-X-Sender: kimaya@cypress To: Mirco Musolesi Subject: Re: [manet] Mobility Models In-Reply-To: <4253DF1C.1070809@cs.ucl.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on localhost X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on letters X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: manet ietf , amr hassan 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: 8b30eb7682a596edff707698f4a80f7d Some work on mobility models has been done in our research group too. Take a look at http://moment.cs.ucsb.edu/mobility/ Kimaya On Wed, 6 Apr 2005, Mirco Musolesi wrote: > > Hi Amr, > > > I'm studying the mobility models in ad hoc networks using network > simulator. I noticed that the only available model in network simulator > is the random model. I was thinking to work on developing some sort of a > deterministic or semi-deterministic model to simulate real life situations. > > So I was wondering if this is a new approach to go on with, or it has > been studied & over. > > If anybody can help with this, it will be great to supply me with > some pdfs. > > We are working on mobility models founded on social networks theory. > > You can find more information and papers at this address: > > http://www.cs.ucl.ac.uk/research/mobile/mobilitymodelsproject.html > > Best regards, > Mirco > > -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 15:10:44 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17629 for ; Wed, 6 Apr 2005 15:10:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJG3j-0001bR-8Z for manet-web-archive@ietf.org; Wed, 06 Apr 2005 15:19:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJFtH-0001CF-IS; Wed, 06 Apr 2005 15:08:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJFtG-0001CA-2c for manet@megatron.ietf.org; Wed, 06 Apr 2005 15:08: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 PAA17309 for ; Wed, 6 Apr 2005 15:08:36 -0400 (EDT) Received: from web52508.mail.yahoo.com ([206.190.39.133]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJG1e-0001XJ-B9 for manet@ietf.org; Wed, 06 Apr 2005 15:17:19 -0400 Received: (qmail 95220 invoked by uid 60001); 6 Apr 2005 19:08:27 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=xI8FQcVOKIwuipcNTz0fmOvtTf0LnGVlxixU/c6MYLxlTc3GlQJYyFQdXBsAFxdRHm/S9GoY1dzMQ0QpMXmdHSb3dy+e7hPcREwfFxILwYzsSmqpJ9O8vcUzuxK+FbJru2cVmCJwwXGlZBa1vUk1sHsG2tffPfiOC0r/LtAM/Bg= ; Message-ID: <20050406190827.95217.qmail@web52508.mail.yahoo.com> Received: from [66.146.170.74] by web52508.mail.yahoo.com via HTTP; Wed, 06 Apr 2005 12:08:27 PDT Date: Wed, 6 Apr 2005 12:08:27 -0700 (PDT) From: Leon Martin To: MANET Newsgroup MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] What is the sequence number for in 802.11 MAC? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Hi all, In 802.11 standard 1999, there is a 12-bit sequence number at the MPDU (see figure 14-Sequence Control field on page 40). What is it for? Do we need sequencing MPDUs at the MAC layer? I think we can uniquely identify a data frame or ACK frame through the source address and destination address pair, since there is at most one MPDU involved in the MAC activities of a single node. Thanks. - Leon __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 6 20:56:13 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28323 for ; Wed, 6 Apr 2005 20:56:13 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJLS6-00040E-Op for manet-web-archive@ietf.org; Wed, 06 Apr 2005 21: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 1DJLE6-0005uH-Sl; Wed, 06 Apr 2005 20:50:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJLE4-0005uC-Gr for manet@megatron.ietf.org; Wed, 06 Apr 2005 20:50: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 UAA27910 for ; Wed, 6 Apr 2005 20:50:26 -0400 (EDT) Received: from copland.udel.edu ([128.175.13.92]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJLMV-0003pP-Q0 for manet@ietf.org; Wed, 06 Apr 2005 20:59:13 -0400 Received: from copland.udel.edu (localhost [127.0.0.1]) by copland.udel.edu (8.12.11/8.12.11) with ESMTP id j370oJUS006146; Wed, 6 Apr 2005 20:50:21 -0400 (EDT) Received: from localhost (andjela@localhost) by copland.udel.edu (8.12.11/8.12.11/Submit) with ESMTP id j370oJbb006143; Wed, 6 Apr 2005 20:50:19 -0400 (EDT) Date: Wed, 6 Apr 2005 20:50:19 -0400 (EDT) From: Andjela Ilic To: amr hassan Subject: Re: [manet] Mobility Models In-Reply-To: <20050406105621.50982.qmail@web54605.mail.yahoo.com> Message-ID: References: <20050406105621.50982.qmail@web54605.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-CanItPRO-Stream: default X-Spam-Score: 0 () X-Scanned-By: CanIt (www . canit . ca) X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: manet ietf 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 Amr, My group has been working on realistic mobility scenarios too. Here is the link: http://www.eecis.udel.edu/~bohacek/UDelModels/index.html Andjela On Wed, 6 Apr 2005, amr hassan wrote: > Hi everybody, > I'm studying the mobility models in ad hoc networks using network simulator. I noticed that the only available model in network simulator is the random model. I was thinking to work on developing some sort of a deterministic or semi-deterministic model to simulate real life situations. > So I was wondering if this is a new approach to go on with, or it has been studied & over. > If anybody can help with this, it will be great to supply me with some pdfs. > > Thanks in advance > Amr > > > > --------------------------------- > Do you Yahoo!? > Better first dates. More second dates. Yahoo! Personals _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 01:56:35 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23608 for ; Thu, 7 Apr 2005 01:56:35 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJQ8o-0003Hd-0q for manet-web-archive@ietf.org; Thu, 07 Apr 2005 02:05:23 -0400 Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1DJPzx-0003mc-Fq for manet-web-archive@ietf.org; Thu, 07 Apr 2005 01:56:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJPx0-00005r-Qi; Thu, 07 Apr 2005 01:53:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJPwy-00005h-0y for manet@megatron.ietf.org; Thu, 07 Apr 2005 01: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 BAA23502 for ; Thu, 7 Apr 2005 01:53:06 -0400 (EDT) Received: from smtp-send.myrealbox.com ([192.108.102.143]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJQ5P-0003Cv-Dh for manet@ietf.org; Thu, 07 Apr 2005 02:01:55 -0400 Received: from nppham [129.94.6.28] by myrealbox.com with NetMail ModWeb Module; Thu, 07 Apr 2005 15:23:02 +0930 Subject: Re: Re: [manet] Mobility Models From: "Peter Pham" To: andjela@UDel.Edu Date: Thu, 07 Apr 2005 15:23:02 +0930 X-Mailer: NetMail ModWeb Module X-Sender: nppham MIME-Version: 1.0 Message-ID: <1112853182.8c26169cnppham@myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org, amr_hassan1@yahoo.com X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nppham@myrealbox.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: quoted-printable Hi Check out the movement using Voronoi diagram. I think that there is a paper= on it. From what I know, there is also ns2 Tcl script to generate it. The basic idea is that, people will tend to move around the building in the= campus (not through the building). So, this model is relevant in quite a= number of cases. About a realistic model, I don't think there is any mobility model that can= be used for ALL the scenarios. Logically, there can not be right ? Regards Peter Pham -----Original Message----- From: Andjela Ilic To: amr hassan Date: Wed, 6 Apr 2005 20:50:19 -0400 (EDT) Subject: Re: [manet] Mobility Models Hi Amr, My group has been working on realistic mobility scenarios too. Here is the link: http://www.eecis.udel.edu/~bohacek/UDelModels/index.html Andjela On Wed, 6 Apr 2005, amr hassan wrote: > Hi everybody, > I'm studying the mobility models in ad hoc networks using network simulat= or. I noticed that the only available model in network simulator is the r= andom model. I was thinking to work on developing some sort of a determin= istic or semi-deterministic model to simulate real life situations. > So I was wondering if this is a new approach to go on with, or it has bee= n studied & over. > If anybody can help with this, it will be great to supply me with some pd= fs. > > Thanks in advance > Amr > > > > --------------------------------- > Do you Yahoo!? > Better first dates. More second dates. Yahoo! Personals _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Peter Phuc Pham _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 03:46:55 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23511 for ; Thu, 7 Apr 2005 03:46:55 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJRrd-0006ut-54 for manet-web-archive@ietf.org; Thu, 07 Apr 2005 03:55:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJRf8-0001Q0-Rf; Thu, 07 Apr 2005 03:42:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJRex-0001Mr-Nx for manet@megatron.ietf.org; Thu, 07 Apr 2005 03:42: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 DAA23127 for ; Thu, 7 Apr 2005 03:42:37 -0400 (EDT) Received: from pop3.ajou.ac.kr ([202.30.0.18] helo=mail.ajou.ac.kr) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJRnQ-0006jN-Bb for manet@ietf.org; Thu, 07 Apr 2005 03:51:27 -0400 Received: from smtp.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.8) with SMTP ID 536 for ; Thu, 7 Apr 2005 16:42:22 +0900 (KST) Received: from 210.107.194.220 ([210.107.194.220]) by seodang.ajou.ac.kr (Spambreaker SMTP Server ); Thu, 7 Apr 2005 16:40:12 +0900 (KST) Message-ID: <014101c53b45$68629300$dcc26bd2@ajoudayhakyu> From: Faisal Adeem Siddiqui To: manet@ietf.org Date: Thu, 7 Apr 2005 16:42:51 +0900 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 1.4 (+) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] Difference between Wireless Mesh Router and Multi-Radio Access Point X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.4 (+) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Hi everybody, I've seen many wireless mesh network architectures. Some use wireless mesh router to connect end-user terminals while others use multi radio Access Points (AP) for the same purpose. The difference between the two approaches is quite ambiguous. In case of AP, do they use some kind of layer-2 routing between APs for relaying packets? Do such APs support routing ? Can these APs be configured like a router and filter packets based on some policies or access lists ? Please clear my doubts. Thanks. Faisal. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 04:06:26 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25162 for ; Thu, 7 Apr 2005 04:06:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJSAQ-0007k8-RA for manet-web-archive@ietf.org; Thu, 07 Apr 2005 04:15:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJS0z-0007Dp-LU; Thu, 07 Apr 2005 04:05:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJS0u-0007DQ-OF for manet@megatron.ietf.org; Thu, 07 Apr 2005 04:05: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 EAA25001 for ; Thu, 7 Apr 2005 04:05:18 -0400 (EDT) Received: from web54604.mail.yahoo.com ([68.142.225.188]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJS9H-0007gx-B6 for manet@ietf.org; Thu, 07 Apr 2005 04:14:09 -0400 Received: (qmail 50868 invoked by uid 60001); 7 Apr 2005 08:05:01 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=tga5lc42yReBIR9ck14YorzAjg6bBQCFxPHrrX8kxapWQU+QnW1GjkipNDo6jr7EA4U4C00m6Dqi70fP0FJbX7Qxu2k9XdEY9JVY2Sa5JTKbmM4VYYvOBcAHKhVDg6UA2CgTTUd2TkCKC5OMprrBk80V8r4TcTkem324EQv1OvM= ; Message-ID: <20050407080501.50863.qmail@web54604.mail.yahoo.com> Received: from [203.200.31.178] by web54604.mail.yahoo.com via HTTP; Thu, 07 Apr 2005 09:05:01 BST Date: Thu, 7 Apr 2005 09:05:01 +0100 (BST) From: aravind rao To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 8bit Subject: [manet] Maximum file size settings X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: avi_16@yahoo.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 8bit hello everyone, I am working on ns-2.26 and the trace files run into many GB in size but linux restricts the file size to 2Gb so the simulation exits with the message "File Size Limit Exceeded". How do I solve this problem? Any help will be appreciated. Regards, Aravind Rao Wireless Networking Lab M.S. Ramaiah Institute of Technology Bangalore, India Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 04:23:12 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26750 for ; Thu, 7 Apr 2005 04:23:11 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJSQk-0008NL-IS for manet-web-archive@ietf.org; Thu, 07 Apr 2005 04:32:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJSCT-0001xe-Qs; Thu, 07 Apr 2005 04:17:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJSCQ-0001x7-7p for manet@megatron.ietf.org; Thu, 07 Apr 2005 04:17: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 EAA26169 for ; Thu, 7 Apr 2005 04:17:11 -0400 (EDT) Received: from web25402.mail.ukl.yahoo.com ([217.12.10.136]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJSKw-00089u-5y for manet@ietf.org; Thu, 07 Apr 2005 04:26:02 -0400 Received: (qmail 75606 invoked by uid 60001); 7 Apr 2005 08:17:04 -0000 Message-ID: <20050407081703.75604.qmail@web25402.mail.ukl.yahoo.com> Received: from [202.5.150.253] by web25402.mail.ukl.yahoo.com via HTTP; Thu, 07 Apr 2005 09:17:03 BST Date: Thu, 7 Apr 2005 09:17:03 +0100 (BST) From: Saqib Ilyas Subject: Re: [manet] Maximum file size settings To: manet@ietf.org In-Reply-To: 6667 MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaqib@ieee.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1448456116==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 --===============1448456116== Content-Type: multipart/alternative; boundary="0-654298815-1112861823=:74301" --0-654298815-1112861823=:74301 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I believe you would need to recompile the kernel for that. Maybe there's a solution that I am overlooking. Regards aravind rao wrote: hello everyone, I am working on ns-2.26 and the trace files run into many GB in size but linux restricts the file size to 2Gb so the simulation exits with the message "File Size Limit Exceeded". How do I solve this problem? Any help will be appreciated. Regards, Aravind Rao Wireless Networking Lab M.S. Ramaiah Institute of Technology Bangalore, India Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Muhammad Saqib Ilyas Assistant Professor Department of Computer and Information Systems Engineering NED University of Engineering and Technology, Karachi, Pakistan http://www.neduet.edu.pk/CISE/faculty/MSaqib/index.htm Chair, Student Activities Committee, IEEE Karachi Section Member Executive Committee, IEEE Karachi Section Country Leader, INETA Pakistan IEEE Student Branch Counselor, NED University Send instant messages to your online friends http://uk.messenger.yahoo.com --0-654298815-1112861823=:74301 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
I believe you would need to recompile the kernel for that. Maybe there's a solution that I am overlooking.
Regards

aravind rao <avi_16@yahoo.com> wrote:
hello everyone,

I am working on ns-2.26 and the trace files run into
many
GB in size but linux restricts the file size to 2Gb so

the simulation exits with the message "File Size Limit

Exceeded".
How do I solve this problem? Any help will be
appreciated.

Regards,
Aravind Rao
Wireless Networking Lab
M.S. Ramaiah Institute of Technology
Bangalore, India

Send instant messages to your online friends http://uk.messenger.yahoo.com

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


Muhammad Saqib Ilyas
Assistant Professor
Department of Computer and Information Systems Engineering
NED University of Engineering and Technology, Karachi, Pakistan
http://www.neduet.edu.pk/CISE/faculty/MSaqib/index.htmChair, Student Activities Committee, IEEE Karachi Section
Member Executive Committee, IEEE Karachi Section
Country Leader, INETA Pakistan
IEEE Student Branch Counselor, NED University

Send instant messages to your online friends http://uk.messenger.yahoo.com --0-654298815-1112861823=:74301-- --===============1448456116== 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 --===============1448456116==-- From manet-bounces@ietf.org Thu Apr 7 06:26:12 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05558 for ; Thu, 7 Apr 2005 06:26:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJULo-0003sQ-3m for manet-web-archive@ietf.org; Thu, 07 Apr 2005 06:35:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJUA6-0002wI-80; Thu, 07 Apr 2005 06:22:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJUA3-0002uU-H4 for manet@megatron.ietf.org; Thu, 07 Apr 2005 06:22: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 GAA05232 for ; Thu, 7 Apr 2005 06:22:51 -0400 (EDT) Received: from mailhub.cs.uoguelph.ca ([131.104.96.75]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJUIa-0003lb-49 for manet@ietf.org; Thu, 07 Apr 2005 06:31:44 -0400 Received: from snowhite.cis.uoguelph.ca (snowhite.cis.uoguelph.ca [131.104.48.1]) by mailhub.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id j37AMnOV012208 for ; Thu, 7 Apr 2005 06:22:49 -0400 Received: from localhost (denko@localhost) by snowhite.cis.uoguelph.ca (8.9.3/8.9.3) with ESMTP id GAA42501 for ; Thu, 7 Apr 2005 06:24:06 -0400 (EDT) Date: Thu, 7 Apr 2005 06:24:06 -0400 (EDT) From: Mieso Denko To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.44 X-Spam-Score: 1.6 (+) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Subject: [manet] CFP: LANC-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: 1.1 (+) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f ------------------------------------------------------------------------------------------- 1st Call for Papers Latin America Networking Conference 2005 (LANC 2005) Sponsored by IFIP-WG6.9, Communication Systems in Developing Countries, in cooperation with ACM-SIGCOMM, Cali, Colombia, October 10 14, 2005 LANC 2005 is organized by CLEI (Centro Latinoamericano de Estudios en Informtica), sponsored by IFIP WG6.9, Communication Systems in Developing Countries, and in cooperation with ACM SIGCOMM. LANC 2005 is co-located with CLEI 2005, CLEIs annual conference (see http://www.clei2005.org). Conference Website: http://lanc05.uib.es ---------------------------------------------------------------------------------------- General Chair Ernst L. Leiss, U. of Houston (US) Organizing Committee Benjamn Barn, U. Nacional de Asuncin (PY) Lyman Chapin, Interisle Consulting (US) Juan Francisco Daz, U. del Valle, Cali (CO) Ernst L. Leiss, U. of Houston (US) Ana Pont, U. Politcnica de Valncia (ES) Ramon Puigjaner, U. de les Illes Balears (ES) Program Committee Benjamn Barn, U. Nacional de Asuncin (PY) Raouf Boutaba, U. of Waterloo, (CA) Ramn Cceres, IBM T.J.Watson Lab. (US) Hctor Cancela, U de la Repblica (UY) Lyman Chapin, Interisle Consulting (US) Mieso Denko, U. of Guelph (CA) Yesid Donoso, U. del Norte (CO) Ramon Fabregat, U. de Girona (ES) Dominique Gati, U. Technique de Troyes (FR) JJ Garcia-Luna, UCSC (US) Lisandro Z. Granville, U. federal do Rio Grande do Sul (BR) Gnter Haring, U. Viena (AT) Germinal Isern, U. Central de Venezuela (VE) Villy Baek Iversen, Technical U. of Denmark (DK) Koos Koen, Wits Business School (ZA) Ernst Leiss, U. of Houston (US) Greg Minshall, unaffiliated (US) Djafar Mynbaev, CUNY (US) Andrs Navarro, U. ICESI, (CO) Jos Neuman de Sousa, U. Federal de Ceara (BR) Miquel Nicolau, U dAndorra (AD) Dave Oran, Cisco (US) Harry Perros, North Carolina State U. (US) Jos M. Piquer, U. de Chile (CL) Ana Pont, U. Politcnica de Valncia (ES) Ramon Puigjaner, U. de les Illes Balears (ES), Chairman Guy Pujolle, LIP6 (FR) Francisco-Jos Quiles, U. de Castilla-La Mancha (ES) S. V. Raghavan, Indian Institute of Technology at Madras (IN) Jennifer Rexford, ATT (US) Daniela Rosu, IBM (US) Gerardo Rubino, IRISA (FR) Bartomeu Serra, U. de les Illes Balears (ES) Edmundo de Souza e Silva, U. Federal de Rio de Janeiro (BR) Otto Spaniol, RWTH Aachen (DE) Yutaka Takahashi, Kyoto U. (JP) Gonzalo Ulloa, U. ICESI (CO) Alberto Valderruten (U. de A Corunha, ES) Alfredo Viola, U. de la Repblica (UY) Conference goals The Latin America Networking Conference 2005 will provide an international technical forum for experts from industry and academia everywhere in the world, but especially from the Latin American countries, to exchange ideas and present results of ongoing research in networking. Topics of Interest Topics include but are not restricted to: * Low cost access networks * Sensor and actor networks * Low rate communications * National/Regional communication infrastructures * Wireless and Mobile Networking * PC Cluster computation * Applications for productivity * Internet based applications * Network management * Network security * Optical Networks * Protocols and routing * Satellite communication systems * Next generation Internet and network architectures * Peer-to-Peer communications * Photonic networks Submission of papers that cover solutions of specific network problems of the Latin America region is especially encouraged. Key Dates * Deadline for Tutorial proposals May 15 * Deadline for papers May 22 * Notification of acceptance June 30 * Camera ready papers received Aug. 1 * Tutorials Oct. 10-11 * Presentation of Accepted Papers Oct. 12-14 Submission of Papers Papers should be uploaded electronically, preferably in .pdf format, to the conference website: http://lanc05.uib.es . For general questions, contact lanc05@hotmail.com . The first page must contain an abstract of about 150 words, name and affiliation of author(s), as well as the lead authors postal address, telephone numbers, fax numbers, and e-mail. Authors submitting a paper must state that it has not been published before and is not being submitted elsewhere. Full papers should have no more than 15 pages, and follow the style to be announced soon. Accepted papers will be published in the conference proceedings and distributed to the conference attendees. At least one of the authors must register at the regular fee at the conference and attend the conference to present the paper. Conference proceedings will be published by ACM SIGCOMM in its Digital Library (confirmation pending). Submitted papers must be in English; accepted papers must be presented in English. Tutorials Proposals for half/full day tutorials are solicited: state subject area, level, goals and objectives, and give a short biography of the speaker(s). Proposals should be sent to the email address of the conference, to the attention of the chairman of the Program Committee. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 07:29:37 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10166 for ; Thu, 7 Apr 2005 07:29:37 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJVLA-0005xw-99 for manet-web-archive@ietf.org; Thu, 07 Apr 2005 07:38:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJV7C-0000rq-LQ; Thu, 07 Apr 2005 07:24:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJV77-0000rl-47 for manet@megatron.ietf.org; Thu, 07 Apr 2005 07:24: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 HAA09648 for ; Thu, 7 Apr 2005 07:23:52 -0400 (EDT) Received: from dolphin.indonoc.com ([65.98.41.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJVFX-0005k8-C5 for manet@ietf.org; Thu, 07 Apr 2005 07:32:46 -0400 Received: from [202.69.97.190] (helo=gudang01) by dolphin.indonoc.com with smtp (Exim 4.50) id 1DJV61-0007nx-8q; Thu, 07 Apr 2005 07:23:20 -0400 Message-ID: <000e01c53b64$2cfbb930$f17aa8c0@gudang01> From: "abdusyarif" To: "aodvimpl" , "luke klein-berndt" , "Familiar" , Date: Thu, 7 Apr 2005 18:22:13 +0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-PopBeforeSMTPSenders: abdusyarif@cizinet.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - dolphin.indonoc.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - cizinet.org X-Spam-Score: 2.9 (++) X-Scan-Signature: 913ee11e7c554f7d4da75d500826397e Cc: riri fitri sari Subject: [manet] Error compiling Kernel-aodv for ARM 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="===============1147565871==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.9 (++) X-Scan-Signature: 872695ea777a517bf5717e5acc69f8be This is a multi-part message in MIME format. --===============1147565871== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C53B9E.B83E4F50" This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C53B9E.B83E4F50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all... I've been trying to compiling kernel-aodv for ARM Linux Familiar v0.2.7. = I did it im my laptop using Linux kernel 2.4. And I follwed 'README' = file in kernel-aodv. When I did 'make' , it show error like this : [root@abdusyarif kernel-aodv_v2.2.2]# make /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c aodv_dev.c -o aodv_dev.o In file included from aodv_route.h:17, from aodv_dev.h:21, from aodv_dev.c:9: packet_queue.h:78: warning: `struct nf_info' declared inside parameter = list packet_queue.h:78: warning: its scope is only this definition or = declaration, which is probably not what you want /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c aodv_neigh.c -o aodv_neigh.o In file included from aodv_route.h:17, from aodv_neigh.h:19, from aodv_neigh.c:9: packet_queue.h:78: warning: `struct nf_info' declared inside parameter = list packet_queue.h:78: warning: its scope is only this definition or = declaration, which is probably not what you want /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c aodv_route.c -o aodv_route.o In file included from aodv_route.h:17, from aodv_route.c:10: packet_queue.h:78: warning: `struct nf_info' declared inside parameter = list packet_queue.h:78: warning: its scope is only this definition or = declaration, which is probably not what you want /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c aodv_thread.c -o aodv_thread.o /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c flood_id.c -o flood_id.o flood_id.c: In function `read_flood_id_proc': flood_id.c:144: warning: passing arg 2 of `strcpy' makes pointer from = integer without a cast /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c hello.c -o hello.o In file included from aodv_route.h:17, from aodv_neigh.h:19, from hello.h:12, from hello.c:9: packet_queue.h:78: warning: `struct nf_info' declared inside parameter = list packet_queue.h:78: warning: its scope is only this definition or = declaration, which is probably not what you want /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c kernel_route.c -o kernel_route.o kernel_route.c: In function `delete_kernel_route_entry': kernel_route.c:109: warning: passing arg 2 of `strcpy' makes pointer = from integer without a cast kernel_route.c:110: warning: passing arg 2 of `strcpy' makes pointer = from integer without a cast /home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE = -I/home/anyip/adhoc/ipaq/include/ -c module.c -o module.o In file included from aodv_route.h:17, from packet_in.h:21, from module.h:20, from module.c:9: packet_queue.h:78: warning: `struct nf_info' declared inside parameter = list packet_queue.h:78: warning: its scope is only this definition or = declaration, which is probably not what you want module.c: In function `init_module': module.c:89: invalid use of undefined type `struct nf_hook_ops' module.c:90: invalid use of undefined type `struct nf_hook_ops' module.c:91: invalid use of undefined type `struct nf_hook_ops' module.c:92: invalid use of undefined type `struct nf_hook_ops' module.c:93: invalid use of undefined type `struct nf_hook_ops' module.c:96: invalid use of undefined type `struct nf_hook_ops' module.c:97: invalid use of undefined type `struct nf_hook_ops' module.c:98: invalid use of undefined type `struct nf_hook_ops' module.c:99: invalid use of undefined type `struct nf_hook_ops' module.c:100: invalid use of undefined type `struct nf_hook_ops' module.c: At top level: module.c:11: storage size of `input_filter' isn't known module.c:12: storage size of `output_filter' isn't known make: *** [module.o] Error 1 [root@abdusyarif kernel-aodv_v2.2.2]#=20 My questions are : (1) What is wrong ? (2) What am I suppose to do? Thanks in advance, Abdusy Syarif ------=_NextPart_000_000B_01C53B9E.B83E4F50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear all...
 
I've been trying to compiling = kernel-aodv for ARM=20 Linux Familiar v0.2.7.
I did it im my laptop using Linux = kernel 2.4. And I=20 follwed 'README' file in kernel-aodv.
When I did 'make' , it show error like = this=20 :
 
[root@abdusyarif kernel-aodv_v2.2.2]# make

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c aodv_dev.c -o aodv_dev.o

In file included from aodv_route.h:17,

from aodv_dev.h:21,

from aodv_dev.c:9:

packet_queue.h:78: warning: `struct nf_info' declared inside = parameter=20 list

packet_queue.h:78: warning: its scope is only this definition or = declaration,=20 which is probably not what you want

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c aodv_neigh.c -o aodv_neigh.o

In file included from aodv_route.h:17,

from aodv_neigh.h:19,

from aodv_neigh.c:9:

packet_queue.h:78: warning: `struct nf_info' declared inside = parameter=20 list

packet_queue.h:78: warning: its scope is only this definition or = declaration,=20 which is probably not what you want

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c aodv_route.c -o aodv_route.o

In file included from aodv_route.h:17,

from aodv_route.c:10:

packet_queue.h:78: warning: `struct nf_info' declared inside = parameter=20 list

packet_queue.h:78: warning: its scope is only this definition or = declaration,=20 which is probably not what you want

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c aodv_thread.c -o aodv_thread.o

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c flood_id.c -o flood_id.o

flood_id.c: In function `read_flood_id_proc':

flood_id.c:144: warning: passing arg 2 of `strcpy' makes pointer from = integer=20 without a cast

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c hello.c -o hello.o

In file included from aodv_route.h:17,

from aodv_neigh.h:19,

from hello.h:12,

from hello.c:9:

packet_queue.h:78: warning: `struct nf_info' declared inside = parameter=20 list

packet_queue.h:78: warning: its scope is only this definition or = declaration,=20 which is probably not what you want

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c kernel_route.c -o = kernel_route.o

kernel_route.c: In function `delete_kernel_route_entry':

kernel_route.c:109: warning: passing arg 2 of `strcpy' makes pointer = from=20 integer without a cast

kernel_route.c:110: warning: passing arg 2 of `strcpy' makes pointer = from=20 integer without a cast

/home/anyip/testbed/arm/bin/arm-linux-gcc -O3 -DMODULE -D__KERNEL__ = -DLINUX=20 -DARM -DMESSAGES -DAODV_GATEWAY -DAODV_SIGNAL -DTRACE=20 -I/home/anyip/adhoc/ipaq/include/ -c module.c -o module.o

In file included from aodv_route.h:17,

from packet_in.h:21,

from module.h:20,

from module.c:9:

packet_queue.h:78: warning: `struct nf_info' declared inside = parameter=20 list

packet_queue.h:78: warning: its scope is only this definition or = declaration,=20 which is probably not what you want

module.c: In function `init_module':

module.c:89: invalid use of undefined type `struct nf_hook_ops'

module.c:90: invalid use of undefined type `struct nf_hook_ops'

module.c:91: invalid use of undefined type `struct nf_hook_ops'

module.c:92: invalid use of undefined type `struct nf_hook_ops'

module.c:93: invalid use of undefined type `struct nf_hook_ops'

module.c:96: invalid use of undefined type `struct nf_hook_ops'

module.c:97: invalid use of undefined type `struct nf_hook_ops'

module.c:98: invalid use of undefined type `struct nf_hook_ops'

module.c:99: invalid use of undefined type `struct nf_hook_ops'

module.c:100: invalid use of undefined type `struct nf_hook_ops'

module.c: At top level:

module.c:11: storage size of `input_filter' isn't known

module.c:12: storage size of `output_filter' isn't known

make: *** [module.o] Error 1

[root@abdusyarif kernel-aodv_v2.2.2]#

My questions are :

(1) What is wrong ? (2)  What am I = suppose to=20 do?

Thanks in advance,

Abdusy Syarif


 

 

 

------=_NextPart_000_000B_01C53B9E.B83E4F50-- --===============1147565871== 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 --===============1147565871==-- From manet-bounces@ietf.org Thu Apr 7 10:56:32 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00911 for ; Thu, 7 Apr 2005 10:56:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJYZR-0005lG-Mg for manet-web-archive@ietf.org; Thu, 07 Apr 2005 11:05:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJY60-0005C7-Fn; Thu, 07 Apr 2005 10:35:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJY5x-0005Bz-Gn for manet@megatron.ietf.org; Thu, 07 Apr 2005 10:34: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 KAA28807 for ; Thu, 7 Apr 2005 10:34:55 -0400 (EDT) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm2.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJYEX-0004vo-0L for manet@ietf.org; Thu, 07 Apr 2005 10:43:49 -0400 Received: from alcatel.com (localhost [127.0.0.1]) by tm2.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j37EYsWg007754; Thu, 7 Apr 2005 10:34:54 -0400 (EDT) Message-ID: <4255450E.555C8714@alcatel.com> Date: Thu, 07 Apr 2005 10:34:54 -0400 From: Ali El-Husseini Organization: Alcatel CID X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: andjela@UDel.Edu References: <200504071133.j37BX8dZ026522@mx4.alcatel.com> Content-Type: multipart/mixed; boundary="------------3D7FFABDEA8604ADC964FD5E" X-Spam-Score: 0.1 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Cc: manet@ietf.org, amr_hassan1@yahoo.com Subject: [manet] Re: manet Digest, Vol 12, Issue 7 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: 2857c5c041d6c02d7181d602c22822c8 This is a multi-part message in MIME format. --------------3D7FFABDEA8604ADC964FD5E Content-Type: multipart/alternative; boundary="------------6CC90B04F2A426C6524BC1DD" --------------6CC90B04F2A426C6524BC1DD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm doing some research on that area that target routing based on mobility model. While I'll believe that there is no deterministic model that covers all scenarios (including random model, used in research, that can be treated as the worst case in studding routing algo.), I believe that probabilistic mobility model (that I'm working on) covers what ever scenario you want and can evolve through time to predict mobility of individual entities based on communities they most fit in. Mobility model of any entity is defined using a probability model that in real life situations can be approximated to a deterministic model (of course with some variance and exception that happens however model can learn to cover these). > Message: 4 > Date: Thu, 07 Apr 2005 15:23:02 +0930 > From: "Peter Pham" > Subject: Re: Re: [manet] Mobility Models > To: andjela@UDel.Edu > Cc: manet@ietf.org, amr_hassan1@yahoo.com > Message-ID: <1112853182.8c26169cnppham@myrealbox.com> > Content-Type: text/plain; charset="UTF-8" > > Hi > Check out the movement using Voronoi diagram. I think that there is a paper on it. From what I know, there is also ns2 Tcl script to generate it. > > The basic idea is that, people will tend to move around the building in the campus (not through the building). So, this model is relevant in quite a number of cases. > > About a realistic model, I don't think there is any mobility model that can be used for ALL the scenarios. Logically, there can not be right ? > > Regards > Peter Pham > --------------6CC90B04F2A426C6524BC1DD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I'm doing some research on that area that target routing based on mobility model. While I'll believe that there is no deterministic model that covers all scenarios (including random model, used in research, that can be treated as the worst case in studding routing algo.), I believe that probabilistic mobility model (that I'm working on) covers what ever scenario you want and can evolve through time to predict mobility of individual entities based on communities they most fit in. Mobility model of any entity is defined using a  probability model that in real life situations can be approximated to a deterministic model (of course with some variance and exception that happens however model can learn to cover these).
 
Message: 4
Date: Thu, 07 Apr 2005 15:23:02 +0930
From: "Peter Pham" <nppham@myrealbox.com>
Subject: Re: Re: [manet] Mobility Models
To: andjela@UDel.Edu
Cc: manet@ietf.org, amr_hassan1@yahoo.com
Message-ID: <1112853182.8c26169cnppham@myrealbox.com>
Content-Type: text/plain; charset="UTF-8"

Hi
Check out the movement using Voronoi diagram. I think that there is a paper on it. From what I know, there is also ns2 Tcl script to generate it.

The basic idea is that, people will tend to move around the building in the campus (not through the building). So, this model is relevant in quite a number of cases.

About a realistic model, I don't think there is any mobility model that can be used for ALL the scenarios. Logically, there can not be right ?

Regards
Peter Pham
 

--------------6CC90B04F2A426C6524BC1DD-- --------------3D7FFABDEA8604ADC964FD5E Content-Type: text/x-vcard; charset=us-ascii; name="ali.el-husseini.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ali El-Husseini Content-Disposition: attachment; filename="ali.el-husseini.vcf" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit begin:vcard n:El-Husseini;Ali tel;cell:(613)799-6473 tel;fax:(613)270-1150 tel;home:(613)270-1150 tel;work:(613)784-3579 x-mozilla-html:FALSE org:Alcatel IP Division ; Verification and Validation Department adr:;;600 March Rd.;Kanata;Ontario;K2K 2E6;Canada version:2.1 email;internet:ali.el-husseini@alcatel.com title:Verification Engineer fn:
Ali El-Husseini
ATM Switched Services

CONNECTING PEOPLE
end:vcard --------------3D7FFABDEA8604ADC964FD5E 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 --------------3D7FFABDEA8604ADC964FD5E-- From manet-bounces@ietf.org Thu Apr 7 11:13:24 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03243 for ; Thu, 7 Apr 2005 11:13:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJYpk-0006dS-Cy for manet-web-archive@ietf.org; Thu, 07 Apr 2005 11:22:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJYQR-00077n-8u; Thu, 07 Apr 2005 10:56:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJYQP-00077a-CF for manet@megatron.ietf.org; Thu, 07 Apr 2005 10:56: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 KAA00805 for ; Thu, 7 Apr 2005 10:56:02 -0400 (EDT) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJYYy-0005jI-0C for manet@ietf.org; Thu, 07 Apr 2005 11:04:57 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Difference between Wireless Mesh Router and Multi-RadioAccess Point Date: Thu, 7 Apr 2005 16:55:58 +0200 Message-ID: <9F1223587A755D47805AECAB7ECAF5D902430D22@swing.cefriel.it> Thread-Topic: [manet] Difference between Wireless Mesh Router and Multi-RadioAccess Point Thread-Index: AcU7Rah9JluiBonbS9SJwOcAE5Ey+AAPDm/g From: "Giorgio Mulas" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: quoted-printable Hi, So far I can understand there is a bit of confusion about three = different architectural elements that could be present in wireless mesh = networks. Usually, by "Access Point" it is meant a "a hardware device ... that = acts as a communication hub for users of a wireless device to connect to = a wired LAN" (www.webopedia.com). An access point does not have routing = capabilities. For reference we can schematize an access point as the two = layer device in figure: ----------------- MAC/LLC ----------------- Radio technology ----------------- Hence, a "Multi-radio Access Point" is simply an access point that can = manage more than one radio technology (using the same MAC/LLC or not = depends on implementation and performance considerations) as depicted in = the following diagram: ------------------------------- MAC/LLC ------------------------------- Different Radio technologies(!) ------------------------------- Finally a Wireless Router can be seen as an access point (single or = multi-radio) with routing capabilities (typical of layer 3 and not of = layer 2!) ------------------------------- Routing capabilities ------------------------------- MAC/LLC ------------------------------- Single/Multi Radio technology ------------------------------- I hope this helps. Giorgio ------------------------------------------ Giorgio Mulas | Consultant CEFRIEL =AD Politecnico di Milano Via Fucini, 2 =B7 20133 Milano (Italy) p. +39 02 23954 265 f. +39 02 23954 465 e. giorgio.mulas@cefriel.it > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]=20 > On Behalf Of Faisal Adeem Siddiqui > Sent: gioved=EC 7 aprile 2005 9.43 > To: manet@ietf.org > Subject: [manet] Difference between Wireless Mesh Router and=20 > Multi-RadioAccess Point >=20 >=20 > Hi everybody, > I've seen many wireless mesh network architectures. Some use=20 > wireless mesh router to connect end-user terminals while=20 > others use multi radio Access Points (AP) for the same=20 > purpose. The difference between the two approaches is quite=20 > ambiguous. In case of AP, do they use some kind of layer-2=20 > routing between APs for relaying packets? Do such APs support=20 > routing ? Can these APs be configured like a router and=20 > filter packets based on some policies or access lists ?=20 > Please clear my doubts. Thanks. Faisal. >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 7 11:38:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05898 for ; Thu, 7 Apr 2005 11:38:35 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJZEA-0007e4-Pg for manet-web-archive@ietf.org; Thu, 07 Apr 2005 11:47:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJZ3O-0003Qp-Bf; Thu, 07 Apr 2005 11:36:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJZ3K-0003Qa-CJ for manet@megatron.ietf.org; Thu, 07 Apr 2005 11:36: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 LAA05745 for ; Thu, 7 Apr 2005 11:36:15 -0400 (EDT) Received: from mail.saic-abingdon.com ([12.167.146.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJZBu-0007ZC-8I for manet@ietf.org; Thu, 07 Apr 2005 11:45:10 -0400 Received: from no.name.available by mail.saic-abingdon.com via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP; Thu, 7 Apr 2005 11:38:39 -0400 Received: from bh-exchange01.saic-abingdon.com ([172.17.10.225]) by bh-exchangefe.saic-abingdon.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 7 Apr 2005 11:40:52 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] Difference between Wireless Mesh Router andMulti-RadioAccess Point Date: Thu, 7 Apr 2005 11:40:51 -0400 Message-ID: <37B2A14433611A4C93B9A22A082E8ED6D40459@bh-exchange01.saic-abingdon.com> Thread-Topic: [manet] Difference between Wireless Mesh Router andMulti-RadioAccess Point Thread-Index: AcU7Rah9JluiBonbS9SJwOcAE5Ey+AAPDm/gAAFK5LE= From: "Roy, Radhika" To: "Giorgio Mulas" , X-OriginalArrivalTime: 07 Apr 2005 15:40:52.0012 (UTC) FILETIME=[2DCFEEC0:01C53B88] X-Spam-Score: 0.0 (/) X-Scan-Signature: e1924de3f9fb68e58c31920136007eb1 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="===============1253746625==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d This is a multi-part message in MIME format. --===============1253746625== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C53B88.2D9FD1BC" This is a multi-part message in MIME format. ------_=_NextPart_001_01C53B88.2D9FD1BC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Right! =20 Sometimes, MAC/LLC and Radio are also combined to represent wireless LAN = tech. =20 Best regards, Radhika ________________________________ From: manet-bounces@ietf.org on behalf of Giorgio Mulas Sent: Thu 4/7/2005 10:55 AM To: manet@ietf.org Subject: RE: [manet] Difference between Wireless Mesh Router = andMulti-RadioAccess Point Hi, So far I can understand there is a bit of confusion about three = different architectural elements that could be present in wireless mesh = networks. Usually, by "Access Point" it is meant a "a hardware device ... that = acts as a communication hub for users of a wireless device to connect to = a wired LAN" (www.webopedia.com). An access point does not have routing = capabilities. For reference we can schematize an access point as the two = layer device in figure: ----------------- MAC/LLC ----------------- Radio technology ----------------- Hence, a "Multi-radio Access Point" is simply an access point that can = manage more than one radio technology (using the same MAC/LLC or not = depends on implementation and performance considerations) as depicted in = the following diagram: ------------------------------- MAC/LLC ------------------------------- Different Radio technologies(!) ------------------------------- Finally a Wireless Router can be seen as an access point (single or = multi-radio) with routing capabilities (typical of layer 3 and not of = layer 2!) ------------------------------- Routing capabilities ------------------------------- MAC/LLC ------------------------------- Single/Multi Radio technology ------------------------------- I hope this helps. Giorgio ------------------------------------------ Giorgio Mulas | Consultant CEFRIEL =AD Politecnico di Milano Via Fucini, 2 =B7 20133 Milano (Italy) p. +39 02 23954 265 f. +39 02 23954 465 e. giorgio.mulas@cefriel.it > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > On Behalf Of Faisal Adeem Siddiqui > Sent: gioved=EC 7 aprile 2005 9.43 > To: manet@ietf.org > Subject: [manet] Difference between Wireless Mesh Router and > Multi-RadioAccess Point > > > Hi everybody, > I've seen many wireless mesh network architectures. Some use > wireless mesh router to connect end-user terminals while > others use multi radio Access Points (AP) for the same > purpose. The difference between the two approaches is quite > ambiguous. In case of AP, do they use some kind of layer-2 > routing between APs for relaying packets? Do such APs support > routing ? Can these APs be configured like a router and > filter packets based on some policies or access lists ? > Please clear my doubts. Thanks. Faisal. > > > _______________________________________________ > 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 ------_=_NextPart_001_01C53B88.2D9FD1BC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= RE: [manet] Difference between Wireless Mesh Router = andMulti-RadioAccess Point=0A= =0A= =0A=
=0A=
Right!
=0A=
 
=0A=
Sometimes, MAC/LLC = and Radio =0A= are also combined to represent wireless LAN = tech.
=0A=
 
=0A=
Best regards,
=0A=
Radhika
=0A=

=0A=
=0A= From: manet-bounces@ietf.org on = behalf of =0A= Giorgio Mulas
Sent: Thu 4/7/2005 10:55 AM
To: =0A= manet@ietf.org
Subject: RE: [manet] Difference between = Wireless Mesh =0A= Router andMulti-RadioAccess Point

=0A=
=0A=

Hi,
So far I can understand there is a bit of = confusion about =0A= three different architectural elements that could be present in wireless = mesh =0A= networks.

Usually, by "Access Point" it is meant a "a hardware = device ... =0A= that acts as a communication hub for users of a wireless device to = connect to a =0A= wired LAN" (www.webopedia.com). An access point does not have routing =0A= capabilities. For reference we can schematize an access point as the two = layer =0A= device in =0A= figure:

-----------------
MAC/LLC
-----------------
Radio= =0A= technology
-----------------

Hence, a "Multi-radio Access = Point" is =0A= simply an access point that can manage more than one radio technology = (using the =0A= same MAC/LLC or not depends on implementation and performance = considerations) as =0A= depicted in the following =0A= diagram:

-------------------------------
MAC/LLC
-----------= --------------------
Different =0A= Radio technologies(!)
-------------------------------

Finally = a =0A= Wireless Router can be seen as an access point (single or multi-radio) = with =0A= routing capabilities (typical of layer 3 and not of layer =0A= 2!)

-------------------------------
Routing =0A= capabilities
-------------------------------
MAC/LLC
-----------= --------------------
Single/Multi =0A= Radio technology
-------------------------------

I hope this =0A= helps.


        =0A= Giorgio


------------------------------------------
Giorgio = Mulas | =0A= Consultant

CEFRIEL ­ Politecnico di Milano
Via Fucini, 2 = =B7 20133 =0A= Milano (Italy)

p. +39 02 23954 265
f. +39 02 23954 465
e. =0A= giorgio.mulas@cefriel.it


> -----Original = Message-----
> =0A= From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]=
> =0A= On Behalf Of Faisal Adeem Siddiqui
> Sent: gioved=EC 7 aprile 2005 =0A= 9.43
> To: manet@ietf.org
> Subject: [manet] Difference = between =0A= Wireless Mesh Router and
> Multi-RadioAccess = Point
>
>
> =0A= Hi everybody,
> I've seen many wireless mesh network = architectures. Some =0A= use
> wireless mesh router to connect end-user terminals = while
> =0A= others use multi radio Access Points (AP) for the same
> purpose. = The =0A= difference between the two approaches is quite
> ambiguous. In = case of AP, =0A= do they use some kind of layer-2
> routing between APs for = relaying =0A= packets? Do such APs support
> routing ? Can these APs be = configured like =0A= a router and
> filter packets based on some policies or access = lists =0A= ?
> Please clear my doubts. Thanks. = Faisal.
>
>
> =0A= _______________________________________________
> manet mailing =0A= list
> manet@ietf.org
> https://www1.ietf.o= rg/mailman/listinfo/manet
>

____________________________= ___________________
manet =0A= mailing list
manet@ietf.org
https://www1.ietf.o= rg/mailman/listinfo/manet

=0A= =0A= =0A= ------_=_NextPart_001_01C53B88.2D9FD1BC-- --===============1253746625== 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 --===============1253746625==-- From manet-bounces@ietf.org Thu Apr 7 12:28:56 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11315 for ; Thu, 7 Apr 2005 12:28:56 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJa0u-0001Fz-FU for manet-web-archive@ietf.org; Thu, 07 Apr 2005 12:37:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJZrG-0008Rk-Vk; Thu, 07 Apr 2005 12:27:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJZrE-0008RL-6E for manet@megatron.ietf.org; Thu, 07 Apr 2005 12:27: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 MAA11156 for ; Thu, 7 Apr 2005 12:27:48 -0400 (EDT) Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJZzj-0001DV-9J for manet@ietf.org; Thu, 07 Apr 2005 12:36:44 -0400 Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 1DBAA1800208 for ; Thu, 7 Apr 2005 16:27:33 +0000 (GMT) X-OB-Received: from unknown (208.36.123.33) by wfilter.us4.outblaze.com; 7 Apr 2005 16:27:32 -0000 Received: by ws7-4.us4.outblaze.com (Postfix, from userid 1001) id 59546CA07A; Thu, 7 Apr 2005 16:27:28 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [144.243.4.200] by ws7-4.us4.outblaze.com with http for yasser.lotfy@lycos.com; Thu, 07 Apr 2005 11:27:28 -0500 From: "yasser lotfy" To: manet@ietf.org Date: Thu, 07 Apr 2005 11:27:28 -0500 Subject: RE: [manet] Difference between Wireless Mesh Router andMulti-RadioAccess Point X-Originating-Ip: 144.243.4.200 X-Originating-Server: ws7-4.us4.outblaze.com Message-Id: <20050407162728.59546CA07A@ws7-4.us4.outblaze.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 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: 6d95a152022472c7d6cdf886a0424dc6 Content-Transfer-Encoding: quoted-printable Hi, I agree with Giorgio on his clear classification. However, once you have mu= ltiple radio, you automatically have to do routing. In many implementation,= the routing is done based on the mac address. This is in practical sense, = a hack, but widely adapted hack. /yasser -------------------- Hi, So far I can understand there is a bit of confusion about three=20 different architectural elements that could be present in wireless=20 mesh networks. Usually, by "Access Point" it is meant a "a hardware device ... that=20 acts as a communication hub for users of a wireless device to connect=20 to a wired LAN" (www.webopedia.com). An access point does not have=20 routing capabilities. For reference we can schematize an access point=20 as the two layer device in figure: ----------------- MAC/LLC ----------------- Radio technology ----------------- Hence, a "Multi-radio Access Point" is simply an access point that=20 can manage more than one radio technology (using the same MAC/LLC or=20 not depends on implementation and performance considerations) as=20 depicted in the following diagram: ------------------------------- MAC/LLC ------------------------------- Different Radio technologies(!) ------------------------------- Finally a Wireless Router can be seen as an access point (single or=20 multi-radio) with routing capabilities (typical of layer 3 and not of=20 layer 2!) ------------------------------- Routing capabilities ------------------------------- MAC/LLC ------------------------------- Single/Multi Radio technology ------------------------------- I hope this helps. Giorgio ------------------------------------------ Giorgio Mulas | Consultant CEFRIEL =AD Politecnico di Milano Via Fucini, 2 =B7 20133 Milano (Italy) p. +39 02 23954 265 f. +39 02 23954 465 e. giorgio.mulas@cefriel.it > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On=20 > Behalf Of Faisal Adeem Siddiqui > Sent: gioved=EC 7 aprile 2005 9.43 > To: manet@ietf.org > Subject: [manet] Difference between Wireless Mesh Router and=20 > Multi-RadioAccess Point > > > Hi everybody, > I've seen many wireless mesh network architectures. Some use=20 > wireless mesh router to connect end-user terminals while others use=20 > multi radio Access Points (AP) for the same purpose. The difference=20 > between the two approaches is quite ambiguous. In case of AP, do=20 > they use some kind of layer-2 routing between APs for relaying=20 > packets? Do such APs support routing ? Can these APs be configured=20 > like a router and filter packets based on some policies or access=20 > lists ? Please clear my doubts. Thanks. Faisal. > > > _______________________________________________ > 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 _______________________________________________ NEW! Lycos Dating Search. The only place to search multiple dating sites at= once. http://datingsearch.lycos.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 8 03:35:32 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14012 for ; Fri, 8 Apr 2005 03:35:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJoAM-0005Tc-Io for manet-web-archive@ietf.org; Fri, 08 Apr 2005 03:44:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJo0u-0000VZ-Tm; Fri, 08 Apr 2005 03:34:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJo0o-0000Us-5O for manet@megatron.ietf.org; Fri, 08 Apr 2005 03:34: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 DAA13963 for ; Fri, 8 Apr 2005 03:34:40 -0400 (EDT) Received: from mailgate.cc.niigata-u.ac.jp ([133.35.14.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJo9U-0005SX-40 for manet@ietf.org; Fri, 08 Apr 2005 03:43:42 -0400 Received: from ms01.net.ie.niigata-u.ac.jp (mailgate.cc.niigata-u.ac.jp [127.0.0.1]) by mailgate.cc.niigata-u.ac.jp (8.11.6/8.11.6) with ESMTP id j387YPK09087 for ; Fri, 8 Apr 2005 16:34:25 +0900 Received: from localhost (ms01 [127.0.0.1]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with ESMTP id 5B0E512048 for ; Fri, 8 Apr 2005 16:33:43 +0900 (JST) Received: from ms01.net.ie.niigata-u.ac.jp ([127.0.0.1]) by localhost (ms01.net.ie.niigata-u.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14057-09 for ; Fri, 8 Apr 2005 16:33:34 +0900 (JST) Received: from localhost (ms02.net.ie.niigata-u.ac.jp [133.35.156.2]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with SMTP id CF0A912046 for ; Fri, 8 Apr 2005 16:33:34 +0900 (JST) Date: Fri, 8 Apr 2005 16:38:57 +0900 From: wjf To: manet@ietf.org Message-Id: <20050408163857.5cf79f8d.wjf@net.ie.niigata-u.ac.jp> X-Mailer: Sylpheed version 1.0.0beta1 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at net.ie.niigata-u.ac.jp X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit Subject: [manet] rate of ACK (using the short PLCP preamble)? 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 Content-Transfer-Encoding: 7bit Hello, when the short preamble is used, can the control frame be transmitted at the 1Mbits rate? or is the understanding that these control frames can only be transmitted at 2M rate right when using the short PLCP preamble? any input is welcomed. wjf _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 8 05:48:53 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28303 for ; Fri, 8 Apr 2005 05:48:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJqFR-0002ch-AI for manet-web-archive@ietf.org; Fri, 08 Apr 2005 05:57:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJq5d-0003xR-Pi; Fri, 08 Apr 2005 05:47:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJq5b-0003x5-Gu for manet@megatron.ietf.org; Fri, 08 Apr 2005 05:47: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 FAA27767 for ; Fri, 8 Apr 2005 05:47:45 -0400 (EDT) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJqAO-0002AX-Sr for manet@ietf.org; Fri, 08 Apr 2005 05:52:46 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j389hVeU017914; Fri, 8 Apr 2005 11:43:32 +0200 (CEST) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id 7E0B23C315; Fri, 8 Apr 2005 11:43:29 +0200 (MEST) Message-ID: <42565241.5010909@eurecom.fr> Date: Fri, 08 Apr 2005 11:43:29 +0200 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: yasser lotfy Subject: Re: [manet] Difference between Wireless Mesh Router andMulti-RadioAccess Point References: <20050407162728.59546CA07A@ws7-4.us4.outblaze.com> In-Reply-To: <20050407162728.59546CA07A@ws7-4.us4.outblaze.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.eurecom.fr id j389hVeU017914 X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 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: b2809b6f39decc6de467dcf252f42af1 Content-Transfer-Encoding: quoted-printable Hello everyone, I agree on the fact that terminology is mesh networks domain is not yet=20 clearly defined. With respect to Giorgio classification, in my opinion,=20 when we use the term "multi-radio" it does not necessarilty mean that=20 the radio technologies are different. I mean that IMHO a "multi radio=20 wireless router" is a router that either exploits several heterogeneous=20 radio technologies at physical layer or several instances of the same=20 radio technology (i.e. two 802.11b antennas). See as a reference the=20 article =93Routing in Multi-Radio, Multi-Hop Wireless Mesh Networks=94=20 (http://research.microsoft.com/mesh/papers/multiradio.pdf). Regards Claudio yasser lotfy wrote: >Hi, >I agree with Giorgio on his clear classification. However, once you have= multiple radio, you automatically have to do routing. In many implementa= tion, the routing is done based on the mac address. This is in practical = sense, a hack, but widely adapted hack. > >/yasser >-------------------- >Hi, >So far I can understand there is a bit of confusion about three=20 >different architectural elements that could be present in wireless=20 >mesh networks. > >Usually, by "Access Point" it is meant a "a hardware device ... that=20 >acts as a communication hub for users of a wireless device to connect=20 >to a wired LAN" (www.webopedia.com). An access point does not have=20 >routing capabilities. For reference we can schematize an access point=20 >as the two layer device in figure: > >----------------- >MAC/LLC >----------------- >Radio technology >----------------- > >Hence, a "Multi-radio Access Point" is simply an access point that=20 >can manage more than one radio technology (using the same MAC/LLC or=20 >not depends on implementation and performance considerations) as=20 >depicted in the following diagram: > >------------------------------- >MAC/LLC >------------------------------- >Different Radio technologies(!) >------------------------------- > >Finally a Wireless Router can be seen as an access point (single or=20 >multi-radio) with routing capabilities (typical of layer 3 and not of=20 >layer 2!) > >------------------------------- >Routing capabilities >------------------------------- >MAC/LLC >------------------------------- >Single/Multi Radio technology >------------------------------- > >I hope this helps. > > > Giorgio > > >------------------------------------------ >Giorgio Mulas | Consultant > >CEFRIEL =AD Politecnico di Milano >Via Fucini, 2 =B7 20133 Milano (Italy) > >p. +39 02 23954 265 >f. +39 02 23954 465 >e. giorgio.mulas@cefriel.it > > > =20 > >>-----Original Message----- >>From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On=20 >>Behalf Of Faisal Adeem Siddiqui >>Sent: gioved=EC 7 aprile 2005 9.43 >>To: manet@ietf.org >>Subject: [manet] Difference between Wireless Mesh Router and=20 >>Multi-RadioAccess Point >> >> >>Hi everybody, >>I've seen many wireless mesh network architectures. Some use=20 >>wireless mesh router to connect end-user terminals while others use=20 >>multi radio Access Points (AP) for the same purpose. The difference=20 >>between the two approaches is quite ambiguous. In case of AP, do=20 >>they use some kind of layer-2 routing between APs for relaying=20 >>packets? Do such APs support routing ? Can these APs be configured=20 >>like a router and filter packets based on some policies or access=20 >>lists ? Please clear my doubts. Thanks. Faisal. >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> =20 >> > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 8 07:28:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05417 for ; Fri, 8 Apr 2005 07:28:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJrnv-0007OQ-Ec for manet-web-archive@ietf.org; Fri, 08 Apr 2005 07:37:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJre3-0003Qi-Bq; Fri, 08 Apr 2005 07:27:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJre1-0003Qd-PF for manet@megatron.ietf.org; Fri, 08 Apr 2005 07:27: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 HAA05249 for ; Fri, 8 Apr 2005 07:27:25 -0400 (EDT) Received: from web40508.mail.yahoo.com ([66.218.78.125]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJrmk-0007G7-Sx for manet@ietf.org; Fri, 08 Apr 2005 07:36:28 -0400 Received: (qmail 49606 invoked by uid 60001); 8 Apr 2005 11:27:14 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ag18NmxW/f3r7oEShAW5x47W4+kx8XC36FO3ryA/Uiju6Uf8ZLW67OxQNW+9mUVHlhjiHiNZnLBVKL4z7LuqDKUXjznCe5Lb92pBA1xpOsgKNsc5QeHL+9aDkCNrQH0nLVDZ9FuBP51Zc7Da63LxuD0pOBfGidHNuYa2sprcLAs= ; Message-ID: <20050408112714.49604.qmail@web40508.mail.yahoo.com> Received: from [210.212.89.5] by web40508.mail.yahoo.com via HTTP; Fri, 08 Apr 2005 04:27:14 PDT Date: Fri, 8 Apr 2005 04:27:14 -0700 (PDT) From: "inforaks@yahoo.com" To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 2.9 (++) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] help :regarding fixed+wireless scenario 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="===============1732548741==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.9 (++) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 --===============1732548741== Content-Type: multipart/alternative; boundary="0-309136725-1112959634=:49433" --0-309136725-1112959634=:49433 Content-Type: text/plain; charset=us-ascii hi i have simulated the scenario(fixed + wireless) in which i m using modified AODV as protocol.I want to check the data packets forwarded by Gateway to the fixed node (sent by mobile nodes). Gateway reciving packets for fixed node at MAC level and then it is sending to fixed node. i want that gateway recive this packets at AGT level. is there any way to check or get packet recived at AGT level. thanks in advance with regards rakesh --------------------------------- Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. --0-309136725-1112959634=:49433 Content-Type: text/html; charset=us-ascii
hi
i have simulated the scenario(fixed + wireless) in which i m using
modified AODV as protocol.I want to check the data packets forwarded by
Gateway to the fixed node (sent by mobile
nodes). Gateway reciving packets for fixed node at MAC level and then
it is sending to fixed node. i want that gateway recive this packets at
AGT level. is there any way to check or get packet recived at AGT level.
 
thanks in advance

with regards
rakesh

Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun. --0-309136725-1112959634=:49433-- --===============1732548741== 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 --===============1732548741==-- From manet-bounces@ietf.org Fri Apr 8 08:45:22 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13404 for ; Fri, 8 Apr 2005 08:45:22 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJt0E-0003CM-KZ for manet-web-archive@ietf.org; Fri, 08 Apr 2005 08:54:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJspt-0002VZ-Gg; Fri, 08 Apr 2005 08:43:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJspq-0002UX-Nu for manet@megatron.ietf.org; Fri, 08 Apr 2005 08:43: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 IAA13212 for ; Fri, 8 Apr 2005 08:43:39 -0400 (EDT) Received: from mail.um.es ([155.54.212.105] helo=xenon2.telemat.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJsyY-00038k-OH for manet@ietf.org; Fri, 08 Apr 2005 08:52:44 -0400 Received: from localhost (localhost [127.0.0.1]) by xenon2.telemat.um.es (Postfix) with ESMTP id 57C4623C3C4; Fri, 8 Apr 2005 14:43:24 +0200 (CEST) Received: from xenon2.telemat.um.es ([127.0.0.1]) by localhost (xenon2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04446-01-39; Fri, 8 Apr 2005 14:43:24 +0200 (CEST) Received: from [155.54.210.26] (dibulibu.um.es [155.54.1.250]) by xenon2.telemat.um.es (Postfix) with ESMTP id 1BE3023C3BD; Fri, 8 Apr 2005 14:43:24 +0200 (CEST) Message-ID: <42567C6A.30305@dif.um.es> Date: Fri, 08 Apr 2005 14:43:22 +0200 From: "Pedro M. Ruiz" User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "inforaks@yahoo.com" Subject: Re: [manet] help :regarding fixed+wireless scenario References: <20050408112714.49604.qmail@web40508.mail.yahoo.com> In-Reply-To: <20050408112714.49604.qmail@web40508.mail.yahoo.com> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es X-Spam-Score: 0.5 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e 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="===============1468260576==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 This is a multi-part message in MIME format. --===============1468260576== Content-Type: multipart/alternative; boundary="------------000805070802020502030302" This is a multi-part message in MIME format. --------------000805070802020502030302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable To do so, you can perform an install-tap at the agent to set the=20 interface to promiscuous mode. Regards, --Pedro PS: I assume you=B4re using ns-2... inforaks@yahoo.com wrote: > hi > i have simulated the scenario(fixed + wireless) in which i m using > modified AODV as protocol.I want to check the data packets forwarded by > Gateway to the fixed node (sent by mobile > nodes). Gateway reciving packets for fixed node at MAC level and then > it is sending to fixed node. i want that gateway recive this packets at > AGT level. is there any way to check or get packet recived at AGT level= . > =20 > thanks in advance > > with regards > rakesh > > -----------------------------------------------------------------------= - > Yahoo! Messenger > Show us what our next emoticon should look like. Join the fun.=20 > =20 > > >------------------------------------------------------------------------ > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > =20 > --------------000805070802020502030302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To do so, you can perform an install-tap at the agent to set the interface to promiscuous mode.

Regards,

--Pedro

PS: I assume you´re using ns-2...

inforaks@yahoo.com wrote:
hi
i have simulated the scenario(fixed + wireless) in which i m using
modified AODV as protocol.I want to check the data packets forwarded by
Gateway to the fixed node (sent by mobile
nodes). Gateway reciving packets for fixed node at MAC level and then
it is sending to fixed node. i want that gateway recive this packets at
AGT level. is there any way to check or get packet recived at AGT level.
 
thanks in advance

with regards
rakesh

Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun. 

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

--------------000805070802020502030302-- --===============1468260576== 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 --===============1468260576==-- From manet-bounces@ietf.org Fri Apr 8 09:05:24 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15191 for ; Fri, 8 Apr 2005 09:05:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJtJc-0004Iv-J3 for manet-web-archive@ietf.org; Fri, 08 Apr 2005 09:14:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJt3b-0004s4-R1; Fri, 08 Apr 2005 08: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 1DJt3Z-0004ro-SD for manet@megatron.ietf.org; Fri, 08 Apr 2005 08:57: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 IAA14580 for ; Fri, 8 Apr 2005 08:57:52 -0400 (EDT) Received: from cs-exs2.bu.edu ([128.197.10.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJtCK-0003nH-QA for manet@ietf.org; Fri, 08 Apr 2005 09:06:57 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 8 Apr 2005 08:58:32 -0400 Message-ID: <0511C607B17F804EBE96FFECD1FD9859319B44@cs-exs2.cs-nt.bu.edu> Thread-Topic: CFP: First IEEE ICNP Workshop on Secure Network Protocols (NPSec) thread-index: AcU8OojAtX1Ntw4BSC20WKk6fxxHcg== From: "Ibrahim Matta" To: X-Spam-Score: 0.1 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Content-Transfer-Encoding: quoted-printable Subject: [manet] CFP: First IEEE ICNP Workshop on Secure Network Protocols (NPSec) 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: 3a4bc66230659131057bb68ed51598f8 Content-Transfer-Encoding: quoted-printable Please accept our apologies if you receive multiple copies of this CFP. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D CALL FOR PAPERS First IEEE ICNP Workshop on Secure Network Protocols (NPSec) Boston, Massachusetts, USA November 6, 2005 http://www.cerias.purdue.edu/npsec/ (In conjunction with ICNP 2005: The 13th IEEE International Conference on Network Protocols) SCOPE: The first IEEE ICNP workshop on Secure Network Protocols (NPSec) is a one-day event held in conjunction with ICNP 2005. NPSec focuses on two general areas. The first focus is on the development and analysis of secure or hardened protocols for the operation (establishment and maintenance) of network infrastructure, including such targets as secure multidomain, ad-hoc, sensor or overlay networks, or other related target areas. This can include new protocols, enhancements to existing protocols, protocol analysis, and new attacks on existing protocols. The second focus is on employing such secure network protocols to create or enhance network applications. Examples include collaborative firewalls, incentive strategies for multiparty networks, and deployment strategies to enable secure applications. TOPICS OF INTEREST: * secure or hardened protocols for operation of networks including (but not limited to): - internetworking, e.g., BGP, DNS - MANETs - LANs and WLANs - cellular data networks - p2p and other overlay networks - federated trust systems - sensor networks * vulnerability analysis of existing protocols and applications (both theoretical and case studies), including novel attacks * key distribution * collaborative intrusion detection and response, such as collaborative firewalling * incentive systems for multiparty networks, such as for p2p and MANET routing * protocol configuration and deployment strategies enabling secure applications, e.g., e-commerce IMPORTANT DATES: Paper submission: June 3, 2005 Notification of acceptance: July 15, 2005 Camera ready version: August 5, 2005 ORGANIZING COMMITTEE: General Chair: Sonia Fahmy, Purdue University Technical Program Committee Chairs: George Kesidis, Pennsylvania State University Nicholas Weaver, International Computer Science Institute Publicity Chair: James Minseok Kwon, Rochester Institute of Technology Web Chair: Cristina Nita-Rotaru, Purdue University TECHNICAL PROGRAM COMMITTEE: David Brumley, Carnegie Mellon University Guohong Cao, Pennsylvania State University Joseph Evans, U.S. National Science Foundation Lixin Gao, University of Massachusetts, Amherst George Kesidis, Pennsylvania State University Edward Knightly, Rice University Carl Landwehr, University of Maryland Marco Ajmone Marsan, Politecnico di Torino, Italy Douglas Maughan, U.S. Department of Homeland Security Patrick McDaniel, Pennsylvania State University Jelena Mirkovic, University of Delaware Peng Ning, North Carolina State University Cristina Nita-Rotaru, Purdue University Phil Porras, SRI Saswati Sarkar, University of Pennsylvania Lakshminarayanan Subramanian, University of California at Berkeley Nina Taft, Intel Research Nicholas Weaver, International Computer Science Institute Felix Wu, University of California at Davis Jun Xu, Georgia Institute of Technology Bulent Yener, Rensselaer Polytechnic Institute SUBMISSION GUIDELINES: Submissions must be in electronic form, as Postscript or PDF documents. Papers can be up to 6 two-column pages, and can convey work-in-progress that is not completely mature but shows promise. For more information, please see: http://www.cerias.purdue.edu/npsec/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 8 09:56:04 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21207 for ; Fri, 8 Apr 2005 09:56:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJu6f-0007Hm-GE for manet-web-archive@ietf.org; Fri, 08 Apr 2005 10:05:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJtq0-0000ub-Ri; Fri, 08 Apr 2005 09:47:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJtpx-0000uT-Jw for manet@megatron.ietf.org; Fri, 08 Apr 2005 09:47: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 JAA20531 for ; Fri, 8 Apr 2005 09:47:51 -0400 (EDT) Received: from mail80.messagelabs.com ([195.245.230.163]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DJtye-0006qT-Of for manet@ietf.org; Fri, 08 Apr 2005 09:56:57 -0400 X-VirusChecked: Checked X-Env-Sender: ronan.de_renesse@kcl.ac.uk X-Msg-Ref: server-2.tower-80.messagelabs.com!1112967809!14658128!1 X-StarScan-Version: 5.4.11; banners=-,-,- X-Originating-IP: [137.73.2.214] Received: (qmail 15228 invoked from network); 8 Apr 2005 13:43:29 -0000 Received: from outbound.kcl.ac.uk (137.73.2.214) by server-2.tower-80.messagelabs.com with SMTP; 8 Apr 2005 13:43:29 -0000 Received: from mailip ([137.73.2.225] helo=elder) by outbound.kcl.ac.uk outbound with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) id 1DJtlc-0003Oq-WB for manet@ietf.org; Fri, 08 Apr 2005 14:43:25 +0100 Received: from [137.73.11.140] (helo=ronanlaptop) by elder mail with esmtp id 1DJtlO-0003K0-5i for manet@ietf.org; Fri, 08 Apr 2005 14:43:11 +0100 From: "Ronan de RENESSE" To: Date: Fri, 8 Apr 2005 14:43:12 +0100 Message-ID: <000d01c53c40$e8c3d990$6664a8c0@ronanlaptop> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-KCLSpamScore: 2 X-KCLRealSpamScore: 0.2 X-KCLZStatus: 2 X-KCLSpamReport: HTML_70_80=0.1,HTML_MESSAGE=0.1 X-KCL-MailScanner: Found to be clean X-MailScanner-From: ronan.de_renesse@kcl.ac.uk X-Spam-Score: 0.7 (/) X-Scan-Signature: 22e211536bda974b2dcf811522dc525d Subject: [manet] MWCN 2005 CFP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0995477911==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: b612707e1a3f67df80ae89cdab1ba981 This is a multi-part message in MIME format. --===============0995477911== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C53C49.4A884190" This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C53C49.4A884190 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear Potential MWCN 2005 Contributor, Please accept our apologies if you receive multiple copies of this announcement. We would like to draw your attention to the 7th IFIP International Conference on Mobile and Wireless Communications Networks (MWCN 2005) Marrakech, Morocco September 19-21, 2005 MWCN 2005 is the seventh annual international conference dedicated to advancing research on mobile and wireless communications networks. MWCN 2005 is aimed at stimulating technical exchange between researchers, providing a platform for presentation and discussion of recent research results and innovations. The scope of MWCN 2005 covers a wide range of technical areas, in view of the growing worldwide interests in wireless Internet access and evolution to Beyond 3G mobile communications systems. Any areas of quality pioneering research, of relevance to the fields mobile and wireless communications, will be considered for publication in this prestigious conference. MWCN 2005 will be held at the five-star Sheraton Hotel in the centre of Marrakech, Morocco. Enchantingly sited at the foot of the High Atlas Mountains, Marrakech is a fantastic medieval city in which the charmed echoes of the past, although unspoilt, are intertwined with modern street life and tourist vibrance. We are sure that Marrakech is a wonderful location in which to host a conference of this calibre. We would like to invite you to participate in MWCN 2005 through submission of your recent research findings. Instructions on the submission process, and further information about the conference, can be found at http://www.ctr.kcl.ac.uk/mwcn2005. We would also be very grateful if you could forward this message to any colleagues or interested potential contributors to MWCN 2005 that you might know of. Thank you for your support in making MWCN2005 a successful event! With highest regards, The Organising Committee Seventh IFIP International Conference on Mobile and Wireless Communications Networks ------=_NextPart_000_000E_01C53C49.4A884190 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear= Potential MWCN 2005 Contributor,

 

Plea= se accept our apologies if you receive multiple copies of this = announcement.

 

We would like to draw your attention to the

 

7th IFIP International Conference = on

Mobile and Wireless Communications = Networks (MWCN 2005)

 =

Marrakech, = Morocco

September 19–21, 2005

 

 

MWCN= 2005 is the seventh annual international conference dedicated to = advancing research on mobile and wireless communications networks. MWCN 2005 is = aimed at stimulating technical exchange between researchers, providing a platform = for presentation and discussion of recent research results and innovations. = The scope of MWCN 2005 covers a wide range of technical areas, in view of = the growing worldwide interests in wireless Internet access and evolution to = Beyond 3G mobile communications systems. Any areas of quality pioneering = research, of relevance to the fields mobile and wireless communications, will be considered for publication in this prestigious conference.

 

MWCN= 2005 will be held at the five-star Sheraton Hotel in the centre of = Marrakech, Morocco. Enchantingly sited at the foot of the High = Atlas Mountains, Marrakech is a fantastic medieval city in which the charmed = echoes of the past, although unspoilt, are intertwined with modern street life and tourist vibrance. We are sure that Marrakech = is a wonderful location in which to host a conference of this = calibre.

 

We would like to invite you to participate in MWCN 2005 through submission = of your recent research findings. Instructions on the submission process, and = further information about the conference, can be found at http://www.ctr.kcl.ac.uk/mwcn2= 005. We would also be very grateful if you could forward this message to any colleagues or interested potential contributors to MWCN 2005 that you = might know of.

 

Than= k you for your support in making MWCN2005 a successful = event!

 

With= highest regards,

 

The Organising Committee

Seve= nth IFIP International Conference on = Mobile and Wireless Communications = Networks

 

 

------=_NextPart_000_000E_01C53C49.4A884190-- --===============0995477911== 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 --===============0995477911==-- From manet-bounces@ietf.org Sun Apr 10 02:09:32 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13995 for ; Sun, 10 Apr 2005 02:09:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKVmc-0003ks-J0 for manet-web-archive@ietf.org; Sun, 10 Apr 2005 02:18:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKVZk-0007QE-2v; Sun, 10 Apr 2005 02:05:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKVZe-0007Pk-V1 for manet@megatron.ietf.org; Sun, 10 Apr 2005 02:05: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 CAA10221 for ; Sun, 10 Apr 2005 02:05:28 -0400 (EDT) Received: from pri-dns.cs.iitm.ernet.in ([202.141.25.89] helo=pridns.cs.iitm.ernet.in) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKVif-0003Vp-Bd for manet@ietf.org; Sun, 10 Apr 2005 02:14:55 -0400 Received: from mail-hpcn.cs.iitm.ernet.in (mail-hpcn.cs.iitm.ernet.in [10.6.6.1]) by pridns.cs.iitm.ernet.in (8.12.10/8.12.10) with ESMTP id j3A6Avxe018373 for ; Sun, 10 Apr 2005 11:40:57 +0530 Received: from mail-hpcn.cs.iitm.ernet.in (localhost [127.0.0.1]) by mail-hpcn.cs.iitm.ernet.in (8.12.11/8.12.11) with ESMTP id j3A6Jidp023213 for ; Sun, 10 Apr 2005 11:49:44 +0530 Received: from localhost (vramana@localhost) by mail-hpcn.cs.iitm.ernet.in (8.12.11/8.12.11/Submit) with ESMTP id j3A6JheD023210 for ; Sun, 10 Apr 2005 11:49:43 +0530 X-Authentication-Warning: mail-hpcn.cs.iitm.ernet.in: vramana owned process doing -bs Date: Sun, 10 Apr 2005 11:49:43 +0530 (IST) From: "B. Venkata Ramana" To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [manet] TCP westwood 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 Dear Manet group members, Currently I am working on the performance of the TCP and its variants in the Ad hoc wireless networks. For this purpose, i require the TCP-new reno, TCP-westwood and TCP-Vegas. Can you please tell me (or give me) where can i get these source codes implemented over the GlomoSim simulator. Thanks and Regards Venkata Ramana Indian Institute of Technology Chennai _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Apr 10 02:19:13 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23400 for ; Sun, 10 Apr 2005 02:19:13 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKVw0-0004AS-8e for manet-web-archive@ietf.org; Sun, 10 Apr 2005 02:28:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKVl9-0001UT-Gc; Sun, 10 Apr 2005 02:17:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKVl3-0001Rb-NY for manet@megatron.ietf.org; Sun, 10 Apr 2005 02: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 CAA21551 for ; Sun, 10 Apr 2005 02:17:20 -0400 (EDT) Received: from web80901.mail.scd.yahoo.com ([66.218.95.64]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DKVuA-000439-Nc for manet@ietf.org; Sun, 10 Apr 2005 02:26:47 -0400 Received: (qmail 35438 invoked by uid 60001); 10 Apr 2005 06:17:11 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=FIIDAvEdfcdzQht5AIIEW/hA4o9HW06IJszyO+FbE7P8qsa/3vKCmmNQF8SWSag1tvOsNnGgdhwbCAEjmo0BdGrHKb2TMgpYk+evn5gOtk/4JcgylAOTt6ImAOtT3Yx9Fla5X4JjEKCdNlsNNbqDxNVJ2TX+wbQePkMZPjsmdsE= ; Message-ID: <20050410061711.35436.qmail@web80901.mail.scd.yahoo.com> Received: from [203.208.193.197] by web80901.mail.scd.yahoo.com via HTTP; Sat, 09 Apr 2005 23:17:11 PDT Date: Sat, 9 Apr 2005 23:17:11 -0700 (PDT) From: Gokina P C To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [manet] Research in service discovery 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="===============1110579449==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 --===============1110579449== Content-Type: multipart/alternative; boundary="0-1564228839-1113113831=:34687" --0-1564228839-1113113831=:34687 Content-Type: text/plain; charset=us-ascii Hi, Presently I am doing research in Resource Discovery, Service Discovery and information distribution and retrieval and closely related areas in Pervasive Computing Environments. I want to know if any body in this group is doing research in a related area in Mobile Ad-hoc Networks. Please let me know if there is any possibility in which we can work on a research problem. Thanking you, GP. --------------------------------- Do you Yahoo!? Make Yahoo! your home page --0-1564228839-1113113831=:34687 Content-Type: text/html; charset=us-ascii
Hi,
 Presently I am doing research in Resource Discovery, Service Discovery and information distribution and retrieval and closely related areas in Pervasive Computing Environments. I want to know if any body in this group is doing research in a related area in Mobile Ad-hoc Networks.
 
 Please let me know if there is any possibility in which we can work on a research problem.
 
Thanking you,
GP.

Do you Yahoo!?
Make Yahoo! your home page --0-1564228839-1113113831=:34687-- --===============1110579449== 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 --===============1110579449==-- From qcksqc@yahoo.com Sun Apr 10 19:14:53 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01725; Sun, 10 Apr 2005 19:14:53 -0400 (EDT) Received: from cpe0008c777bbac-cm0012c99ebc84.cpe.net.cable.rogers.com ([24.43.118.177]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DKlb4-0000SH-FM; Sun, 10 Apr 2005 19:12:12 -0400 Received: from [158.172.56.235] (helo=..dearriba.com) by smtp2.cistron.nl with esmtp ( 3.35 #1 ()) id 293LFL-0041PT-23 Message-ID: <70848623144732.R37484@.noc..gr> Sender: freeradius-devel-qcksqc@yahoo.com X-Mailman-Version: 2.0.1 Date: Sun, 10 Apr 2005 22:06:13 -0200 From: "Frederic Vasquez" To: manet@ietf.org Cc: manet-admin@ietf.org, manet-archive@ietf.org, manet-request@ietf.org, manet-web-archive@ietf.org Subject: You Need This Manet X-Spam-Score: 6.1 (++++++) X-Spam-Flag: YES X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Look at this of-fers: V-codin - 225.00 (90 pi lls) Valliuum - 153.00 (90 pi lls) Vi graa - 270.00 (90 pi lls) Cai llis - 348.00 (90 pi lls) Codeinne - 126.00 (90 pi lls) X|a naax - 171.00 (90 pi lls) All orderrs are delivered by Fedex with full tracking 24/7. Satisfactiionnss guaaranteeed... http://www.ltxmeds.com to get rid of maiiling list: http://www.ltxmeds.com/aldfhsdlfh.asp From manet-bounces@ietf.org Mon Apr 11 05:25:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25141 for ; Mon, 11 Apr 2005 05:25:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKvK9-0001oh-Nb for manet-web-archive@ietf.org; Mon, 11 Apr 2005 05: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 1DKums-0000Q9-4i; Mon, 11 Apr 2005 05:00:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKump-0000Pu-1x for manet@megatron.ietf.org; Mon, 11 Apr 2005 05:00: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 FAA23631 for ; Mon, 11 Apr 2005 05:00:39 -0400 (EDT) Received: from smtp.ee.ethz.ch ([129.132.2.219] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKuw0-0001H0-N4 for manet@ietf.org; Mon, 11 Apr 2005 05:10:22 -0400 Received: from localhost (tranquillity.ee.ethz.ch [129.132.2.222]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 478E2D9332; Mon, 11 Apr 2005 11:00:37 +0200 (MEST) Received: from smtp.ee.ethz.ch ([129.132.2.217]) by localhost (tranquillity [129.132.2.222]) (amavisd-new, port 10024) with LMTP id 02854-02-7; Mon, 11 Apr 2005 11:00:37 +0200 (MEST) Received: from [82.130.103.191] (nb-4152.ethz.ch [82.130.103.191]) by smtp.ee.ethz.ch (Postfix) with ESMTP id F2F5CD9322; Mon, 11 Apr 2005 11:00:36 +0200 (MEST) Message-ID: <425A3CB4.3060606@tik.ee.ethz.ch> Date: Mon, 11 Apr 2005 11:00:36 +0200 From: Vincent Lenders User-Agent: Debian Thunderbird 1.0.2 (X11/20050331) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gokina P C Subject: Re: [manet] Research in service discovery in MANET References: <20050410061711.35436.qmail@web80901.mail.scd.yahoo.com> In-Reply-To: <20050410061711.35436.qmail@web80901.mail.scd.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at ee.ethz.ch X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, Vincent Lenders 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 Content-Transfer-Encoding: 7bit Hi Gokina P C We are doing research in service discovery for mobile ad hoc networks at the Swiss Federal Institute of Technology (ETH). Here is a paper that will be presented at WoWMoM 2005: Vincent Lenders, Martin May and Bernhard Plattner: Service Discovery in Mobile Ad Hoc Networks: A Field Theoretic Approach. http://www.tik.ee.ethz.ch/~lenders/publication/lenders_wowmom05.pdf Vincent Lenders wrote: > Hi, > Presently I am doing research in Resource Discovery, Service > Discovery and information distribution and retrieval and closely > related areas in Pervasive Computing Environments. I want to know if > any body in this group is doing research in a related area in Mobile > Ad-hoc Networks. > > Please let me know if there is any possibility in which we can > work on a research problem. > > Thanking you, > GP. > > ------------------------------------------------------------------------ > Do you Yahoo!? > Make Yahoo! your home page > > >------------------------------------------------------------------------ > >_______________________________________________ >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 Apr 11 10:42:43 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18630 for ; Mon, 11 Apr 2005 10:42:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DL0H6-0001S8-3W for manet-web-archive@ietf.org; Mon, 11 Apr 2005 10:52:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKztI-0003A0-4g; Mon, 11 Apr 2005 10:27:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKztG-00039J-Un for manet@megatron.ietf.org; Mon, 11 Apr 2005 10:27: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 KAA17425 for ; Mon, 11 Apr 2005 10:27:39 -0400 (EDT) Received: from ppsw-2.csi.cam.ac.uk ([131.111.8.132]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DL02V-000178-CU for manet@ietf.org; Mon, 11 Apr 2005 10:37:25 -0400 Received: from c84.al.cl.cam.ac.uk ([128.232.110.134]:33231) by ppsw-2.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.152]:25) with esmtpsa (PLAIN:ap458) (TLSv1:RC4-MD5:128) id 1DKzsV-00060N-7N (Exim 4.44) for manet@ietf.org (return-path ); Mon, 11 Apr 2005 15:27:03 +0100 From: Andrea Passarella Date: Mon, 11 Apr 2005 15:27:01 +0100 User-Agent: KMail/1.7.1 To: manet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504111527.01128.andrea.passarella@cl.cam.ac.uk> X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned X-Spam-Score: 0.0 (/) X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07 Content-Transfer-Encoding: 7bit Subject: [manet] CFP ISPA05 Deadline extended to April 20 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: df9edf1223802dd4cf213867a3af6121 Content-Transfer-Encoding: 7bit (Our apologies for possible duplicates of this message) ------------------------------------------------------ Third International Symposium on Parallel and Distributed Processing and Applications (ISPA'2005) http://keysoftlab.nju.edu.cn/ispa2005/ Nanjing ,China , 2-5 Nov. 2005 Organized by: State Key Laboratory of Novel Software Technology (Nanjing University) Following the traditions of previous successful ISPA confer-ences, ISPA '03 (held in Aizu-Wakamatsu City, Japan) and ISPA '04 (held in Hong Kong), the objective of ISPA '05 is to provide a forum for scientists and engineers in academia and in-dustry to exchange and discuss their experiences, new ideas, re-search results, and applications about all aspects of parallel and distributed computing and networking. ISPA '05 will feature ses-sion presentations, workshops, tutorials and keynote speeches. Topics of particular interest include, but are not limited to: Computer networks Network routing and communication algorithms Parallel/distributed system architectures Tools and environments for software development Parallel/distributed algorithms Parallel compilers Parallel programming languages Distributed systems Wireless networks, mobile and pervasive computing Reliability, fault-tolerance, and security Performance evaluation and measurements High-performance scientific and engineering computing Internet computing and Web technologies Database applications and data mining Grid and cluster computing Parallel/distributed applications High performance bioinformatics Submission Procedure Submissions should include an abstract, key words, the e-mail address of the corresponding author, and must not exceed 15 pages, including tables and figures, with PDF, PostScript, or MS Word format. Electronic submission through the submission website is strongly encouraged. Hard copies will be accepted only if electronic submission is not possible. Submission of a paper should be regarded as an undertaking that, should the pa-per be accepted, at least one of the authors will register and at-tend the conference to present the work. Important Dates: Workshop proposals due: April 1, 2005 Paper submission due: April 20, 2005 Acceptance notification: July 1, 2005 Camera-ready due: July 30, 2005 Conference: November 2-5, 2005 Publication: The proceedings of the symposium will be published in Springer's Lecture Notes in Computer Science. A selection of the best papers for the conference will be published in a special is-sue of The Journal of Supercomputing and International Journal of High Performance Computing and Networking (IJHPCN). Location: ISPA'05 will be held at the Nanjing University, one of the most famous universities in China, It has a history of about 103 years. The Nanjing Univerity is located in the Nanjing City, the Capital of Jiangsu Province in China. Present-day Nanjing, with tens of universities and hundreds of high-tech companies, ranks fifth among the "50 strongest" of Chinese cities. It is a transport and telecommunication hub in East China, and the second largest in-ternational trade port after Shanghai in the Yangzi River Delta. Like a bright pearl inlayed in the Yangtze River, Nanjing, the capital of Jiangsu province, an important political and economi-cal center, boasts of its ancient culture, unique topography and picturesque landscape. Known as Metropolis of 10 Dynasties, it has a long history of over 2000 years. With the Purple Mountain to the east (likened to a coiling dragon) and Stone Citadel to the west (likened to a crouching tiger), the city assumes a strategic importance. A perfect combination of culture and natural land-scape, Nanjing attracts millions of Chinese and overseas tourists each year with more than 50 famous places of interest. Bestowed with numerous well-known historical sites, like Dr. Sun Yat-sen's Mausoleum, Confucius Temple, the Citadels of Zhonghua Gate, the Ming Tomb, Linggu Temple, Qixia Temple, Rain-flower Terrace, it also presents the beautiful scenery of the Qinhuai River, Qixia Mountain, Purple Mountain, Xuanwu Lake and Mochou(Worry-not) Lake. The advanced transportation en-ables people to travel conveniently to major Chinese cities. General Co-Chairs: Jack Dongarra, University of Tennessee, USA Jiannong Cao, Hong Kong Polytechnic University, China Jian Lu, Nanjing University, China Program Co-Chair: Yi Pan Department Chair and Professor Georgia State University, USA http://www.cs.gsu.edu/pan Daoxu Chen Department Chair and Professor Nanjing University, China http://cs.nju.edu.cn/cs2/shizi/szchendx.html Vice Program Co-Chairs: Algorithms Ivan Stojmenovic, University of Ottawa, Canada Architecture and Networks Mohamed Ould-Khaoua, University of Glasgow, UK Middleware and Grid Computing Mark Baker, University of Portsmouth, UK Software Jingling Xue, University of New South Wales, Australia Applications Zhi-Hua Zhou, Nanjing University, China Steering Committee Co-Chairs: Sartaj Sahni, University of Florida, USA Yaoxue Zhang, Ministry of Education, China Minyi Guo, University of Aizu, Japan Steering Committee: Jiannong Cao, Hong Kong Polytechnic University, China Francis Lau, University of Hong Kong, China Yi Pan, Georgia State University, USA Li Xie, Nanjing University, China Jie Wu, Florida Altantic University, USA Laurence T. Yang, St. Francis Xavier University, Canada Hans P. Zima, California Institute of Technology, USA Weiming Zheng, Tsinghua University, China Orgainizing Chairs: Xianglin Fei, Nanjing University, China Baowen Xu, Southeast University, China Ling Chen, Yangzhou University, China Workshop Chair: Guihai Chen, Nanjing University, China Tutorial Chair: Yuzhong Sun, Institute of Computing Technology, CAS, China Publicity Chair: Cho-Li Wang, Univ. of Hong Kong, China Publication Chair: Hui Wang, University of Aizu, Japan Registration Chair: Xianglin Fei, Nanjing University, China IEEE Technical Committee on Scalable Computing http://www.ieeetcsc.org IEEE Technical Committee on Scalable Computing http://www.ieeetcsc.org IEEE Technical Committee on Scalable Computing http://www.ieeetcsc.org If you wish to unsubscribe from this mailing list, send a blank message to discuss-unsubscribe@ieeetcsc.org. ------------------------------------------------------- -- Andrea Passarella ISPA 05 TPC member ========================================================= University of Cambridge The Computer Laboratory || voice:+44 (0)1223 763658 15 JJ Thomson Avenue || fax: +44 (0)1223 334678 Cambridge CB3 0FD, UK || web: www.cl.cam.ac.uk/~ap458/ email: andrea.passarella@cl.cam.ac.uk ========================================================= Pervasive Computing & Networking Lab. (PerLab) University of Pisa, Dept. of Information Engineering _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 01:20:33 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04572 for ; Tue, 12 Apr 2005 01:20:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLDyh-0004NG-GP for manet-web-archive@ietf.org; Tue, 12 Apr 2005 01:30:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLDjj-0005y0-QH; Tue, 12 Apr 2005 01:14:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLDjg-0005xM-Tg for manet@megatron.ietf.org; Tue, 12 Apr 2005 01:14: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 BAA04301 for ; Tue, 12 Apr 2005 01:14:43 -0400 (EDT) Received: from beru.its.uow.edu.au ([130.130.68.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLDt3-0004F8-QZ for manet@ietf.org; Tue, 12 Apr 2005 01:24:35 -0400 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by beru.its.uow.edu.au with esmtp (Exim 4.43) id 1DLDjL-00014P-2B for manet@ietf.org; Tue, 12 Apr 2005 15:14:31 +1000 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AZC27099; Tue, 12 Apr 2005 15:14:29 +1000 (EST) Received: from 130.130.66.78 by mirapoint.uow.edu.au (MOS 3.5.6-GR) with HTTP/1.1; Tue, 12 Apr 2005 15:14:29 +1000 Date: Tue, 12 Apr 2005 15:14:29 +1000 From: Cindy To: manet@ietf.org X-Mailer: Mirapoint Webmail Direct 3.5.6-GR MIME-Version: 1.0 Message-Id: <5defad90.ebaed8ab.81bc100@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Subject: [manet] Help me with AODV destination sequence number 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: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7bit Hi, i've been thinking about the effect of destination sequence number in AODV routing protocol, and wanna make something more clear about it. according to the RFC 3651 page 17, when an forwarding node received a RREQ, but does not generate a RREP (does not have an active route towards the destination, or the "destination only" flag is set, the forwarding node will update the destination sequence number in RREQ by "set to the maximum of the corresponding value received in the RREQ message, and the destination sequence value currently maintained by the node for the requested destination". so, does this mean the destination sequence number in RREQ might be changed during the transmission? but what the effect of updating the destination sequence number during the transmission of RREQ, since all the forwarding node will no update their route table entry regarding to that destination untill the RREP is sent back? I'll really appreciate quick answers. Thanks a lot! Cindy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 04:39:32 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09029 for ; Tue, 12 Apr 2005 04:39:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLH5K-0001A1-RZ for manet-web-archive@ietf.org; Tue, 12 Apr 2005 04:49:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLGsa-0007ju-El; Tue, 12 Apr 2005 04:36:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLGsY-0007he-ED for manet@megatron.ietf.org; Tue, 12 Apr 2005 04:36: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 EAA08809 for ; Tue, 12 Apr 2005 04:35:59 -0400 (EDT) Received: from beru.its.uow.edu.au ([130.130.68.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLH1s-00015Y-8Y for manet@ietf.org; Tue, 12 Apr 2005 04:45:53 -0400 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by beru.its.uow.edu.au with esmtp (Exim 4.43) id 1DLGsC-0006E6-SU for manet@ietf.org; Tue, 12 Apr 2005 18:35:52 +1000 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AZC56006; Tue, 12 Apr 2005 18:35:51 +1000 (EST) Received: from 130.130.66.78 by mirapoint.uow.edu.au (MOS 3.5.6-GR) with HTTP/1.1; Tue, 12 Apr 2005 18:35:51 +1000 Date: Tue, 12 Apr 2005 18:35:51 +1000 From: Cindy Subject: Re: [manet] Help me with AODV destination sequence number To: manet@ietf.org X-Mailer: Mirapoint Webmail Direct 3.5.6-GR MIME-Version: 1.0 Message-Id: <2e0b9e5a.ebc147fa.81bc100@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad 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.9 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hi Jackson, Thanks for your reply! In the RFC, same place, it also says "the forwarding node MUST NOT modify its maintained value for the destination sequence number, even if the value received in the incoming RREQ is larger than the value currently maintained by the forwarding node". so the part setting to maximum should be targeting the RREQ, am i right? Cheers Cindy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 05:01:51 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10867 for ; Tue, 12 Apr 2005 05:01:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLHQw-0001q8-C6 for manet-web-archive@ietf.org; Tue, 12 Apr 2005 05:11:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLH9i-0003K9-GP; Tue, 12 Apr 2005 04:53:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLH9X-0003EK-Tb for manet@megatron.ietf.org; Tue, 12 Apr 2005 04: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 EAA10184 for ; Tue, 12 Apr 2005 04:53:37 -0400 (EDT) Received: from mailgate.cc.niigata-u.ac.jp ([133.35.14.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLHIw-0001b4-OZ for manet@ietf.org; Tue, 12 Apr 2005 05:03:32 -0400 Received: from ms01.net.ie.niigata-u.ac.jp (mailgate.cc.niigata-u.ac.jp [127.0.0.1]) by mailgate.cc.niigata-u.ac.jp (8.11.6/8.11.6) with ESMTP id j3C8rQK26728 for ; Tue, 12 Apr 2005 17:53:26 +0900 Received: from localhost (ms01 [127.0.0.1]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with ESMTP id 211BC11DE6 for ; Tue, 12 Apr 2005 17:53:11 +0900 (JST) Received: from ms01.net.ie.niigata-u.ac.jp ([127.0.0.1]) by localhost (ms01.net.ie.niigata-u.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20991-05 for ; Tue, 12 Apr 2005 17:53:02 +0900 (JST) Received: from localhost (ms02.net.ie.niigata-u.ac.jp [133.35.156.2]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with SMTP id 712A311DDC for ; Tue, 12 Apr 2005 17:53:02 +0900 (JST) Date: Tue, 12 Apr 2005 17:58:49 +0900 From: wjf To: manet@ietf.org Message-Id: <20050412175849.5981da61.wjf@net.ie.niigata-u.ac.jp> X-Mailer: Sylpheed version 1.0.0beta1 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at net.ie.niigata-u.ac.jp X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit Subject: [manet] care about the perspective of fragmentation 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, all. it is obvious that the fragmentation is very useful to increase the transmission reliability against the channel noise, fading. but whether this way can improve the throughput of WLAN and raise the efficiency of bandwidth is still vague. i simulated the conventional fragmentation algorithm by using HR/DSSS, and found there is not any merit to use this way. even, the fragmentation can result in the performance degradation(maybe, my simulation model is too common to discover the value of fragmentation). i think the redundant overhead (like the SIFS, ACK & PLCP preamble..) is the primary reason on performance deterioration, especially under the high rate environment. and today, like the frame aggregation technology, to decrease the needless overhead, it permits to concatenate some smaller frames headed for the same next hop into a big frame at mac layer. however, the fragmentation runs in the opposite direction(maybe, the reason is only available 1M or 2M bandwidth in the past). i think the coming 802.11n will provide more high rate sets and more technologies for users. So, is the fragmentation promising yet? thank for any help. WANG JF _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 05:05:00 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10982 for ; Tue, 12 Apr 2005 05:05:00 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLHTu-0001wB-S0 for manet-web-archive@ietf.org; Tue, 12 Apr 2005 05:14:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLHB8-0003UJ-EL; Tue, 12 Apr 2005 04:55:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLHB5-0003T7-Pm for manet@megatron.ietf.org; Tue, 12 Apr 2005 04:55: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 EAA10285 for ; Tue, 12 Apr 2005 04:55:13 -0400 (EDT) Received: from smtp11.clb.oleane.net ([213.56.31.48]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLHKV-0001f4-RI for manet@ietf.org; Tue, 12 Apr 2005 05:05:08 -0400 Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be forged)) (authenticated) by smtp11.clb.oleane.net with ESMTP id j3C8t4iM016313 for ; Tue, 12 Apr 2005 10:55:05 +0200 Message-Id: <200504120855.j3C8t4iM016313@smtp11.clb.oleane.net> From: "Chantal Ladouce" To: Date: Tue, 12 Apr 2005 10:54:58 +0200 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcU/PU3boXNLdUwKRuuUjBdslgQZCQ== X-Spam-Score: 0.1 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Subject: [manet] WiFi Voice conference - Paris - France 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="===============0900961850==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 This is a multi-part message in MIME format. --===============0900961850== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0189_01C53F4E.11FF4C30" This is a multi-part message in MIME format. ------=_NextPart_000_0189_01C53F4E.11FF4C30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Only four weeks left before the starting of the second edition of the WiFi Voice conference to be held in Paris next 9-10 May. Experts and service providers will address all the technical issues related to VoWLAN. Registration is still open. Please get all details at: http://www.upperside.fr/wifi05/wifivoice2005intro.htm ------=_NextPart_000_0189_01C53F4E.11FF4C30 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Only four weeks left before the starting of = the second edition of the WiFi Voice conference to be held in = Paris next = 9-10 May.

Experts and service providers will address all = the technical issues related to VoWLAN.

Registration is still open.

Please get all details at:

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

 

------=_NextPart_000_0189_01C53F4E.11FF4C30-- --===============0900961850== 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 --===============0900961850==-- From manet-bounces@ietf.org Tue Apr 12 06:26:41 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16162 for ; Tue, 12 Apr 2005 06:26:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLIl3-000441-1q for manet-web-archive@ietf.org; Tue, 12 Apr 2005 06:36:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLIOz-0007Fy-Jj; Tue, 12 Apr 2005 06:13:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLIOy-0007FP-Am for manet@megatron.ietf.org; Tue, 12 Apr 2005 06:13: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 GAA15269 for ; Tue, 12 Apr 2005 06:13:29 -0400 (EDT) Received: from beru.its.uow.edu.au ([130.130.68.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLIYG-0003i0-10 for manet@ietf.org; Tue, 12 Apr 2005 06:23:25 -0400 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by beru.its.uow.edu.au with esmtp (Exim 4.43) id 1DLIOY-00008N-3l for manet@ietf.org; Tue, 12 Apr 2005 20:13:22 +1000 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AZE01311; Tue, 12 Apr 2005 20:13:20 +1000 (EST) Received: from 130.130.66.78 by mirapoint.uow.edu.au (MOS 3.5.6-GR) with HTTP/1.1; Tue, 12 Apr 2005 20:13:20 +1000 Date: Tue, 12 Apr 2005 20:13:20 +1000 From: Cindy Subject: Re: [manet] Help me with AODV destination sequence number To: manet@ietf.org X-Mailer: Mirapoint Webmail Direct 3.5.6-GR MIME-Version: 1.0 Message-Id: <8aab3950.ebca34b7.81d4000@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a 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.9 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 7bit Hi Jackson, I'm not quite sure about that. To my knowledege, the value of destination sequence number (DSN) has no effect on the generation of RREP. It is supposed to be used by forwarding nodes (forwarding RREP) to update their route table, i.e. if the value of DSN is greater than the maintained one, the route is recognized as fresh and the node will update its route table entry. When an intermediate node wants to generate RREP, it simpley drops the RREQ, and copies the DSN maintained into RREP. Beside, go back to the previous question. If a node maintains the DSN in its route table, this means it should have an active route toward that destination. So why doesn't it generate RREP itself? So, what i can reason about these above is: either the forwarding has a route but set as "invalid", or it only works for the siatuation that only the destination node can generate RREP. Expecting your correction! Cheers! Cindy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 08:13:14 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23638 for ; Tue, 12 Apr 2005 08:13:14 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLKQ9-00074v-RK for manet-web-archive@ietf.org; Tue, 12 Apr 2005 08:23:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLK0B-00044X-EY; Tue, 12 Apr 2005 07:56:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLK09-0003ya-DG for manet@megatron.ietf.org; Tue, 12 Apr 2005 07:56:17 -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 HAA21983 for ; Tue, 12 Apr 2005 07:56:07 -0400 (EDT) Received: from x86unx3.comp.nus.edu.sg ([137.132.80.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLK9Z-0006Ua-Mm for manet@ietf.org; Tue, 12 Apr 2005 08:06:03 -0400 Received: from e500d.comp.nus.edu.sg (e500d.comp.nus.edu.sg [137.132.90.69]) by x86unx3.comp.nus.edu.sg (8.9.1-20030924/8.9.1) with SMTP id TAA05707; Tue, 12 Apr 2005 19:55:53 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500d.comp.nus.edu.sg via csmap id 9c198bf6_ab4b_11d9_8ebb_0030482985c3_29907; Tue, 12 Apr 2005 20:08:41 +0800 (SGT) Received: from localhost (ohhangsi@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id TAA12546; Tue, 12 Apr 2005 19:55:52 +0800 (GMT-8) Date: Tue, 12 Apr 2005 19:55:52 +0800 (GMT-8) From: Jackson Oh To: Cindy Subject: Re: [manet] Help me with AODV destination sequence number In-Reply-To: <8aab3950.ebca34b7.81d4000@mirapoint.uow.edu.au> Message-ID: References: <8aab3950.ebca34b7.81d4000@mirapoint.uow.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 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 Hi Cindy, If the intermediate node has a valid and higher DSN value, and assuming that intermediate nodes are allowed to generate RREPs, i don't see why any won't be generated. My guess to your question would be that intermediate nodes are not allowed to generate RREPs. Cheers, Jackson On Tue, 12 Apr 2005, Cindy wrote: > Hi Jackson, > > I'm not quite sure about that. > > To my knowledege, the value of destination sequence number > (DSN) has no effect on the generation of RREP. It is > supposed to be used by forwarding nodes (forwarding RREP) to > update their route table, i.e. if the value of DSN is > greater than the maintained one, the route is recognized as > fresh and the node will update its route table entry. When > an intermediate node wants to generate RREP, it simpley > drops the RREQ, and copies the DSN maintained into RREP. > > Beside, go back to the previous question. If a node > maintains the DSN in its route table, this means it should > have an active route toward that destination. So why doesn't > it generate RREP itself? > > So, what i can reason about these above is: either the > forwarding has a route but set as "invalid", or it only > works for the siatuation that only the destination node can > generate RREP. > > Expecting your correction! > > Cheers! > Cindy > > _______________________________________________ > 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 Apr 12 08:30:33 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24811 for ; Tue, 12 Apr 2005 08:30:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLKgv-0007X3-Lj for manet-web-archive@ietf.org; Tue, 12 Apr 2005 08:40:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLKO8-0007AQ-LC; Tue, 12 Apr 2005 08:21:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLKO6-00072A-Jp for manet@megatron.ietf.org; Tue, 12 Apr 2005 08:21: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 IAA24070 for ; Tue, 12 Apr 2005 08:20:43 -0400 (EDT) Received: from evaki.its.uow.edu.au ([130.130.68.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLKXO-0007Hn-0R for manet@ietf.org; Tue, 12 Apr 2005 08:30:39 -0400 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by evaki.its.uow.edu.au with esmtp (Exim 4.43) id 1DLKNk-0006f4-1l; Tue, 12 Apr 2005 22:20:40 +1000 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AZE12774; Tue, 12 Apr 2005 22:20:39 +1000 (EST) Received: from 130.130.66.78 by mirapoint.uow.edu.au (MOS 3.5.6-GR) with HTTP/1.1; Tue, 12 Apr 2005 22:20:39 +1000 Date: Tue, 12 Apr 2005 22:20:39 +1000 From: Cindy Subject: Re: [manet] Help me with AODV destination sequence number To: Jackson Oh X-Mailer: Mirapoint Webmail Direct 3.5.6-GR MIME-Version: 1.0 Message-Id: <51f2571d.ebd5dc6c.81bc300@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) 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.9 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hi Jackson, I agree. At this stage, can we draw the conclusion that the DNS number in RREQ might be changed during transmission? if so, it almost implies that their security adds-on: SAODV, is completely Wrong! because it assume thes DSN field will not be changed, and simply put a signature over it... well, that's where my unsureness comes from, cos i don't believe the internet draft of SAODV is wrong. Goodnight Cindy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 12:42:45 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13822 for ; Tue, 12 Apr 2005 12:42:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOd2-0006Ke-DF for manet-web-archive@ietf.org; Tue, 12 Apr 2005 12:52:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOMo-0002eu-Tt; Tue, 12 Apr 2005 12:35:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOMm-0002eK-LX for manet@megatron.ietf.org; Tue, 12 Apr 2005 12:35: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 MAA13009 for ; Tue, 12 Apr 2005 12:35:45 -0400 (EDT) Received: from ns.ustc.edu.cn ([202.38.64.1] helo=mx1.ustc.edu.cn) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOWE-000627-EW for manet@ietf.org; Tue, 12 Apr 2005 12:45:45 -0400 Received: from ustc.edu.cn (email.ustc.edu.cn [202.38.64.8]) by mx1.ustc.edu.cn (8.11.6/8.11.6) with SMTP id j3CGW7w18286 for ; Wed, 13 Apr 2005 00:32:07 +0800 Received: (eyou send program); Wed, 13 Apr 2005 00:30:11 +0800 Message-ID: <313323411.05920@ustc.edu.cn> Received: from 202.38.75.11 by email.ustc.edu.cn with HTTP; Wed, 13 Apr 2005 00:30:11 +0800 X-WebMAIL-MUA: [202.38.75.11] From: "Peng Hu" To: manet@ietf.org Date: Wed, 13 Apr 2005 00:30:11 +0800 X-Priority: 3 Content-Type: text/plain X-Spam-Score: 1.6 (+) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: Question@mail.ustc.edu.cn, debug@mail.ustc.edu.cn, about@mail.ustc.edu.cn, wireless@mail.ustc.edu.cn, routing@mail.ustc.edu.cn Subject: [manet] (no subject) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peng Hu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.6 (+) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 While simulating the wireless routing protocol, I am puzzled how to print the temporary info during the routing protocol is executed. As the related code goes: ... set val(rp) DSDV ... ... $ns node-config -adhocRouting $val(rp) \ -llType $val(ll) \ ... ... Stepped into the protocol implementation in NS-2.27/dsdv/dsdv.cc, I found there're lots of printfs for dump.I added one printf and made sure that it can be executed during the simulation. But I can not get any output info after I make the new ns. Does anybody know how to display the debug info in the routing protocol source file? or how can I watch the variable in every process function in dsdv.cc files? I ever read some document on NS website, and did not find the related question till now. So any advice is welcome! Thanks all. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 12:50:42 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14809 for ; Tue, 12 Apr 2005 12:50:41 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOkj-0006g4-HQ for manet-web-archive@ietf.org; Tue, 12 Apr 2005 13:00:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOY9-0004g3-A0; Tue, 12 Apr 2005 12:47:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOY6-0004fh-Go for manet@megatron.ietf.org; Tue, 12 Apr 2005 12:47: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 MAA14537 for ; Tue, 12 Apr 2005 12:47:35 -0400 (EDT) Received: from ns.ustc.edu.cn ([202.38.64.1] helo=mx1.ustc.edu.cn) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOhg-0006Wq-K5 for manet@ietf.org; Tue, 12 Apr 2005 12:57:35 -0400 Received: from ustc.edu.cn (email.ustc.edu.cn [202.38.64.8]) by mx1.ustc.edu.cn (8.11.6/8.11.6) with SMTP id j3CGitw23258 for ; Wed, 13 Apr 2005 00:44:55 +0800 Received: (eyou send program); Wed, 13 Apr 2005 00:42:59 +0800 Message-ID: <313324179.07034@ustc.edu.cn> Received: from 202.38.75.11 by email.ustc.edu.cn with HTTP; Wed, 13 Apr 2005 00:42:59 +0800 X-WebMAIL-MUA: [202.38.75.11] From: "Peng Hu" To: manet@ietf.org Date: Wed, 13 Apr 2005 00:42:59 +0800 X-Priority: 3 Content-Type: text/plain X-Spam-Score: 1.6 (+) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [manet] Question about wireless routing debug X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peng Hu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.6 (+) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Send it again, sorry for lack of the title and duplication letter. >From: "Peng Hu" >Reply-To: "Peng Hu" >To: manet@ietf.org >Subject: >Date:Wed, 13 Apr 2005 00:30:11 +0800 > >While simulating the wireless routing protocol, I am puzzled how > to print the temporary info during the routing protocol is executed. > > As the related code goes: > > ... > set val(rp) DSDV > ... > ... > $ns node-config -adhocRouting $val(rp) \ > -llType $val(ll) \ > ... > ... > > Stepped into the protocol implementation in NS-2.27/dsdv/dsdv.cc, > I found there're lots of printfs for dump.I added one printf and made > sure that it can be executed during the simulation. But I can > not get any output info after I make the new ns. > > Does anybody know how to display the debug info in the routing > protocol source file? or how can I watch the variable in every > process function in dsdv.cc files? > > I ever read some document on NS website, and did not find the > related question till now. So any advice is welcome! Thanks all. > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 12 23:03:54 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09318 for ; Tue, 12 Apr 2005 23:03:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLYKE-0000Lb-HX for manet-web-archive@ietf.org; Tue, 12 Apr 2005 23:13:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLY91-0001NZ-Hr; Tue, 12 Apr 2005 23:02:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLY8z-0001GG-2w for manet@megatron.ietf.org; Tue, 12 Apr 2005 23:02: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 XAA09251 for ; Tue, 12 Apr 2005 23:02:10 -0400 (EDT) Received: from beru.its.uow.edu.au ([130.130.68.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLYIX-0000JE-B8 for manet@ietf.org; Tue, 12 Apr 2005 23:12:14 -0400 Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220] helo=febris.its.uow.edu.au) by beru.its.uow.edu.au with esmtp (Exim 4.43) id 1DLY8h-0006nd-KR for manet@ietf.org; Wed, 13 Apr 2005 13:02:03 +1000 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.6-GR) with ESMTP id AZG28589; Wed, 13 Apr 2005 10:53:57 +1000 (EST) Received: from 130.130.66.78 by mirapoint.uow.edu.au (MOS 3.5.6-GR) with HTTP/1.1; Wed, 13 Apr 2005 10:53:57 +1000 Date: Wed, 13 Apr 2005 10:53:57 +1000 From: Cindy To: "MANET@ieft.org" X-Mailer: Mirapoint Webmail Direct 3.5.6-GR MIME-Version: 1.0 Message-Id: X-Spam-Score: 0.9 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [manet] the effect of destination sequence number 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="===============0798309680==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c --===============0798309680== Content-Type: multipart/alternative; boundary="-----69bb0e1e86605818d05316de3188ee8a" -------69bb0e1e86605818d05316de3188ee8a Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all, Following my previous question, can anybody who has a clear thoughs about destination sequence number(DSN) tell me, what is the effect of DSN during the RREQ transmission? 2 facts are: 1. the forwarding node will not modify its route table entry for the destination node during RREQ transmission. 2. the node generating RREP simply copies its known or its own destination sequence number into RREP field, which is obviously the freshest one. This means the RREQ will be accepted anyway if it is not a duplicate one. I am wondering can we ignore the DSN during RREQ transmission? Looking forward to any clarifications! Cheers, Cindy -------69bb0e1e86605818d05316de3188ee8a Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Hello all,

Following my previous question, can anybody who has a clear thoughs about destination sequence number(DSN) tell me, what is the effect of DSN during the RREQ transmission?

2 facts are:

1. the forwarding node will not modify its route table entry for the destination node during RREQ transmission.

2. the node generating RREP simply copies its known or its own destination sequence number into RREP field, which is obviously the freshest one.

This means the RREQ will be accepted anyway if it is not a duplicate one.  I am wondering can we ignore the DSN during RREQ transmission?

Looking forward to any clarifications!

Cheers,

Cindy

-------69bb0e1e86605818d05316de3188ee8a-- --===============0798309680== 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 --===============0798309680==-- From manet-bounces@ietf.org Wed Apr 13 04:58:43 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07023 for ; Wed, 13 Apr 2005 04:58:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLdre-0000IN-78 for manet-web-archive@ietf.org; Wed, 13 Apr 2005 05:08:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLdWt-0002EY-Cv; Wed, 13 Apr 2005 04:47:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLdWU-00029t-M4 for manet@megatron.ietf.org; Wed, 13 Apr 2005 04:46: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 EAA06245 for ; Wed, 13 Apr 2005 04:46:48 -0400 (EDT) Received: from netlx014.civ.utwente.nl ([130.89.1.88]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLdg5-0008QQ-Mk for manet@ietf.org; Wed, 13 Apr 2005 04:56:55 -0400 Received: from ewi483.ewi.utwente.nl (ewi483.ewi.utwente.nl [130.89.145.64]) by netlx014.civ.utwente.nl (8.11.7/HKD) with ESMTP id j3D8fmT23456 for ; Wed, 13 Apr 2005 10:41:48 +0200 From: Omer Sinan Kaya To: manet@ietf.org Date: Wed, 13 Apr 2005 10:41:29 +0200 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504131041.30076.o.s.kaya@ewi.utwente.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-MailScanner-From: o.s.kaya@ewi.utwente.nl X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: quoted-printable Subject: [manet] Ewsnsim Code Public Release 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 Content-Transfer-Encoding: quoted-printable Dear All, We have released our simulation framework and our new tool named NesCT in t= he=20 following address to public usage . http://wwwes.cs.utwente.nl/ewsnsim/ With the help of NesCT, we are able to run TinyOS applications under OMNeT+= +=20 with our simulation framework. The code is very much experimental at the moment. Nevertheless, we are able= to=20 get most of the applications working. =A0We would like to invite anyone=20 interested to experiment with our tools, hear about suggestions and receive= =20 contributions / feedbacks. We hope that we'll be able to attract wireless sensor networks researchers = to=20 OMNeT++ environment.=20 Best Regards, =2D-=20 Omer Sinan Kaya Phd Student Computer Science Department Distributed and Embedded Systems Group University of Twente campus Hallenweg 7522 NB Enschede The Netherlands _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 13 05:29:12 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08658 for ; Wed, 13 Apr 2005 05:29:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLeL7-0000x0-Uo for manet-web-archive@ietf.org; Wed, 13 Apr 2005 05:39:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLe54-00082o-S4; Wed, 13 Apr 2005 05:22:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLe3p-0007p6-1i for manet@megatron.ietf.org; Wed, 13 Apr 2005 05:21: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 FAA08222 for ; Wed, 13 Apr 2005 05:21:14 -0400 (EDT) Received: from ppsw-2.csi.cam.ac.uk ([131.111.8.132]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLeDR-0000nq-Sw for manet@ietf.org; Wed, 13 Apr 2005 05:31:22 -0400 Received: from c01.al.cl.cam.ac.uk ([128.232.110.47]:33276) by ppsw-2.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.152]:25) with esmtpsa (PLAIN:ap458) (TLSv1:RC4-MD5:128) id 1DLe3Q-000401-9A (Exim 4.44) for manet@ietf.org (return-path ); Wed, 13 Apr 2005 10:21:00 +0100 From: Andrea Passarella To: manet Date: Wed, 13 Apr 2005 10:20:51 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504131020.51861.andrea.passarella@cl.cam.ac.uk> X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned X-Spam-Score: 0.0 (/) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a Content-Transfer-Encoding: 7bit Subject: [manet] IEEE ICPS REALMAN Workshop: Multi-hop Ad hoc Networks: from theory to reality 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: 7bit [Our apologies for possible duplicates of this message] ----------------------------------------------------------- CALL FOR PAPERS IEEE ICPS Workshop on Multi-hop Ad hoc Networks: from theory to reality REALMAN 2005 http://www.cl.cam.ac.uk/realman jointly organized by: MobileMAN EC IST Project University of Cambridge, UK CNR-Institute for Informatics and Telematics, I in conjunction with ICPS 2005 http://icps2005.cs.ucr.edu/ July 14, 2005 Santorini, Greece After almost a decade of research into ad hoc networking, off-the-shelf MANET technology has not yet affected our way of using wireless networks. To consolidate the field, it is now the time to constructing and experiencing with realistic and complete MANET solutions. Prototypes and measurements on real test-beds provide insights in the ad hoc technology behavior and fundamental information for a realistic tuning of simulation models (mobility models, link-level models, etc.). This workshop constitutes a unique forum for presenting and discussing experiences based on real ad hoc networks test-beds and prototypes. Original contributions are solicited, related to systems and protocols development and testing, in all areas related to ad hoc networking. Topics of interest include, but are not limited to: * Ad hoc networks applications * System prototypes and experiences * Software technologies and systems * Mobile Ad Hoc Networks * Sensor Networks * Vehicular Networks * Mesh Networks * Routing and Transport protocols * Security and cooperation protocols * Middleware platforms for ad hoc networks * Ad Hoc Networking for ambient intelligence and pervasive environments * Situated and Autonomic Communications * Location services * Positioning and Tracking Technologies * Measurement studies * Mobility Models * Enabling Technologies Models (802.11, 802.15, etc.) * Experiment-based Social and/or Economic Analysis of Mobile Ad hoc Networks DEMO SESSION A demo session will be held during the workshop, showing ad hoc and sensor network prototypes at work. Demo proposals are highly welcome, and will be evaluated ty the Program Committee. Please submit one-page demo proposal to the program chair (realman@iit.cnr.it) before May 1, 2005. The proposal should briefly summarize the research framework of the proposed demo. Please also state clearly what equipments will be required to set up the experiments. As a general rule, demo proposers will be in charge for all the equipment material required for the experiments. Please contact the program chair for particular needs in this regard. PAPER SUBMISSION AND PUBLICATION Please submit your short paper via e-mail (PDF format is mandatory) to the program chair (realman@iit.cnr.it). We encourage the authors to format their papers according to the IEEE double-column standard format, except the font size, which must be Times Roman 11pt (or greater). Paper length must not exceed 8 pages, including figures, appendixes, bibliography, etc. Format templates and detailed instructions can be found at http://www.cl.cam.ac.uk/realman/authors.html ****************************************************************** High quality papers will be selected for possible publication on "Ad Hoc & Sensor Wireless Networks Journal (AHSWN)" http://www.oldcitypublishing.com/AHSWN/AHSWN.html ****************************************************************** IMPORTANT DATES Papers due: May 1, 2005 Notification: June 1, 2005 Camera Ready due: June 14, 2005 ORGANIZING COMMITTEE General Chair Jon Crowcroft University of Cambridge, UK jon.crowcroft@cl.cam.ac.uk Program Chair Marco Conti IIT-CNR, Italy marco.conti@iit.cnr.it Program Vice-Chair Andrea Passarella University of Cambridge, UK andrea.passarella@cl.cam.ac.uk Program Committee G. Anastasi, Pisa University, Italy A.T. Campbell, Columbia University, USA S.R. Das, SUNY at Stony Brook, USA A. Ephremides, University of Maryland, USA S. Giordano, SUPSI, CH E. Gregori, IIT-CNR, Italy T. Henderson, Dartmouth College, USA H. Karl, Paderborn University, Germany E. Knightly, Rice University, USA M. Mauve, Dusseldorf University, Germany P. Michiardi, EURECOM, France R. Molva, EURECOM, France S. Olariu, Old Dominion University, USA G. Polyzos, Athens University of Economics and Business, Greece D. Remondo, Catalonia University of Technology, Spain C. Rohner, Uppsala University, Sweden J.H. Schiller, Freie University Berlin, Germany J. Scott, Intel Research, UK F. Sestini, European Commission V.A. Siris, FORTH-ICS and Crete University, Greece I. Stavrakakis, Athens University, Greece I. Stojmenovic, Ottawa University, Canada C. Tschudin, Basel University, Switzerland N. Vaidya, Illinois University at Urbana-Champaign, USA J. Wu, Florida Atlantic University, USA -- Andrea Passarella IEEE ICPS REALMAN Workshop Program Vice-Chair ========================================================= University of Cambridge The Computer Laboratory || voice:+44 (0)1223 763658 15 JJ Thomson Avenue || fax: +44 (0)1223 334678 Cambridge CB3 0FD, UK || web: www.cl.cam.ac.uk/~ap458/ email: andrea.passarella@cl.cam.ac.uk ========================================================= Pervasive Computing & Networking Lab. (PerLab) University of Pisa, Dept. of Information Engineering _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 13 13:08:58 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14650 for ; Wed, 13 Apr 2005 13:08:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLlWA-00054S-CJ for manet-web-archive@ietf.org; Wed, 13 Apr 2005 13:19:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLlGo-0004mN-B8; Wed, 13 Apr 2005 13:03:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLlGm-0004lu-8v for manet@megatron.ietf.org; Wed, 13 Apr 2005 13:03: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 NAA14025 for ; Wed, 13 Apr 2005 13:03:13 -0400 (EDT) Received: from web53303.mail.yahoo.com ([206.190.39.232]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLlQa-0004o1-CF for manet@ietf.org; Wed, 13 Apr 2005 13:13:25 -0400 Received: (qmail 15391 invoked by uid 60001); 13 Apr 2005 17:03:03 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ngw61hmeFAYGobLwHwNn+6oQ/e3ZREWC6CV+m1vXxs0A/WNq9I1/EkZzsY89jfnjVCSa4FVnad/GuNPIclYQQdP7i4zH7hisB0JZEERSOL04Gg0kvsU+ioaQwsUNt6pVhwLimIRczWAL+CRFHz15WMUxjaRR/X9yzGJM7McmDgg= ; Message-ID: <20050413170303.15387.qmail@web53303.mail.yahoo.com> Received: from [205.129.164.35] by web53303.mail.yahoo.com via HTTP; Wed, 13 Apr 2005 10:03:03 PDT Date: Wed, 13 Apr 2005 10:03:03 -0700 (PDT) From: papa Arkhurst To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 2.9 (++) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [manet] Glomosim X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.9 (++) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Hello, I am pretty new at glomosim and i am trying to figure out its full functionality. I have been running some simulations with it but i have been trying to in troduce noice into the system by varying the noise figure but that does not give me any results that make sense, can someone please let me know how i can introduce noise into the system. __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 13 19:58:39 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21583 for ; Wed, 13 Apr 2005 19:58:39 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLruh-0000T2-2P for manet-web-archive@ietf.org; Wed, 13 Apr 2005 20:08:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLraD-0001yB-4P; Wed, 13 Apr 2005 19:47:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLraA-0001y2-Tb for manet@megatron.ietf.org; Wed, 13 Apr 2005 19:47: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 TAA21010 for ; Wed, 13 Apr 2005 19:47:39 -0400 (EDT) Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLrk2-0000D2-52 for manet@ietf.org; Wed, 13 Apr 2005 19:57:55 -0400 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) id <0IEW00J0CSR7EH@mailout3.samsung.com> for manet@ietf.org; Thu, 14 Apr 2005 08:47:31 +0900 (KST) Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IEW00EH1SR3IC@mailout3.samsung.com> for manet@ietf.org; Thu, 14 Apr 2005 08:47:27 +0900 (KST) Received: from joseph ([165.213.109.215]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPSA id <0IEW00CLUSR2DL@mmp2.samsung.com> for manet@ietf.org; Thu, 14 Apr 2005 08:47:27 +0900 (KST) Date: Thu, 14 Apr 2005 08:45:54 +0900 From: Hyunwook Cha In-reply-to: <0IEW00EXU8BQUE@mailin3.samsung.com> To: sdx86@uow.edu.au Message-id: <000001c54082$f3adffc0$d76dd5a5@joseph> Organization: Samsung Electronics MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 1.1 (+) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: 7BIT Cc: manet@ietf.org Subject: [manet] RE: manet Digest, Vol 12, Issue 13 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hyunwook.cha@samsung.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: 7BIT Hi Cindy, As long as I understand AODV, DSN is essential for route discovery because routing loop can be avoided through comparison between maintained one in route tables and one in control messages. RREQ can not update existing route entries in receiving nodes because sender node does not have valid route information. And receiving node decides that it can generate RREP or not by comparing DSN in its table with DSN in RREQ (hop count is also used for tie-breaking) unless the "destination only" flag is set. In this case, when RREQ is forwarded again, actually DSN in RREQ remains unchanged. Only if the "destination only" flag is set, DSN in RREQ can be changed to make sure that RREP generated by destination node can update routing table in nodes on the reverse path. Hoping this helps. HyunWook Cha > Date: Wed, 13 Apr 2005 10:53:57 +1000 > From: Cindy > Subject: [manet] the effect of destination sequence number > To: "MANET@ieft.org" > Message-ID: > Content-Type: text/plain; charset="us-ascii" > > Hello all, > > Following my previous question, can anybody who has > a clear thoughs about destination sequence > number(DSN) tell me, what is the effect of > DSN during the RREQ transmission? > > 2 facts are: > > 1. the forwarding node will not modify its route > table entry for the destination node during RREQ > transmission. > > 2. the node generating RREP simply copies its known > or its own destination sequence number into RREP > field, which is obviously the freshest one. > > This means the RREQ will be accepted anyway if it is > not a duplicate one. I am wondering can we ignore > the DSN during RREQ transmission? > > Looking forward to any clarifications! > > Cheers, > > Cindy > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://www1.ietf.org/pipermail/manet/attachments/20050413/4cac > 43a7/attachment.htm > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 13 21:09:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25760 for ; Wed, 13 Apr 2005 21:09:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLt1M-00026D-2r for manet-web-archive@ietf.org; Wed, 13 Apr 2005 21:19:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLslZ-00071V-VO; Wed, 13 Apr 2005 21:03:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLslX-0006yd-SW for manet@megatron.ietf.org; Wed, 13 Apr 2005 21:03: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 VAA25236 for ; Wed, 13 Apr 2005 21:03:10 -0400 (EDT) Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLsv6-0001wU-AA for manet@ietf.org; Wed, 13 Apr 2005 21:13:25 -0400 Received: from giovannipc (ar12-136.research.telcordia.com [192.4.12.136]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id j3E12hsD016297 for ; Wed, 13 Apr 2005 21:02:43 -0400 (EDT) From: "Giovanni Di Crescenzo" To: Date: Wed, 13 Apr 2005 21:02:43 -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, Build 10.0.4024 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Subject: [manet] Call for papers (deadline: Apr 29): 1st Workshop onCryptography over Ad hoc Networks (WCAN 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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit CALL FOR PAPERS: 1st Workshop on Cryptography over Ad hoc Networks (WCAN 05) (A Satellite Workshop of Wirelesscom 05, http://sa1.sice.umkc.edu/wc05) Workshop Location: Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, http://www.sheraton-maui.com Important Dates: Submission Deadline: April 29, 2005 Notification of Acceptance: May 13, 2005 Camera-Ready Papers: May 20, 2005 Workshop Dates: June 15-16 Topics: all topics related to cryptology AND ad-hoc networks. The detailed call for paper can be found at: http://www.argreenhouse.com/society/wcan05/wcan05cfp.pdf _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 13 22:08:16 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29300 for ; Wed, 13 Apr 2005 22:08:16 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLtw8-0003ai-Lt for manet-web-archive@ietf.org; Wed, 13 Apr 2005 22:18:33 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLtfW-000786-0i; Wed, 13 Apr 2005 22:01:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLtfU-00077p-3F for manet@megatron.ietf.org; Wed, 13 Apr 2005 22:01: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 WAA28892 for ; Wed, 13 Apr 2005 22:01:10 -0400 (EDT) Received: from mail.ajou.ac.kr ([202.30.0.18]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLtpE-0003PE-EY for manet@ietf.org; Wed, 13 Apr 2005 22:11:26 -0400 Received: from seodang.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.8) with SMTP ID 323 for ; Thu, 14 Apr 2005 11:02:56 +0900 (KST) Received: from 210.107.203.187 ([210.107.203.187]) by spam.ajou.ac.kr (Spambreaker SMTP Server ); Thu, 14 Apr 2005 11:00:35 +0900 (KST) Message-ID: <015401c54096$219349a0$dcc26bd2@ajoudayhakyu> From: Faisal Adeem Siddiqui To: manet@ietf.org Date: Thu, 14 Apr 2005 11:03:18 +0900 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 1.4 (+) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Subject: [manet] question about simultaneous use of different routing protocols in a single 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: 1.4 (+) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit Hi all, I was wondering if it is possible and practical to use two different routing protocols in a single MANET ? I think if we are using two routing protocols then it will make two segments of MANET and there must be a node (gateway) between these segments which understands both routing protocols to relay traffic from one segment to another. On the other hand, if we want to switch from one routing protocol to another depending upon the network conditions, will it be practical ? For example, initially we have a proactive routing protocol running but after some time the mobility of nodes increase considerably and the performance of proactive routing protocol is decreased. Now if we want to switch to a reactive routing protocol, will it incur a lot of overhead ? Is it practical ? If someone has done any experiments of this kind please refer it to me. Thanks. Faisal. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 14 02:21:46 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05599 for ; Thu, 14 Apr 2005 02:21:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLxtT-0001Se-KG for manet-web-archive@ietf.org; Thu, 14 Apr 2005 02:32:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLxXa-0007EM-Js; Thu, 14 Apr 2005 02:09:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLxXR-0007CO-91 for manet@megatron.ietf.org; Thu, 14 Apr 2005 02:09:17 -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 CAA23456 for ; Thu, 14 Apr 2005 02:09:08 -0400 (EDT) Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLxhC-0001A7-M0 for manet@ietf.org; Thu, 14 Apr 2005 02:19:25 -0400 Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1 #31112) with ESMTP id <01LN395OLC9S9AMOT0@vaxh.its.monash.edu.au> for manet@ietf.org; Thu, 14 Apr 2005 16:08:43 +1000 Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 9D05CAB543 for ; Thu, 14 Apr 2005 16:08:43 +1000 (EST) Received: from localhost.localdomain (portal-web3.its.monash.edu.au [130.194.13.179]) by curly.its.monash.edu.au (Postfix) with ESMTP id 70A9A4FB05 for ; Thu, 14 Apr 2005 16:08:43 +1000 (EST) Date: Thu, 14 Apr 2005 06:08:43 +0000 From: Thanh Nguyen To: manet@ietf.org Message-id: <130.194.136.10.1113458317.10349@my.monash.edu.au> MIME-version: 1.0 X-Mailer: my.monash Portal Mail Reader Content-type: text/plain Content-transfer-encoding: 7BIT Content-disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7BIT Subject: [manet] Any one implement AODV on Mobility Frame Work 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: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7BIT Dear members, I am a research student at Centre for Telecommunications and Information Engineering (CTIE),Monash University which develop MIPv6 use IPv6 suite on Omnet++. I am wondering that is there any one who implement AODV protocol on Mobility Frame Work which is available on http://www.omnetpp.org Thank you. Thanh Tung _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 14 07:46:38 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02869 for ; Thu, 14 Apr 2005 07:46:38 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM2xu-0002uF-90 for manet-web-archive@ietf.org; Thu, 14 Apr 2005 07:56:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM2hq-0000Jt-Ld; Thu, 14 Apr 2005 07:40:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM2hp-0000Ff-0S for manet@megatron.ietf.org; Thu, 14 Apr 2005 07:40: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 HAA02309 for ; Thu, 14 Apr 2005 07:40:14 -0400 (EDT) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM2rh-0002d5-TR for manet@ietf.org; Thu, 14 Apr 2005 07:50:35 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j3EBe4Lu013720 for ; Thu, 14 Apr 2005 13:40:05 +0200 (CEST) Received: from [172.17.10.132] (vigo.eurecom.fr [172.17.10.132]) by monza.eurecom.fr (Postfix) with ESMTP id 7D29B3C334 for ; Thu, 14 Apr 2005 13:40:04 +0200 (MEST) Message-ID: <425E5694.7020308@eurecom.fr> Date: Thu, 14 Apr 2005 13:40:04 +0200 From: Refik Molva User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: 7bit Subject: [manet] ESAS 2005 - last call for papers - deadline April 18 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: 7bit (apologies for multiple copies of this announcement) LAST CALL FOR PAPERS (submission deadline April 18, 2005) ------------------------------------ Second European Workshop on Security and Privacy in Ad hoc and Sensor Networks ESAS 2005 http://www.crysys.hu/ESAS2005/ in conjunction with the First International Conference on Wireless Internet (WICON) Visegrad, Hungary, July 14-15, 2005 -------------------------------------------------------- Important dates Submission Deadline: extended to April 18, 2005 Notification of Acceptance: May 20, 2005 Workshop Version Deadline: May 31, 2005 Workshop: July 14-15, 2005 Proceedings Version Deadline: August 15, 2005 -------------------------------------------------------- Instructions for Authors Authors are invited to submit original papers. All submissions will be refereed. Submissions must not substantially duplicate work that any of the authors have published elsewhere or have submitted in parallel. The submissions must not exceed 10 pages (excluding the title page, bibliography and appendices) nor 12 pages overall. The final version should not exceed 15 pages. The preferred submission format is PDF or PostScript. We recommend that you generate the PDF or PS file using LaTeX and the LNCS style available at www.springer.de/comp/lncs. Further information on how to submit papers will be available on the web site of the workshop: http://www.crysys.hu/ESAS2005/ Workshop proceedings The Proceedings will be published by Springer after the Workshop in the Lecture Notes in Computer Science (LNCS) Series (www.springer.de/comp/lncs). Notice that in order to be included in the proceedings, the authors of an accepted paper must guarantee to present their contribution at the ESAS workshop. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 14 12:24:47 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28747 for ; Thu, 14 Apr 2005 12:24:47 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM7J9-0006j4-3n for manet-web-archive@ietf.org; Thu, 14 Apr 2005 12:35:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM6pe-0003EB-Lu; Thu, 14 Apr 2005 12:04:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM6pc-0003Cx-B0 for manet@megatron.ietf.org; Thu, 14 Apr 2005 12:04: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 MAA27169 for ; Thu, 14 Apr 2005 12:04:29 -0400 (EDT) Received: from mail.ece.gatech.edu ([199.77.227.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM6zT-0005ru-Uc for manet@ietf.org; Thu, 14 Apr 2005 12:14:53 -0400 Received: from localhost (k4-3.ece.gatech.edu [199.77.227.203]) by mail.ece.gatech.edu (8.12.10/8.12.10) with ESMTP id j3EG4TAO027793 for ; Thu, 14 Apr 2005 12:04:29 -0400 (EDT) Received: from mail.ece.gatech.edu ([199.77.227.200]) by localhost (k4-3.ece.gatech.edu [199.77.227.203]) (amavisd-new, port 10024) with LMTP id 21188-02-2 for ; Thu, 14 Apr 2005 12:04:22 -0400 (EDT) Received: from secure2.ece.gatech.edu (seiya.ece.gatech.edu [130.207.225.101]) by mail.ece.gatech.edu (8.12.10/8.12.10) with ESMTP id j3EG2xfI027579 for ; Thu, 14 Apr 2005 12:02:59 -0400 (EDT) Received: from 130.39.224.122 (SquirrelMail authenticated user sjpark) by secure2.ece.gatech.edu with HTTP; Thu, 14 Apr 2005 12:02:59 -0400 (EDT) Message-ID: <2513.130.39.224.122.1113494579.squirrel@secure2.ece.gatech.edu> Date: Thu, 14 Apr 2005 12:02:59 -0400 (EDT) From: "Seung-Jong Park" To: manet@ietf.org User-Agent: SquirrelMail/1.4.4 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 ece.gatech.edu X-Spam-Score: 0.8 (/) X-Scan-Signature: 093efd19b5f651b2707595638f6c4003 Content-Transfer-Encoding: 8bit Subject: [manet] [CFP] SenMetrics 2005 (Extended Deadline:April 22) 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: 2beba50d0fcdeee5f091c59f204d4365 Content-Transfer-Encoding: 8bit (apologies for multiple copies of this announcement) LAST CALL FOR PAPERS (extened submission deadline April 22, 2005) ----------------------------------------------------------------- SenMetrics 2005 Third International Workshop on Measurement, Modeling, and Performance Analysis of Wireless Sensor Networks San Diego, CA, USA July 21, 2005 (in conjunction with MobiQuitous 2005) http://www.senmetrics.org/ E-mail: senmetrics@ece.osu.edu ----------------------------------------------------------------- The SenMetrics Workshop solicits papers on the development and application of analytic, simulation, prototype testbed, and measurement-based performance evaluation techniques to the area of wireless sensor networks. Of particular interest is work that furthers the state-of-the-art in performance evaluation methods, or those that creatively apply previously developed methods to understand or to gain important insights into key design trade-offs in wireless sensor networks. Topics of interest include, but are not limited to: Performance-oriented design and evaluation studies of: - wireless sensor networks - sensor node hardware and software architectures - data collection - addressing - security, reliability, and robustness - operating systems - energy aware network protocols - applications - localization - fundamental limits and tradeoffs - topology management - deployment - distributed actuation and control - system development and testbed experience - benchmarks Performance methodology techniques and algorithms for: - system, protocol, and algorithm modeling - analytic evaluation - system measurement and monitoring - model verification and validation - workload characterization - simulation - statistical analysis - stochastic modeling - experimental design - reliability analysis - performance optimization IMPORTANT DATES: Extended Paper Submission Deadline: April 22, 2005 Notification of Acceptance: June 1, 2005 Camera Ready Paper Due: June 15, 2005 Workshop Date: July 21, 2005 PAPERS: Authors are invited to submit for review, papers that neither have been previously published nor are under review by another conference or journal. Priority will be given to original contributions describing recent and innovative research results or developments in the scope of the workshop. Best papers will be considered for publication in a special issue of the Ad-hoc Networks Journal. Papers must be written in English, using font no smaller than 10 points and not to exceed 10 pages. Only PDF and PostScript formats will be accepted, and all submissions will be handled electronically. Further details on submission procedures are available at http://www.senmetrics.org/ GENERAL CHAIR: Raghupathy Sivakumar, Georgia Institute of Technology PROGRAM CHAIRS: Eylem Ekici, Ohio State University Ibrahim Matta, Boston University PUBLICITY CHAIR: Seung-Jong Park, Louisiana State University TECHNICAL PROGRAM COMMITTEE: Alhussein Abouzeid (RPI) Ozgur B. Akan (Middle East Technical U, Turkey) Andrew Campbell (Columbia University) Sonia Fahmy (Purdue University) Paul Havinga (University of Twente, The Netherlands) Ahmed Helmy (USC) Holger Karl (University of Paderborn, Germany) Bhaskar Khrisnamachari (USC) Marwan Krunz (University of Arizona) Kang-Won Lee (IBM Research) Mingyan Liu (University of Michigan) Stephan Olariu (Old Dominion University) Sergio Palazzo (University of Catania, Italy) Seung-Jong Park (Louisiana State University) Ness Shroff (Purdue University) David Starobinski (Boston University) Ioannis Stavrakakis (University of Athens, Greece) Xin Wang (University at Buffalo) Wenye Wang (North Carolina State University) Lixia Zhang (UCLA) Taieb Znati (University of Pittsburgh) ---------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 14 12:40:58 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00502 for ; Thu, 14 Apr 2005 12:40:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM7Yo-0007SS-K9 for manet-web-archive@ietf.org; Thu, 14 Apr 2005 12:51:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM7K8-000847-Lc; Thu, 14 Apr 2005 12:36:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM7K6-00082z-DT for manet@megatron.ietf.org; Thu, 14 Apr 2005 12:36: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 MAA29988 for ; Thu, 14 Apr 2005 12:35:56 -0400 (EDT) Received: from web25406.mail.ukl.yahoo.com ([217.12.10.140]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DM7Tv-0007Gg-9Y for manet@ietf.org; Thu, 14 Apr 2005 12:46:21 -0400 Received: (qmail 11622 invoked by uid 60001); 14 Apr 2005 16:35:47 -0000 Message-ID: <20050414163547.11620.qmail@web25406.mail.ukl.yahoo.com> Received: from [202.163.98.82] by web25406.mail.ukl.yahoo.com via HTTP; Thu, 14 Apr 2005 17:35:47 BST Date: Thu, 14 Apr 2005 17:35:47 +0100 (BST) From: Saqib Ilyas Subject: Re: [manet] question about simultaneous use of different routing protocols in a single MANET To: manet@ietf.org In-Reply-To: 6667 MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaqib@ieee.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0613786295==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 --===============0613786295== Content-Type: multipart/alternative; boundary="0-251837566-1113496547=:11588" --0-251837566-1113496547=:11588 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I think that the idea of administrative distance could be exploited here. If the network is not "wild enough" then the node somehow modifies the administrative distance of the more suitable protocol to favor it, and later set it back when the going gets tough. Just my two cents. Regards Faisal Adeem Siddiqui wrote: Hi all, I was wondering if it is possible and practical to use two different routing protocols in a single MANET ? I think if we are using two routing protocols then it will make two segments of MANET and there must be a node (gateway) between these segments which understands both routing protocols to relay traffic from one segment to another. On the other hand, if we want to switch from one routing protocol to another depending upon the network conditions, will it be practical ? For example, initially we have a proactive routing protocol running but after some time the mobility of nodes increase considerably and the performance of proactive routing protocol is decreased. Now if we want to switch to a reactive routing protocol, will it incur a lot of overhead ? Is it practical ? If someone has done any experiments of this kind please refer it to me. Thanks. Faisal. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Muhammad Saqib Ilyas Assistant Professor Department of Computer and Information Systems Engineering NED University of Engineering and Technology, Karachi, Pakistan http://www.neduet.edu.pk/CISE/faculty/MSaqib/index.htm Chair, Student Activities Committee, IEEE Karachi Section Member Executive Committee, IEEE Karachi Section Country Leader, INETA Pakistan IEEE Student Branch Counselor, NED University Send instant messages to your online friends http://uk.messenger.yahoo.com --0-251837566-1113496547=:11588 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
I think that the idea of administrative distance could be exploited here. If the network is not "wild enough" then the node somehow modifies the administrative distance of the more suitable protocol to favor it, and later set it back when the going gets tough. Just my two cents.
Regards

Faisal Adeem Siddiqui <faysal@ajou.ac.kr> wrote:
Hi all,
I was wondering if it is possible and practical to use two different routing
protocols in a single MANET ? I think if we are using two routing protocols
then it will make two segments of MANET and there must be a node (gateway)
between these segments which understands both routing protocols to relay
traffic from one segment to another.
On the other hand, if we want to switch from one routing protocol to another
depending upon the network conditions, will it be practical ? For example,
initially we have a proactive routing protocol running but after some time
the mobility of nodes increase considerably and the performance of proactive
routing protocol is decreased. Now if we want to switch to a reactive
routing protocol, will it incur a lot of overhead ? Is it practical ? If
someone has done any experiments of this kind please refer ! it to me.
Thanks.

Faisal.


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


Muhammad Saqib Ilyas
Assistant Professor
Department of Computer and Information Systems Engineering
NED University of Engineering and Technology, Karachi, Pakistan
http://www.neduet.edu.pk/CISE/faculty/MSaqib/index.htm
Chair, Student Activities Committee, IEEE Karachi Section
Member Executive Committee, IEEE Karachi Section
Country Leader, INETA Pakistan
IEEE Student Branch Counselor, NED University

Send instant messages to your online friends http://uk.messenger.yahoo.com --0-251837566-1113496547=:11588-- --===============0613786295== 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 --===============0613786295==-- From manet-bounces@ietf.org Thu Apr 14 14:05:10 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07345 for ; Thu, 14 Apr 2005 14:05:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM8sH-0002Yv-Nu for manet-web-archive@ietf.org; Thu, 14 Apr 2005 14:15:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM8ge-0003uM-Se; Thu, 14 Apr 2005 14:03:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM8gb-0003rY-Qr for manet@megatron.ietf.org; Thu, 14 Apr 2005 14:03: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 OAA07143 for ; Thu, 14 Apr 2005 14:03:28 -0400 (EDT) Received: from mailg.surrey.ac.uk ([131.227.102.21]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DM8qd-0002SA-Ov for manet@ietf.org; Thu, 14 Apr 2005 14:13:52 -0400 Received: from ads33.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP) with ESMTP; Thu, 14 Apr 2005 19:03:03 +0100 Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136]) by ads33.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211); Thu, 14 Apr 2005 19:03:02 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5411C.335F5795" Subject: RE: [manet] question about simultaneous use of different routing Date: Thu, 14 Apr 2005 19:03:02 +0100 Message-ID: X-MS-TNEF-Correlator: Thread-Topic: [manet] question about simultaneous use of different routing Thread-Index: AcVBD9Cvz4Qj2Ud+Sl+7QuQlc05fPQABp2e4 From: "S.Sivavakeesar" To: manet X-OriginalArrivalTime: 14 Apr 2005 18:03:02.0931 (UTC) FILETIME=[33871E30:01C5411C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 562cdc9baa87554b29d950396a30cf75 Cc: faysal 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: 8aa7cbc518894eb04182283f0682f662 This is a multi-part message in MIME format. ------_=_NextPart_001_01C5411C.335F5795 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Faisal : =20 We are currently working on an intersting project called PAN = (programmable ad hoc networks), that investigates=20 the issues related to dynamically deploying/switching/modifying = services/protocols in an MANET environmnet. =20 Our objective is to come up with a context-aware middleware that can = facilitate programmability in dynamic MANETs.=20 We argued in our IM 2005 paper (see below for paper details) that this = kind of programmability is important in MANET,=20 as in MANETs the network itself needs to be self-created, self-managed, = self-optimised and so on. The above features=20 of MANETs often require the ability to rapidly create, deploy and manage = services and protocols in response to user=20 demands and context. For example, while routing and Quality of Service = (QoS) conform to standardised frameworks and=20 protocols in fixed IP networks, there are many potential solutions for = ad hoc networks that depend also on the characteristics=20 of the particular ad hoc network, e.g. topology volatility, = characteristics of radio links, capabilities of nodes, etc. Given=20 the multitude of potential solutions that may be environment-dependent, = programmability is of paramount importance to=20 allow mobile nodes to be enhanced on the fly with the required = capabilities in the ad hoc environment. =20 Although people can argue that this might involve some overhead, it is = inevitable in the future MANETs, given that=20 not only will there be hetrogeneous devises, but also we would have = various complex services/protocols. In other words,=20 in order to facilitate self-optimisation/self-management aspects based = on the current context, dynamic switching/deploying of=20 services/protocols at any level is important. As you mentioned in your = mail, if a group (cluster) of MANET nodes are=20 stationary for a while (or their relative velocity is minimal or zero = w.r.t each other) and where almost every node is involved in some potential data transmissions (it may happen in battlefiel = situation), it is better to use proactive routing protocols=20 (together with some QoS mechanisms). On the other hand, when the = relative mobility pattern is very random, then it is better to use reactive routing protocols. Although, switch-over may involve some = overhead, this strategy is still econmical if we are to=20 conserve scarce resources. =20 Please refer to our IM paper, which investigates this problem through = real test-bed experiments and simulations. The paper details are as follows : =20 S. Gouveris, S. Sivavakeesar, G. Pavlou, A. Malatras, Programmable = Middleware for the Dynamic=20 Deployment of Services and Protocols in Ad hoc Networks, to appear in = the Proceedings of the=20 IEEE/IFIP Integrated Management Symposium (IM'2005), Nice, France, = IEEE, May 2005.=20 =20 We hope this would help. =20 Cheers =20 Siva Sivavakeesar Centre for Communication Systems Research University of Surrey Guildford Surrey GU2 7XH United Kingdom =20 Tel : +44 (0) 1483 689495. =20 =20 Date: Thu, 14 Apr 2005 11:03:18 +0900 From: Faisal Adeem Siddiqui Subject: [manet] question about simultaneous use of different routing protocols in a single MANET To: manet@ietf.org Message-ID: <015401c54096$219349a0$dcc26bd2@ajoudayhakyu> Content-Type: text/plain; charset=3D"iso-8859-1" Hi all, I was wondering if it is possible and practical to use two different = routing protocols in a single MANET ? I think if we are using two routing = protocols then it will make two segments of MANET and there must be a node = (gateway) between these segments which understands both routing protocols to relay traffic from one segment to another. On the other hand, if we want to switch from one routing protocol to = another depending upon the network conditions, will it be practical ? For = example, initially we have a proactive routing protocol running but after some = time the mobility of nodes increase considerably and the performance of = proactive routing protocol is decreased. Now if we want to switch to a reactive routing protocol, will it incur a lot of overhead ? Is it practical ? If someone has done any experiments of this kind please refer it to me. Thanks. Faisal. ------------------------------ Message: 5 Date: Thu, 14 Apr 2005 06:08:43 +0000 From: Thanh Nguyen Subject: [manet] Any one implement AODV on Mobility Frame Work To: manet@ietf.org Message-ID: <130.194.136.10.1113458317.10349@my.monash.edu.au> Content-Type: text/plain Dear members, I am a research student at Centre for Telecommunications and Information = Engineering (CTIE),Monash University which develop MIPv6 use IPv6 suite = on Omnet++. I am wondering that is there any one who implement AODV protocol on = Mobility Frame Work which is available on http://www.omnetpp.org Thank you. Thanh Tung ------------------------------ Message: 6 Date: Thu, 14 Apr 2005 13:40:04 +0200 From: Refik Molva Subject: [manet] ESAS 2005 - last call for papers - deadline April 18 To: manet@ietf.org Message-ID: <425E5694.7020308@eurecom.fr> Content-Type: text/plain; charset=3Dus-ascii; format=3Dflowed (apologies for multiple copies of this announcement) LAST CALL FOR PAPERS (submission deadline April 18, 2005) ------------------------------------ Second European Workshop on Security and Privacy in Ad hoc and Sensor Networks ESAS 2005 http://www.crysys.hu/ESAS2005/ in conjunction with the First International Conference on Wireless Internet (WICON) Visegrad, Hungary, July 14-15, 2005 -------------------------------------------------------- Important dates Submission Deadline: extended to April 18, 2005 Notification of Acceptance: May 20, 2005 Workshop Version Deadline: May 31, 2005 Workshop: July 14-15, 2005 Proceedings Version Deadline: August 15, 2005 -------------------------------------------------------- Instructions for Authors Authors are invited to submit original papers. All submissions will be refereed. Submissions must not substantially duplicate work that any of the authors have published elsewhere or have submitted in parallel. The submissions must not exceed 10 pages (excluding the title page, bibliography and appendices) nor 12 pages overall. The final version should not exceed 15 pages. The preferred submission format is PDF or PostScript. We recommend that you generate the PDF or PS file using LaTeX and the LNCS style available at www.springer.de/comp/lncs. Further information on how to submit papers will be available on the web site of the workshop: http://www.crysys.hu/ESAS2005/ Workshop proceedings The Proceedings will be published by Springer after the Workshop in the Lecture Notes in Computer Science (LNCS) Series (www.springer.de/comp/lncs). Notice that in order to be included in the proceedings, the authors of an accepted paper must guarantee to present their contribution at the ESAS workshop. ------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet End of manet Digest, Vol 12, Issue 14 ************************************* ------_=_NextPart_001_01C5411C.335F5795 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 eJ8+IgMSAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAQQAAAFJFOiBbbWFuZXRdIHF1ZXN0 aW9uIGFib3V0IHNpbXVsdGFuZW91cyB1c2Ugb2YgZGlmZmVyZW50IHJvdXRpbmcAOxgBBYADAA4A AADVBwQADgATAAMAAgAEAAoBASCAAwAOAAAA1QcEAA4AEwADAAIABAAKAQEJgAEAIQAAADM4NTA1 ODc5NEY4QUZDNDg5QTNDRDBCMzYwNTNCNjVDACwHAQOQBgCYLgAANwAAAAMANgAAAAAAQAA5AJVX XzMcQcUBHgA9AAEAAAAFAAAAUkU6IAAAAAACAUcAAQAAADMAAABjPVVTO2E9IDtwPVVOSVM7bD1F VlMtRUMxLU5PREUxLTA1MDQxNDE4MDMwMlotOTc1MgAAHgBJAAEAAAAfAAAAbWFuZXQgRGlnZXN0 LCBWb2wgMTIsIElzc3VlIDE0AABAAE4AAG3ayA9BxQEeAFoAAQAAABcAAABtYW5ldC1ib3VuY2Vz QGlldGYub3JnAAACAVsAAQAAAEsAAAAAAAAAgSsfpL6jEBmdbgDdAQ9UAgAAAABtYW5ldC1ib3Vu Y2VzQGlldGYub3JnAFNNVFAAbWFuZXQtYm91bmNlc0BpZXRmLm9yZwAAAgFcAAEAAAAcAAAAU01U UDpNQU5FVC1CT1VOQ0VTQElFVEYuT1JHAB4AXQABAAAAFwAAAG1hbmV0LXJlcXVlc3RAaWV0Zi5v cmcAAAIBXgABAAAASwAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAG1hbmV0LXJlcXVlc3RAaWV0 Zi5vcmcAU01UUABtYW5ldC1yZXF1ZXN0QGlldGYub3JnAAACAV8AAQAAABwAAABTTVRQOk1BTkVU LVJFUVVFU1RASUVURi5PUkcAHgBmAAEAAAAFAAAAU01UUAAAAAAeAGcAAQAAABcAAABtYW5ldC1i b3VuY2VzQGlldGYub3JnAAAeAGgAAQAAAAUAAABTTVRQAAAAAB4AaQABAAAAFwAAAG1hbmV0LXJl cXVlc3RAaWV0Zi5vcmcAAB4AcAABAAAAPQAAAFttYW5ldF0gcXVlc3Rpb24gYWJvdXQgc2ltdWx0 YW5lb3VzIHVzZSBvZiBkaWZmZXJlbnQgcm91dGluZwAAAAACAXEAAQAAABsAAAABxUEP0K/PhCPZ R35KX7tC5CVzTl89AAGnZ7gAHgB0AAEAAAAPAAAAbWFuZXRAaWV0Zi5vcmcAAB4AGgwBAAAAIAAA AFNpdmF2YWtlZXNhciBTIE1yIChQRy9SIC0gQ0NTUikAHgAdDgEAAAA9AAAAW21hbmV0XSBxdWVz dGlvbiBhYm91dCBzaW11bHRhbmVvdXMgdXNlIG9mIGRpZmZlcmVudCByb3V0aW5nAAAAAAIBCRAB AAAAVicAAFInAAB9pgAATFpGdeErBUEDAAoAcmNwZzEyNYIyA0NodG1sMQMwPwEDAfcKgAKkA+MC AGNowQrAc2V0MCAHEwKA/xADAFAEVghVB7IR1Q5RAwHdENcyBgAGwxHVMwRGENlvEusR4wjvCfc7 GM8OMDU7EdIMYGMAUAsJAWQzNpMRYAulNCAQAipcDrK9AZBnFPAKoxHjHeg0FPAAPCFET0NUWVAA RSBIVE1MIFAAVUJMSUMgIi0gLy9XM0MhgERUIkQglDMuMiGARU6cIj4e7R6PI8ExOB/wbyCiIw8k HyaQMx2AJXBFfEFEJc0O8SbvKW8k9DZBDvA8TUVUQQewQTEsYD0iRwnwBJBhdEUFsCIS0E9OVCLQ VBMs8AXhRXgQ8W5nZT0GUnYTMS9BAJACICA2qC41LgHAMjAAMCL+EyrPJQM3Nx/wVElUdExFJc40 DvADgRFAIAREaS7gc3QsIFbtBvAgDiA1gEkEEApQNdDqNCRuNR/wLzNPMX8mRV80kTfAKE8mnzuU NRFgPHBCT0RZOw0c8TwvZwQ5Nh/wRElWIGkEZD1AgE9XQVJlwQtQeVRleHQsEB/QoR2AZGlyPTuw cjsA+ztzACEgAABCMQqxQyIQ8PxccQMhQpURYD3vPv9ABv9B/0MPRBo7SUGgR/pETyT0KjQlUUYt 0SAAkHplnD0yR+sL4kQpRGUKwUpGC3BzB0AgOiR8Nf1AES9NkkfpR/dKOwHAR/fvCqJS+AqAJHww KBEh4EBQ/1JPTC9Fn0avR79Iz1MvSu//WE9ND04fTyxQ31HvWB87hYI4HYAmbmJzcAKA8Vv3XCdh AUBdv1QvVT//Vk9XX2ZvWX9aj1ufXK9pH99ez24/YO9h/08dVy7wCsA9LvBjCHAY0AIwQTAgd+UF sGsLgGcgL9EDkQuAunQvkXR7Qjmsb6VwA2C6agWQdGbPZ99o6mMHQIZsCYAg4EFOICh94XkJwGFt AMACYHoBgYBomG9jIDThewJzKTWA/nQRAAVAfl9/b2jqC4AvQP18MWctYAeRfJ9v32TPUr//ac9q 32vvbP9uD28fcC9xP/9yT3NfdG91f3aPd594r5iC/YPgZYQ/hU9o6mPvij+Qb/+ZH5ovmz9AcDYy BCAY0AtgH3wAgYAtcIffkiNkeW4/gkAN4IFBeuABAAtQb3n1e0EvA+F0EPCpYgRhBpDfqVKjoC8h DeAHkC994S1w7xhBBCALgHuiTYGwLHCm70+SIwnwqxADYG5tNOEu/5yPnZ+er5+/oM+WP4yvjb// js+zX6IPkf+TD5QflS+0P9+XT7lfou+j/087Twhwe3D6Yn4SaS9ApcGmsa7vr///aOqx37LvuR/B z8Lfw+8FoHEHgCB1cKzPusOpsWiPehDPUXvxQXAtYXd6IvmogGRkgWDSM4PjgTADoN5mANADEKnA h5EggfjT8j964KwRqEXP37rDrHNzLv/I/8oPs++0/7YPtx+4L8tP/7pPu1+8b71/vo+/n8CvzC/3 zT/OT3nkZwpQgYDX/9kP/98/5+/o/+oPrBHrv+zP7d8/7u8Ko+//8Q8IYTYQTSCtAdAwN6AKsHAT MSgRMPUu8GKmUG8H4AIQBcD5tP8BAAGQAxCDoIPUg+DF0XsxfYGAb+OA1i99pdSsq/Ft/nAYcQ2w BUCsEaxzNYDyT//zX9of2y/cP91P3l/0n+B//+GP4p/jr+S/5c/m3/V/9t/99+9hq/PXdJxCgybG L8c//7EPAR8CLw//9b8RzxLfQHDydPogbGYVfxaPaOotMJ+BcMXi+lGq0R9QLWOmQD+mcjWAIxM0 wTvQI7dvcL98QKiA+iCBgP/wgYBzpt//CbQv0NffGV8abxt/Eb8d73tmrwcAU4GiHKTVQIFgPQIi HFItU0laRTo1NdAwJTA7UEAwUkZBkE1JTFkw0CdU/5BlphFO0tAgUs9w//An9TEwbSYALdPAI3E1 YDOA39GxM4GogKjQMNBChAD/8FxnQ5xgMzU0Imt8EG57e0Ew0S4xAzNS//AsAC0bpmB7UHUkcTDQ RU4tzFVTMzw3uEtPMzTVAK8LYDepQPAwgEEzNG4zcNd94fzgMNB5phAiLGstl15UFNEmPwnS1PBv xaFm5yOBenCHvjkyBwEvMik//y3fKI8CrwO/BM8F3wbvQv//CQ8KHwsvDD8NTw5fD28qr/8rvyzP Uw8u7y//MQ8yHzMv/zQ/NU82XzdvOH85jzqfO6//PL9Smvzv1wsffyCPgHpnQOd8AKwgpkBxdU5g Pq1B3/9K30P/RQ9vL1PvVP9WD1cf/1gvWT9aT1tfXG9df16PX5//YK9hv2LPY99k72X/nBVnb+8/ xdUUpsHUsHDSkKjRI2T/I9CpBCWzJESq1yWzq3tAwd//sH9Qho9MpKbBdarhbN//be9xz3APkC9G T0dfSG9Jf/+TL0ufTK9Nv07PT99Q71H//5kvcz90T3Vfdm93f3iPeZ//eq97v3zPfd9+73//gQ+C H/+DL4Q/n//7UalxIoGM/z/T//yx0aUnrY+fmJ+Rv5LPue//oa+iv6PPpN+l76b/qA+pH/+qL6s/ rE+tX65vr3+wj7Gf97Kvs7/Agkb60bWPmoK3UP/V0InAiXG3r7i/wC+639S//9XPvg+/H9g/wT/C T8NfxG//xX/Gj8efyK/Jv8rPy9/M7/fN/88P0B93/FDeQNFfmnPd6sB1JUDksIoDUeYw/xONZ0FT itT6AFFvU/vQ+7cR+sFtIqLiICXBHMCcEP0lgmb+oeDgFUGLNO0vmo//1B/X/9Y/10+ef5Tvlf+X D//4v/b/mj+bT5xfnW/5n5+P//6/2W/af9uP3J/dr96/38//4N/h7+L/5A/lH+Yv5z/oT//pX+pv BY8KIouY8z8AQowxSGZpeCWRSVAiQXT/8pPTL/V//n/3n/ivIH8Hj/8InwmvCr8LzwzfDe8O/xAP /xEfEi8TPxRPFV8Wbxd/GI//GZ+GQ2y+P5dssSwB75CMkP9sIe6g71AlAIvw7pGMoUBg9dExYbbw aIvQHWeGUS4A/4mSbDC28O9QLHBnMGxAhm+naEYDsCywYWOJYHLx8P3uoGMbTR7vIs8hDyIfBD// +q/7v/zPRF9Cn///AQ8CH/8DL0U/BU9KXyQ/JU8mXydv/yh/KY8qnyuvLL8tzy7fL+//MP8yDzMf NC81P1Eva8Q9z++N9D2hV3E/0XVfkDs3QC//QT9Vb0Nfar9rz1NPVF9uP/9Wf1ePWJ9Zr1q/W89c 313v/17/YA9hH2IvYz9kT2VfHXXzHf3SNy5nt4CIcIyQidD6Z++QdovweTCIE4mAPy5f77GIoH8A 8VDvYG4d0mPuYXPQfuDvYWl2oe+xgIAntQAd7tI3dGO3gEdp/nY6AGk/ak9uL2xvjR9Fb/9Gf0eP SJ+QH0q/S89M303v/07/UA9RH5Yfb59wr3G/cs//c99073X/dw94H3kvej97T/98X31vfn9/j4Cf nO89j7ZH5m1ogO6gdHW1AO+iOdj/i7+Mz6D/ju+2b7d/nt+f7/+576IPox+kL6U/pk+nX6hv/6l/ qo+rn6yvrb+uz6/fsO+/OniyP2ekPHHC4O+QYjlg94uA8BDMcG7CQMQhPKQ6Afsd8MxhZ/JRwuCI g++Q8fC7tBM/QW3ugMQg04BtOdD/knDC8PAx8UHPH5d/tc+5r/+377j/m2+R35Lvk//a/9k//5cv mD+ZT5pf29+cf+D/ux//vC+9P75Pv1/Ab8F/wo/Dn//Er8W/xs/H38jvyf/LD8wff+fP7GI9EIUw 8TDVf7NDb/+IgTlgiUPVMtDx1s/X3+wP/9n/AV8Cb+nv6v8E3+0f7i//7z/wT/Ff8m/zf/SP9Z/2 r//3v/jP+d/67/v/i4A8YNUBL2jg/W/igj1lZg+AIHfNhfBoseMOkHF15CAZwb+ISxFAseNo34P6 0Tgu/+//AP8IbwMfIk/cH90v3j/fT/8lT+Fv4n/jj+Sf5a/mvxgf/ytPBk8HXzKPCX8KjwufDK// Db8Ozw/fEO8R/xMPFB8VL/8WPxdPMh8g3yHvRn8kD0iPA0mfN4EmbmJzcDvhLqhcJ2EwMG8m3yfv /yj/Kg9MPywvLT8uTy9fTu//MX9UDzOfNK81vzbPN9847/85/zsPPB89Lz4/P09AX0Fv30J/Q49E n0WvX3RBg+AegPx1ZxwgHs9VstIAhQD+8f+IQB3wYVBs0NUh0HKx8NOR/2YwcJDUcdEwzoCLcM5h ZAD7iQCLcHKyAIeAiCCF8NOC7WgQZdFAVUBi/vEd5XDPlVWyZs6gdWVgIE1hAPRFVIgRZ4tj0GNH H0gv/18/Sk97f09PUF9Rb1J/fn//VJ9Vr1a/V89Y31nvbu+Ef/9dH14vi79gT2FfYm9jf2SP/2Wf Zq9nv2jPad9q72v/bQ//bh+LT54Aee0ayBvD/RB2wv94of+/eu+D730Pfh+lX4z//44Pjx+QL5E/ kk+TX5RvlX//lo+Xn5ivmb+az5vfnO+d/3+fD4SBduCHoNKweYByIHVvzv+FpNHg0UBzsGB5MGJf zqD88bFgG+D/AHfUQGx1HmFhdHF2raDOwL0hY3uw4HJBeKnwtDDRQNUQcx4v0pHVQMEgv4AuIEk/ HfCgUKKBvU+Fs7/wcmT/eSGjD6Qfq4+mP8avf1+Ab/+Bf4KPya+Er4W/hs+H34jv/4n/uz/Pr6lv qn/W76yfra//rr+vz7Dfse+y/7QPtR+2L/+3P7hPuV+6b9Z/HeHDfxsD78Tgw0H/geCAYx1i4eCi 7//GL88vyE/JX/Cf2D/ZT9pf/9tv3H/dj96f36/gv+HP4t//4+/k/+YP5x/oL+k/6k/PwHG+4Gxm LXIwHZD9sHPz/iDA0G4vB7P8IQRxIILP65/Q4/0AchBjdL097w//8u/xL/I/De/0X/Vv9n/3j//4 n/mv+r/7z/zf/e/+/wAPfwEfAi8DPwRPBV8GbxSCYr0acGXAMAnfoZR2w2N4kF8aUAmhwSAa0MFw dHkwZLZ5CUAbIGMSkKIgdNRgzR0BL76gckBveR0BwwD/ToALrwy/FC8O3yu/yo/Ln//Mr82/Lr/P 39Dv0f/TD9Qf/9UvI980vxIPEx87/xU/Fk//F18Ybxl/Go8bnxyvHb8ez/8f3yDvIf8jDzuPwa+9 PwrF/b9RbqIAQgB5cDmwdcLBQKvE0EcBdMLAQURweb0Q/0kQCZEIkSVRdqFU4UGwRPA3RpB1cT7w YXlAToB1cDAgKGNsvSDuAHIp/1GvoYQ+8HjToDG+oERwRaH/Kj8rTzRPLW9b3y+PMJ8xr/8yv17f NN817zb/OA85Hzov/zs/ZN89Xz5vP39Aj0GfQq//Q79Ez0XfRu9H/0kPSh9LL/9MP01PTl9rr3Hx CHNx0KIA31f/ZjJ2QHHgVtB3KSByMO9XQILBJwFn0CB14HngCCD/wHII4MJw7dCiAFPRdrB4gD91 IGnggsFuUH6wv+Aucv4uv1B18GmgwwRX0HUwJW/nxGWig79wbW92EIawwHBngTFZ0lPDbnbCkMBw ZP9af1uPb79dr4y/X89g32Hv/2L/j79lH2YvZz9oT2lfam//f2+Vv22fbq+c/3DPcd9y7/9z/3UP dh93L3g/eU96X3tvH3x/fY9+n5yPoS4mbmKFCzA7mRhcJ2Ew6t/3iA+mYKVQIFQg7gBVQYWx9mSn 8SbwcqphCEGfAKcgvaVwKO3QVjFTUMBQcAtAJ8LwVcElIHR0owBmadtToZ8AdKrwCIIpxR1Yxv+L T4xfsO+Of71fvm+eb59//8DfoZ+ir6O/pM+l36bvp///qQ+qH6svrD+tT65fr2+wf8+4Ebqfu6JT 0WJluUDtJP9XgLYR02DtkIRTVwEIICnh/1EfvF/AP8FPv4+P/5EPkh//ky+UP9vPll+Xb5h/mY+a n/+br7Cvwa/Cv8PPxN/F78b//8gPyR/KL8s/zE/NX85vz3/f0I/Rn9Kv07/u+CjZQPzAP4ci1Y+I xCjwhvC141FvvlNVEejg9HC3gPiQKVSQ/k8m5IcTuHGHkFaAiREm5PeEF4mQ/BBshPLxANcytH/3 1oeJ87cxZPRQVoAnAbjR/1MQ1urZv9rP7v/c7wv/3w//4B/hL+I/Dv/kX+Vv5n/nj//on+mv/q8U /+zf7e8cP/AP//Ef8i/zP/RP9V/2b/d/+I//+Z/6r/u//M/93xvP17IG/78WQiXx2D/ZRFSRWIBo VxA0Z2hWgHMB4RmwLW+/ifG4M4rFAiQ1IgPQYQSRfzEPFkIDwFPRJiC3MLZQZ3+FEyYgJtAZ8ALQ JmAmwGP7hbFWoXeJUVpB14EKjwuf/x/PDb88zw/fEO8R/xMPP8//FS8WPxdPGF8Zbxp/L39Fz/8d rx6/TQ8g3yHvIv8kDyUf/yYvJz8oTylfKm8rfyyPLZ/vLq9Mnznx18ByhHE3L7Wj7zpASnAFMlZw dWOhM+A7X/88b1CfPo9l/0CvQb9Cz0Pf/2j/Rf9HD0gfSS9KP0tPYE//bv9Of0+Pdj9nv23vei+y X/+zbmofay9sP21PfF9vb3B//3GPcp9zr3S/dc9233fveP/djHRQUxBW4AUyZtdUZBHYIElNBmG4 sHIEojow7wIQNbFVcNjAZzjxVYA4c9diL4ZCX4FiUxBtA7Ey4b80cGPRtqGTMVdQ1xBkOdB+eJHx VVFXQFWABHGOMW3udQVyt8EDcFQD0ZHTk7/VhjNk1yBhV6Bzem97f/9pb4B/gY+Cn4OvjF+Fz4bf /4fviP+KD4sfjC+NP45Pj1+bOuJW4CBXIDmwb3dVgP46my+cP51Pnl+fb6B/oY//qj+jr6S/pc+m 36fvqP+qD/+rH6wvrT+vT7Bfto99n36v/7xfss+z37Tvw/+3D7gfuS//uj+7T8e/vW/M37+PwJ/B r//Fj8af1//ZD9of2y/cP8c838Jfw2/Mf9Uv1jQz1q4x0fXjV1MDcEcy8DUxAyA0kNfncZlvzkJT MqBh6eBZMNdVcFKwNJBHA3BQ6fCu4Op1NJBBA3BNOlBYADjgo+gRUT9TVFLWAEfWq9Zij7pfkGc4 4G1WAJVB6+twXcBkUxB3OuJXIApBRwPR6H/OQkR5bleBY/87T2WB7U7jP+F/9H/Hz8jf/8nvyv/3 f80fzi/PP9BP0V//0m/Tf/1/5K/lv9e/7I/tnz8If96/388Lzwzf4B5EZbpwruB5l1I2cNcwU2HR /zowVXGXsvEv/tLvITOUkpGfXpCW0DRA8tBVoHR38LD+a5sc88/3rjSQOyGR4Jkg/1KxFWHw4u8h Y7CWwFlxVYD/X7AO3w/v4Evw7zHW9d/27//3//kP+h/7L/w/Dl/+X/9v/wB/AY8CnwOvBL8Fzwbf B+8/G38cjw4fM280f+CWSUXBOPAvSUZJUJGQV0D+Ze9RkzATUOuA8pBeYBIj0lMSEHBv1kB1lXAe rxUo8iiRoCfXkDA1Ka0ZYE4S4RlgRuvQbj2i5zjiGWDrgHkgPRLoXSDP/yHfIu8j/yUPJh8nLyg/ KU//Kl8rbyx/LY8unzYfNy9MP/9Cr0O/RM9F306PR/9JD0of70svUT9NT1ZYV65gFcCZIA+TZBYw mCAVoWVscC7/Ud9S71P/VQ9WH1cvWD9ZT/9aX1tvXH9dj07/UA9RH2Bv/2F/Yo9jn2xPZb9mz2ff aO+3af9rD2waQ5jQErBzb7//cM9x33Lvc/91D3Yfdy94P/95T3pfe29s323vbv99L34//39PgF+J D4J/g4+En4Wvhr//h8+I2unCmSPqBox/jY+On/+Pr5C/kc+S35PvlP+WD5cfTZgvQxIx8HVDb++A dWZu8sA54GlvFXA64HP1OfBtExBSEwAZ4aPgmk//m1+cb51/no+fn6Cvob+iz3ej36Tvpf9VqADn 0dZAdNM+4BJydXKnQHmpn6qv/6u/rM+t367vr/+xD7Ifsy9jtD+1T0d1aV+Q8KFk/7efuK+5v7rP u9+8773/vw+/wB/BL8I/w0+3NOeQVRdg+DdYSMTvxf/HD8gfyS//yj/LT8xfzW/Of8+P0J+2UfU5 8ksbAWSnwNKP05/Ur//Vv9bP19/Y79n/2w/cH90v/94/iZ+Kr4u/4H/hj+Kf46//7F/lz+bf5+/o /+oP6x/sKoJUX9AgOiArNPMQECgwKSAwUTMgNvA4OTQ5PzDvz/Df8e//8v/0D/Uf9i/3P/hP+V/6 b/f7fy+PMJkyMV4EEQpfP+//Ag/sv+3P7t/+T/9fAG8Bf/8QjwOfBK8FvwbPB98I7wn//wsPDB8N LyCvD08YXxFvEn//Hi8UnxWvFr8XzybfGe8a//8cDx0fKY8fPy6vIV8ibyN+ikSoMGX8wFRodT5A cf1gIEFwMGA9Ev1QMSA6MDM6MTfQKzCWOT8QNuwxMXFCUjJZmzOA38BlL0A2SEZyp8Dp/MBGYV8w YTQAL0stcKkwNEFkfJBtmSFkMeC2ccRgJz8mNTAomTw2SIxmYaigQGBAYWpfcEAuYWMua3JC32c9 Q/o+Nk89Pz5P0TdiaohlY3T8wFttYT7gOHRdIEKQmgCoQ2Fi/V9wdECPMEM4UKfgNTE+4D9fcF9A T/CnULcBMeBmZv+2kKcRTf8wQz/QTdDfwUkP/0ofPuxGfyhfKWpV/1cPWB//WS9aP1tPXF9db15/ X49gn79hr2K/Y89k32XvZvIgO2DAb3RvY29sqPDfwHdNkDhB39Bsp1BRPzBSTXBBTkVUUv9UDz7s VCZv/MBMo0BpTNBmLm/EsFLvbi8+3U2aAJoQZ/BlLUlE/MBrjzBfQ6/VRLkwJUA0eOBjeQExYGAk MjE5M/3gKWAkAGRjYzI2YmQylUXDZEVwaJnQeXV2X/9Hj2bPce9y/6bDqGCowKcg8C1UeXA6oXUP dhKowCB4dC9wbEAwbjv/e59oT2Z/hF+Fb4Z/h4+In/+Jr4q/i8+M343vjv+QD5Efj2nTM8B2EKkw dD0iQEAAby04ODU5LTF+In4vfz9VH5bPl98/GUjnQr1BZkBgbCyZn5qvPuzQSSB3Yajwd6hgQfB+ ct/BarA2EN9garCo8HDyb3RgaWJrUUyw35A7YL9GIKhAqCA0AGpQUBN0obD/UI9Rn1Kvnx+gLy8g ai9rM0ls0yA/oUF0aN/Aa/2iQnejUaVQUBGiEqTCpvX/pZ92A6pnp2+ofz7srGClYN2icnfEcDQA TKBrpKRQMPxnbaVhUAC3AavEo3KzYSetMU9wTUAgYqNRIG7Ob0Hwrn92AyhnOoGhcPx5KbBvsX8+ 7LbQpMBCAO9q0LNhUDG0x3escDPAUBD/odJNQKNxUABNsKxgrfeqaP+kUbd/prP8kHsguV+6b7KN /6PApSCkAEVQP9FQUD7gtLbvpEJMsL7xpUAuwi/DPz7s7k+8s1BQtiIge0Ch0DsAv6zEoXClf4Lm tKGz4HS98f/Fp78+xqnHb8h/PuxB8IHAe6HQohJ1ouDKdEzBobByv6ygzE92Eqqw07FNUnM7AF+z 46KBttGjuKwgRnEQIOmDYGFtg6Blnk/Rfz7dt9/A1rGeEXms4ntAdrbiv6pho9LdUdUvprnPOHK+ IPvccKIhYk3RxUCBUDBglfD/tPCkQE9gmMHZj9qfsq1wUPxvYrPw3IDc4FBhtyJqov5jpVChgN4v 1hc4UKHhTaBv3NG15apQpUBmcRBMoWP/UEPdp+Jf428+7N+forFB8Bnm1GQu5z92A05vd//Lis2Y xrKt8Obw6x/sL+0/b+5PnjDXJ+axdTBgavBsr6qA8E92A1Bhb91QcrNwPmGjkKwhaqH5QNfqSWb/ 9A/1Hz7s4cLF8ntA74HF8v9MsNzgg2Dp4eIhtRWsYVAA+/lvdhJrayCjkWtQ5wKlUP+lMaJywF91 5bTwx1/9328++csxa3MGrwe/mK8KTwtf/z8LQDMKHw4vDD8QvxHPEt//E+8U/xYPFx8YLxk/Gk8b X/0vES0fnyBqHJ8drxu/Ia/vIr9zn4HfdeU1JH8ljz7sEzp/O4QwNjwAODo0/jM8YS5xKW8qfz7v P/EJsuG+AE5ndXmzgSgPdh9Xdy9EuTITLjJ0QKVgZ/ou5ZBuAGA3APAQRgF7j798nyP/L08wX0u/ TMNBAPE/xfJPYNkhxmMy7zPyQU/8RFbF4auw5aYxsNkAUED+V9ThOz88T29PcF9Dj0SfPya/dJ8z jzSfNa8tADMwyi55wDRPUDM2T1BPQYNIUHngNTgzMTdP0fF54UBteTfPON857zr//0hfSW+BH0tv gzpUv1XPI5+/Wr9bzyu65vC4kOIwbbbQ/5WA2V9ej1yfYX9ij6Cc2QD/81MEQExQvfG2oHsAQCIs cL9XoEAhtlHqEViPTENUweB/77Ax0LaA3HCkENbDo2NJ5m7qE9bCIEWrcDDBofSAKENUSUUpLEIw +VFyIFXccPrxrXDl8b3EX2m/TFLTcN1Q+SBwq7BJnFB2ZUCkgnHDc3XcgJPqgasQT23UoSsrEI// ZV9jb3PfdO9mn6G4vwBo0f8CMbYkAOJv7/pzxgG9wKTg/z/IQbPPR0IPQxO9tQIx3UCfEDCDsKMy 1DFSLjxBTCQOaARxlcB2IHRwOi+cL3eEMEdAc0JwcEdCXiJ3+XbQxWDB4GR20mYHhjCrYLage0hZ UEXAUkxJTksgg7+ExTx9fYXhhjCVgFKwXGPwZjFcde9QdhiHz4TTn5PXk8d2kIxvdo45Mnew/C9B d/B2v3fPdd+Qb5F/9wkOe79MQ3mnAHOvlD+ST/+YT5lflX5vz2qlviBHf5wv/5o/oD+hT6Jfo2+k f6WPpp//p68fP6y/IV+qD6gfrg+vH/tJvyezNrD/sg8rj1hvapb3LN5PIC4gMC3wTBAuYC2Br7Sf ta8w3zHhUgSAaYBg/X9AbIEgt+9MT01fNgq+k94uvvM3gPjQazIuxaDArz9TP7CPu9+87z3/PwJF U/RBUy10LfkQAGBAQNhB/+9QaX/AJsBQ6eHmkMvQ03Df+0C9Mi0ygUAtADjHL8g//0WPRp/P79D/ sz9K37//wQ8Bwh8gNDI1RTU27U9xN7rxTzA4w+/E/8YP38cf1O9Wz1faWeg715/oRFeeMG8g03A9 chAtAGBj7Glp5EBslD2GkPGw8BC/38/g37Af59/o772JKM4wfb8Ab21Q1vDMg2tw3cBpfwQBzDBx gO4SAe9qSjIwbvf3EPiwQAMp6q/rv+nP8m8r83+9iUzLUFRXoEFMgkwxoE9SIFBBhzHly2AocqBi be/gbzB/Ef/Ovyzw8B/Ysi2C8i/2P6svfwAvAT/9H/4vyU3cwWxBRf/coHGAzsAywEMibqBxgft/ f3zUAl8DbwR/3KBCgmwyUPt6UIEgY3ughsAtMGxQfWDeY2wjBVBsAMyhTtNwegD/BnEIXwlvvVzL Nw5/D4/0X4eCH4MvhDJjcnlzF7DaLizQL8syLYIvhS+GP/+HTxd/GIOJP4pPG78YRo2v/41/FK+P nxJ/E48jFQyhBu/b5XNucGrxoWzjd0KAaDB7eyExoGlvIEBAbHBX4HLvUXBs4sxQV6Jme0HxsX8C /lcqsGsR1wAk3yXveN0rEwfTcCf/2KMoV0lDTy5O/Q8uT71NVu/gZWe1QtBkuXBIn+HYsHm5cI5K HlB7oLmQLTE1+1///GgynzOv/z88Pz1PPl8CP/86Dy9PfaDTsEAwfgE3j3Dz/7ehLT9An8k/+bdg gc7jypD/WfF98PpAbFB+sPrJON9Fr/dGvw3gfqBpGaBrtO+CQz/p2LJBY/HAcELh8cDXgPxNYXug ugBKb0t/TI/1AZ0GV1ZvEkhbUNIzMVE//1JPU19UadeP2JQ2ylbPV9/fWO8MEX7AbYAaUWfv8FUv +bmwdWdyEEMQN084X11P/15fO49nj2ifPr9kT2VfL5v5GoBydSmz7//YlMySYdD/eqDTsETPa5+9 TW/1ecB7UX0aYHZ/kEmE+ZNDENOwaffuACuiziQuubDMYfmYbk/32JQqEMxhYhQxcI9xnxRK/4Nx LCHngHYwR9hwX3ofvU1/7pDMEfGAQxD5kRqAQvFp88xRNvBkdePwThIscA4if++xTjB3T/EVNvDv kyxwYbtzdZ4wdnkPfm+9TXDKMN+9MAaQSYEZwDWwdypwc/H/zKGFn4avh790xXRiJ9HYof/MURnA djCDH7kELHB2moBn/+OwYCK6QIix1yF9X4uP7L65kdFsdWBSKlNOQHTu8XeO/83k1zAsks+T371c Ys5piPHt8DXgcGgLxM4wb+NgC/BOENbwKYChuRAx/yRgknPvgIpgjnKO0JBCGaD/K6KXH9iynmH5 8pi/mc+Mrf8GoB5QDACRmmQPok+H7pKC/57Ez1B8ItywDAD5mebUJ8BxdzBQREaffwfkuRBQWm8a gFMf0O7QdI7QV3+Kf6aPey/c0fHhSZGC0nn98ZAg1zC9UDXg4vCtz67f/71cKmKrIqyyy2AZoO7x YgAHljKrb9iyTGFUZVhjC9MqYkxOQ8tgGoB5v+7xilDkEOQAiPCE8XSyf3ezj0G8H5Jzz1GWQCwg LsX6QC/c0XAvbPGwF+D3uq+7v0G8RtygKmHMv9iU3xpg5tROUyfgBqB3dJnOJd94pbnZLJEqYudw Yr9PwF//jK10UYSWws94Y1oWyB/JL/8ULxU/Fk8fnxhvGX8aj9LP/xyvHb8ez9fPIO8h/9A/JB// zg/PH1l/y8+YFGAI4I/hn19BvJBCX/rGVojYYjbwU/u99QvQZishKlPjj8NNKlLv5h/nL/ddsNB0 C4AscE3B/54h1hDu3+/vQbwr4EKgcADvwpGtINVgLFIouTKdYAVQv3VQniHtLzHjva++timO0P9N wixhgsLy3/PvJv91QElw/+wxdLB4//yP/Z+/AJYBjfT/y5/k72CAXJCE2k6RQvAL0P9QI0mBxeOR M/9/AI9BvGHw/45hKxGWkXSwqTE1sEMPMbX/KmEqsAfvCP9BvClRbcCbwP9wAKpCguEqYtPiDC/M 278//w7fz88UbxV/Fo8XnxivGb//Gs8b3xzvHf8fD2bvaZ8gX98hbx9/JW8mfyeIXysvLD/fLQoo Lyk/f41C8GUMH/i0/6qweLCWMokBB98vHzAvMTHWQNVgJ+AudUBnM480n5cnT9Dv0fxz2xQxLjbm /i8ywjERvuAzUcQSPZExMf/Uf9WP1po8jz2fPqXZD9oe/0HvQv8+pN3/3c86D9/vN9//OO9LH01/ To9Pn1CvUb8SAN+ckTF/rHNUoDEURHVgniBydFyQVm91sJ3AXJBJ/aogdQNf+LRcQFLfU+9svP4q Xc9e318AWs9b32y8Sk/zOjFgOTcyYWf4skmYYBCFYBwwO0EvRElWYVkjSt86xTI0OExxRk/8TlRM vmefaK86p2Lx+MMLbc9u3zVqYkJPRFkvTL1MYHAPaiE3THFIVBRNTEywfXTAAAAeADUQAQAAAEQA AAA8QTU5RUM4NzZERjRGRUI0Mzk3NzFGREREN0UzQzcyQ0I5NjM1QUZARVZTLUVDMS1OT0RFMS5z dXJyZXkuYWMudWs+AB4ARxABAAAADwAAAG1lc3NhZ2UvcmZjODIyAAALAPIQAQAAAB8A8xABAAAA jgAAAFIARQAlADMAQQAgAFsAbQBhAG4AZQB0AF0AIABxAHUAZQBzAHQAaQBvAG4AIABhAGIAbwB1 AHQAIABzAGkAbQB1AGwAdABhAG4AZQBvAHUAcwAgAHUAcwBlACAAbwBmACAAZABpAGYAZgBlAHIA ZQBuAHQAIAByAG8AdQB0AGkAbgBnAC4ARQBNAEwAAAAAAAsA9hAAAAAAQAAHME3lTW4WQcUBQAAI MF1qcjMcQcUBAwDeP69vAAADAPE/CQQAAB4A+D8BAAAAKAAAAFNpdmF2YWtlZXNhciBTIE1yIChQ RyAtIEVsZWN0cm9uaWMgRW5nKQACAfk/AQAAAEgAAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAA AAAAL089VU5JUy9PVT1JU0JTU0lURS9DTj1SRUNJUElFTlRTL0NOPUVFUDVTUwAeAPo/AQAAABUA AABTeXN0ZW0gQWRtaW5pc3RyYXRvcgAAAAACAfs/AQAAAB4AAAAAAAAA3KdAyMBCEBq0uQgAKy/h ggEAAAAAAAAALgAAAAMA/T/kBAAAAwAZQAAAAAADABpAAAAAAAMAHUAAAAAAAwAeQAAAAAAeADBA AQAAAAcAAABFRVA1U1MAAB4AMUABAAAABwAAAEVFUDVTUwAAHgAyQAEAAAAXAAAAbWFuZXQtYm91 bmNlc0BpZXRmLm9yZwAAHgAzQAEAAAAXAAAAbWFuZXQtcmVxdWVzdEBpZXRmLm9yZwAAHgA4QAEA AAAHAAAARUVQNVNTAAAeADlAAQAAAAIAAAAuAAAAAwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAG EB9FlgcDAAcQ/BYAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABERUFSRkFJU0FMOldFQVJF Q1VSUkVOVExZV09SS0lOR09OQU5JTlRFUlNUSU5HUFJPSkVDVENBTExFRFBBTihQUk9HUkFNTUFC TEVBREhPQ05FVFdPUktTKSxUSEFUSU5WRVNUAAAAAAIBfwABAAAARAAAADxBNTlFQzg3NkRGNEZF QjQzOTc3MUZEREQ3RTNDNzJDQjk2MzVBRkBFVlMtRUMxLU5PREUxLnN1cnJleS5hYy51az4ARvM= ------_=_NextPart_001_01C5411C.335F5795 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------_=_NextPart_001_01C5411C.335F5795-- From manet-bounces@ietf.org Thu Apr 14 16:42:31 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24585 for ; Thu, 14 Apr 2005 16:42:31 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMBKa-0001Wk-Vi for manet-web-archive@ietf.org; Thu, 14 Apr 2005 16:52:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMAWW-0000db-Jc; Thu, 14 Apr 2005 16:01:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMAWD-0000XU-TM for manet@megatron.ietf.org; Thu, 14 Apr 2005 16:00: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 QAA17829 for ; Thu, 14 Apr 2005 16:00:51 -0400 (EDT) Received: from che.ojctech.com ([209.254.158.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMAgE-0007HR-LY for manet@ietf.org; Thu, 14 Apr 2005 16:11:17 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id j3EK0fu6015772 for ; Thu, 14 Apr 2005 15:00:41 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id j3EK0eDw015770 for manet@ietf.org; Thu, 14 Apr 2005 15:00:40 -0500 Date: Thu, 14 Apr 2005 15:00:40 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] question about simultaneous use of different routing protocols in a single MANET Message-ID: <20050414200040.GX6156@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: <20050414163547.11620.qmail@web25406.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050414163547.11620.qmail@web25406.mail.ukl.yahoo.com> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb 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 On Thu, Apr 14, 2005 at 05:35:47PM +0100, Saqib Ilyas wrote: > I think that the idea of administrative distance could be exploited > here. If the network is not "wild enough" then the node somehow modifies > the administrative distance of the more suitable protocol to favor it, > and later set it back when the going gets tough. Just my two cents. An aspect of Adaptive Hazy Sighted Link State (A-HSLS) may interest you: it changes its operating mode from standard link-state to HSLS when, as you say, "the going gets rough." A technical memo from BBN Technologies, , describes A-HSLS. BTW, an open-source A-HSLS implementation is part of the system that the Champaign-Urbana Community Wireless Network is developing. See for download instructions. Dave > Regards > > Faisal Adeem Siddiqui wrote: > Hi all, > I was wondering if it is possible and practical to use two different routing > protocols in a single MANET ? I think if we are using two routing protocols > then it will make two segments of MANET and there must be a node (gateway) > between these segments which understands both routing protocols to relay > traffic from one segment to another. > On the other hand, if we want to switch from one routing protocol to another > depending upon the network conditions, will it be practical ? For example, > initially we have a proactive routing protocol running but after some time > the mobility of nodes increase considerably and the performance of proactive > routing protocol is decreased. Now if we want to switch to a reactive > routing protocol, will it incur a lot of overhead ? Is it practical ? If > someone has done any experiments of this kind please refer it to me. > Thanks. > > Faisal. -- 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 Thu Apr 14 20:25:08 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14895 for ; Thu, 14 Apr 2005 20:25:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMEo3-00034E-GF for manet-web-archive@ietf.org; Thu, 14 Apr 2005 20:35:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMEc0-0006JE-3i; Thu, 14 Apr 2005 20:23:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMEbi-0006EV-DA for manet@megatron.ietf.org; Thu, 14 Apr 2005 20:22: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 UAA14789 for ; Thu, 14 Apr 2005 20:22:32 -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 1DMElW-0002xt-PI for manet@ietf.org; Thu, 14 Apr 2005 20:33:00 -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 j3F0MUJJ003873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 17:22:30 -0700 (PDT) Date: Thu, 14 Apr 2005 17:22:30 -0700 (PDT) From: Manoj K Pandey To: manet@ietf.org In-Reply-To: <20050414200040.GX6156@che.ojctech.com> Message-ID: References: <20050414163547.11620.qmail@web25406.mail.ukl.yahoo.com> <20050414200040.GX6156@che.ojctech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on vitalstatistix X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [manet] SYNCHRONIZATION_TIME at Radio Layer X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Hi Everyone, In glomosim SYNCHRONIZATION_TIME is added to every frame that is being sent at the radio layer. And this is a large amount of time (192 micro-second). Why do we need to add SYNCHRONIZATION_TIME to every frame (RTS/CTS/DATA/ACK/Broadcast)? Isn't synchronization done only with PCF of 802.11 and not with DCF? Also isn't sychronization used only with FHSS (stations needs to synchrnoize the next frequency) at the radio layer and so do we need this when we use DSSS? Is SYNCHRONIZATION_TIME added to frames in other versions of 802.11, which support higher data rates than that provided in glomosim? If so, what is the value that is used? Thanks in advance, Manoj Pandey _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 14 21:01:12 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17363 for ; Thu, 14 Apr 2005 21:01:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFMy-0004ME-1M for manet-web-archive@ietf.org; Thu, 14 Apr 2005 21: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 1DMFAG-0003gd-HZ; Thu, 14 Apr 2005 20:58:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFAC-0003dI-Fq for manet@megatron.ietf.org; Thu, 14 Apr 2005 20:58: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 UAA17188 for ; Thu, 14 Apr 2005 20:58:26 -0400 (EDT) Received: from primary.vmtllc.com ([216.64.2.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFKH-0004GH-7T for manet@ietf.org; Thu, 14 Apr 2005 21:08:54 -0400 Received: from amd2100 (localhost.localdomain [127.0.0.1]) by primary.vmtllc.com (8.11.6/8.11.6) with ESMTP id j3F0wKA06660; Thu, 14 Apr 2005 20:58:20 -0400 From: "Herbert Rubens" To: "'Manoj K Pandey'" , Subject: RE: [manet] SYNCHRONIZATION_TIME at Radio Layer Date: Thu, 14 Apr 2005 20:58:07 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <000a01c54156$30647510$6501a8c0@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 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: Importance: Normal 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 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: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit During the first 192 micro-seconds the radio transmits a training sequence so that the receiver can establish a phase locked loop. It's 192 micro seconds in 802.11b/g and I believe it's less in 802.11a. -Herb -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Manoj K Pandey Sent: Thursday, April 14, 2005 8:23 PM To: manet@ietf.org Subject: [manet] SYNCHRONIZATION_TIME at Radio Layer Hi Everyone, In glomosim SYNCHRONIZATION_TIME is added to every frame that is being sent at the radio layer. And this is a large amount of time (192 micro-second). Why do we need to add SYNCHRONIZATION_TIME to every frame (RTS/CTS/DATA/ACK/Broadcast)? Isn't synchronization done only with PCF of 802.11 and not with DCF? Also isn't sychronization used only with FHSS (stations needs to synchrnoize the next frequency) at the radio layer and so do we need this when we use DSSS? Is SYNCHRONIZATION_TIME added to frames in other versions of 802.11, which support higher data rates than that provided in glomosim? If so, what is the value that is used? Thanks in advance, Manoj Pandey _______________________________________________ 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 Apr 14 21:28:35 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19197 for ; Thu, 14 Apr 2005 21:28:35 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFnT-0005Ls-3k for manet-web-archive@ietf.org; Thu, 14 Apr 2005 21:39:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFbA-0000xk-Us; Thu, 14 Apr 2005 21:26:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFb8-0000vC-M6 for manet@megatron.ietf.org; Thu, 14 Apr 2005 21:26:18 -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 VAA19043 for ; Thu, 14 Apr 2005 21:26:11 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.201]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFl9-0005JN-3Q for manet@ietf.org; Thu, 14 Apr 2005 21:36:40 -0400 Received: by rproxy.gmail.com with SMTP id a41so527438rng for ; Thu, 14 Apr 2005 18:26:11 -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:content-disposition; b=fZqTe4IXct9QFsIJ1GNo00gBHgz/QcN78W0fINsdmowAgvB/cCduzajc7br2iRzUQYFN6/v8pY0QOpCtPesfcC0IeGurpzDR5YLpf+I8pYPlf1DLU5qYIlzihr1CJc0hryK2NmPRFaSz7KpF6xgsgJYxrXAR6roTBG6ucaHnhxY= Received: by 10.38.86.53 with SMTP id j53mr2539352rnb; Thu, 14 Apr 2005 18:26:11 -0700 (PDT) Received: by 10.38.125.21 with HTTP; Thu, 14 Apr 2005 18:26:11 -0700 (PDT) Message-ID: <89f024905041418266b05c79a@mail.gmail.com> Date: Fri, 15 Apr 2005 07:26:11 +0600 From: Usman Gardezi To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: quoted-printable Subject: [manet] question about simultaneous use of different routing RE: protocols in a single MANET (Faisal Adeem Siddiqui) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Usman Gardezi 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: quoted-printable hi=20 In general the idea of switching b/w routing protocols within a single MANET may lead to lots of overhead and inconsistencies within a single network and the emphasis is laid on MULTIMODE protocols or some sort of adaptiveness in response to changes in network conditions .. some of the work which I know " A FRAME WORK FOR MULTI MODE ROUTING PROTOCOL FOR MANET" by Cesar Santivanez and Ioannis Stavrakakis Boston , and many others related to adaptive protocols you may search ... Regards --=20 ~ Gardezi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 15 03:44:15 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02664 for ; Fri, 15 Apr 2005 03:44:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMLf4-0001Vc-E5 for manet-web-archive@ietf.org; Fri, 15 Apr 2005 03:54:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMLLB-0001jm-Pi; Fri, 15 Apr 2005 03:34:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMLKv-0001i9-9P for manet@megatron.ietf.org; Fri, 15 Apr 2005 03:33: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 DAA02139 for ; Fri, 15 Apr 2005 03:33:44 -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 1DMLUq-000189-B6 for manet@ietf.org; Fri, 15 Apr 2005 03:44:15 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id 0545219E6E4 for ; Fri, 15 Apr 2005 09:33:27 +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 23817-07 for ; Fri, 15 Apr 2005 09:33:26 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id DF4FB19E6E1 for ; Fri, 15 Apr 2005 09:33:26 +0200 (CEST) Received: from afontenayssb-151-1-59-78.w83-114.abo.wanadoo.fr ([83.114.93.78]) (SquirrelMail authenticated user badis) by www.lri.fr with HTTP; Fri, 15 Apr 2005 09:33:26 +0200 (CEST) Message-ID: <1390.83.114.93.78.1113550406.squirrel@www.lri.fr> Date: Fri, 15 Apr 2005 09:33:26 +0200 (CEST) To: manet@ietf.org User-Agent: SquirrelMail/1.4.4 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: 1.1 (+) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: 8bit Subject: [manet] An update QOLSR 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: 1.1 (+) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 8bit Hi all ;==) I have submitted an update individual draft version (00 ==> 01), which focuses on QoS in ad hoc networks using OLSR (QOLSR). Major changes from version 00 to version 01 - Generalization for all possible QoS metrics. Available bandwidth and delay metrics are default QoS parameters for QOLSR. All other metrics are optional parameters and used according to QoS flows requirements or network scenarios. - Introduction of an efficient QoS routing algorithm based on Lagrange relaxation , which provides a polynomial heuristic solution to multiple-metric constraints. Admission control and reservation mechanisms under multiple interfaces will be integrated in next versions. A more detail about QOLSR project and simulation code can be found at http://qolsr.lri.fr/ and an implementaion will be soon available. Any comments on the subject are welcome. draft URL: http://www.ietf.org/internet-drafts/draft-badis-manet-qolsr-01.txt Hakim. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 15 04:14:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04951 for ; Fri, 15 Apr 2005 04:14:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMM8S-0002p4-4m for manet-web-archive@ietf.org; Fri, 15 Apr 2005 04:25:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMLo3-0006Av-Hs; Fri, 15 Apr 2005 04:04:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMLnI-000628-9t for manet@megatron.ietf.org; Fri, 15 Apr 2005 04:03:17 -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 EAA04307 for ; Fri, 15 Apr 2005 04:03:06 -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 1DMLxJ-0002Pz-Uc for manet@ietf.org; Fri, 15 Apr 2005 04:13:38 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id 09BBD19E6F6; Fri, 15 Apr 2005 10:02:59 +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 26536-09; Fri, 15 Apr 2005 10:02:58 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id E3A1519E6E4; Fri, 15 Apr 2005 10:02:58 +0200 (CEST) Received: from afontenayssb-151-1-59-78.w83-114.abo.wanadoo.fr ([83.114.93.78]) (SquirrelMail authenticated user badis) by www.lri.fr with HTTP; Fri, 15 Apr 2005 10:02:58 +0200 (CEST) Message-ID: <1914.83.114.93.78.1113552178.squirrel@www.lri.fr> Date: Fri, 15 Apr 2005 10:02:58 +0200 (CEST) To: manet@ietf.org User-Agent: SquirrelMail/1.4.4 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: 1.1 (+) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 8bit Cc: alagha@lri.fr Subject: [manet] An update QOLSR 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: 1.1 (+) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 8bit Hi all ;==) I have submitted an update individual draft version (00 ==> 01), which focuses on QoS in ad hoc networks using OLSR (QOLSR). Major changes from version 00 to version 01 - Generalization for all possible QoS metrics. Available bandwidth and delay metrics are default QoS parameters for QOLSR. All other metrics are optional parameters and used according to QoS flows requirements or network scenarios. - Introduction of an efficient QoS routing algorithm based on Lagrange relaxation , which provides a polynomial heuristic solution to multiple-metric constraints. Admission control and reservation mechanisms under multiple interfaces will be integrated in next versions. A more detail about QOLSR project and simulation code can be found at http://qolsr.lri.fr/ and an implementaion will be soon available. Any comments on the subject are welcome. draft URL: http://www.ietf.org/internet-drafts/draft-badis-manet-qolsr-01.txt Hakim. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 15 14:49:36 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01490 for ; Fri, 15 Apr 2005 14:49:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMW33-0006Qe-44 for manet-web-archive@ietf.org; Fri, 15 Apr 2005 15:00:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMVjM-0006pf-8l; Fri, 15 Apr 2005 14:39:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMVjK-0006pL-Oq for manet@megatron.ietf.org; Fri, 15 Apr 2005 14:39: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 OAA00261 for ; Fri, 15 Apr 2005 14:39:46 -0400 (EDT) Received: from mta1.aucegypt.edu ([213.181.245.106]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMVtU-0005ru-By for manet@ietf.org; Fri, 15 Apr 2005 14:50:23 -0400 Received: from aucegypt.edu (smms1.aucegypt.edu [10.0.0.108]) by mta1.aucegypt.edu (Switch-3.1.5/Switch-3.1.0) with ESMTP id j3FIdMvV021331; Fri, 15 Apr 2005 20:39:22 +0200 Date: Fri, 15 Apr 2005 18:36:40 +0000 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "mhelali" To: "ns mail list" , "manet" X-XaM3-API-Version: 4.1 (B86) X-type: 0 X-SenderIP: 213.181.237.78 X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: quoted-printable Cc: cperkins Subject: [manet] How to identify RREP coming from Inter. node 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: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable Hi all Can any one tell me how to differentiate between a RREP issued by an inte= rmediate node and a forwarded RREP for AODV protocol? I was not able to f= ind this information in the RFC for AODV I know that a RREP issued by the= destination node can be identified since the IPsource address in the IP = header will be equal to the destination IP in the RREP header, but what a= bout the RREP coming from an intermediate node? Thanx _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Apr 16 15:21:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMsre-0000br-OD; Sat, 16 Apr 2005 15:21:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMsrc-0000ag-3e for manet@megatron.ietf.org; Sat, 16 Apr 2005 15:21: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 PAA00094 for ; Sat, 16 Apr 2005 15:21:51 -0400 (EDT) Received: from web80909.mail.scd.yahoo.com ([66.218.95.75]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DMt20-0002bw-Uj for manet@ietf.org; Sat, 16 Apr 2005 15:32:42 -0400 Received: (qmail 60589 invoked by uid 60001); 16 Apr 2005 19:21:42 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=HK2/A81yhp9Vs3+GDaWQG/awlZjjm701iY7c7TajZBB3FuKmv1iOj0DdsUBo5T8rFyQjK3xmaRGd/3O3YbK5ClB1GTaw4Zp6krY1LxI8HGMj5xVuABSvY2CJn0JqTkMpb8j8gEQGdhDrXdWvAOUpbLOz1p+TjTXXR/Vs7A+HRGw= ; Message-ID: <20050416192142.60587.qmail@web80909.mail.scd.yahoo.com> Received: from [203.208.193.197] by web80909.mail.scd.yahoo.com via HTTP; Sat, 16 Apr 2005 12:21:42 PDT Date: Sat, 16 Apr 2005 12:21:42 -0700 (PDT) From: Gokina P C To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [manet] QoS issue at MAC level 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="===============1605002758==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org --===============1605002758== Content-Type: multipart/alternative; boundary="0-909164283-1113679302=:59666" --0-909164283-1113679302=:59666 Content-Type: text/plain; charset=us-ascii Hi, I am interested in research at QoS issues at MAC layer. To the best of my knowledge there is no previous work which introduces packet prioritization in sleep/wake-up based MAC protocols in Wireless Sensor Networks. I am very much interested to know if anybody is doing research focused in this direction or in closely related areas in Mobile Ad-hoc Networks. Thanking you, GP. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-909164283-1113679302=:59666 Content-Type: text/html; charset=us-ascii

Hi,
 I am interested in research at QoS issues at MAC layer. To the best of my knowledge there is no previous work which introduces packet prioritization in sleep/wake-up based MAC protocols in Wireless Sensor Networks.
 
 I am very much interested to know if anybody is doing research focused in this direction or in closely related areas in Mobile Ad-hoc Networks.
 
Thanking you,
GP.
 

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-909164283-1113679302=:59666-- --===============1605002758== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1605002758==-- From manet-bounces@ietf.org Sat Apr 16 22:34:06 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMzbq-0004pr-KJ; Sat, 16 Apr 2005 22:34:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DMzbp-0004pm-7Y for manet@megatron.ietf.org; Sat, 16 Apr 2005 22:34: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 WAA26636 for ; Sat, 16 Apr 2005 22:34:02 -0400 (EDT) From: voberoi@mtu.edu Received: from mailoff.mtu.edu ([141.219.70.111]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMzmL-0001WZ-F8 for manet@ietf.org; Sat, 16 Apr 2005 22:44:57 -0400 Received: from node5.edge.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id j3H2Y2B23782 for ; Sat, 16 Apr 2005 22:34:02 -0400 (EDT) Received: from node34.edge.dcsint.mtu.edu (node34.mtu.edu [141.219.69.34]) by node5.edge.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id j3H2Y2wH025332 for ; Sat, 16 Apr 2005 22:34:02 -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 j3H2Y1vG032271 for ; Sat, 16 Apr 2005 22:34:01 -0400 (envelope-from voberoi@mtu.edu) Received: from node5.edge.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id j3H2Y1q05069 for ; Sat, 16 Apr 2005 22:34:01 -0400 (EDT) Received: from huskymail.mtu.edu (node74.mtu.edu [141.219.69.74]) by node5.edge.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with SMTP id j3H2Y1BV025329 for ; Sat, 16 Apr 2005 22:34:01 -0400 Received: from 141.219.193.31 (SquirrelMail authenticated user voberoi) by huskymail.mtu.edu with HTTP; Sat, 16 Apr 2005 22:34:01 -0400 (EDT) Message-ID: <2187.141.219.193.31.1113705241.squirrel@huskymail.mtu.edu> Date: Sat, 16 Apr 2005 22:34:01 -0400 (EDT) To: manet@ietf.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.0, Antispam-Data: 2005.4.16.18 X-PerlMx-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, NO_REAL_NAME 0, __C230066_P1_2 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 3.8 (+++) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 8bit Subject: [manet] Hello packets in ad hoc networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org Hi, I am a masters student and presently working on routing protocols for ad hoc networks. I wanted to know whether, HELLO packets which are used to update neighbor information, are generated at the MAC layer or the network layer? Thanks alot for your help, I really appreciate it. Vikram Oberoi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Apr 17 06:59:24 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN7Uq-00048q-20; Sun, 17 Apr 2005 06:59:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN7Uk-000489-4U for manet@megatron.ietf.org; Sun, 17 Apr 2005 06:59: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 GAA10471 for ; Sun, 17 Apr 2005 06:59:14 -0400 (EDT) Received: from bugs.comnets.uni-bremen.de ([134.102.186.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DN7fJ-0001nJ-Je for manet@ietf.org; Sun, 17 Apr 2005 07:10:15 -0400 Received: from IBM03126B99387 (bugs.comnets.uni-bremen.de [134.102.155.1]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id j3HAxAU17203; Sun, 17 Apr 2005 12:59:10 +0200 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host bugs.comnets.uni-bremen.de [134.102.155.1] claimed to be IBM03126B99387 From: "Asanga Udugama" To: "'mhelali'" , "'ns mail list'" , "'manet'" Subject: RE: [manet] How to identify RREP coming from Inter. node in AODV? Date: Sun, 17 Apr 2005 12:59:13 +0200 Message-ID: <000001c5433c$7eb2e840$8302a8c0@IBM03126B99387> 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: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Cc: 'cperkins' 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 Hello, >From RFC 3561, section 6.7 (one before last paragraph) this is the way that we understood (and this is how we have implemented also in JAdhoc & UoBWinAODV), Every intermediate node that receives the RREP will change the hop count and resend the RREP to the next hop (not forward as in a normal router operation). So you can determine the Source IP address form the IP header. Kind regards, Asanga > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > mhelali > Sent: Friday, April 15, 2005 8:37 PM > To: ns mail list; manet > Cc: cperkins > Subject: [manet] How to identify RREP coming from Inter. node in AODV? > > Hi all > > Can any one tell me how to differentiate between a RREP issued by an > intermediate node and a forwarded RREP for AODV protocol? I was not able > to find this information in the RFC for AODV I know that a RREP issued by > the destination node can be identified since the IPsource address in the > IP header will be equal to the destination IP in the RREP header, but what > about the RREP coming from an intermediate node? > Thanx > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Apr 17 07:08:29 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN7dd-00050w-SM; Sun, 17 Apr 2005 07:08:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN7db-00050r-T0 for manet@megatron.ietf.org; Sun, 17 Apr 2005 07:08: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 HAA10778 for ; Sun, 17 Apr 2005 07:08:24 -0400 (EDT) Received: from bugs.comnets.uni-bremen.de ([134.102.186.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DN7oC-0002J0-OB for manet@ietf.org; Sun, 17 Apr 2005 07:19:25 -0400 Received: from IBM03126B99387 (bugs.comnets.uni-bremen.de [134.102.155.1]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id j3HB8PU17303; Sun, 17 Apr 2005 13:08:25 +0200 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host bugs.comnets.uni-bremen.de [134.102.155.1] claimed to be IBM03126B99387 From: "Asanga Udugama" To: , Subject: RE: [manet] Hello packets in ad hoc networks Date: Sun, 17 Apr 2005 13:08:28 +0200 Message-ID: <000501c5433d$c8f76650$8302a8c0@IBM03126B99387> 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: <2187.141.219.193.31.1113705241.squirrel@huskymail.mtu.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Cc: 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 Hello, The Hellos described in RFC 3561 (section 6.10) refer to the packets that are sent (generated) at the Network layer. But the RFC also indicates that one can also detect link connectivity at MAC layer using 2 possible mechanisms, but not thru generating any packet. Kind regards, Asanga > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > voberoi@mtu.edu > Sent: Sunday, April 17, 2005 4:34 AM > To: manet@ietf.org > Subject: [manet] Hello packets in ad hoc networks > > Hi, > > I am a masters student and presently working on routing protocols for ad > hoc networks. > > I wanted to know whether, HELLO packets which are used to update neighbor > information, are generated at the MAC layer or the network layer? > > Thanks alot for your help, I really appreciate it. > > Vikram Oberoi > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Apr 17 20:33:54 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNKD4-0001SW-DK; Sun, 17 Apr 2005 20:33:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNKD1-0001SI-L7 for manet@megatron.ietf.org; Sun, 17 Apr 2005 20:33: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 UAA06800 for ; Sun, 17 Apr 2005 20:33:49 -0400 (EDT) Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNKNi-0003vM-Ih for manet@ietf.org; Sun, 17 Apr 2005 20:44:55 -0400 Received: from photon.ece.cornell.edu (photon.ece.cornell.edu [128.84.81.138]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 4BA451E8007; Sun, 17 Apr 2005 20:33:49 -0400 (EDT) Date: Sun, 17 Apr 2005 20:33:49 -0400 (EDT) From: Prince Samar To: Faisal Adeem Siddiqui Subject: Re: [manet] question about simultaneous use of different routing protocols in a single MANET In-Reply-To: <015401c54096$219349a0$dcc26bd2@ajoudayhakyu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 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 Dear Faisal, The Independent Zone Routing (IZR) framework has the capability to switch between proactive and reactive routing if the network characteristics (e.g., mobility, call patterns and rate) so dictate. Perhaps more importantly, the IZR framework has the ability to adaptively determine and support the optimal proportions of proactive and reactive routing in the network, leading to efficient and scalable performance. The decisions to vary the proportions of proactive and reactive routing is totally distributed, on a per node basis, resulting in reduced overhead and eliminating any inconsistency issues. Details are documented in the following paper: * P. Samar, M.R. Pearlman, Z.J. Haas, "Independent Zone Routing: An Adaptive Hybrid Routing Framework for Ad Hoc Wireless Networks," in IEEE/ACM Transactions on Networking, Vol. 12, Issue 4, pages 595-608, Aug. 2004. Regards, Prince On Thu, 14 Apr 2005, Faisal Adeem Siddiqui wrote: : Hi all, : I was wondering if it is possible and practical to use two different routing : protocols in a single MANET ? I think if we are using two routing protocols : then it will make two segments of MANET and there must be a node (gateway) : between these segments which understands both routing protocols to relay : traffic from one segment to another. : On the other hand, if we want to switch from one routing protocol to another : depending upon the network conditions, will it be practical ? For example, : initially we have a proactive routing protocol running but after some time : the mobility of nodes increase considerably and the performance of proactive : routing protocol is decreased. Now if we want to switch to a reactive : routing protocol, will it incur a lot of overhead ? Is it practical ? If : someone has done any experiments of this kind please refer it to me. : Thanks. : : Faisal. : : : _______________________________________________ : 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 Apr 18 04:35:12 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNRiq-0001T6-IJ; Mon, 18 Apr 2005 04:35:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNRio-0001Sl-DH for manet@megatron.ietf.org; Mon, 18 Apr 2005 04:35: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 EAA26903 for ; Mon, 18 Apr 2005 04:35:08 -0400 (EDT) Received: from web31709.mail.mud.yahoo.com ([68.142.201.189]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DNRtZ-00042g-CI for manet@ietf.org; Mon, 18 Apr 2005 04:46:18 -0400 Received: (qmail 63937 invoked by uid 60001); 18 Apr 2005 08:34:59 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=XVsUlohAtgcOTcJzcNh8Ui30T13yBC14m8CaDBGzMd3GrXjgLuUSqkvXTIMMJOmXf1C//7105W7uLkj5IK73fzhM17rLzO343f4MGgUPhgddUAz+7a4g1nz0/Tpn6HNXhj7Zjk0hm5d56/L2cu1bML9o8Vn8nwyO3uAZR2/y7ho= ; Message-ID: <20050418083459.63935.qmail@web31709.mail.mud.yahoo.com> Received: from [210.211.178.124] by web31709.mail.mud.yahoo.com via HTTP; Mon, 18 Apr 2005 01:34:59 PDT Date: Mon, 18 Apr 2005 01:34:59 -0700 (PDT) From: rajendra gunnam To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 2.7 (++) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [manet] leader election, glomosim help 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 hello all, I am Rajendra, doing my Masters now. Currently working on Leader Election Algorithm for MANet. I have developed my Algorithm and want to simulate it using GloMoSim. I have Installed glomosim perfectly and unable to view the GUI mode of that. I have few example files which are done in glomosim. Iam unable to run them in GUI. Please help me if you are familier with this. Thank u. Regards, RAJA. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 18 16:43:02 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNd5C-0000Hq-7W; Mon, 18 Apr 2005 16: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 1DNd59-0000G6-2O for manet@megatron.ietf.org; Mon, 18 Apr 2005 16:42: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 QAA08427 for ; Mon, 18 Apr 2005 16:42:56 -0400 (EDT) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNdFy-00022V-WD for manet@IETF.ORG; Mon, 18 Apr 2005 16:54:13 -0400 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j3IKgsMC026167 for ; Mon, 18 Apr 2005 16:42:54 -0400 (EDT) Received: (from gateway [129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005041816425312047 for ; Mon, 18 Apr 2005 16:42:53 -0400 Date: Mon, 18 Apr 2005 16:42:54 -0400 (EDT) From: Yue Fang To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [manet] 802.11 NAV setting in overlapping BSS case 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 Dear manet users: I have a couple of questions regarding the 802.11 nav setting in overlapping BSS cases, could you please share your understanding of these issues? Thanks in advance. 1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs receiving a valid frame shall update their NAV with the information received in the duration/ID field, but only when the new NAV value is greater than the current NAV value and only when the frame is not addressed to the receiving STA." My questions are: a: Does it imply that STAs in DCF will not differentiate frames from other BSS? b: If a STA receives a CFP data frame from another BSS, since the duration field is set to 32768, what will it do? 2 As the NAV setting in CFP, in section 9.3.2.2: "Each STA, except the STA with the PC, shall preset its NAV to the CFPMaxDuration value (obtained from the CF Parameter Set elements in beacons from this PC) at each target beacon transmission time (TBTT) at which a CFP is scheduled to start (based on the CFPPeriod field in the CF Parameter Set element of the beacon frames from this PC). Each non-PC STA shall update its NAV using the CFDurRemaining value in any error-free CF Parameter Set element of the Beacon frame that the STA receives. This includes CFPDurRemaining values in CF Parameter Set elements from beacon frames from other (overlapping) BSS" My question is, is this rule only applies to STA that operate in CFP? similarly like question 1, if a STA works in CP hears the beacon from another CFP BSS contains CFPDurRemaining value, what does it do? Any input is appreciated. Bests Yue ----------------------------------- Yue Fang 227 Egan Research Building Dept. of Electrical & Computer Eng. Northeastern University Boston, MA, 02115 (tel) 617-373-3009 ----------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 18 18:26:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNeh4-000157-Bo; Mon, 18 Apr 2005 18:26:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNeh1-00014y-SB for manet@megatron.ietf.org; Mon, 18 Apr 2005 18:26: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 SAA19234 for ; Mon, 18 Apr 2005 18:26:09 -0400 (EDT) Received: from che.ojctech.com ([209.254.158.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNerv-0006p2-BK for manet@ietf.org; Mon, 18 Apr 2005 18:37:27 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id j3IMQ1u6018743 for ; Mon, 18 Apr 2005 17:26:01 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id j3IMQ1W0018736 for manet@ietf.org; Mon, 18 Apr 2005 17:26:01 -0500 Date: Mon, 18 Apr 2005 17:26:00 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case Message-ID: <20050418222600.GJ22250@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: 9466e0365fc95844abaf7c3f15a05c7d 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 On Mon, Apr 18, 2005 at 04:42:54PM -0400, Yue Fang wrote: > > Dear manet users: > > I have a couple of questions regarding the 802.11 nav setting in > overlapping BSS cases, could you please share your understanding of these > issues? Thanks in advance. > > 1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs > receiving a valid frame shall update their NAV with the information > received in the duration/ID field, but only when the new NAV value is > greater than the current NAV value and only when the frame is not > addressed to the receiving STA." > > My questions are: > a: Does it imply that STAs in DCF will not differentiate frames from > other BSS? Yes. > b: [...] I do not know the answer to your question regarding the CFP. 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 Apr 18 21:33:34 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNhcM-0003Hv-7k; Mon, 18 Apr 2005 21:33:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNhcK-0003Hq-0i for manet@megatron.ietf.org; Mon, 18 Apr 2005 21:33:32 -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 VAA01372 for ; Mon, 18 Apr 2005 21:33:30 -0400 (EDT) Received: from mail.netgate.com ([64.62.194.115] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNhnF-0005DZ-19 for manet@ietf.org; Mon, 18 Apr 2005 21:44:49 -0400 Received: by netgate.com (Postfix, from userid 45) id AA64028000C; Mon, 18 Apr 2005 18:33:25 -0700 (PDT) Received: from [192.168.1.188] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 1CCCA28000C; Mon, 18 Apr 2005 18:33:22 -0700 (PDT) Message-ID: <42645FE0.4060005@netgate.com> Date: Mon, 18 Apr 2005 15:33:20 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 1.0 (X11/20050325) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Young Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case References: <20050418222600.GJ22250@che.ojctech.com> In-Reply-To: <20050418222600.GJ22250@che.ojctech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on he-colo.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org David Young wrote: >On Mon, Apr 18, 2005 at 04:42:54PM -0400, Yue Fang wrote: > > >>Dear manet users: >> >>I have a couple of questions regarding the 802.11 nav setting in >>overlapping BSS cases, could you please share your understanding of these >>issues? Thanks in advance. >> >>1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs >>receiving a valid frame shall update their NAV with the information >>received in the duration/ID field, but only when the new NAV value is >>greater than the current NAV value and only when the frame is not >>addressed to the receiving STA." >> >>My questions are: >>a: Does it imply that STAs in DCF will not differentiate frames from >>other BSS? >> >> > >Yes. > > I don't think so. From IEEE-802.11-1999 (7.2.2): A station uses the contents of the Address 1 field to perform address matching for receive decisions. In cases where the Address 1 field contains a group address, the BSSID also is validated to ensure that the broadcast or multicast originated in the same BSS. So certainly if its a group addressed (multicast, broadcast) frame, then the BSSID is consulted. Otherwise, if addr1 matches, then the packet is received. This leaves open the possibility that a given STA could be associated with more than one AP, but 5.4.2.2 says: "At any given instant, a STA may be associated with no more than one AP. This ensures that the DS may determine a unique answer to the question, "Which AP is serving STA X?" Once an association is completed, a STA may make full use of a DS (via the AP) to communicate. Association is always initiated by the mobile STA, not the AP." Since each AP is its on BSS, any given STA can't be associated with more than one AP, and the combination of BSSID+RA *has* to be unique, the answer is 'STAs in DCF will certainly differentiate frames from other BSS'. Frames in an IBSS always have "FromDS" and "ToDS" clear, and there can only (are only supposed to) be a single IBSS in a given environment. (IEEE-802.11-1999.5.6) "An IBSS consists of STAs that are directly connected. Thus there is (by definition) only one BSS." >>b: If a STA receives a CFP data frame from another BSS, since the >>duration field is set to 32768, what will it do? >> If the the STA in another (I)BSS does this, its misbehaving, for starters. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Apr 18 22:30:32 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNiVU-0001lJ-S6; Mon, 18 Apr 2005 22:30:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNiVS-0001lE-8u for manet@megatron.ietf.org; Mon, 18 Apr 2005 22: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 WAA05366 for ; Mon, 18 Apr 2005 22:30:28 -0400 (EDT) Received: from che.ojctech.com ([209.254.158.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNigN-00070y-81 for manet@ietf.org; Mon, 18 Apr 2005 22:41:48 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id j3J2UJu6028753 for ; Mon, 18 Apr 2005 21:30:19 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id j3J2UJMX028751 for manet@ietf.org; Mon, 18 Apr 2005 21:30:19 -0500 Date: Mon, 18 Apr 2005 21:30:19 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case Message-ID: <20050419023019.GK22250@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: <20050418222600.GJ22250@che.ojctech.com> <42645FE0.4060005@netgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42645FE0.4060005@netgate.com> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 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 On Mon, Apr 18, 2005 at 03:33:20PM -1000, Jim Thompson wrote: > David Young wrote: > > >On Mon, Apr 18, 2005 at 04:42:54PM -0400, Yue Fang wrote: > > > > > >>Dear manet users: > >> > >>I have a couple of questions regarding the 802.11 nav setting in > >>overlapping BSS cases, could you please share your understanding of these > >>issues? Thanks in advance. > >> > >>1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs > >>receiving a valid frame shall update their NAV with the information > >>received in the duration/ID field, but only when the new NAV value is > >>greater than the current NAV value and only when the frame is not > >>addressed to the receiving STA." > >> > >>My questions are: > >>a: Does it imply that STAs in DCF will not differentiate frames from > >>other BSS? > >> > >> > > > >Yes. > > > > > I don't think so. Jim, I think your understanding of Yue Fang's question is different from mine. I understood his question (a) to implicitly begin, "For the purpose of updating its NAV, ...". I do not believe a STA will differentiate frames from another BSS, when it comes to updating its NAV. (Consider the case of RTS/CTS/ACK packets, whose BSS you cannot always infer.) 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 Apr 19 02:16:12 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNlws-0004Hc-T8; Tue, 19 Apr 2005 02:11:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNlwm-0004Gc-KO for manet@megatron.ietf.org; Tue, 19 Apr 2005 02:10: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 CAA28255 for ; Tue, 19 Apr 2005 02:10:53 -0400 (EDT) Received: from web54609.mail.yahoo.com ([68.142.225.193]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DNm7e-0006gg-23 for manet@ietf.org; Tue, 19 Apr 2005 02:22:14 -0400 Received: (qmail 9713 invoked by uid 60001); 19 Apr 2005 06:10:41 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Z5zJZh7w2VkoH2gWWZLYTFBjTw8zmDvrHMHTTIxMiZEUfFPDwyIitpXTtieNOpvdCARhwA0M30g52MgE0CiwxEsoyk2TpDUoVATGzw8dbCu31HVeuKajJAsBR/Atj37opR49DHSbEO1ZbPuI1HdDxcuQX/9txHgAMC81QzwXcSc= ; Message-ID: <20050419061041.9711.qmail@web54609.mail.yahoo.com> Received: from [203.200.31.178] by web54609.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 07:10:41 BST Date: Tue, 19 Apr 2005 07:10:41 +0100 (BST) From: aravind rao To: manet@ietf.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 8bit Subject: [manet] Re: How to identify RREP by Intermediate node X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: avi_16@yahoo.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org hi, the AODV implementation in ns-2 takes care of each case as given below: /**************************************************/ // First check if I am the destination .. if(rq->rq_dst == index) { /*** Action Taken - Send RREP ***/ } // I am not the destination, but I may have a fresh enough route. else if (rt && (rt->rt_hops != INFINITY2) && (rt->rt_seqno >= rq->rq_dst_seqno) ) { /***Action taken- Intermediate node sending RREP***/ } else { /*** Forward the packet ***/ } /**************************************************/ hope this will answer your query regards Aravind Rao Wireless Networking Lab M.S. Ramaiah Institute of Technology India Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 19 02:34:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNmJR-0000m0-Go; Tue, 19 Apr 2005 02:34:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNmJO-0000lf-VN for manet@megatron.ietf.org; Tue, 19 Apr 2005 02:34: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 CAA10600 for ; Tue, 19 Apr 2005 02:34:16 -0400 (EDT) Received: from web54601.mail.yahoo.com ([68.142.225.185]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DNmUL-0007aZ-AE for manet@ietf.org; Tue, 19 Apr 2005 02:45:38 -0400 Received: (qmail 34235 invoked by uid 60001); 19 Apr 2005 06:34:08 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Fm8ks8J3RKj3MtUi+AUsQqRcjsIyqcbDNcuDLdynew6Cy77Emn7xhYFZZ2T3Q4ZCVHwzFSe7DJtCX0xQXPfE5oB8d51V9KljeVEV1hj2aYXMv0HYgCw92F8mvjKYMMKRFkUc2FPuVpE4MnzNusMpasqLX0isebD+FfMKh1YPRNA= ; Message-ID: <20050419063408.34233.qmail@web54601.mail.yahoo.com> Received: from [203.200.31.178] by web54601.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 07:34:08 BST Date: Tue, 19 Apr 2005 07:34:08 +0100 (BST) From: aravind rao To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 8bit Subject: [manet] MAODV Patch for ns-2.28 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: avi_16@yahoo.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org Hi, I have recently switched from ns-2.26 to ns-2.26 because I have been told that many of the bugs in ns-2.26 (especially in MAC implementation) have been fixed in the newer version. But my work mainly involves AODV/MAODV protocols. I am unable to find a MAODV patch for ns-2.28. Does such a patch exist? Or will the patch developed for ns-2.26 work for ns-2.28 also. Thanks a lot, Aravind Rao and Ashwin Kumar Wireless Networking Lab M.S. Ramaiah Institute of Technology Bangalore, India Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 19 06:46:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNqFt-0000T4-W7; Tue, 19 Apr 2005 06:46:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNqFs-0000Sz-Mr for manet@megatron.ietf.org; Tue, 19 Apr 2005 06:46: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 GAA27170 for ; Tue, 19 Apr 2005 06:46:52 -0400 (EDT) Received: from mail.netgate.com ([64.62.194.115] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNqQq-00008z-OQ for manet@ietf.org; Tue, 19 Apr 2005 06:58:18 -0400 Received: by netgate.com (Postfix, from userid 45) id 5DAB328000C; Tue, 19 Apr 2005 03:46:52 -0700 (PDT) Received: from [192.168.1.188] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id A53E8280004; Tue, 19 Apr 2005 03:46:49 -0700 (PDT) Message-ID: <4264E196.8080607@netgate.com> Date: Tue, 19 Apr 2005 00:46:46 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 1.0 (X11/20050325) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Young Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case References: <20050418222600.GJ22250@che.ojctech.com> <42645FE0.4060005@netgate.com> <20050419023019.GK22250@che.ojctech.com> In-Reply-To: <20050419023019.GK22250@che.ojctech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on he-colo.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 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 David Young wrote: >On Mon, Apr 18, 2005 at 03:33:20PM -1000, Jim Thompson wrote: > > >>David Young wrote: >> >> >> >>>On Mon, Apr 18, 2005 at 04:42:54PM -0400, Yue Fang wrote: >>> >>> >>> >>> >>>>Dear manet users: >>>> >>>>I have a couple of questions regarding the 802.11 nav setting in >>>>overlapping BSS cases, could you please share your understanding of these >>>>issues? Thanks in advance. >>>> >>>>1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs >>>>receiving a valid frame shall update their NAV with the information >>>>received in the duration/ID field, but only when the new NAV value is >>>>greater than the current NAV value and only when the frame is not >>>>addressed to the receiving STA." >>>> >>>>My questions are: >>>>a: Does it imply that STAs in DCF will not differentiate frames from >>>>other BSS? >>>> >>>> >>>> >>>> >>>Yes. >>> >>> >>> >>> >>I don't think so. >> >> > >Jim, > >I think your understanding of Yue Fang's question is different from mine. >I understood his question (a) to implicitly begin, "For the purpose of >updating its NAV, ...". I do not believe a STA will differentiate frames >from another BSS, when it comes to updating its NAV. (Consider the case >of RTS/CTS/ACK packets, whose BSS you cannot always infer.) > >Dave > > Dave, Every control frame (RTS, CTS, ACK, CF-END, CF-END+CF-ACK) except PS-POLL has a RA in it. This RA must match, in the case of CF-END, CF-END+CF-ACK and ACK. RTS and CTS frames will cross BSS boundries. This is by design. Perhaps this is the question Yue Fang was asking. RTS and CTS can't be used for group-addressed frames, btw. The duration for CF-END and CF-END+CF-ACK, is 0. The duration for RTS, CTS and ACK all follow similar rules, which I won't repeat here (7.1.2 for those who want to go look.) PS-POLL has a TA and BSSID in it, such that any STA can tell if the PS-POLL is something it should pay attention to. Upon reception of a PS-POLL (for the BSSID to which the STA belongs) "All STAs, upon receipt of a PS-Poll frame, update their NAV settings as appropriate under the coordination function rules using a duration value equal to the time, in microseconds, required to transmit one ACK frame plus one SIFS interval." _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 19 08:29:23 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNrr0-0007xR-UH; Tue, 19 Apr 2005 08:29:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNrqy-0007xG-EW for manet@megatron.ietf.org; Tue, 19 Apr 2005 08:29: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 IAA04491 for ; Tue, 19 Apr 2005 08:29:18 -0400 (EDT) Received: from smtp2.libero.it ([193.70.192.52]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNs1v-0004f2-EA for manet@ietf.org; Tue, 19 Apr 2005 08:40:40 -0400 Received: from localhost (172.16.1.84) by smtp2.libero.it (7.0.027-DD01) id 41BDB66301BADE6E for manet@ietf.org; Tue, 19 Apr 2005 14:29:23 +0200 Received: from libero.it (172.16.1.13) by smtp0.libero.it (7.0.027-DD01) id 41BDA6DE011EA6B6 for manet@ietf.org; Tue, 19 Apr 2005 14:29:03 +0200 Date: Tue, 19 Apr 2005 14:29:03 +0200 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "jers\@inwind\.it" To: "manet" X-XaM3-API-Version: 4.1 (B27pl2) X-type: 0 X-SenderIP: 151.97.6.47 X-Virus-Scanned: by amavisd-new at libero.it serv5 X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: quoted-printable Subject: [manet] An opnet simulation error X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org Hi all, I'm a new user of Opnet Modeler and I'm utilizing it for my st= udies on manet environment. To learn how to use the modeler, I have dev= eloped a simple new process model but, during the simulation process, = while loading the model libraries, the simulation expires and shows the= following error message: Beginning simulation of project_name-scen= ario1 at 11:31:26 mar apr 19 2005 ----- Kernel: development (not opti= mized), sequential ----- <<< Warning >>> Repository missing process= model (process_model_name) T (0), EV (-), MOD (NONE), PROC (sim_load_r= epos_prmatch) ----- <<< Program Abort >>> The set of models necessa= ry for running the simulation is incomplete. Check that all the 'reposi= tories' attributes are complete. T (0), EV (-), MOD (NONE), PROC (sim_l= oad_repos_load) ----- I noticed that I can successfully carry out t= he simulations of the "M/M/1 Queue" project included in the tutorial = but, if at the beginning I change the name of the process model (e.g., = from simple_source in my_source) and then I procede according to the "M= /M/1 queue" tutorial example, the simulation leads to the aforementione= d error. I suppose that this error may be due to wrong directory settin= gs or to an installation problem. Could someone please suggest me a way = to solve my problem? Thanks a lot. Jers =0A=0A=0A=0A_______________= _____________________________________________=0ANavighi a 4 MEGA e i prim= i 3 mesi sono GRATIS. =0AScegli Libero Adsl Flat senza limiti su http://w= ww.libero.it=0A _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 19 09:58:59 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNtFi-0005NL-US; Tue, 19 Apr 2005 09:58:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNtFf-0005N8-L2 for manet@megatron.ietf.org; Tue, 19 Apr 2005 09:58: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 JAA12133 for ; Tue, 19 Apr 2005 09:58:53 -0400 (EDT) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNtQh-0008To-3R for manet@ietf.org; Tue, 19 Apr 2005 10:10:19 -0400 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j3JDwqMC025301; Tue, 19 Apr 2005 09:58:52 -0400 (EDT) Received: (from gateway [129.10.60.71]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005041909585215578 ; Tue, 19 Apr 2005 09:58:52 -0400 Date: Tue, 19 Apr 2005 09:58:52 -0400 (EDT) From: Yue Fang To: Jim Thompson Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case In-Reply-To: <42645FE0.4060005@netgate.com> Message-ID: References: <20050418222600.GJ22250@che.ojctech.com> <42645FE0.4060005@netgate.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 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 On Mon, 18 Apr 2005, Jim Thompson wrote: > David Young wrote: > > >On Mon, Apr 18, 2005 at 04:42:54PM -0400, Yue Fang wrote: > > > > > >>Dear manet users: > >> > >>I have a couple of questions regarding the 802.11 nav setting in > >>overlapping BSS cases, could you please share your understanding of these > >>issues? Thanks in advance. > >> > >>1. As the general NAV setting, in the protocol, section 9.2.5.4, "STAs > >>receiving a valid frame shall update their NAV with the information > >>received in the duration/ID field, but only when the new NAV value is > >>greater than the current NAV value and only when the frame is not > >>addressed to the receiving STA." > >> > >>My questions are: > >>a: Does it imply that STAs in DCF will not differentiate frames from > >>other BSS? > >> > >> > > > >Yes. > > > > > I don't think so. > > From IEEE-802.11-1999 (7.2.2): > > A station uses the contents of the Address 1 field to perform > address matching for receive decisions. > In cases where the Address 1 field contains a group address, the > BSSID also is validated to ensure > that the broadcast or multicast originated in the same BSS. > > So certainly if its a group addressed (multicast, broadcast) frame, then > the BSSID is consulted. Otherwise, > if addr1 matches, then the packet is received. > > This leaves open the possibility that a given STA could be associated > with more than one AP, but 5.4.2.2 says: > > "At any given instant, a STA may be associated with no more than one > AP. This ensures that the DS may > determine a unique answer to the question, "Which AP is serving STA > X?" Once an association is > completed, a STA may make full use of a DS (via the AP) to > communicate. Association is always initiated by > the mobile STA, not the AP." > > Since each AP is its on BSS, any given STA can't be associated with more > than one AP, and the combination of > BSSID+RA *has* to be unique, the answer is 'STAs in DCF will certainly > differentiate frames from other BSS'. > > Frames in an IBSS always have "FromDS" and "ToDS" clear, and there can > only (are only supposed to) be a single IBSS in a given environment. > (IEEE-802.11-1999.5.6) > > "An IBSS consists of STAs that are directly connected. Thus there is > (by definition) only one BSS." hello, Jim: If we consider that two IBSSs located close enough that STAs from one BSS may overhear the transmission from another BSS. In this case, let's assume a STA received a data packet transmitted in another BSS, should it update its NAV to defer channel access? I think it should even though it is originated and addressed to STA in another BSS otherwise transmission from this STA may cause collision at the other end. > > > >>b: If a STA receives a CFP data frame from another BSS, since the > >>duration field is set to 32768, what will it do? > >> > If the the STA in another (I)BSS does this, its misbehaving, for > starters. As in previous case, the CFP frame is not addressed to this STA, but since there are overlapping BSS, the STA may overhear the CFP transmission from another BSS, what should we do? This is more difficult for me since there is no duration information contained in CFP data frame. Even we can update NAV, we don't know which value we should use. > _______________________________________________ > 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 Apr 19 12:15:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNvNW-0002Om-CL; Tue, 19 Apr 2005 12:15:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNvNS-0002Nh-QV for manet@megatron.ietf.org; Tue, 19 Apr 2005 12:15: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 MAA23256 for ; Tue, 19 Apr 2005 12:15:00 -0400 (EDT) Received: from luminis-email.nmsu.edu ([128.123.4.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNvYR-0004NA-NI for manet@ietf.org; Tue, 19 Apr 2005 12:26:29 -0400 Received: from mullenlt (mullen-lt.NMSU.Edu [128.123.246.27]) by luminis-email.nmsu.edu (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IF700AY2BSYDS@luminis-email.nmsu.edu> for manet@ietf.org; Tue, 19 Apr 2005 10:14:58 -0600 (MDT) Date: Tue, 19 Apr 2005 10:15:01 -0600 From: "John P. Mullen" Subject: RE: [manet] An opnet simulation error In-reply-to: To: jers@inwind.it, "'manet'" Message-id: <0IF700AY3BSYDS@luminis-email.nmsu.edu> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcVE25zaibFvWI2ZSI2wXf1ch1AniAAHwRoA X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: 7BIT Cc: 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 Hi Jers, I think you are on the right track. When you change the process model, how do you do this? John Mullen -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of jers@inwind.it Sent: Tuesday, April 19, 2005 6:29 AM To: manet Subject: [manet] An opnet simulation error Hi all, I'm a new user of Opnet Modeler and I'm utilizing it for my studies on manet environment. To learn how to use the modeler, I have developed a simple new process model but, during the simulation process, while loading the model libraries, the simulation expires and shows the following error message: Beginning simulation of project_name-scenario1 at 11:31:26 mar apr 19 2005 ----- Kernel: development (not optimized), sequential ----- <<< Warning >>> Repository missing process model (process_model_name) T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) ----- <<< Program Abort >>> The set of models necessary for running the simulation is incomplete. Check that all the 'repositories' attributes are complete. T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) ----- I noticed that I can successfully carry out the simulations of the "M/M/1 Queue" project included in the tutorial but, if at the beginning I change the name of the process model (e.g., from simple_source in my_source) and then I procede according to the "M/M/1 queue" tutorial example, the simulation leads to the aforementioned error. I suppose that this error may be due to wrong directory settings or to an installation problem. Could someone please suggest me a way to solve my problem? Thanks a lot. Jers ____________________________________________________________ Navighi a 4 MEGA e i primi 3 mesi sono GRATIS. Scegli Libero Adsl Flat senza limiti su http://www.libero.it _______________________________________________ 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 Apr 19 15:46:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNyfb-0000uU-KM; Tue, 19 Apr 2005 15:46:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNyfa-0000uK-3j for manet@megatron.ietf.org; Tue, 19 Apr 2005 15:46: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 PAA14113 for ; Tue, 19 Apr 2005 15:45:59 -0400 (EDT) Received: from mailgw3a.lmco.com ([192.35.35.7]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNyqa-0003Ss-Im for manet@ietf.org; Tue, 19 Apr 2005 15:57:29 -0400 Received: from emss04g01.ems.lmco.com (relay4.ems.lmco.com [166.17.13.122]) by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id j3JJjrPl029829; Tue, 19 Apr 2005 15:45:53 -0400 (EDT) Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30884) id <0IF700B01LKHVR@lmco.com>; Tue, 19 Apr 2005 15:45:53 -0400 (EDT) Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF V6.1-1X6 #30884) with ESMTP id <0IF7007NSLKG2J@lmco.com>; Tue, 19 Apr 2005 15:45:52 -0400 (EDT) Received: from EMSS04M12.us.lmco.com ([166.17.13.94]) by EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 19 Apr 2005 15:45:52 -0400 Date: Tue, 19 Apr 2005 15:45:52 -0400 From: "Flynn, Matthew" Subject: RE: [manet] An opnet simulation error To: jers@inwind.it, manet Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-Topic: [manet] An opnet simulation error Thread-Index: AcVE29dcmsNWF5YqQGG1fbs3fRlAmQAPBNvQ content-class: urn:content-classes:message X-OriginalArrivalTime: 19 Apr 2005 19:45:52.0959 (UTC) FILETIME=[65376CF0:01C54518] X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7BIT Cc: 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 You need to have a C compiler installed. Modeler ships with prebuilt DLLs of all of the models. If you change any of the process models they need to be recompiled and linked into a simulation executable or recompiled and linked into a DLL repository. Either way you need a compiler. -Matt -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of jers@inwind.it Sent: Tuesday, April 19, 2005 8:29 AM To: manet Subject: [manet] An opnet simulation error Hi all, I'm a new user of Opnet Modeler and I'm utilizing it for my studies on manet environment. To learn how to use the modeler, I have developed a simple new process model but, during the simulation process, while loading the model libraries, the simulation expires and shows the following error message: Beginning simulation of project_name-scenario1 at 11:31:26 mar apr 19 2005 ----- Kernel: development (not optimized), sequential ----- <<< Warning >>> Repository missing process model (process_model_name) T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) ----- <<< Program Abort >>> The set of models necessary for running the simulation is incomplete. Check that all the 'repositories' attributes are complete. T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) ----- I noticed that I can successfully carry out the simulations of the "M/M/1 Queue" project included in the tutorial but, if at the beginning I change the name of the process model (e.g., from simple_source in my_source) and then I procede according to the "M/M/1 queue" tutorial example, the simulation leads to the aforementioned error. I suppose that this error may be due to wrong directory settings or to an installation problem. Could someone please suggest me a way to solve my problem? Thanks a lot. Jers ____________________________________________________________ Navighi a 4 MEGA e i primi 3 mesi sono GRATIS. Scegli Libero Adsl Flat senza limiti su http://www.libero.it _______________________________________________ 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 Apr 19 17:11:04 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNzzr-0002zD-VT; Tue, 19 Apr 2005 17:11:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNzzp-0002z4-51 for manet@megatron.ietf.org; Tue, 19 Apr 2005 17:11: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 RAA27642 for ; Tue, 19 Apr 2005 17:10:58 -0400 (EDT) Received: from mail.netgate.com ([64.62.194.115] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO0At-0008Vz-Iy for manet@ietf.org; Tue, 19 Apr 2005 17:22:29 -0400 Received: by netgate.com (Postfix, from userid 45) id ECCEE280005; Tue, 19 Apr 2005 14:10:57 -0700 (PDT) Received: from [192.168.1.199] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 1A503280004; Tue, 19 Apr 2005 14:10:54 -0700 (PDT) Message-ID: <426573DC.5090603@netgate.com> Date: Tue, 19 Apr 2005 11:10:52 -1000 From: Jim Thompson User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050419) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yue Fang Subject: Re: [manet] 802.11 NAV setting in overlapping BSS case References: <20050418222600.GJ22250@che.ojctech.com> <42645FE0.4060005@netgate.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on he-colo.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 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 Yue Fang wrote: >hello, Jim: > >If we consider that two IBSSs located close enough that STAs from one >BSS may overhear the transmission from another BSS. In this case, let's >assume a STA received a data packet transmitted in another BSS, should it >update its NAV to defer channel access? I think it should even though >it is originated and addressed to STA in another BSS otherwise >transmission from this STA may cause collision at the other end. > > potentially, but there is no requirement in the specification for this behavior, and normal filtering will mean that the card rejects the packet. Note that CCA is still a requirement, so if the two STAs are close enough that they can hear each other, it is likely that they will not co-interfere. The situation becomes problematic when one of the STAs is receiving a packet that doesn't set CCA in the second STA. The second STA is free to transmit. Your solution doesn't help, since the second STA couldn't decode the packet (by definition). RTS/CTS *might* help in this situation, and is part of the reason that RTS and CTS packets were designed to cross BSS boundries. >As in previous case, the CFP frame is not addressed to this STA, but since >there are overlapping BSS, the STA may overhear the CFP transmission from >another BSS, what should we do? This is more difficult for me since there >is no duration information contained in CFP data frame. Even we can update >NAV, we don't know which value we should use. > > On a second reading, I don't think that the CFP is even defined when operating in IBSS mode. To your question, all communcation during the CFP is initiated by the PC (which is the AP). The duration infomation during the CFP is carried by the PS-POLL frame, which would proceed any data frame transmitted by any associated STA, so the PS-POLL is used to update the NAV. Special considerations concerning operation with overlapping point-coordinated BSSs is covered in section 9.3.3.2 of the standard. jim _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 20 02:57:46 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DO99d-0001mz-Rk; Wed, 20 Apr 2005 02:57:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DO99b-0001mu-2W for manet@megatron.ietf.org; Wed, 20 Apr 2005 02:57: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 CAA08510 for ; Wed, 20 Apr 2005 02:57:42 -0400 (EDT) Received: from smtp20.libero.it ([193.70.192.147]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO9Kl-0007pd-Dp for manet@ietf.org; Wed, 20 Apr 2005 03:09:16 -0400 Received: from localhost (172.16.1.82) by smtp20.libero.it (7.0.027-DD01) id 41D02C98018A5C04; Wed, 20 Apr 2005 08:57:26 +0200 Received: from pc (62.98.237.56) by smtp3.libero.it (7.0.027-DD01) id 42079BE102CFA428; Wed, 20 Apr 2005 08:57:25 +0200 Message-ID: <000a01c54576$35d47260$38ed623e@pc> From: "Jers" To: "John P. Mullen" , "'manet'" References: <0IF700AY3BSYDS@luminis-email.nmsu.edu> Subject: Re: [manet] An opnet simulation error Date: Wed, 20 Apr 2005 08:55:36 +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 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Virus-Scanned: by amavisd-new at libero.it serv3 X-Spam-Score: 0.2 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Content-Transfer-Encoding: 7bit Cc: 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 Hi, thanks for your replies. I already have a C compiler installed. To change the model, I follow these procedures: - load the "simple_source" process model - change its name by clicking on "save as" - compile the code, without any error or warning - save again (CTRL+S) - use this new model as source in the tutorial m/m/1 queue project. I tried to save the new file both in "11.0A\models\std\traff_gen" and in "Documents and Settings/Adiministrator/op_models" directories... same error! I suppose that the simulation executable file link is authomatically generated when, after that I have construct the project, I configure the simulation (DES > Configure/Run Discrete Event Simulation (Advanced)). Is it so? In last mentioned configuration box I only change the probe_file included in the "output statistic collection" section. Do I have to set something in the input section, maybe? Do I do anything wrong? Thanks again. Jers ----- Original Message ----- From: "John P. Mullen" < To: ; "'manet'" Sent: Tuesday, April 19, 2005 6:15 PM Subject: RE: [manet] An opnet simulation error > Hi Jers, > I think you are on the right track. > When you change the process model, how do you do this? > John Mullen > ----- Original Message ----- From: "Flynn, Matthew" To: ; "manet" Sent: Tuesday, April 19, 2005 9:45 PM Subject: RE: [manet] An opnet simulation error > You need to have a C compiler installed. Modeler ships with prebuilt > DLLs of all of the models. If you change any of the process models they > need to be recompiled and linked into a simulation executable or > recompiled and linked into a DLL repository. Either way you need a > compiler. > > > -Matt > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > jers@inwind.it > Sent: Tuesday, April 19, 2005 6:29 AM > To: manet > Subject: [manet] An opnet simulation error > >> Hi all, >> >> I'm a new user of Opnet Modeler and I'm utilizing it for my studies on manet >> environment. >> To learn how to use the modeler, I have developed a simple new process model >> but, >> during the simulation process, while loading the model libraries, the >> simulation expires and shows the following >> error message: >> >> Beginning simulation of project_name-scenario1 at 11:31:26 mar apr 19 2005 >> ----- >> Kernel: development (not optimized), sequential >> ----- >> <<< Warning >>> >> Repository missing process model (process_model_name) >> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) >> ----- >> <<< Program Abort >>> >> The set of models necessary for running the simulation is incomplete. >> Check that all the 'repositories' attributes are complete. >> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) >> ----- >> >> I noticed that I can successfully carry out the simulations of the "M/M/1 >> Queue" project >> included in the tutorial but, if at the beginning I change the name of the >> process model (e.g., from simple_source in my_source) and then I procede >> according to the "M/M/1 queue" tutorial example, the simulation leads >> to the aforementioned error. I suppose that this error may be due to wrong >> directory settings or to an installation problem. Could someone please >> suggest me a way to solve my problem? >> Thanks a lot. >> Jers >> >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 20 04:28:50 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOAZk-0004eI-0J; Wed, 20 Apr 2005 04:28:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOAZg-0004db-IX for manet@megatron.ietf.org; Wed, 20 Apr 2005 04:28: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 EAA15827 for ; Wed, 20 Apr 2005 04:28:42 -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 1DOAkr-0002Gq-QW for manet@ietf.org; Wed, 20 Apr 2005 04:40:18 -0400 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id 1E39919E720; Wed, 20 Apr 2005 10:28:16 +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 10461-10; Wed, 20 Apr 2005 10:28:16 +0200 (CEST) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id F3C3D19E716; Wed, 20 Apr 2005 10:28:15 +0200 (CEST) Received: from pc11-175 ([129.175.11.175]) (SquirrelMail authenticated user badis) by www.lri.fr with HTTP; Wed, 20 Apr 2005 10:28:16 +0200 (CEST) Message-ID: <2143.129.175.11.175.1113985696.squirrel@www.lri.fr> In-Reply-To: <000a01c54576$35d47260$38ed623e@pc> References: <0IF700AY3BSYDS@luminis-email.nmsu.edu> <000a01c54576$35d47260$38ed623e@pc> Date: Wed, 20 Apr 2005 10:28:16 +0200 (CEST) Subject: Re: [manet] An opnet simulation error To: "Jers" User-Agent: SquirrelMail/1.4.4 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: 1.1 (+) X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA15827 Cc: "John P. Mullen" , '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 Hi Jers ;=3D=3D) > Hi, > thanks for your replies. > I already have a C compiler installed. It is logicl that compiler is installed, because you said =93I can successfully carry out the simulations of the "M/M/1 Queue" project included in the tutorial. Otherwise, you cannot compile any project. > To change the model, I follow these procedures: > - load the "simple_source" process model > - change its name by clicking on "save as" > - compile the code, without any error or warning > - save again (CTRL+S) > - use this new model as source in the tutorial m/m/1 queue project. > I tried to save the new file both in > "11.0A\models\std\traff_gen" > and in "Documents and Settings/Adiministrator/op_models" directories... > same > error! If you have OPNET 10.0, you can create your own directory for you project= s and use it as default directory. To do this, select [File > Model Files > Add Model Directory], in OPNET Modeler 10.0 window, then create you directory and make it as default. > > I suppose that the simulation executable file link is authomatically > generated when, after that I have construct the project, I configure t= he > simulation (DES > Configure/Run Discrete Event Simulation (Advanced)). = Is > it > so? Yes, M/M/1 is a simple example (you have not any promoted variables), so you set only the simulation time, the seed, the Probe file and YOU SHOULD not forget to select your Project-scenario in =93Environment Files=94 > In last mentioned configuration box I only change the probe_file includ= ed > in > the "output statistic collection" section. Do I have to set something i= n > the > input section, maybe? Do I do anything wrong? check that the process model attribute of your "src module" is positioned to your new saved simple_source process. > Thanks again. > Jers Best regards Hakim > > ----- Original Message ----- > From: "John P. Mullen" < > To: ; "'manet'" > Sent: Tuesday, April 19, 2005 6:15 PM > Subject: RE: [manet] An opnet simulation error > > >> Hi Jers, >> I think you are on the right track. >> When you change the process model, how do you do this? >> John Mullen >> > ----- Original Message ----- > From: "Flynn, Matthew" > To: ; "manet" > Sent: Tuesday, April 19, 2005 9:45 PM > Subject: RE: [manet] An opnet simulation error > > >> You need to have a C compiler installed. Modeler ships with prebuilt >> DLLs of all of the models. If you change any of the process models th= ey >> need to be recompiled and linked into a simulation executable or >> recompiled and linked into a DLL repository. Either way you need a >> compiler. >> >> >> -Matt > > > > > >> -----Original Message----- >> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf >> Of >> jers@inwind.it >> Sent: Tuesday, April 19, 2005 6:29 AM >> To: manet >> Subject: [manet] An opnet simulation error >> >>> Hi all, >>> >>> I'm a new user of Opnet Modeler and I'm utilizing it for my studies o= n > manet >>> environment. >>> To learn how to use the modeler, I have developed a simple new proces= s > model >>> but, >>> during the simulation process, while loading the model libraries, th= e >>> simulation expires and shows the following >>> error message: >>> >>> Beginning simulation of project_name-scenario1 at 11:31:26 mar apr 1= 9 > 2005 >>> ----- >>> Kernel: development (not optimized), sequential >>> ----- >>> <<< Warning >>> >>> Repository missing process model (process_model_name) >>> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) >>> ----- >>> <<< Program Abort >>> >>> The set of models necessary for running the simulation is incomplete. >>> Check that all the 'repositories' attributes are complete. >>> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) >>> ----- >>> >>> I noticed that I can successfully carry out the simulations of the > "M/M/1 >>> Queue" project >>> included in the tutorial but, if at the beginning I change the name = of > the >>> process model (e.g., from simple_source in my_source) and then I >>> procede >>> according to the "M/M/1 queue" tutorial example, the simulation lead= s >>> to the aforementioned error. I suppose that this error may be due to > wrong >>> directory settings or to an installation problem. Could someone plea= se >>> suggest me a way to solve my problem? >>> Thanks a lot. >>> Jers >>> >>> > > > > _______________________________________________ > 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 Apr 20 04:34:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOAfc-0005Ob-R5; Wed, 20 Apr 2005 04:34:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOAfX-0005OT-4i for manet@megatron.ietf.org; Wed, 20 Apr 2005 04:34: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 EAA16378 for ; Wed, 20 Apr 2005 04:34:45 -0400 (EDT) Received: from smtp1.libero.it ([193.70.192.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOAqi-0002Vi-Fq for manet@ietf.org; Wed, 20 Apr 2005 04:46:21 -0400 Received: from localhost (172.16.1.82) by smtp1.libero.it (7.0.027-DD01) id 41BDB2AB01BE219E; Wed, 20 Apr 2005 10:34:30 +0200 Received: from pc (62.98.238.87) by smtp20.libero.it (7.0.027-DD01) id 41D02BD30575E218; Wed, 20 Apr 2005 10:34:33 +0200 Message-ID: <000e01c54580$62043320$57ee623e@pc> From: "Jers" To: "Duong Hoang" , "'manet'" References: <000001c54580$a26dc340$31396f80@ece2k.ece.ucsb.edu> Subject: Re: [manet] An opnet simulation error Date: Wed, 20 Apr 2005 10:09:13 +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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Virus-Scanned: by amavisd-new at libero.it serv3 X-Spam-Score: 0.2 (/) X-Scan-Signature: 225414c974e0d6437992164e91287a51 Content-Transfer-Encoding: 7bit Cc: 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 Hi Duong, I'm sorry, my english is bad... I have changed the file name everytime. Moreover, I have tried to save the process model files, with different filenames, in the two directories. Bye. Jers ----- Original Message ----- From: "Duong Hoang" To: "'Jers'" Sent: Wednesday, April 20, 2005 10:11 AM Subject: RE: [manet] An opnet simulation error > Your problem is that you are trying to save two processes with the same > name (even in different directories). The solution for this is to delete > any process that you have already created as you mentioned above. Save > the new process with a DIFFERENT FILE NAME. Then, it should work. > Duong > > > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf > Of Jers > Sent: Tuesday, April 19, 2005 11:56 PM > To: John P. Mullen; 'manet' > Subject: Re: [manet] An opnet simulation error > > Hi, > thanks for your replies. > I already have a C compiler installed. > To change the model, I follow these procedures: > - load the "simple_source" process model > - change its name by clicking on "save as" > - compile the code, without any error or warning > - save again (CTRL+S) > - use this new model as source in the tutorial m/m/1 queue project. > I tried to save the new file both in > "11.0A\models\std\traff_gen" > and in "Documents and Settings/Adiministrator/op_models" directories... > same > error! > > I suppose that the simulation executable file link is authomatically > generated when, after that I have construct the project, I configure > the > simulation (DES > Configure/Run Discrete Event Simulation (Advanced)). > Is it > so? > In last mentioned configuration box I only change the probe_file > included in > the "output statistic collection" section. Do I have to set something in > the > input section, maybe? Do I do anything wrong? > > Thanks again. > Jers > > > ----- Original Message ----- > From: "John P. Mullen" < > To: ; "'manet'" > Sent: Tuesday, April 19, 2005 6:15 PM > Subject: RE: [manet] An opnet simulation error > > > > Hi Jers, > > I think you are on the right track. > > When you change the process model, how do you do this? > > John Mullen > > > ----- Original Message ----- > From: "Flynn, Matthew" > To: ; "manet" > Sent: Tuesday, April 19, 2005 9:45 PM > Subject: RE: [manet] An opnet simulation error > > > > You need to have a C compiler installed. Modeler ships with prebuilt > > DLLs of all of the models. If you change any of the process models > they > > need to be recompiled and linked into a simulation executable or > > recompiled and linked into a DLL repository. Either way you need a > > compiler. > > > > > > -Matt > > > > > > > -----Original Message----- > > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf > Of > > jers@inwind.it > > Sent: Tuesday, April 19, 2005 6:29 AM > > To: manet > > Subject: [manet] An opnet simulation error > > > >> Hi all, > >> > >> I'm a new user of Opnet Modeler and I'm utilizing it for my studies > on > manet > >> environment. > >> To learn how to use the modeler, I have developed a simple new > process > model > >> but, > >> during the simulation process, while loading the model libraries, > the > >> simulation expires and shows the following > >> error message: > >> > >> Beginning simulation of project_name-scenario1 at 11:31:26 mar apr > 19 > 2005 > >> ----- > >> Kernel: development (not optimized), sequential > >> ----- > >> <<< Warning >>> > >> Repository missing process model (process_model_name) > >> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) > >> ----- > >> <<< Program Abort >>> > >> The set of models necessary for running the simulation is > incomplete. > >> Check that all the 'repositories' attributes are complete. > >> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) > >> ----- > >> > >> I noticed that I can successfully carry out the simulations of the > "M/M/1 > >> Queue" project > >> included in the tutorial but, if at the beginning I change the name > of > the > >> process model (e.g., from simple_source in my_source) and then I > procede > >> according to the "M/M/1 queue" tutorial example, the simulation > leads > >> to the aforementioned error. I suppose that this error may be due to > wrong > >> directory settings or to an installation problem. Could someone > please > >> suggest me a way to solve my problem? > >> Thanks a lot. > >> Jers > >> > >> > > > > _______________________________________________ > 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 Apr 20 05:07:21 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOBB2-0000nJ-Qk; Wed, 20 Apr 2005 05:07:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOBB0-0000nE-56 for manet@megatron.ietf.org; Wed, 20 Apr 2005 05:07:18 -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 FAA18366 for ; Wed, 20 Apr 2005 05:07:16 -0400 (EDT) Received: from smtp20.libero.it ([193.70.192.147]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOBMB-0003PH-Qu for manet@ietf.org; Wed, 20 Apr 2005 05:18:52 -0400 Received: from localhost (172.16.1.80) by smtp20.libero.it (7.0.027-DD01) id 41D02C98018B0F6A; Wed, 20 Apr 2005 11:07:07 +0200 Received: from pc (62.98.172.30) by smtp2.libero.it (7.0.027-DD01) id 41BF65E4069DC72A; Wed, 20 Apr 2005 11:07:26 +0200 Message-ID: <001a01c54584$edb9bee0$57ee623e@pc> From: "Jers" To: References: <0IF700AY3BSYDS@luminis-email.nmsu.edu> <000a01c54576$35d47260$38ed623e@pc> <2143.129.175.11.175.1113985696.squirrel@www.lri.fr> Subject: Re: [manet] An opnet simulation error Date: Wed, 20 Apr 2005 10:42:04 +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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Virus-Scanned: by amavisd-new at libero.it serv2 X-Spam-Score: 0.2 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Content-Transfer-Encoding: 7bit Cc: '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 Hi Hakim, > If you have OPNET 10.0, you can create your own directory for you projects > and use it as default directory. To do this, select [File > Model Files > > Add Model Directory], in OPNET Modeler 10.0 window, then create you > directory and make it as default. I have already done that. > > > > > I suppose that the simulation executable file link is authomatically > > generated when, after that I have construct the project, I configure the > > simulation (DES > Configure/Run Discrete Event Simulation (Advanced)). Is > > it > > so? > > Yes, M/M/1 is a simple example (you have not any promoted variables), so > you set only the simulation time, the seed, the Probe file and YOU SHOULD > not forget to select your Project-scenario in "Environment Files" Of course! > > > In last mentioned configuration box I only change the probe_file included > > in > > the "output statistic collection" section. Do I have to set something in > > the > > input section, maybe? Do I do anything wrong? > > check that the process model attribute of your "src module" is positioned > to your new saved simple_source process. > It is so. Regards. Jers > > > > > >> -----Original Message----- > >> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf > >> Of > >> jers@inwind.it > >> Sent: Tuesday, April 19, 2005 6:29 AM > >> To: manet > >> Subject: [manet] An opnet simulation error > >> > >>> Hi all, > >>> > >>> I'm a new user of Opnet Modeler and I'm utilizing it for my studies on > > manet > >>> environment. > >>> To learn how to use the modeler, I have developed a simple new process > > model > >>> but, > >>> during the simulation process, while loading the model libraries, the > >>> simulation expires and shows the following > >>> error message: > >>> > >>> Beginning simulation of project_name-scenario1 at 11:31:26 mar apr 19 > > 2005 > >>> ----- > >>> Kernel: development (not optimized), sequential > >>> ----- > >>> <<< Warning >>> > >>> Repository missing process model (process_model_name) > >>> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) > >>> ----- > >>> <<< Program Abort >>> > >>> The set of models necessary for running the simulation is incomplete. > >>> Check that all the 'repositories' attributes are complete. > >>> T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) > >>> ----- > >>> > >>> I noticed that I can successfully carry out the simulations of the > > "M/M/1 > >>> Queue" project > >>> included in the tutorial but, if at the beginning I change the name of > > the > >>> process model (e.g., from simple_source in my_source) and then I > >>> procede > >>> according to the "M/M/1 queue" tutorial example, the simulation leads > >>> to the aforementioned error. I suppose that this error may be due to > > wrong > >>> directory settings or to an installation problem. Could someone please > >>> suggest me a way to solve my problem? > >>> Thanks a lot. > >>> Jers > >>> > >>> > > > > > > > > _______________________________________________ > > 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 Apr 20 09:10:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOEyI-0006NS-KS; Wed, 20 Apr 2005 09:10:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOEyE-0006N7-Ok for manet@megatron.ietf.org; Wed, 20 Apr 2005 09:10: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 JAA06258 for ; Wed, 20 Apr 2005 09:10:21 -0400 (EDT) Received: from smtp20.libero.it ([193.70.192.147]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOF9R-00023T-Q1 for manet@ietf.org; Wed, 20 Apr 2005 09:21:58 -0400 Received: from localhost (172.16.1.84) by smtp20.libero.it (7.0.027-DD01) id 41D02C98018C3B64; Wed, 20 Apr 2005 15:10:02 +0200 Received: from libero.it (172.16.1.85) by smtp2.libero.it (7.0.027-DD01) id 41BDB59901218A7C; Wed, 20 Apr 2005 15:10:21 +0200 Date: Wed, 20 Apr 2005 15:10:01 +0200 Message-Id: Subject: Re: [manet] An opnet simulation error MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "jers\@inwind\.it" To: "Hakim\.Badis" , "manet" X-XaM3-API-Version: 4.1 (B27pl2) X-type: 0 X-SenderIP: 151.97.6.47 X-Virus-Scanned: by amavisd-new at libero.it serv5 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44 Content-Transfer-Encoding: quoted-printable Cc: 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 Sorry Hkim, I'd like to specify that in the prevous mail I meant that al= l may settings correspond with your suggestions but my problem remains un= solved. Jers > Hi Hakim, > > > If you have OPNET 10.0, you can c= reate your own directory for you projects > > and use it as default dire= ctory. To do this, select [File > Model Files > > > Add Model Directory]= , in OPNET Modeler 10.0 window, then create you > > directory and make = it as default. > > I have already done that. > > > > > > > > > I = suppose that the simulation executable file link is authomatically > > >= generated when, after that I have construct the project, I configure > = the > > > simulation (DES > Configure/Run Discrete Event Simulation (Adv= anced)). > Is > > > it > > > so? > > > > Yes, M/M/1 is a simple exam= ple (you have not any promoted variables), so > > you set only the simul= ation time, the seed, the Probe file and YOU SHOULD > > not forget to se= lect your Project-scenario in "Environment Files" > > Of course! > =0D = > > > > > In last mentioned configuration box I only change the probe_fi= le > included > > > in > > > the "output statistic collection" section= . Do I have to set something in > > > the > > > input section, maybe? D= o I do anything wrong? > > > > check that the process model attribute o= f your "src module" is positioned > > to your new saved simple_source pr= ocess. > > > > It is so. > > Regards. > Jers > > > > > >= > > > > > > >> -----Original Message----- > > >> From: manet-bounces@= ietf.org [mailto:manet-bounces@ietf.org] On Behalf > > >> Of > > >> jer= s@inwind.it > > >> Sent: Tuesday, April 19, 2005 6:29 AM > > >> To: man= et > > >> Subject: [manet] An opnet simulation error > > >> > > >>> Hi= all, > > >>> > > >>> I'm a new user of Opnet Modeler and I'm utilizing= it for my studies on > > > manet > > >>> environment. > > >>> To lear= n how to use the modeler, I have developed a simple new process > > > mo= del > > >>> but, > > >>> during the simulation process, while loading = the model libraries, the > > >>> simulation expires and shows the follo= wing > > >>> error message: > > >>> > > >>> Beginning simulation of = project_name-scenario1 at 11:31:26 mar apr 19 > > > 2005 > > >>> -----= > > >>> Kernel: development (not optimized), sequential > > >>> ----= - > > >>> <<< Warning >>> > > >>> Repository missing process model (p= rocess_model_name) > > >>> T (0), EV (-), MOD (NONE), PROC (sim_load_re= pos_prmatch) > > >>> ----- > > >>> <<< Program Abort >>> > > >>> Th= e set of models necessary for running the simulation is incomplete. > > = >>> Check that all the 'repositories' attributes are complete. > > >>> = T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) > > >>> -----=0D = > > >>> > > >>> I noticed that I can successfully carry out the simulat= ions of the > > > "M/M/1 > > >>> Queue" project > > >>> included in = the tutorial but, if at the beginning I change the name > of > > > the=0D = > > >>> process model (e.g., from simple_source in my_source) and then I= > > >>> procede > > >>> according to the "M/M/1 queue" tutorial examp= le, the simulation leads > > >>> to the aforementioned error. I suppose= that this error may be due to > > > wrong > > >>> directory settings = or to an installation problem. Could someone > please > > >>> suggest m= e a way to solve my problem? > > >>> Thanks a lot. > > >>> Jers > > >= >> > > >>> > > > > > > > > > > > > _________________________________= ______________ > > > manet mailing list > > > manet@ietf.org > > > htt= ps://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > > =0D = > > _______________________________________________ > manet mailing li= st > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > =0A= =0A=0A=0A____________________________________________________________=0A6= X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!=0AS= caricalo su INTERNET GRATIS 6X http://www.libero.it=0A _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 20 10:19:40 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOG3I-00076M-MI; Wed, 20 Apr 2005 10:19:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOG3F-00076B-V2 for manet@megatron.ietf.org; Wed, 20 Apr 2005 10:19: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 KAA13034 for ; Wed, 20 Apr 2005 10:19:36 -0400 (EDT) Received: from mailgw3a.lmco.com ([192.35.35.7]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOGET-00049u-1F for manet@ietf.org; Wed, 20 Apr 2005 10:31:14 -0400 Received: from emss04g01.ems.lmco.com (relay4.ems.lmco.com [166.17.13.122]) by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id j3KEJZPl022921; Wed, 20 Apr 2005 10:19:35 -0400 (EDT) Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30884) id <0IF900C0114M0K@lmco.com>; Wed, 20 Apr 2005 10:19:34 -0400 (EDT) Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF V6.1-1X6 #30884) with ESMTP id <0IF900D7H148LQ@lmco.com>; Wed, 20 Apr 2005 10:19:34 -0400 (EDT) Received: from EMSS04M12.us.lmco.com ([166.17.13.94]) by EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Apr 2005 10:18:23 -0400 Date: Wed, 20 Apr 2005 10:18:22 -0400 From: "Flynn, Matthew" Subject: RE: [manet] An opnet simulation error To: jers@inwind.it, manet Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-Topic: [manet] An opnet simulation error Thread-Index: AcVFqvGwsn2vKXKLTLe9MVStAAErkgACFkew content-class: urn:content-classes:message X-OriginalArrivalTime: 20 Apr 2005 14:18:23.0390 (UTC) FILETIME=[CF92E3E0:01C545B3] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 Content-Transfer-Encoding: 7BIT Cc: 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 Jers, Check the Modeler preferences for an item called "repositories". Is this blank? When I want to run the standard models WITHOUT a compiler I put "stdmod" as an entry for "repositories". If the compiler is installed, "repositories" has no entries. -Matt -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of jers@inwind.it Sent: Wednesday, April 20, 2005 9:10 AM To: Hakim.Badis; manet Subject: Re: [manet] An opnet simulation error Sorry Hkim, I'd like to specify that in the prevous mail I meant that all may settings correspond with your suggestions but my problem remains unsolved. Jers > Hi Hakim, > > > If you have OPNET 10.0, you can create your own directory for you > > projects and use it as default directory. To do this, select [File > > > Model Files > Add Model Directory], in OPNET Modeler 10.0 window, > > then create you directory and make it as default. > > I have already done that. > > > > > > > > > I suppose that the simulation executable file link is > > > authomatically generated when, after that I have construct the > > > project, I configure > the > > > simulation (DES > Configure/Run Discrete Event Simulation > > > (Advanced)). > Is > > > it > > > so? > > > > Yes, M/M/1 is a simple example (you have not any promoted > > variables), so you set only the simulation time, the seed, the Probe > > file and YOU SHOULD not forget to select your Project-scenario in > > "Environment Files" > > Of course! > > > > > > In last mentioned configuration box I only change the probe_file > included > > > in > > > the "output statistic collection" section. Do I have to set > > > something in the input section, maybe? Do I do anything wrong? > > > > check that the process model attribute of your "src module" is > > positioned to your new saved simple_source process. > > > > It is so. > > Regards. > Jers > > > > > > > > > > > > >> -----Original Message----- > > >> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On > > >> Behalf Of jers@inwind.it > > >> Sent: Tuesday, April 19, 2005 6:29 AM > > >> To: manet > > >> Subject: [manet] An opnet simulation error > > >> > > >>> Hi all, > > >>> > > >>> I'm a new user of Opnet Modeler and I'm utilizing it for my > > >>> studies on > > > manet > > >>> environment. > > >>> To learn how to use the modeler, I have developed a simple new > > >>> process > > > model > > >>> but, > > >>> during the simulation process, while loading the model > > >>> libraries, the simulation expires and shows the following > > >>> error message: > > >>> > > >>> Beginning simulation of project_name-scenario1 at 11:31:26 mar > > >>> apr 19 > > > 2005 > > >>> ----- > > >>> Kernel: development (not optimized), sequential > > >>> ----- > > >>> <<< Warning >>> > > >>> Repository missing process model (process_model_name) T (0), > > >>> EV (-), MOD (NONE), PROC (sim_load_repos_prmatch) > > >>> ----- > > >>> <<< Program Abort >>> > > >>> The set of models necessary for running the simulation is > > >>> incomplete. Check that all the 'repositories' attributes are > > >>> complete. T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) > > >>> ----- > > >>> > > >>> I noticed that I can successfully carry out the simulations of > > >>> the > > > "M/M/1 > > >>> Queue" project > > >>> included in the tutorial but, if at the beginning I change the > > >>> name > of > > > the > > >>> process model (e.g., from simple_source in my_source) and then > > >>> I procede according to the "M/M/1 queue" tutorial example, the > > >>> simulation leads to the aforementioned error. I suppose that > > >>> this error may be due to > > > wrong > > >>> directory settings or to an installation problem. Could someone > please > > >>> suggest me a way to solve my problem? > > >>> Thanks a lot. > > >>> Jers > > >>> > > >>> > > > > > > > > > > > > _______________________________________________ > > > 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 > ____________________________________________________________ 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero! Scaricalo su INTERNET GRATIS 6X http://www.libero.it _______________________________________________ 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 Apr 20 22:12:34 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOR9Q-0003ma-2v; Wed, 20 Apr 2005 22:10:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOR9N-0003lm-No for manet@megatron.ietf.org; Wed, 20 Apr 2005 22:10: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 WAA20695 for ; Wed, 20 Apr 2005 22:10:39 -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 1DORKh-0008Rn-Gj for manet@ietf.org; Wed, 20 Apr 2005 22:22:24 -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 j3L2AYdK018868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Apr 2005 19:10:36 -0700 (PDT) Date: Wed, 20 Apr 2005 19:10:34 -0700 (PDT) From: Manoj K Pandey To: manet@ietf.org In-Reply-To: <20050416192142.60587.qmail@web80909.mail.scd.yahoo.com> Message-ID: References: <20050416192142.60587.qmail@web80909.mail.scd.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on vitalstatistix X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Subject: [manet] Is background noise a function of data rate? 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 Hi Group, For a SNR based radio simulator, is it correct to assume that the background noise would be a fuction of data rate at which frames are being transmitted? If signals from other radios is already accounted into estimation of SNR, shouldn't the background noise be a constant (equal to white noise perhaps)? Any pointers? Thanks in advance. -Manoj On Sat, 16 Apr 2005, Gokina P C wrote: > Hi, > I am interested in research at QoS issues at MAC layer. To the best of my knowledge there is no previous work which introduces packet prioritization in sleep/wake-up based MAC protocols in Wireless Sensor Networks. > > I am very much interested to know if anybody is doing research focused in this direction or in closely related areas in Mobile Ad-hoc Networks. > > Thanking you, > GP. > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 21 01:25:47 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOUCB-0004bp-7M; Thu, 21 Apr 2005 01:25:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOUC8-0004bd-Jz for manet@megatron.ietf.org; Thu, 21 Apr 2005 01: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 BAA02149 for ; Thu, 21 Apr 2005 01:25:44 -0400 (EDT) Received: from pri-dns.cs.iitm.ernet.in ([202.141.25.89] helo=pridns.cs.iitm.ernet.in) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOUNS-0003gS-Sn for manet@ietf.org; Thu, 21 Apr 2005 01:37:29 -0400 Received: from mail-hpcn.cs.iitm.ernet.in (mail-hpcn.cs.iitm.ernet.in [10.6.6.1]) by pridns.cs.iitm.ernet.in (8.12.10/8.12.10) with ESMTP id j3L5Uuxe007180 for ; Thu, 21 Apr 2005 11:00:59 +0530 Received: from mail-hpcn.cs.iitm.ernet.in (localhost [127.0.0.1]) by mail-hpcn.cs.iitm.ernet.in (8.12.11/8.12.11) with ESMTP id j3L5f1W1020476 for ; Thu, 21 Apr 2005 11:11:01 +0530 Received: from localhost (vramana@localhost) by mail-hpcn.cs.iitm.ernet.in (8.12.11/8.12.11/Submit) with ESMTP id j3L5ep0r020471 for ; Thu, 21 Apr 2005 11:11:01 +0530 X-Authentication-Warning: mail-hpcn.cs.iitm.ernet.in: vramana owned process doing -bs Date: Thu, 21 Apr 2005 11:10:51 +0530 (IST) From: "B. Venkata Ramana" To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [manet] TCP reno vs new reno 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 Dear manet group memers: currently I am testing the performance of TCP reno over new reno over ad hoc wireless networks. TCP NEWRENO shows higher throughput over RENO. However, NEWRENO is showing higher number of retransmissions over RENO. Can you tell me, it this a correct behavior and under what circumstances it behaves like this. Kindly give me appropriate information. regards ramana _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 21 04:20:21 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOWv6-0007M5-J3; Thu, 21 Apr 2005 04:20:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOWv3-0007Lv-Md for manet@megatron.ietf.org; Thu, 21 Apr 2005 04:20:18 -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 EAA04330 for ; Thu, 21 Apr 2005 04:20:16 -0400 (EDT) Received: from smtp20.libero.it ([193.70.192.147]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOX6R-00079L-Hg for manet@ietf.org; Thu, 21 Apr 2005 04:32:04 -0400 Received: from localhost (172.16.1.82) by smtp20.libero.it (7.0.027-DD01) id 41D02C98018F338C; Thu, 21 Apr 2005 10:20:04 +0200 Received: from libero.it (172.16.1.80) by smtp1.libero.it (7.0.027-DD01) id 41BDB1240123C5E2; Thu, 21 Apr 2005 10:19:59 +0200 Date: Thu, 21 Apr 2005 10:20:03 +0200 Message-Id: Subject: RE: [manet] An opnet simulation error MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "jers\@inwind\.it" To: "matthew\.flynn" X-XaM3-API-Version: 4.1 (B27pl2) X-type: 0 X-SenderIP: 151.97.6.47 X-Virus-Scanned: by amavisd-new at libero.it serv3 X-Spam-Score: 0.0 (/) X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9 Content-Transfer-Encoding: quoted-printable Cc: 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 Matt, well done! Thanks a lot! Jers > Jers, > > Check the Mod= eler preferences for an item called "repositories". Is > this blank? W= hen I want to run the standard models WITHOUT a compiler I > put "stdmod= " as an entry for "repositories". If the compiler is > installed, "repo= sitories" has no entries. > > > -Matt > > -----Original Message--= --- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Be= half > Of jers@inwind.it > Sent: Wednesday, April 20, 2005 9:10 AM > T= o: Hakim.Badis; manet > Subject: Re: [manet] An opnet simulation error=0D = > > > Sorry Hkim, > I'd like to specify that in the prevous mail I m= eant that all may > settings correspond with your suggestions but my pro= blem remains > unsolved. Jers > > > > Hi Hakim, > > > > > If you = have OPNET 10.0, you can create your own directory for you > > > projec= ts and use it as default directory. To do this, select [File > > > > >= Model Files > Add Model Directory], in OPNET Modeler 10.0 window, > >= > then create you directory and make it as default. > > > > I have alr= eady done that. > > > > > > > > > > > > > I suppose that the simulati= on executable file link is > > > > authomatically generated when, after= that I have construct the > > > > project, I configure > > the > > >= > simulation (DES > Configure/Run Discrete Event Simulation > > > > (A= dvanced)). > > Is > > > > it > > > > so? > > > > > > Yes, M/M/1 is a= simple example (you have not any promoted > > > variables), so you set= only the simulation time, the seed, the Probe > > > > file and YOU SH= OULD not forget to select your Project-scenario in > > > "Environment F= iles" > > > > Of course! > > > > > > > > > In last mentioned config= uration box I only change the probe_file > > included > > > > in > > >= > the "output statistic collection" section. Do I have to set > > > > = something in the input section, maybe? Do I do anything wrong? > > > > = > > check that the process model attribute of your "src module" is > > = > positioned to your new saved simple_source process. > > > > > > > It= is so. > > > > Regards. > > Jers > > > > > > > > > > > > > > > = > > > > >> -----Original Message----- > > > >> From: manet-bounces@ietf= .org [mailto:manet-bounces@ietf.org] On > > > >> Behalf Of jers@inwind.= it > > > >> Sent: Tuesday, April 19, 2005 6:29 AM > > > >> To: manet=0D = > > > >> Subject: [manet] An opnet simulation error > > > >> > > > >>> = Hi all, > > > >>> > > > >>> I'm a new user of Opnet Modeler and I'm uti= lizing it for my > > > >>> studies on > > > > manet > > > >>> environ= ment. > > > >>> To learn how to use the modeler, I have developed a simp= le new > > > >>> process > > > > model > > > >>> but, > > > >>> dur= ing the simulation process, while loading the model > > > >>> libraries= , the simulation expires and shows the following > > > >>> error mess= age: > > > >>> > > > >>> Beginning simulation of project_name-scenario= 1 at 11:31:26 mar > > > >>> apr 19 > > > > 2005 > > > >>> ----- > >= > >>> Kernel: development (not optimized), sequential > > > >>> -----= > > > >>> <<< Warning >>> > > > >>> Repository missing process model= (process_model_name) T (0), > > > >>> EV (-), MOD (NONE), PROC (sim_l= oad_repos_prmatch) > > > >>> ----- > > > >>> <<< Program Abort >>>=0D = > > > >>> The set of models necessary for running the simulation is > = > > >>> incomplete. Check that all the 'repositories' attributes are =0D = > > > >>> complete. T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load= ) > > > >>> ----- > > > >>> > > > >>> I noticed that I can successfu= lly carry out the simulations of > > > > >>> the > > > > "M/M/1 > > = > >>> Queue" project > > > >>> included in the tutorial but, if at the = beginning I change the > > > >>> name > > of > > > > the > > > >>> = process model (e.g., from simple_source in my_source) and then > > > >>= > I procede according to the "M/M/1 queue" tutorial example, the > > >= >>> simulation leads to the aforementioned error. I suppose that > > = > >>> this error may be due to > > > > wrong > > > >>> directory setti= ngs or to an installation problem. Could someone > > please > > > >>> s= uggest me a way to solve my problem? > > > >>> Thanks a lot. > > > >>>= Jers > > > >>> > > > >>> > > > > > > > > > > > > > > > > _________= ______________________________________ > > > > manet mailing list > > >= > manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet > > > >=0D = > > > > > > > > > > > > > > > > > ________________________________= _______________ > > manet mailing list > > manet@ietf.org > > https://= www1.ietf.org/mailman/listinfo/manet > > > > > > _______________= _____________________________________________ > 6X velocizzare la tua na= vigazione a 56k? 6X Web Accelerator di Libero! > Scaricalo su INTERNET G= RATIS 6X http://www.libero.it > > > > ____________________________= ___________________ > manet mailing list > manet@ietf.org > https://ww= w1.ietf.org/mailman/listinfo/manet > =0A=0A=0A=0A_______________________= _____________________________________=0ANavighi a 4 MEGA e i primi 3 mesi= sono GRATIS. =0AScegli Libero Adsl Flat senza limiti su http://www.liber= o.it=0A _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 21 04:29:46 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOX4D-00008E-SM; Thu, 21 Apr 2005 04:29:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOX4A-000089-Qu for manet@megatron.ietf.org; Thu, 21 Apr 2005 04:29: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 EAA05025 for ; Thu, 21 Apr 2005 04:29:41 -0400 (EDT) Received: from web32010.mail.mud.yahoo.com ([68.142.207.107]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DOXFU-0007Ky-TQ for manet@ietf.org; Thu, 21 Apr 2005 04:41:29 -0400 Received: (qmail 73410 invoked by uid 60001); 21 Apr 2005 08:29:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=m1Inp1CzCFguw9IJPXI0t23JI90hsWPfB9g/UuiKvKK0D9nxO4h1IcA5ULsWbrh5CZ5rBMG4SjTgT0fE1vS2+6LamFSbforRakLblIzZ7TXhSG1WwyFgyhn54aqI9vw9yQskGiFnmz3Tx+a0LunapOsjonHTlXVOmqB0jwcb688= ; Message-ID: <20050421082929.73408.qmail@web32010.mail.mud.yahoo.com> Received: from [210.245.124.96] by web32010.mail.mud.yahoo.com via HTTP; Thu, 21 Apr 2005 01:29:29 PDT Date: Thu, 21 Apr 2005 01:29:29 -0700 (PDT) From: phucnguyen nguyenhoang To: manet In-Reply-To: MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] multihop routing for Internet connectivity in handover 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="===============1003147659==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org --===============1003147659== Content-Type: multipart/alternative; boundary="0-405514426-1114072169=:72838" --0-405514426-1114072169=:72838 Content-Type: text/plain; charset=us-ascii Hi all, I am researching multihop MANET routing protocol for Internet connectivity in handover in HMIP v6. If you have researched it before, please tell me thanks a lot Nguyen Hoang Phuc Nguyen __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-405514426-1114072169=:72838 Content-Type: text/html; charset=us-ascii

Hi all,

I am researching multihop MANET routing protocol for Internet connectivity in handover in HMIP v6.

If you have researched it before, please tell me

 

thanks a lot

Nguyen Hoang Phuc Nguyen

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-405514426-1114072169=:72838-- --===============1003147659== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1003147659==-- From manet-bounces@ietf.org Thu Apr 21 05:33:16 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOY3f-00079K-Kz; Thu, 21 Apr 2005 05:33:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOY3d-00078M-IJ for manet@megatron.ietf.org; Thu, 21 Apr 2005 05:33: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 FAA10060 for ; Thu, 21 Apr 2005 05:33:11 -0400 (EDT) From: vkumar@ece.iisc.ernet.in Received: from ece.iisc.ernet.in ([144.16.64.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOYEz-0000A7-OJ for manet@ietf.org; Thu, 21 Apr 2005 05:45:00 -0400 Received: from sandbox.ece.iisc.ernet.in (sandbox.ece.iisc.ernet.in [10.32.13.14]) by ece.iisc.ernet.in (8.12.6/8.12.6) with ESMTP id j3L9RpEF067518; Thu, 21 Apr 2005 14:58:13 +0530 (IST) (envelope-from vkumar@ece.iisc.ernet.in) Received: from sandbox.ece.iisc.ernet.in (localhost.localdomain [127.0.0.1]) by sandbox.ece.iisc.ernet.in (8.12.10/8.12.10) with ESMTP id j3L6GnLf017391; Thu, 21 Apr 2005 11:46:49 +0530 Received: from localhost (vkumar@localhost) by sandbox.ece.iisc.ernet.in (8.12.10/8.12.10/Submit) with ESMTP id j3L6GnBo017387; Thu, 21 Apr 2005 11:46:49 +0530 X-Authentication-Warning: sandbox.ece.iisc.ernet.in: vkumar owned process doing -bs Date: Thu, 21 Apr 2005 11:46:49 +0530 (IST) To: "B. Venkata Ramana" Subject: Re: [manet] TCP reno vs new reno In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.3 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 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 please check the following web page for the relevant info: http://www.hep.ucl.ac.uk/~ytl/tcpip/background/tahoe-reno.html Vinod Kumar On Thu, 21 Apr 2005, B. Venkata Ramana wrote: > > Dear manet group memers: > > currently I am testing the performance of TCP reno over new reno over ad hoc > wireless networks. TCP NEWRENO shows higher throughput over RENO. However, > NEWRENO is showing higher number of retransmissions over RENO. Can you tell > me, it this a correct behavior and under what circumstances it behaves like > this. Kindly give me appropriate information. > > regards > ramana > > > _______________________________________________ > 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 Apr 21 05:43:55 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOYDx-00005d-Rl; Thu, 21 Apr 2005 05:43:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOYDr-00005Q-PD for manet@megatron.ietf.org; Thu, 21 Apr 2005 05:43: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 FAA10823 for ; Thu, 21 Apr 2005 05:43:45 -0400 (EDT) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOYPG-0000Oz-6b for manet@ietf.org; Thu, 21 Apr 2005 05:55:34 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j3L9hSgA010524 for ; Thu, 21 Apr 2005 11:43:28 +0200 (CEST) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id A36133C2D9 for ; Thu, 21 Apr 2005 11:43:30 +0200 (MEST) Message-ID: <426775C2.3000403@eurecom.fr> Date: Thu, 21 Apr 2005 11:43:30 +0200 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: 7bit Subject: [manet] Sensitiveness in MANET node 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 Hello everyone, I have a question regarding the setup of a 802.11 MANET. I am setting up a MANET using an iPaq and a laptop as nodes. On iPaq (a.k.a LAB1)I use Familiar Linux (version 0.7.2) as an OS. I use Dell Truemobile 1150 WLAN adapters (Orinoco driver version 0.11b) set in ad hoc mode. I configure the eth0 interface on my iPaq LAB1 with a script (wifi.sh) that contains the following lines. ~ # more ./wifi.sh ifconfig eth0 down ifconfig eth0 up ifconfig eth0 inet $1 iwconfig eth0 mode Ad-Hoc iwconfig eth0 channel 10 iwconfig eth0 essid mobman In this script I statically assign an IP address to the node, then set the node in ad-hoc mode, set the channel and give it an ESSID Straight after executing this script, iwconfig gives the following results: ~ # iwconfig eth0 eth0 IEEE 802.11-DS ESSID:"mobman" Nickname:"HERMES I" Mode:Ad-Hoc Frequency:2.462GHz Cell: 00:09:5B:FD:F3:20 Bit Rate:5.5Mb/s Tx-Power=15 dBm Sensitivity:1/242700000 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:26 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 This outcome is really odd for (at least) the following reasons: 1) Frequency does not correspond to channel 10 2) Despite the fact that there is already another node (a Linux laptop equipped with the same Dell Truemobile 1150 WLAN adapter that I will call LAB2) online belonging to the same IBSS (=having the same ESSID and set in channel 10), the iPaq does not associate with this latter device but with "Cell: 00:09:5B:FD:F3:20". 3) "Sensitivity" value seems to be low. At the beginning I did not figure out what this MAC address was. Then using a Wireless Network utility on a third PC ( a.k.a. LAB3) I found out that "Cell: 00:09:5B:FD:F3:20" corresponds to the MAC address of is an AP located in a besides building. This MAC address does not always appear in the wireless network utility on LAB3 but even when it does not, it seems somehow to perturbate the configuration of LAB1. I guess that this MAC appears on LAB3 only when the received signal is stronger than a given threshold. My questions are: 1) Could this LAB1 strange behavior depend on the value of the "Sensitivity" parameter? This value seems to be extremely low, does this indicate that my LAB1 is very prone to be perturbated by surrounding devices? 2) If the sensitivity is the cause of my problem, how can I set it differently? I did not succeed in changing it using iwconfig. What are reasonable values? 3) What are the scripts to modify to make it so that my iPaq tunes to the right network every time I put the WLAN adapter in the PCMCIA slot? I heard that if I do so, the WLAN adapter will sty tuned to the selected network forever. Is this true? Thx for any hint/suggestion/help Claudio _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 21 05:46:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOYGc-0000Oa-GY; Thu, 21 Apr 2005 05:46:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOYGV-0000LT-Kt for manet@megatron.ietf.org; Thu, 21 Apr 2005 05:46: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 FAA11025 for ; Thu, 21 Apr 2005 05:46:29 -0400 (EDT) Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOYRu-0000Ty-Bb for manet@ietf.org; Thu, 21 Apr 2005 05:58:18 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id j3L9kJv8010678 for ; Thu, 21 Apr 2005 11:46:19 +0200 (CEST) Received: from eurecom.fr (bekipan.eurecom.fr [172.17.10.219]) by monza.eurecom.fr (Postfix) with ESMTP id 957D63C2D9 for ; Thu, 21 Apr 2005 11:46:21 +0200 (MEST) Message-ID: <4267766D.3020009@eurecom.fr> Date: Thu, 21 Apr 2005 11:46:21 +0200 From: Claudio Lavecchia User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Content-Transfer-Encoding: 7bit Subject: [manet] Configuration problem on a 802.11 MANET node 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 SORRY PEOPLE: THIS IS A REPEATED POST BUT PREVIOUS SUBJECT WAS NOT APPROPRIATE Hello everyone, I have a question regarding the setup of a 802.11 MANET. I am setting up a MANET using an iPaq and a laptop as nodes. On iPaq (a.k.a LAB1)I use Familiar Linux (version 0.7.2) as an OS. I use Dell Truemobile 1150 WLAN adapters (Orinoco driver version 0.11b) set in ad hoc mode. I configure the eth0 interface on my iPaq LAB1 with a script (wifi.sh) that contains the following lines. ~ # more ./wifi.sh ifconfig eth0 down ifconfig eth0 up ifconfig eth0 inet $1 iwconfig eth0 mode Ad-Hoc iwconfig eth0 channel 10 iwconfig eth0 essid mobman In this script I statically assign an IP address to the node, then set the node in ad-hoc mode, set the channel and give it an ESSID Straight after executing this script, iwconfig gives the following results: ~ # iwconfig eth0 eth0 IEEE 802.11-DS ESSID:"mobman" Nickname:"HERMES I" Mode:Ad-Hoc Frequency:2.462GHz Cell: 00:09:5B:FD:F3:20 Bit Rate:5.5Mb/s Tx-Power=15 dBm Sensitivity:1/242700000 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:26 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 This outcome is really odd for (at least) the following reasons: 1) Frequency does not correspond to channel 10 2) Despite the fact that there is already another node (a Linux laptop equipped with the same Dell Truemobile 1150 WLAN adapter that I will call LAB2) online belonging to the same IBSS (=having the same ESSID and set in channel 10), the iPaq does not associate with this latter device but with "Cell: 00:09:5B:FD:F3:20". 3) "Sensitivity" value seems to be low. At the beginning I did not figure out what this MAC address was. Then using a Wireless Network utility on a third PC ( a.k.a. LAB3) I found out that "Cell: 00:09:5B:FD:F3:20" corresponds to the MAC address of is an AP located in a besides building. This MAC address does not always appear in the wireless network utility on LAB3 but even when it does not, it seems somehow to perturbate the configuration of LAB1. I guess that this MAC appears on LAB3 only when the received signal is stronger than a given threshold. My questions are: 1) Could this LAB1 strange behavior depend on the value of the "Sensitivity" parameter? This value seems to be extremely low, does this indicate that my LAB1 is very prone to be perturbated by surrounding devices? 2) If the sensitivity is the cause of my problem, how can I set it differently? I did not succeed in changing it using iwconfig. What are reasonable values? 3) What are the scripts to modify to make it so that my iPaq tunes to the right network every time I put the WLAN adapter in the PCMCIA slot? I heard that if I do so, the WLAN adapter will sty tuned to the selected network forever. Is this true? Thx for any hint/suggestion/help Claudio _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 21 13:55:40 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOfts-0004IU-9Z; Thu, 21 Apr 2005 13:55:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOftp-0004IP-Sr for manet@megatron.ietf.org; Thu, 21 Apr 2005 13:55: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 NAA21897 for ; Thu, 21 Apr 2005 13:55:37 -0400 (EDT) Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOg5J-0006H1-1r for manet@ietf.org; Thu, 21 Apr 2005 14:07:29 -0400 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j3LHtV1R012448; Thu, 21 Apr 2005 10:55:31 -0700 (MST) Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j3LHvZHf010571; Thu, 21 Apr 2005 12:57:36 -0500 (CDT) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id A4787865980; Thu, 21 Apr 2005 19:55:29 +0200 (CEST) Message-ID: <4267E911.5010704@motorola.com> Date: Thu, 21 Apr 2005 19:55:29 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Claudio Lavecchia Subject: Re: [manet] Configuration problem on a 802.11 MANET node References: <4267766D.3020009@eurecom.fr> In-Reply-To: <4267766D.3020009@eurecom.fr> X-Enigmail-Version: 0.89.0.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: 73734d43604d52d23b3eba644a169745 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 Claudio, after you fix this, are you going to run IPv6 on this setup? Claudio Lavecchia wrote: > ~ # more ./wifi.sh > ifconfig eth0 down > ifconfig eth0 up > ifconfig eth0 inet $1 > iwconfig eth0 mode Ad-Hoc > iwconfig eth0 channel 10 No need of the channel parameter. Why one one specifically need a specific channel? I thought the link-layer manages to automatically hop between channels as appropriate (I'm not sure whether "hopping" is the right term). > 1) Frequency does not correspond to channel 10 In my experience of iwconfig the reported frequency and channels, as well as the selected bandwidth (2, 5, 11) don't always correspond to what's actually happening. Various cards are supported to various extents by iwconfig. > 2) Despite the fact that there is already another node (a Linux laptop > equipped with the same Dell Truemobile 1150 WLAN adapter that I will > call LAB2) online belonging to the same IBSS (=having the same ESSID and > set in channel 10), the iPaq does not associate with this latter device > but with "Cell: 00:09:5B:FD:F3:20". That other Linux laptop must also be in iwconfig ad-hoc mode. Make sure that the iwconfig mode ad-hoc is successfull (echo $?) and no error reported on the command line after iwconfig. > 3) "Sensitivity" value seems to be low. > > At the beginning I did not figure out what this MAC address was. Then > using a Wireless Network utility on a third PC ( a.k.a. LAB3) I found > out that "Cell: 00:09:5B:FD:F3:20" corresponds to the MAC address of is > an AP located in a besides building. Fun fun. If you want to make sure that a certain ESSID is used, always use a key for that ESSID. Uisng a combination ESSID+key (instead of just ESSID and some channel) is deterministic in a wide range of cases for me. I let the devices choose the channels they want to talk to each other, I don't care about them. > My questions are: > 1) Could this LAB1 strange behavior depend on the value of the > "Sensitivity" parameter? This value seems to be extremely low, does this > indicate that my LAB1 is very prone to be perturbated by surrounding > devices? > 2) If the sensitivity is the cause of my problem, how can I set it > differently? I did not succeed in changing it using iwconfig. What are > reasonable values? > 3) What are the scripts to modify to make it so that my iPaq tunes to > the right network every time I put the WLAN adapter in the PCMCIA slot? Just decide an ESSID and a key on both peers in the ad-hoc mode. Don't choose channels and sensitivity. No other AP or Client will get in your way (unless they use same ESSID and key) even the APs that are completely open (no ESSID no key). The MAC address that's going to be seen as "Cell" is not the MAC address of any of the clients of the ad-hoc network, but it is somehow decided randomly(?) by the first client on which the iwconfig mode ad-hoc is done. E.g.: 1# ifconfig eth1 down 1# iwconfig essid "myadhocnet" key "1122334455" mode ad-hoc 1# ifconfig eth1 up 2# ifconfig eth1 down 2# iwconfig essid "myadhocnet" key "1122334455" mode ad-hoc 2# ifconfig eth1 up 1# iwconfig eth1 Cell: a-random-mac-like-address 2# iwconfig eth1 Cell: same-mac-like-address > I heard that if I do so, the WLAN adapter will sty tuned to the selected > network forever. Is this true? "Forever" :-)? Alex _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 22 00:46:48 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOq40-0007Sl-0l; Fri, 22 Apr 2005 00:46:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOq3x-0007Sg-Sc for manet@megatron.ietf.org; Fri, 22 Apr 2005 00:46: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 AAA19702 for ; Fri, 22 Apr 2005 00:46:43 -0400 (EDT) Received: from mail1.engr.ucsb.edu ([128.111.53.4] helo=smtp.engr.ucsb.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOqFV-0007bi-Ql for manet@ietf.org; Fri, 22 Apr 2005 00:58:43 -0400 Received: from ip70-185-181-15.sb.sd.cox.net ([70.185.181.15]:53463 helo=[192.168.0.11]) by smtp.engr.ucsb.edu with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1DOq3k-0001aA-Ou; Thu, 21 Apr 2005 21:46:35 -0700 Mime-Version: 1.0 (Apple Message framework v622) Message-Id: From: Ian Chakeres Date: Thu, 21 Apr 2005 21:46:35 -0700 To: manet X-Mailer: Apple Mail (2.622) X-Virus-Scanned: Determined clean by smtp.engr.ucsb.edu using clamd / ClamAV version 0.80 X-SA-Exim-Connect-IP: 70.185.181.15 X-SA-Exim-Mail-From: idc@cs.ucsb.edu Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on smtp.engr.ucsb.edu X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-SA-Exim-Version: 4.1 (built Mon, 13 Dec 2004 10:51:27 -0800) X-SA-Exim-Scanned: Yes (on smtp.engr.ucsb.edu) X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Content-Transfer-Encoding: 7bit Subject: [manet] IETF-62 Proceedings Available 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 The IETF-62 proceedings have been posted at http://www3.ietf.org/proceedings/05mar/index.html. Ian Chakeres _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 22 01:16:36 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOqWp-0002v3-Ps; Fri, 22 Apr 2005 01:16:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOqWl-0002us-Sd for manet@megatron.ietf.org; Fri, 22 Apr 2005 01:16:32 -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 BAA21375 for ; Fri, 22 Apr 2005 01:16:31 -0400 (EDT) Received: from wproxy.gmail.com ([64.233.184.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOqiK-0008C3-4V for manet@ietf.org; Fri, 22 Apr 2005 01:28:29 -0400 Received: by wproxy.gmail.com with SMTP id 58so694063wri for ; Thu, 21 Apr 2005 22:16:21 -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:content-disposition; b=LplLTlwCNGnypLggLpAh2r4polg0c59CKWQHWNjvl3mn7ODHluq/UTCrkiWqioxl54Sc+vjFszs8dDIjGV0V21sdM7oVLp3oj7UXyMNPIg2k6OaqBKIrlNE9eeu44p856S3WBUEStIRpsR10092mo4Vxkd5FzAP0+AXP++3za8Q= Received: by 10.54.49.34 with SMTP id w34mr256374wrw; Thu, 21 Apr 2005 22:16:21 -0700 (PDT) Received: by 10.54.149.8 with HTTP; Thu, 21 Apr 2005 22:16:21 -0700 (PDT) Message-ID: <2411362d050421221670b152e9@mail.gmail.com> Date: Fri, 22 Apr 2005 14:16:21 +0900 From: Pradipta Pradhan To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Score: 0.9 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: quoted-printable Subject: [manet] Simulation run error X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pradipta Pradhan 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 Dear ALL, I am new in OPNET. I am trying to simulate manet with aodv using OPNET.=20 I want to see the effect of misbehaving nodes. For RREQ and RREP flooding, I have modified process models and saved with different names. I have successfully compiled them but during simulation run I have encountered with following errors: Low-Lev.=09Simulation=09Error=09<<< Recoverable Error >>> reported by Simulation Kernel Object repository construction failed due to errors encountered by the binder program (bind_so_msvc) T (0), EV (-), MOD (NONE), PROC (sim_load_repos_rebuild) =09Low-Lev.=09Simulation=09Error=09<<< Program Abort >>> reported by Simulation Kernel Error encountered rebuilding repository -- unable to proceed T (0), EV (-), MOD (NONE), PROC (sim_load_repos_load) I could not figure out the solution. Could anybody help me to solve this problem?? Thanks in advance. Pradipta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 22 05:05:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOu6G-0003KP-MJ; Fri, 22 Apr 2005 05:05:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOu6D-0003KK-Ev for manet@megatron.ietf.org; Fri, 22 Apr 2005 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 FAA26730 for ; Fri, 22 Apr 2005 05:05:19 -0400 (EDT) Received: from exch1.jmu.ac.uk ([150.204.37.7]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOuHo-0004ga-Lf for manet@ietf.org; Fri, 22 Apr 2005 05:17:21 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 22 Apr 2005 10:04:36 +0100 Message-ID: <536E572B1EF26E4A8ADCFFF245FCCEE00145C9D1@EXCH1.jmu.ac.uk> Thread-Topic: Call for proposals - 2nd IEEE Workshop on Digital Rights Management Impact on Consumer Communications Thread-Index: AcVGWO/ugUB5mu5HRxS2DkJcuFAkdAAwV55n From: "Fergus, Paul" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 Content-Transfer-Encoding: quoted-printable Subject: [manet] FW: Call for proposals - 2nd IEEE Workshop on Digital Rights Management Impact on Consumer Communications 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 =20 CALL FOR PROPOSALS =20 2nd Workshop on Digital Rights Management Impact on Consumer = Communications 10 January 2006 http://www.ieee-ccnc.org/2006/conf_program/drm_workshop/index.htm = =20 Las Vegas Convention Center, Las Vegas, NV, USA =20 Held in conjunction with CCNC 2006 (http://www.ieee-ccnc.org/2006 = ) and the Consumer Electronics Show = (CES) =20 Consumers and consumer electronics are increasingly using the Internet = for distribution of digital goods, including digital versions of books, = articles, music, and images. The ease with which digital goods can be = copied and redistributed makes the Internet well suited for unauthorized = copying, modification and redistribution. The rapid adoption of new = technologies such as high-bandwidth connections, wireless networks, and = peer-to-peer networks is accelerating this process.=20 This half-day workshop on Digital Rights Management Impact on Consumer = Communications addresses problems faced by rights holders (who seek to = protect their intellectual property rights) and by end consumers (who = seek to protect their privacy and to preserve access they now enjoy in = traditional media under).=20 Digital Rights Management (DRM) systems are intended to protect the = rights of content owners in scenarios in which the participants have = conflicting goals and are not fully trusted. This adversarial situation = introduces interesting new twists on classical problems studied in = cryptology and security research, such as key management and access = control. Furthermore, novel security mechanisms can enable new business = models and applications. Recent research has also proposed new = primitives for DRM, such as hash functions that make it possible to = identify content in an adversarial setting.=20 The workshop will contain some invited presentations and presentations = accepted by open submission. The format will be a series of = presentations held in a panel/forum type of environment to encourage = interaction and discussion of topics and issues.=20 The workshop seeks workshop proposal submissions (consisting of a paper) = on all theoretical and practical aspects of DRM, as well as experimental = studies of fielded systems on topics including, but not limited to, = those shown below: * DRM protocols=20 * architectures for DRM systems=20 * interoperability=20 * auditing=20 * business models for online content distribution=20 * copyright-law issues, including but not limited to fair use=20 * digital policy management=20 * information ownership=20 * privacy and anonymity=20 * risk management=20 * robust identification of digital content=20 * security issues, including but not limited to authorization, = encryption, tamper resistance, and watermarking=20 * threat and vulnerability assessment=20 * usability aspects of DRM systems=20 * web services=20 * CAPEX, OPEX, TCO examples/ estimations/models=20 * computing environments and platforms for DRM (TCP - Trusted Computing = Platform)=20 * Implementations and case studies A journal special issue consisting of selected papers from this = conference is being planned. Authors of selected papers will be invited = to submit an extended version of their paper for the journal.=20 Guidelines for Submission Interested participants should submit a paper (6 pages) describing their = proposed topic. This paper should define the specific problem being = addressed, describe the novelty of the solution to the problem and/or = the issues surrounding the problem. The paper should be used as the = basis for a 20-30 minute Workshop presentation which will be made = available online. Participants are required to develop and submit = presentations. =20 1. Submit an electronic copy of the paper in a .pdf or .ps format = by selecting CCNC'06 at the EDAS paper submission site (http://edas.info = ). 2. A separate cover sheet should show the title of the paper, the = author(s) name(s) and affiliation(s), and the address (including e-mail, = telephone, and fax) to which the correspondence should be sent. =20 Important Dates 15 June 2005................... Paper submission 1 September 2005............. Author Notification 15 October 2005............... Final Camera Ready Paper Submission = Deadline 10 January 2006................Workshop =20 Chair: Madjid Merabti, Liverpool John Moores University=20 =20 Proposed Technical Program Committee: Leonardo Chiariglione, Digital Media Project Rajit Gadh, UCLA Lindsey Holman, Panasonic Deepa Kundur, Texas A&M University Wenjun Zeng, University of Missouri Marc Waldman, Manhattan College Heather Yu, Panasonic =20 Bin Zhu, Microsoft Research Asia Madjid Merabti, Liverpool John Moores University=20 Ning Zhang, Manchester University =20 Participation Go to http://www.ieee-ccnc.org/2006/conf_program/drm_workshop/index.htm = for registration/participation information _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Apr 23 04:33:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPG51-00083P-DV; Sat, 23 Apr 2005 04:33:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPG4v-00083H-DZ for manet@megatron.ietf.org; Sat, 23 Apr 2005 04:33: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 EAA07352 for ; Sat, 23 Apr 2005 04:33:27 -0400 (EDT) Received: from web40507.mail.yahoo.com ([66.218.78.124]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DPGGh-0007HG-0Z for manet@ietf.org; Sat, 23 Apr 2005 04:45:41 -0400 Received: (qmail 27070 invoked by uid 60001); 23 Apr 2005 08:33:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=m345d+16VEheIEjtyChz5M46qOYCypAtJy2W7W2AcLzqZdwPOAh8nRFxrQUioyAYls1F1R3BqZthe7/L2IWklqgbfpBnIr7L9MJPTHY5QN75yo4XqsFg53W9MKQYIlKHK9W5wTwDehRKxuoVc2UVrCXqVVDtbrZvIJUO+1nZTjk= ; Message-ID: <20050423083317.27068.qmail@web40507.mail.yahoo.com> Received: from [210.212.89.5] by web40507.mail.yahoo.com via HTTP; Sat, 23 Apr 2005 01:33:17 PDT Date: Sat, 23 Apr 2005 01:33:17 -0700 (PDT) From: "inforaks@yahoo.com" To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 2.9 (++) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [manet] Please help:How to get "Average link duration" in ns2 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0101961005==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org --===============0101961005== Content-Type: multipart/alternative; boundary="0-1532476766-1114245197=:26511" --0-1532476766-1114245197=:26511 Content-Type: text/plain; charset=us-ascii Hi Please guide me how to get "Average link duration" in ns2. i know that we can change avg.link duration by varying speed and/or pause time but how to get it. any example will b really helpful to me. Thanks in advance rakesh Sorry: I have put this mail to ns user list but i didnt get any reply so i have mailed in this group. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-1532476766-1114245197=:26511 Content-Type: text/html; charset=us-ascii

Hi
Please guide me how to get "Average link duration" in ns2. i know that
we can change avg.link duration by varying speed and/or pause time but
how to get it. any example will b really helpful to me.

Thanks in advance
rakesh
Sorry: I have put this mail to ns user list but i didnt get any reply so i have mailed in this group.
 

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-1532476766-1114245197=:26511-- --===============0101961005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0101961005==-- From manet-bounces@ietf.org Tue Apr 26 11:23:25 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQRuH-0002G6-2f; Tue, 26 Apr 2005 11:23:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQRuE-0002Fq-MZ for manet@megatron.ietf.org; Tue, 26 Apr 2005 11:23: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 LAA17740 for ; Tue, 26 Apr 2005 11:23:20 -0400 (EDT) Received: from web26403.mail.ukl.yahoo.com ([217.146.176.27]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DQS6h-0007GT-39 for manet@ietf.org; Tue, 26 Apr 2005 11:36:16 -0400 Received: (qmail 53595 invoked by uid 60001); 26 Apr 2005 15:23:07 -0000 Message-ID: <20050426152307.53593.qmail@web26403.mail.ukl.yahoo.com> Received: from [196.203.126.9] by web26403.mail.ukl.yahoo.com via HTTP; Tue, 26 Apr 2005 17:23:07 CEST Date: Tue, 26 Apr 2005 17:23:07 +0200 (CEST) From: amine elabidi To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 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 LAA17740 Subject: [manet] autoconfiguration in manet 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: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org Hi I=92m interested in auto configuration in manet network using OLSR as routing algorithm. My question is can I use the information in the hello message like (list of neighbour =85) to detect a duplicated address =20 any response will b really helpful to me. thinks =20 =09 =09 =09 __________________________________________________________________ D=E9couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos= mails !=20 Cr=E9ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Apr 26 12:44:44 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQTAy-00008l-4X; Tue, 26 Apr 2005 12:44:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQTAw-00008g-Jm for manet@megatron.ietf.org; Tue, 26 Apr 2005 12:44: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 MAA25046 for ; Tue, 26 Apr 2005 12:44:39 -0400 (EDT) Received: from mailg.surrey.ac.uk ([131.227.102.21]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DQTNP-0001FQ-Iv for manet@ietf.org; Tue, 26 Apr 2005 12:57:36 -0400 Received: from ads33.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP) with ESMTP; Tue, 26 Apr 2005 17:19:08 +0100 Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136]) by ads33.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Apr 2005 17:19:08 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 26 Apr 2005 17:17:04 +0100 Message-ID: Thread-Topic: Face Routing in MANETs Thread-Index: AcUy74KVGorGgjzUQ0CFIFXIinjOxAAAilJhBeJtvSc= From: "S.Sivavakeesar" To: manet X-OriginalArrivalTime: 26 Apr 2005 16:19:08.0085 (UTC) FILETIME=[AC3A1E50:01C54A7B] X-Spam-Score: 0.2 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Subject: [manet] Face Routing in MANETs X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0065931261==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============0065931261== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C54A7B.AC218C0B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C54A7B.AC218C0B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear All : =20 Can somebody please tell me whether there exists any implementation for = face-routing [OR perimeter routing approach -namely compass routing II, = GPSR, GEDIR] in GloMoSim ? Thanks in advance for your time. =20 Cheers =20 Siva ------_=_NextPart_001_01C54A7B.AC218C0B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= =0A= manet Digest, Vol 11, Issue 39=0A= =0A= =0A=

=0A=
Dear All :
=0A=
 
=0A=
Can somebody please tell me whether there = exists any =0A= implementation for face-routing [OR perimeter routing approach -namely = compass =0A= routing II, GPSR, GEDIR]  in GloMoSim ?
=0A=
=0A=
=0A=
=0A=
Thanks in advance for your = time.
=0A=
 
=0A=
Cheers
=0A=
 
=0A=
Siva
=0A= =0A= =0A= ------_=_NextPart_001_01C54A7B.AC218C0B-- --===============0065931261== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0065931261==-- From manet-bounces@ietf.org Tue Apr 26 22:42:44 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQcVg-0004F8-QR; Tue, 26 Apr 2005 22:42:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQcVe-0004Ex-SJ for manet@megatron.ietf.org; Tue, 26 Apr 2005 22:42: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 WAA16873 for ; Tue, 26 Apr 2005 22:42:40 -0400 (EDT) Received: from mailgate.cc.niigata-u.ac.jp ([133.35.14.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQciB-0007GK-R9 for manet@ietf.org; Tue, 26 Apr 2005 22:55:42 -0400 Received: from mh.ie.niigata-u.ac.jp (mailgate.cc.niigata-u.ac.jp [127.0.0.1]) by mailgate.cc.niigata-u.ac.jp (8.11.6/8.11.6) with SMTP id j3R2gTo22799 for ; Wed, 27 Apr 2005 11:42:29 +0900 Received: (qmail 28703 invoked by uid 1003); 27 Apr 2005 02:42:28 -0000 Received: from unknown (HELO MS191.ie.niigata-u.ac.jp) (133.35.156.191) by noppei.ie.niigata-u.ac.jp with SMTP; 27 Apr 2005 02:42:28 -0000 Message-Id: <5.0.2.5.2.20050427113705.06ad0ad0@127.0.0.1> X-Sender: mh.ie.niigata-u.ac.jp:mase:apop@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J Date: Wed, 27 Apr 2005 11:42:22 +0900 To: amine elabidi , manet@ietf.org From: mase Subject: Re: [manet] autoconfiguration in manet network In-Reply-To: <20050426152307.53593.qmail@web26403.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Cc: 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 Hi, Exactly. We have developed an autoconfiguration proposal for OLSR (NOA-OLSR) Please see Regards, Kenichi At 17:23 05/04/26 +0200, amine elabidi wrote: >Hi >I$BCN(B interested in auto configuration in manet network >using OLSR as routing algorithm. My question is can I >use the information in the hello message like (list of >neighbour $B)>any response will b really helpful to me. >thinks > > > > > > > > >__________________________________________________________________ >D$BqD(Bouvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! >Cr$BqF(Bz votre Yahoo! Mail sur http://fr.mail.yahoo.com/ > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 27 00:03:57 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQdmG-0007D2-TT; Wed, 27 Apr 2005 00: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 1DQdmE-0007Cx-Sn for manet@megatron.ietf.org; Wed, 27 Apr 2005 00:03: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 AAA21878 for ; Wed, 27 Apr 2005 00:03:50 -0400 (EDT) Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQdyl-0000F3-Ri for manet@ietf.org; Wed, 27 Apr 2005 00:16:53 -0400 Received: from hazy (hazy.research.telcordia.com [207.3.231.19]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id j3R43QOf019522; Wed, 27 Apr 2005 00:03:26 -0400 (EDT) Date: Wed, 27 Apr 2005 00:03:26 -0400 (EDT) From: Giovanni Di Crescenzo X-X-Sender: giovanni@hazy To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Subject: [manet] WCAN 05 deadline extended to Apr 31st 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 WCAN 05 call for paper - deadline extended to Apr 31st (apologies if the following is undesired or was already received) CALL FOR PAPERS: 1st Workshop on Cryptography over Ad hoc Networks (WCAN 05) (A Satellite Workshop of Wirelesscom 05, http://sa1.sice.umkc.edu/wc05) Workshop Dates: June 15-16 Workshop Location: Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, http://www.sheraton-maui.com Wireless ad hoc networks are today receiving a lot of attention for militar, commercial and civilian applications, thus raising several challenging security, privacy and anonimity research questions. The security research community has mainly focused on securing routing and is only recently widening its scope of analysis to other security areas. The cryptography research community has mainly focused on standard networks, like the Internet; however, cryptographic protocols for the Internet face serious challenges to be adapted to the ad-hoc, partial-connectivity, mobile, and infrastructureless nature of ad-hoc networks. The aim of this workshop is to help bridging this gap, towards a more comprehensive investigation of security and cryptographic tools, analysis and modeling methodologies over (mobile) ad hoc networks, by bringing together the cryptography, network security, and wireless networking communities. We seek submissions containing original research on all aspects of cryptology in wireless ad hoc networks. Short surveys of sub-areas are also encouraged. Main topics of interest include, but are not limited to the following: Ad Hoc Networks and Resources Modeling Secure Routing Security Bootstrapping Trust Establishment Distributed Public-Key Infrastructures Key Agreement, Management and (Pre)Distribution over Ad Hoc Networks Resource-Constrained Cryptography over Ad Hoc Networks Threshold Cryptography over Ad Hoc Networks Identity-Based Cryptography over Ad Hoc Networks Policy-Based Cryptography over Ad Hoc Networks Secure Multi-Party Protocols over Ad Hoc Networks Security in Distributed Algorithms and Protocols Important Dates: Submission Deadline: April 31, 2005 Notification of Acceptance: May 13, 2005 Camera-Ready Papers: May 20, 2005 Program Chair: Giovanni Di Crescenzo, Telcordia, NJ, USA. giovanni@research.telcordia.com Program Committee: Mike Burmester (Florida State University) David Carman (Johns Hopkins AP Lab), Giovanni Di Crescenzo (Telcordia), Renwei Ge (University of Delaware), Jonathan Katz (University of Maryland), David Naccache (Gemplus), Giuseppe Persiano (University of Salerno), Zulfikar Ramzan (Docomo Labs), Raj Rajagopalan (Hewlett Packard Labs), Ravi Sundaram (Northeastern University), Doug Tygar (UC Berkeley), Serge Vaudenay (Swiss Federal Institute of Technologies). Moti Yung (RSA & Columbia University) General Chair: Farooq Anjum, Telcordia. fanjum@telcordia.com Instructions for Authors: Authors are invited to submit surveys or original papers, possibly about work in progress, that deal with both cryptology and ad hoc networks. All submissions will be refereed and must not substantially duplicate work that any of the authors have published elsewhere or have submitted in parallel. The submissions, preferably in PDF or PS format, must not exceed 6 pages (excluding appendices) nor 12 pages overall. In order to submit a paper, please send your paper as an attachment of an ascii e-mail to acns05chair@research.telcordia.com, indicating title of paper, names and affiliations of authors, and full contact information (affiliation, e-mail and phone number) of the contact author. The camera-ready version should not exceed 6 pages in standard double-column IEEE format. Workshop Proceedings: to be published by IEEE. More details will be provided to the authors. Hotel Information: Posted at http://sa1.sice.umkc.edu/wc05/HotelRes.txt. Early reservation is recommended to benefit from workshop discount. Registration Information: Posted at http://sa1.sice.umkc.edu/wc05/reg.txt for authors, and http://sa1.sice.umkc.edu/wc05/nreg.txt for non-authors. Authors of an accepted paper must guarantee presentation of their paper at the workshop. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 27 09:15:37 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQmO9-0004Y7-3M; Wed, 27 Apr 2005 09:15:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQmO6-0004Xz-Px for manet@megatron.ietf.org; Wed, 27 Apr 2005 09:15: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 JAA09547 for ; Wed, 27 Apr 2005 09:15:28 -0400 (EDT) Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQmae-000342-CE for manet@ietf.org; Wed, 27 Apr 2005 09:28:35 -0400 Received: from hazy (hazy.research.telcordia.com [207.3.231.19]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id j3RDF6Of020414 for ; Wed, 27 Apr 2005 09:15:06 -0400 (EDT) Date: Wed, 27 Apr 2005 09:15:06 -0400 (EDT) From: Giovanni Di Crescenzo X-X-Sender: giovanni@hazy To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Subject: [manet] WCAN 05 deadline extended to MAY 1ST 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 WCAN 05 call for paper - deadline extended to MAY 1st (apologies if the following is undesired or was already received) CALL FOR PAPERS: 1st Workshop on Cryptography over Ad hoc Networks (WCAN 05) (A Satellite Workshop of Wirelesscom 05, http://sa1.sice.umkc.edu/wc05) Workshop Dates: June 15-16 Workshop Location: Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, http://www.sheraton-maui.com Wireless ad hoc networks are today receiving a lot of attention for militar, commercial and civilian applications, thus raising several challenging security, privacy and anonimity research questions. The security research community has mainly focused on securing routing and is only recently widening its scope of analysis to other security areas. The cryptography research community has mainly focused on standard networks, like the Internet; however, cryptographic protocols for the Internet face serious challenges to be adapted to the ad-hoc, partial-connectivity, mobile, and infrastructureless nature of ad-hoc networks. The aim of this workshop is to help bridging this gap, towards a more comprehensive investigation of security and cryptographic tools, analysis and modeling methodologies over (mobile) ad hoc networks, by bringing together the cryptography, network security, and wireless networking communities. We seek submissions containing original research on all aspects of cryptology in wireless ad hoc networks. Short surveys of sub-areas are also encouraged. Main topics of interest include, but are not limited to the following: Ad Hoc Networks and Resources Modeling Secure Routing Security Bootstrapping Trust Establishment Distributed Public-Key Infrastructures Key Agreement, Management and (Pre)Distribution over Ad Hoc Networks Resource-Constrained Cryptography over Ad Hoc Networks Threshold Cryptography over Ad Hoc Networks Identity-Based Cryptography over Ad Hoc Networks Policy-Based Cryptography over Ad Hoc Networks Secure Multi-Party Protocols over Ad Hoc Networks Security in Distributed Algorithms and Protocols Important Dates: Submission Deadline: April 31, 2005 Notification of Acceptance: May 13, 2005 Camera-Ready Papers: May 20, 2005 Program Chair: Giovanni Di Crescenzo, Telcordia, NJ, USA. giovanni@research.telcordia.com Program Committee: Mike Burmester (Florida State University) David Carman (Johns Hopkins AP Lab), Giovanni Di Crescenzo (Telcordia), Renwei Ge (University of Delaware), Jonathan Katz (University of Maryland), David Naccache (Gemplus), Giuseppe Persiano (University of Salerno), Zulfikar Ramzan (Docomo Labs), Raj Rajagopalan (Hewlett Packard Labs), Ravi Sundaram (Northeastern University), Doug Tygar (UC Berkeley), Serge Vaudenay (Swiss Federal Institute of Technologies). Moti Yung (RSA & Columbia University) General Chair: Farooq Anjum, Telcordia. fanjum@telcordia.com Instructions for Authors: Authors are invited to submit surveys or original papers, possibly about work in progress, that deal with both cryptology and ad hoc networks. All submissions will be refereed and must not substantially duplicate work that any of the authors have published elsewhere or have submitted in parallel. The submissions, preferably in PDF or PS format, must not exceed 6 pages (excluding appendices) nor 12 pages overall. In order to submit a paper, please send your paper as an attachment of an ascii e-mail to acns05chair@research.telcordia.com, indicating title of paper, names and affiliations of authors, and full contact information (affiliation, e-mail and phone number) of the contact author. The camera-ready version should not exceed 6 pages in standard double-column IEEE format. Workshop Proceedings: to be published by IEEE. More details will be provided to the authors. Hotel Information: Posted at http://sa1.sice.umkc.edu/wc05/HotelRes.txt. Early reservation is recommended to benefit from workshop discount. Registration Information: Posted at http://sa1.sice.umkc.edu/wc05/reg.txt for authors, and http://sa1.sice.umkc.edu/wc05/nreg.txt for non-authors. Authors of an accepted paper must guarantee presentation of their paper at the workshop. _______________________________________________ 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 Apr 27 09:57:29 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQn2e-00033Q-Uw; Wed, 27 Apr 2005 09:57:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQn2d-00033L-0e for manet@megatron.ietf.org; Wed, 27 Apr 2005 09:57:27 -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 JAA12635 for ; Wed, 27 Apr 2005 09:57:25 -0400 (EDT) Received: from mail.um.es ([155.54.212.105] helo=xenon2.telemat.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQnFH-0003yV-13 for manet@ietf.org; Wed, 27 Apr 2005 10:10:32 -0400 Received: from localhost (localhost [127.0.0.1]) by xenon2.telemat.um.es (Postfix) with ESMTP id 8CE2B23C2C3 for ; Wed, 27 Apr 2005 15:57:06 +0200 (CEST) Received: from xenon2.telemat.um.es ([127.0.0.1]) by localhost (xenon2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27493-01-26 for ; Wed, 27 Apr 2005 15:57:06 +0200 (CEST) Received: from [155.54.210.26] (dibulibu.um.es [155.54.1.250]) by xenon2.telemat.um.es (Postfix) with ESMTP id 2667323C2A8 for ; Wed, 27 Apr 2005 15:57:06 +0200 (CEST) Message-ID: <426F9A31.6090801@dif.um.es> Date: Wed, 27 Apr 2005 15:57:05 +0200 From: "Pedro M. Ruiz" User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'IETF Manet'" Content-Type: multipart/mixed; boundary="------------000504070006070908090408" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es X-Spam-Score: 0.0 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Subject: [manet] AD HOC NOW 2005: Submission deadline May 1st 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 This is a multi-part message in MIME format. --------------000504070006070908090408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Please find attached the CFP for the AD HOC NOW 2005 conference to be held next october in Cancun. Regards, -- Pedro M. Ruiz Publicity Chair, Ad Hoc Now 2005 --------------000504070006070908090408 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="cfp.txt" Content-Disposition: inline; filename="cfp.txt" Content-Transfer-Encoding: 7bit We apologize if you receive the CFP more than once. ---------------------------------------------------------------------------- CALL FOR PAPERS - AD HOC NOW 2005 4th International Conference on Ad hoc Networks and Wireless Cancun, October 6-8, 2005 http://fismat.umich.mx/adhocnow/ ---------------------------------------------------------------------------- You can find a PDF version of this CFP at: http://fismat.umich.mx/adhocnow/doc/cfp.pdf IMPORTANT DATES --------------- Submission Deadline: May 1st, 2005 Notification of Acceptance: July 10th, 2005 Camera-ready versions due: July 24th, 2005 Panel and demo proposals due: August 1st, 2005 SCOPE ----- Ad hoc networks are self-organising, wireless systems, formed by co-operating nodes equiped with wireless interfaces. Communications among nodes which are not directly reachable, are carried out through multihop paths. Their topology is dynamic, decentralized and ever changing due to the arbritarily movement of ad hoc nodes. We are interested in work in progress, experimental and theoretical research in Ad-hoc, Mobile and Wireless Networks. Topics of interest for which we are soliciting papers include, but are not limited to, the following: *Access control, scheduling *Ad hoc and sensor networks *Analytic methods and modelling for performance evaluation, optimization... *Auto-configuration *Incentives and pricing *Location awareness, discovery, dependence, and management *Mesh networks *New applications *Power management, power control, and energy-efficiency *Quality-of-service, resource allocation, multimedia *Routing (unicast, multicast, etc.) *Security and privacy *Service discovery *Systems and testbeds *Wireless Internet, and data management PROCEEDINGS ----------- The proceedings of Ad hoc Now 2005 will be published by Springer-Verlag, as part of the Lecture Notes in Computer Science (LCNS) series. The best papers with a clear algorithmic content will be selected for publication in a special issue of the Journal of Discrete Algorithms. PAPER SUBMISION INSTRUCTIONS ---------------------------- Authors should prepare a full paper not to exceed 14 pages in Springer Verlag LNCS format. This page budget must contain all figures, tables, and references. The paper should also include a brief abstract of up to 150 words, three keywords, and full contact information for the corresponding author. Submissions not in the appropriate format will be rejected without review. All paper submissions will be handled electronically at the conference website. PANELS AND DEMONSTRATIONS ------------------------- Proposals for panels that examine controversial or otherwise provocative issues are solicited. Panel proposals should not exceed 3 pages, including biographical sketches of the panelists. Potential panel organizers should contact the Panel Chair, S.S. Ravi (mailto:ravi@cs.albany.edu). Proposals for demonstrations are solicited. Proposals should not exceed 3 pages and should include a description of the demo and equipment to be used. Potentialdemonstrators are requested to submit a proposal to the Demo Chair, Antonio Garcia Macias (mailto:jagm@cicese.mx). TECHNICAL COMITTEES ___________________ Program Co-Chairs: Violet R. Syrotiuk, Arizona State Univ., USA Edgar Chavez, Univ. Michoacana, Mexico Steering Comittee: Evangelos Kranakis, Carleton University, Canada Michel Barbeau, Carleton University, Canada S. S. Ravi, SUNY Albany, USA Ioanis Nikolaidis, Univ. of Alberta, Canada Violet R. Syrotiuk, Arizona State Univ., USA Publicity Chair: Pedro M. Ruiz, Univ. of Murcia, Spain Panel Chair: S. S. Ravi, SUNY Albany, USA Demonstration Chair: Antonio Garcia Maccias, CICESE, Mexico Technical Program Comittee: Eitan Altman, INRIA, France Michel Barbeau, Carleton University, Canada Prosenjit Bose, Carleton University, Canada Rida Bazzi, Arizona State Univ., USA Tracy Camp, Colorado School of Mines, USA Edgar Chavez, Univ. Michoacana, Mexico Jorge Cobb, Univ. Texas at Dallas, USA Marco Conti, CNR-IIT, Italy Stefan Dobrev, Univ. of Ottawa, Canada Andras Farago, UT Dallas, USA Laura Feeney, Swedish Institute of Computer Science, Sweeden Antonio Garcia-Macias, CICESE, Mexico Silvia Giordano, Univ. of Applied Science, SUPSI, Switzerland Antonio Gomez-Skarmeta, Univ. of Murcia, Spain Admela Jukan, Georgia Tech, USA Goran Konjevod, Arizona State Univ., USA Evangelos Kranakis, Carleton University, Canada Danny Krizanc, Wesleyan University, USA Sven Krumke, Univ. Kaiseslautern, Germany Jelena Misic, Univ. Manitoba, Canada Pat Morin, Carleton University, Canada Lata Narayanan, Concordia Univ, Canada Ioanis Nikolaidis, U. Alberta, Canada J. Opatrny, Concordia Univ., Canada Ravi Prakash, Univ. Texas at Dallas, USA Sergio Rajsbaum, UNAM, Mexico S. S. Ravi, SUNY Albany, USA Martin Reisslein, Arizona State Univ., USA Frank Rousseau, LSR-IMAG, France Pedro M. Ruiz, Univ. of Murcia, Spain Ladislav Stacho, Simon Fraiser University, Canada Martha Steenstrup, Stow Research LLC, USA Violet R. Syrotiuk, Arizona State Univ., USA Godfried Toussaint, Mc Gill Univ., Canada Damla Turgut, Univ. of Florida, USA Peter Widmayer, ETH, Switzerland Gergely Zaruba, Univ. Texas at Arlington, USA Jerry Zhao, ICSI-Berkeley, USA Rong Zheng, Univ. of Houston, USA FOR ADDITIONAL INFORMATON ------------------------- For questions regarding obtaining visas, accomodation, etc, please contact Edgar Chavez (mailto:elchavez@fismat.umich.mx). Questions regarding paper submissions should be addressed to Violet R. Syrotiuk (mailto:syrotiuk@asu.edu) and Edgar Chavez (mailto:elchavez@fismat.umich.mx). Other comments or questions about the conference should be addressed to S. S. Ravi (ravi@cs.albany.edu) --------------000504070006070908090408 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --------------000504070006070908090408-- From manet-bounces@ietf.org Wed Apr 27 11:55:37 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQosz-0006uu-Bf; Wed, 27 Apr 2005 11:55:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQosx-0006ud-2e for manet@megatron.ietf.org; Wed, 27 Apr 2005 11: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 LAA26289 for ; Wed, 27 Apr 2005 11:55:32 -0400 (EDT) Received: from gate.eu.panasonic.com ([194.173.20.12] helo=hhe500-02.hbg.de.pan.eu) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DQp5a-0007ma-Cv for manet@ietf.org; Wed, 27 Apr 2005 12:08:41 -0400 Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via smtp id 0a43_a97dd5aa_b73e_11d9_8f4a_003048253456; Wed, 27 Apr 2005 19:06:18 +0200 (CEST) Received: from VPN-MRelay-01.PEL.Panasonic.de ([10.100.176.55]) by eundadmi01.pan.eu (Lotus Domino Release 6.5.2) with ESMTP id 2005042717550736-107148 ; Wed, 27 Apr 2005 17:55:07 +0200 Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PEL.Panasonic.de; Wed, 27 Apr 2005 17:56:19 +0200 MIME-Version: 1.0 Subject: RE: [manet] autoconfiguration in manet network X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 27 Apr 2005 17:54:44 +0200 Message-ID: <9D277E44D6EF0942B928C6F0DE99BB31B9702C@lan-ex-01.panasonic.de> Thread-Topic: [manet] autoconfiguration in manet network Thread-Index: AcVKc/pDAp5mdSZpT5amKTGCiXcluwAzEJ2Q To: "amine elabidi" From: "Kilian Weniger" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 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 Hi Amine, Yes, information from the routing protocol can be used for detecting = duplicate addresses. Passive Duplicate Address Detection (PDAD) uses = this approach and Passive Autoconfiguration in Mobile Ad hoc Networks = (PACMAN) is an autoconfiguration protocol for MANETs that uses PDAD. For = details about PDAD and PACMAN see=20 K. Weniger, PACMAN: Passive Autoconfiguration for Mobile Ad hoc = Networks, IEEE Journal on Selected Areas in Communications (JSAC), March = 2005 The paper also discusses the application of PDAD to OLSR, FSR and AODV.=20 A Linux-implementation of PACMAN supporting OLSR and FSR is available = for download at http://pacman-autoconf.sourceforge.net. Regards, Kilian > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]=20 > On Behalf Of amine elabidi > Sent: Dienstag, 26. April 2005 17:23 > To: manet@ietf.org > Subject: [manet] autoconfiguration in manet network >=20 > Hi > I'm interested in auto configuration in manet network using=20 > OLSR as routing algorithm. My question is can I use the=20 > information in the hello message like (list of neighbour ...)=20 > to detect a duplicated address any response will b really=20 > helpful to me. > thinks > =20 >=20 >=20 >=20 > =09 >=20 > =09 > =09 > __________________________________________________________________ > D=E9couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de=20 > stockage pour vos mails !=20 > Cr=E9ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Apr 27 23:12:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQzRt-0001gx-EG; Wed, 27 Apr 2005 23:12:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQzRr-0001gr-G5 for manet@megatron.ietf.org; Wed, 27 Apr 2005 23:12: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 XAA05102 for ; Wed, 27 Apr 2005 23:12:16 -0400 (EDT) From: apple-red2000@sohu.com Received: from [61.135.145.13] (helo=websmtp2.mail.sohu.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQzeb-0003jy-Vs for manet@ietf.org; Wed, 27 Apr 2005 23:25:31 -0400 Received: from mx30.mail.sohu.com (unknown [192.168.41.180]) by websmtp2.mail.sohu.com (Postfix) with ESMTP id 171E62222811 for ; Thu, 28 Apr 2005 11:11:37 +0800 (CST) Message-ID: <11044709.1114657903376.JavaMail.postfix@mx30.mail.sohu.com> Date: Thu, 28 Apr 2005 11:11:43 +0800 (CST) To: Mime-Version: 1.0 X-Mailer: Sohu Web Mail 2.0.13 X-SHIP: 202.115.65.227 X-Priority: 3 X-SHMOBILE: 0 X-Sohu-Antivirus: 0 X-Spam-Score: 2.5 (++) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Subject: [manet] Preamble length of IEEE 802.11a OFDM PHY 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="===============2044079777==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org --===============2044079777== Content-Type: multipart/related; boundary="----=_Part_774_23494460.1114657903369" ------=_Part_774_23494460.1114657903369 Content-Type: multipart/alternative; boundary="----=_Part_773_25919386.1114657903369" ------=_Part_773_25919386.1114657903369 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Hi, all! In IEEE Std 802.11a-1999 Table 93?OFDM PHY characteristics, I find that aPreambleLength is 20 µs. But now I need to know the preamble length of IEEE 802.11a OFDM PHY measured in bit. In Figure 122?PLCP transmit procedure, PLCP Preamble is 12 symbols. How to understand the meaning of one symbol? Any information will be appreciated! Thanks in advance! ------=_Part_773_25919386.1114657903369 Content-Type: text/html Content-Transfer-Encoding: 8bit 
Hi, all!

In IEEE Std 802.11a-1999 Table 93?OFDM PHY characteristics, I find that aPreambleLength is 20 µs. But now I need to know the preamble length of IEEE 802.11a OFDM PHY measured in bit. In Figure 122?PLCP transmit procedure, PLCP Preamble is 12 symbols. How to understand the meaning of one symbol?

Any information will be appreciated!
Thanks in advance!
------=_Part_773_25919386.1114657903369-- ------=_Part_774_23494460.1114657903369-- --===============2044079777== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2044079777==-- From manet-bounces@ietf.org Thu Apr 28 10:20:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9sI-0007Zb-1C; Thu, 28 Apr 2005 10:20:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9sC-0007Xv-5A for manet@megatron.ietf.org; Thu, 28 Apr 2005 10:20: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 KAA19778 for ; Thu, 28 Apr 2005 10:20:10 -0400 (EDT) Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRA4z-0004TQ-OU for manet@ietf.org; Thu, 28 Apr 2005 10:33:30 -0400 X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from c01.al.cl.cam.ac.uk ([128.232.110.47]:36455 helo=mobileman-2) by ppsw-0.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.150]:25) with esmtpsa (PLAIN:ap458) (TLSv1:RC4-MD5:128) id 1DR9s1-0004qw-2m (Exim 4.51) (return-path ); Thu, 28 Apr 2005 15:20:02 +0100 From: Andrea Passarella To: manet Date: Thu, 28 Apr 2005 15:20:04 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200504281520.04970.andrea.passarella@cl.cam.ac.uk> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb Content-Transfer-Encoding: 7bit Subject: [manet] IEEE ICPS REALMAN Workshop: deadline extended to 9 May 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 [Apologies for possible duplicates of this message] --------------------------------------------------------------- CALL FOR PAPERS IEEE ICPS Workshop on Multi-hop Ad hoc Networks: from theory to reality REALMAN 2005 http://www.cl.cam.ac.uk/realman jointly organized by: MobileMAN EC FET-IST Project University of Cambridge, UK CNR-Institute for Informatics and Telematics, I in conjunction with ICPS 2005 http://icps2005.cs.ucr.edu/ July 14, 2005 Santorini, Greece ------------------------------------------------------------------------ Submission Deadline: ***Extended*** May 9th, 2005. ------------------------------------------------------------------------ After almost a decade of research into ad hoc networking, off-the-shelf MANET technology has not yet affected our way of using wireless networks. To consolidate the field, it is now the time to constructing and experiencing with realistic and complete MANET solutions. Prototypes and measurements on real test-beds provide insights in the ad hoc technology behavior and fundamental information for a realistic tuning of simulation models (mobility models, link-level models, etc.). This workshop constitutes a unique forum for presenting and discussing experiences based on real ad hoc networks test-beds and prototypes. Original contributions are solicited, related to systems and protocols development and testing, in all areas related to ad hoc networking. Topics of interest include, but are not limited to: * Ad hoc networks applications * System prototypes and experiences * Software technologies and systems * Mobile Ad Hoc Networks * Sensor Networks * Vehicular Networks * Mesh Networks * Routing and Transport protocols * Security and cooperation protocols * Middleware platforms for ad hoc networks * Ad Hoc Networking for ambient intelligence and pervasive environments * Situated and Autonomic Communications * Location services * Positioning and Tracking Technologies * Measurement studies * Mobility Models * Enabling Technologies Models (802.11, 802.15, etc.) * Experiment-based Social and/or Economic Analysis of Mobile Ad hoc Networks DEMO SESSION A demo session will be held during the workshop, showing ad hoc and sensor network prototypes at work. Demo proposals are highly welcome, and will be evaluated ty the Program Committee. Please submit one-page demo proposal to the program chair (realman@iit.cnr.it) before May 1, 2005. The proposal should briefly summarize the research framework of the proposed demo. Please also state clearly what equipments will be required to set up the experiments. As a general rule, demo proposers will be in charge for all the equipment material required for the experiments. Please contact the program chair for particular needs in this regard. PAPER SUBMISSION AND PUBLICATION Please submit your short paper via e-mail (PDF format is mandatory) to the program chair (realman@iit.cnr.it). We encourage the authors to format their papers according to the IEEE double-column standard format, except the font size, which must be Times Roman 11pt (or greater). Paper length must not exceed 8 pages, including figures, appendixes, bibliography, etc. Format templates and detailed instructions can be found at http://www.cl.cam.ac.uk/realman/authors.html ****************************************************************** High quality papers will be selected for possible publication on "Ad Hoc & Sensor Wireless Networks Journal (AHSWN)" http://www.oldcitypublishing.com/AHSWN/AHSWN.html ****************************************************************** IMPORTANT DATES Paper/Demo Submission due: May 9, 2005 Notification: June 1, 2005 Camera Ready due: June 14, 2005 ORGANIZING COMMITTEE General Chair Jon Crowcroft University of Cambridge, UK jon.crowcroft@cl.cam.ac.uk Program Chair Marco Conti IIT-CNR, Italy marco.conti@iit.cnr.it Program Vice-Chair Andrea Passarella University of Cambridge, UK andrea.passarella@cl.cam.ac.uk Program Committee G. Anastasi, Pisa University, Italy A.T. Campbell, Columbia University, USA S.R. Das, SUNY at Stony Brook, USA A. Ephremides, University of Maryland, USA S. Giordano, SUPSI, CH E. Gregori, IIT-CNR, Italy T. Henderson, Dartmouth College, USA R. Kantola, Helsinki University of Technology, Finland H. Karl, Paderborn University, Germany E. Knightly, Rice University, USA M. Mauve, Dusseldorf University, Germany P. Michiardi, EURECOM, France R. Molva, EURECOM, France S. Olariu, Old Dominion University, USA G. Polyzos, Athens University of Economics and Business, Greece D. Remondo, Catalonia University of Technology, Spain C. Rohner, Uppsala University, Sweden J.H. Schiller, Freie University Berlin, Germany J. Scott, Intel Research, UK F. Sestini, European Commission V.A. Siris, FORTH-ICS and Crete University, Greece I. Stavrakakis, Athens University, Greece I. Stojmenovic, Ottawa University, Canada C. Tschudin, Basel University, Switzerland N. Vaidya, Illinois University at Urbana-Champaign, USA J. Wu, Florida Atlantic University, USA -- Andrea Passarella IEEE ICPS REALMAN Program Vice-Chair ========================================================= University of Cambridge The Computer Laboratory || voice:+44 (0)1223 763658 15 JJ Thomson Avenue || fax: +44 (0)1223 334678 Cambridge CB3 0FD, UK || web: www.cl.cam.ac.uk/~ap458/ email: andrea.passarella@cl.cam.ac.uk ========================================================= Pervasive Computing & Networking Lab. (PerLab) University of Pisa, Dept. of Information Engineering _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 28 11:39:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRB6a-0007q9-EX; Thu, 28 Apr 2005 11:39:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRB6X-0007no-Kd for manet@megatron.ietf.org; Thu, 28 Apr 2005 11:39: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 LAA27112 for ; Thu, 28 Apr 2005 11:39:03 -0400 (EDT) From: pvillanu@site.uottawa.ca Received: from mailn.site.uottawa.ca ([137.122.89.142] helo=mail.site.uottawa.ca ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRBJP-000835-Ka for manet@ietf.org; Thu, 28 Apr 2005 11:52:25 -0400 Received: from www.site.uottawa.ca (web0.site.uottawa.ca [137.122.89.222]) by mail.site.uottawa.ca (8.9.3/8.9.3) with ESMTP id LAA24626 for ; Thu, 28 Apr 2005 11:38:56 -0400 (EDT) Received: from 127.0.0.1 (SquirrelMail authenticated user pvillanu); by www.site.uottawa.ca with HTTP; Thu, 28 Apr 2005 11:38:56 -0400 (EDT) Message-ID: <1758.127.0.0.1.1114702736.squirrel@127.0.0.1> Date: Thu, 28 Apr 2005 11:38:56 -0400 (EDT) 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-Spam-Score: 0.3 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 8bit Subject: [manet] OOLSR on NS-2 v. 2.28... how to install? 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 Hello, I wonder if anyone has installed the new OLSR implementation of OLSR done by INRIA (OOLSR http://hipercom.inria.fr/OOLSR/), on NS-2 ver. 2.28... The all-in-one downloandable version is for NS-2 ver. 2.27 which does not work with Fedora Core 3 (gcc ver 3.4 problem)... Thanks Pedro Villanueva _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Apr 28 18:38:06 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRHe1-0005em-Up; Thu, 28 Apr 2005 18:38:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRHdz-0005dp-7s for manet@megatron.ietf.org; Thu, 28 Apr 2005 18:38: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 SAA02972 for ; Thu, 28 Apr 2005 18:38:00 -0400 (EDT) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRHqv-0000O3-Sk for manet@ietf.org; Thu, 28 Apr 2005 18:51:26 -0400 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id j3SMc1nI002955 for ; Thu, 28 Apr 2005 18:38:01 -0400 (EDT) Received: from ECE.NEU.EDU ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2005042818380006769 for ; Thu, 28 Apr 2005 18:38:00 -0400 Received: from localhost (basagni@localhost) by ECE.NEU.EDU (8.12.8/8.12.5/Submit) with ESMTP id j3SMc1Oi007043 for ; Thu, 28 Apr 2005 18:38:01 -0400 Date: Thu, 28 Apr 2005 18:38:01 -0400 (EDT) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Subject: [manet] IEEE SECON 2005, Call for Demos 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 We apologize if you receive multiple copies of this call ************************************************************* CALL FOR DEMOS The Second IEEE International Conference on Sensor and Ad Hoc Communications and Networks : SECON 2005 http://ingr.cse.ucsc.edu/secon05/ September 26-29, 2005 Santa Clara, California, USA Technical demonstrations showing original research, practical implementations, industrial and commercial developments, and new applications for ad hoc and sensor networks are solicited. Specific topics of interest include, but are not limited to: * New architectures, protocols and access control to support communication, localization, time synchronization, routing and data dissemination in heterogeneous, large-scale distributed, ad hoc networks and sensor networks * Novel algorithms and theories for management, supervisory control and monitoring of distributed ad hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes * Modeling and performance evaluation of large-scale distributed and ad hoc sensor networks, practical implementations, and real-work experiences * Theories and models on fundamental information and communication aspects of wireless ad hoc and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and ad hoc networks * Integration of sensors into engineered systems, including novel techniques for sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing and efficient schemes to maximize accuracy and minimize false alarms * Chip-based systems incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware and tools for ad hoc and sensor network applications development, deployment and management Please consult the demo co-chairs at if you are uncertain whether your demo falls within the scope of the conference. DEMO SUBMISSION INSTRUCTIONS Please send a one-page description of your demo to in plain text or PDF format by the dates listed below. (Plain text is preferred unless there are graphics.) Demos are independent of the technical paper review and acceptance process. IMPORTANT DATES One-page demo descriptions: June 15, 2005 Notification of acceptance: July 1, 2005 Conference dates: September 26-29, 2005 SECON 2005 DEMO CHAIRS: Bhaskar Krisnamachari, Fabio Silva (USC/ISI) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Apr 29 07:10:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRTOM-0001Wd-E2; Fri, 29 Apr 2005 07:10:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRTOK-0001WV-NF; Fri, 29 Apr 2005 07:10: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 HAA13046; Fri, 29 Apr 2005 07:10:37 -0400 (EDT) Received: from mail.um.es ([155.54.212.105] helo=xenon2.telemat.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRTbN-0005nj-Qp; Fri, 29 Apr 2005 07:24:10 -0400 Received: from localhost (localhost [127.0.0.1]) by xenon2.telemat.um.es (Postfix) with ESMTP id 342CA23C387; Fri, 29 Apr 2005 13:10:25 +0200 (CEST) Received: from xenon2.telemat.um.es ([127.0.0.1]) by localhost (xenon2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25559-01-10; Fri, 29 Apr 2005 13:10:24 +0200 (CEST) Received: from [155.54.210.26] (dibulibu.um.es [155.54.1.250]) by xenon2.telemat.um.es (Postfix) with ESMTP id DC87523C15D; Fri, 29 Apr 2005 13:10:19 +0200 (CEST) Message-ID: <42721619.4010209@dif.um.es> Date: Fri, 29 Apr 2005 13:10:17 +0200 From: "Pedro M. Ruiz" User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'IETF Manet'" Content-Type: multipart/mixed; boundary="------------060609000909020303080502" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es X-Spam-Score: 0.0 (/) X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1 Subject: [manet] AD HOC NOW 2005: Deadline extended to May 8th 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 This is a multi-part message in MIME format. --------------060609000909020303080502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit --------------060609000909020303080502 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="cfp-ext.txt" Content-Disposition: inline; filename="cfp-ext.txt" Content-Transfer-Encoding: 7bit We apologize if you receive the CFP more than once. Due to a large number of requests, we are extending the deadline for submissions. We are also requesting authors to register the paper abstract earlier, to help the program committee to speed up the reviewing process. Extended deadline: Full paper May 8th. (Abstract registration May 2nd) ---------------------------------------------------------------------------- CALL FOR PAPERS - AD HOC NOW 2005 4th International Conference on Ad hoc Networks and Wireless Cancun, October 6-8, 2005 http://fismat.umich.mx/adhocnow/ ---------------------------------------------------------------------------- You can find a PDF version of this CFP at: http://fismat.umich.mx/adhocnow/doc/cfp.pdf IMPORTANT DATES --------------- Abstract registration: May 2nd, 2005 Extended Deadline: May 8th, 2005 Notification of Acceptance: July 10th, 2005 Camera-ready versions due: July 24th, 2005 Panel and demo proposals due: August 1st, 2005 SCOPE ----- Ad hoc networks are self-organising, wireless systems, formed by co-operating nodes equiped with wireless interfaces. Communications among nodes which are not directly reachable, are carried out through multihop paths. Their topology is dynamic, decentralized and ever changing due to the arbritarily movement of ad hoc nodes. We are interested in work in progress, experimental and theoretical research in Ad-hoc, Mobile and Wireless Networks. Topics of interest for which we are soliciting papers include, but are not limited to, the following: *Access control, scheduling *Ad hoc and sensor networks *Analytic methods and modelling for performance evaluation, optimization... *Auto-configuration *Incentives and pricing *Location awareness, discovery, dependence, and management *Mesh networks *New applications *Power management, power control, and energy-efficiency *Quality-of-service, resource allocation, multimedia *Routing (unicast, multicast, etc.) *Security and privacy *Service discovery *Systems and testbeds *Wireless Internet, and data management PROCEEDINGS ----------- The proceedings of Ad hoc Now 2005 will be published by Springer-Verlag, as part of the Lecture Notes in Computer Science (LCNS) series. The best papers with a clear algorithmic content will be selected for publication in a special issue of the Journal of Discrete Algorithms. PAPER SUBMISION INSTRUCTIONS ---------------------------- Authors should prepare a full paper not to exceed 14 pages in Springer Verlag LNCS format. This page budget must contain all figures, tables, and references. The paper should also include a brief abstract of up to 150 words, three keywords, and full contact information for the corresponding author. Submissions not in the appropriate format will be rejected without review. All paper submissions will be handled electronically at the conference website. PANELS AND DEMONSTRATIONS ------------------------- Proposals for panels that examine controversial or otherwise provocative issues are solicited. Panel proposals should not exceed 3 pages, including biographical sketches of the panelists. Potential panel organizers should contact the Panel Chair, S.S. Ravi (mailto:ravi@cs.albany.edu). Proposals for demonstrations are solicited. Proposals should not exceed 3 pages and should include a description of the demo and equipment to be used. Potentialdemonstrators are requested to submit a proposal to the Demo Chair, Antonio Garcia Macias (mailto:jagm@cicese.mx). TECHNICAL COMITTEES ___________________ Program Co-Chairs: Violet R. Syrotiuk, Arizona State Univ., USA Edgar Chavez, Univ. Michoacana, Mexico Steering Comittee: Evangelos Kranakis, Carleton University, Canada Michel Barbeau, Carleton University, Canada S. S. Ravi, SUNY Albany, USA Ioanis Nikolaidis, Univ. of Alberta, Canada Violet R. Syrotiuk, Arizona State Univ., USA Publicity Chair: Pedro M. Ruiz, Univ. of Murcia, Spain Panel Chair: S. S. Ravi, SUNY Albany, USA Demonstration Chair: Antonio Garcia Maccias, CICESE, Mexico Technical Program Comittee: Eitan Altman, INRIA, France Michel Barbeau, Carleton University, Canada Prosenjit Bose, Carleton University, Canada Rida Bazzi, Arizona State Univ., USA Tracy Camp, Colorado School of Mines, USA Edgar Chavez, Univ. Michoacana, Mexico Jorge Cobb, Univ. Texas at Dallas, USA Marco Conti, CNR-IIT, Italy Stefan Dobrev, Univ. of Ottawa, Canada Andras Farago, UT Dallas, USA Laura Feeney, Swedish Institute of Computer Science, Sweeden Antonio Garcia-Macias, CICESE, Mexico Silvia Giordano, Univ. of Applied Science, SUPSI, Switzerland Antonio Gomez-Skarmeta, Univ. of Murcia, Spain Admela Jukan, Georgia Tech, USA Goran Konjevod, Arizona State Univ., USA Evangelos Kranakis, Carleton University, Canada Danny Krizanc, Wesleyan University, USA Sven Krumke, Univ. Kaiseslautern, Germany Jelena Misic, Univ. Manitoba, Canada Pat Morin, Carleton University, Canada Lata Narayanan, Concordia Univ, Canada Ioanis Nikolaidis, U. Alberta, Canada J. Opatrny, Concordia Univ., Canada Ravi Prakash, Univ. Texas at Dallas, USA Sergio Rajsbaum, UNAM, Mexico S. S. Ravi, SUNY Albany, USA Martin Reisslein, Arizona State Univ., USA Frank Rousseau, LSR-IMAG, France Pedro M. Ruiz, Univ. of Murcia, Spain Ladislav Stacho, Simon Fraiser University, Canada Martha Steenstrup, Stow Research LLC, USA Violet R. Syrotiuk, Arizona State Univ., USA Godfried Toussaint, Mc Gill Univ., Canada Damla Turgut, Univ. of Florida, USA Peter Widmayer, ETH, Switzerland Gergely Zaruba, Univ. Texas at Arlington, USA Jerry Zhao, ICSI-Berkeley, USA Rong Zheng, Univ. of Houston, USA FOR ADDITIONAL INFORMATON ------------------------- For questions regarding obtaining visas, accomodation, etc, please contact Edgar Chavez (mailto:elchavez@fismat.umich.mx). Questions regarding paper submissions should be addressed to Violet R. Syrotiuk (mailto:syrotiuk@asu.edu) and Edgar Chavez (mailto:elchavez@fismat.umich.mx). Other comments or questions about the conference should be addressed to S. S. Ravi (ravi@cs.albany.edu) --------------060609000909020303080502 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --------------060609000909020303080502-- From manet-bounces@ietf.org Sat Apr 30 13:39:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRvwF-0008Sg-2l; Sat, 30 Apr 2005 13:39:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRvwC-0008Sb-Tc for manet@megatron.ietf.org; Sat, 30 Apr 2005 13:39: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 NAA19605 for ; Sat, 30 Apr 2005 13:39:29 -0400 (EDT) Received: from amber.ccs.neu.edu ([129.10.116.51]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRw9W-0001Jg-EB for manet@ietf.org; Sat, 30 Apr 2005 13:53:18 -0400 Received: from denali.ccs.neu.edu ([129.10.116.200]) by amber.ccs.neu.edu with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.50) id 1DRvwA-00039E-22; Sat, 30 Apr 2005 13:39:31 -0400 Date: Sat, 30 Apr 2005 13:39:29 -0400 (EDT) From: Guevara Noubir To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.1 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Subject: [manet] CFP: Vehicle-to-Vehicle Communications 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 We apologize if you receive multiple copies of this CFP. ****************************************************** V2VCOM 2005 VEHICLE-TO-VEHICLE COMMUNICATIONS WORKSHOP San Diego, CA, July 21, 2005 in conjunction with MobiQuitous 2005 http://www.v2vcom.org or from http://www.mobiquitous.org/ ****************************************************** OVERVIEW: High-tech sensors, radars, cameras, navigation systems, and tens of microprocessors are some of the technologies that are already being used in vehicles to enable systems such as parking assist units, lane keeping assistance, adaptive cruise-control systems, and more. These technologies have all brought more safety, comfort and convenience to drivers and passengers. Coupled with the advances in wireless communications technology, recently, governments, highway authorities and automobile manufacturers push the move from "passive safety" to "active safety" by employing communications functions in vehicles. Once the communications and networking capabilities are integrated into vehicles, not only safety applications, but also many other applications ranging from intelligent/interactive transportation systems that could help smooth the flow of traffic, to vehicular diagnostics, mobile commerce, and business services could become a reality. TOPICS This one-day workshop intends to bring together researchers, professionals, and practitioners to discuss and address recent developments and challenges in deploying vehicle-to-vehicle and infrastructure-to-vehicle networking technologies, as well as their subsequent applications with a focus on safety assistance applications. Specifically, we solicit original research contributions addressing the following areas: - Vehicular mobile ad-hoc networks - Potential applications of vehicular networks - Vehicle-to-infrastructure communications - Role of V2V communications in Intelligent Transportation Systems - Routing protocols for V2V communications - High-speed mobility management for V2V communications - MAC layer issues in V2V communications - Physical layer and RF level issues in V2V communications - Antenna technologies for V2V communications - Security and authentication issues in V2V communication - Cross-layer designs - Radio resource management and QoS support - Mobility models and mobility management - Experimental systems and testbeds - Algorithms, protocols and systems for data dissemination SUBMISSION GUIDELINES Authors are invited to submit full papers of up to 20 double-spaced pages, including references, figures and tables. All submissions should be submitted electronically in Postscript or Adobe PDF format to both of the workshop co-chairs: Onur Altintas onur@jp.toyota-itc.com and Wai Chen wchen@research.telcordia.com IMPORTANT DATES: Full Papers due: May 15, 2005 Notification of Acceptance: June 6, 2005 Camera-ready Manuscripts due: June 20, 2005 Workshop Date: July 21, 2005 ORGANIZING COMMITTEE: V2VCOM Workshop Co-chairs: Dr. Onur Altintas (Toyota InfoTechnology Center, Japan) Dr. Wai Chen (Telcordia Technologies, USA) V2VCOM Workshop Program Advisor: Prof. Tadao Saito (Professor Emeritus, Univ. of Tokyo, Japan) PROGRAM COMMITTEE: Dr. Stephane Amarger (Hitachi Europe, France) Richard Bishop (Bishop Consulting, USA) Dr. Jasmine Chennikara-Varghese (Telcordia Technologies, USA) Prof. Eylem Ekici (Ohio State University, USA) Prof. Mario Gerla (UCLA, USA) Dr. Kenneth Laberteaux (Toyota Technical Center, USA) Prof. Ken?ichi Mase (Niigata University, Japan) Dr. Carsten Metz (Bell Labs, Lucent, USA) Prof. Guevara Noubir (Northeastern University, USA) Dr. Sadao Obana (ATR, Japan) Prof. Umit Ozguner (Ohio State University, USA) Prof. Dipankar Raychaudhuri (WINLAB, Rutgers University, USA) Prof. Behcet Sarikaya (University of Northern British Columbia, Canada) Matthias Schulze (DaimlerChrysler AG, Germany) Prof. Sirin Tekinay (New Jersey Institute of Technology, USA) Prof. Ryuji Wakikawa (Keio University, Japan) Prof. Halim Yanikomeroglu (Carleton University, Canada) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet